Gasgano Frequently Asked Questions
- What documentation is available for Gasgano?
Answer: There is a user manual that can be downloaded from http://www.eso.org/sci/software/gasgano.html.
- What do I do if I get the messaged "CPL initialisation failed" in gasgano?
Answer: If you get an error message like:
Lost output message: 10:52:04 [WARNING] CPL-messaging
Lost error message: 10:52:04 [ ERROR ] Dumping all 1 error(s):
Lost error message: 10:52:04 [ ERROR ] [1/1] 'File cannot be created'
(8) at cpl_msg_set_log_level:cpl_msg.c:874
Likely you do not have write access for the current directory. Change directory permissions or change the directory itself to somewhere where you can create files.
- I successfully ran the installation script to install the pipeline, but when I try to run gasgano I get the following error:
Exception in thread "main" java.lang.UnsatisfiedLinkError: no cplgasgano in java .library.path
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0 (Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
Answer: For Gasgano in particular the variable CPLDIR, which must point to an installation of the CPL library, has to be set as shown in the following example taken from a run of the installer script. In this example the root directory of the installation is " /home/dummy/tmp".
In order to use the recipes from gasgano you need to set the environment variable CPLDIR to /home/dummy/tmp
Depending on your type of shell a possible command for doing this may be: export CPLDIR=/home/dummy/tmp
If the CPL has been (manually) installed in a different location the variable must be set to the directory which contains the "include" and "lib" or "lib64" subdirectories.
Note that the output of the installer script shown before is also available from the "install.log" log file which is created in the directory where the installer script was executed (usually the directory containing the unpacked pipeline kit).
After executing this command, gasgano should start up normally.
- Gasgano hangs when adding new files, what do I do?
Answer: You may have *fits.gz files in the tree. Either move them somewhere else, or gunzip them.
- What do I do if recipe fails because frames are not classified?
Answer: Occasionally you may see an "UNDEF" in the "Classication" column of gasgano recipe window. This either means that there is a problem with the FITS headers (DPR.CATG, DPR.TECH and/or DPR.TYPE), or that the rules set used to classify the frames is not loaded and/or is faulty. You can still force gasgano to do a reduction by entering the classication by hand, for example click on "UNDEF" and change to "CALPRO FLAT" if you are sure that image is a master flatfield.
An alternative solution could be to change the header of the files that gasgano fails to classify, so that they can be classified (for expert users only).
- The pipeline cannot find recipe files, what is the problem?
Answer: Sometimes you may have several versions of a pipeline on your computer. To select a particular set of recipes just add the following to your esorex command, e.g.: esorex --recipe-dir=/path/crire-kit-2.3.0/crire-2.3.0/recipes/.libs
To check which recipes gasgano is looking at go to File ! Preferences ! Recipe Configuration from the gasgano main panel.