23.04.2015 Views

ISOCAM Interactive Analysis User's Manual Version 5.0 - ISO - ESA

ISOCAM Interactive Analysis User's Manual Version 5.0 - ISO - ESA

ISOCAM Interactive Analysis User's Manual Version 5.0 - ISO - ESA

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

14 CHAPTER 2. ABOUT CIA<br />

This will probably be a link. You can use the ls -l commandtoseewhatitispointingto<br />

if you wish, though it is not particularly important. Inspect this file to see what cia vers is<br />

defined as. Alternatively, this information will probably be printed when CIA is started. Now<br />

you can copy the file $cia vers/unix/user init.pro. In order for CIA to find it you should<br />

put it in your $HOME/bin directory.<br />

To change the default version you can either copy and modify the cia file or alias cia to<br />

include the version, though remember you can also specify it on the command line.<br />

By default, no log files are written. You can turn on the logging by reinstating the<br />

commented-out line set logfile in user init.pro. Then they are written to the directory<br />

specified by the environment variable logfile dir which in turn is set to the environment variable<br />

cia logfile dir. These variables are set in, respectively, cia and setup/cshrc.camia<br />

if it exists. If it does exist and sets cia logfile dir, you will need your own version of cia to<br />

change the logfile directory, otherwise you can simply define cia logfile dir yourself.<br />

2.4 CIA caveats<br />

Some points to note about IDL and CIA:<br />

• Do to a bug concerning nesting structure in IDL 5.5 CIA will not run under IDL 5.5<br />

• You have to include the “obsolete” directory in the IDL PATH in order to run pickfile<br />

and CIA routines using this program.<br />

• CIA should only be run in a directory where the user has write permission.<br />

• Run only one CIA session per directory. Some CIA routines create temporary files in the<br />

current directory. Running more than one CIA session in the same directory can cause a<br />

file I/O conflict.<br />

• xv raster might crash for some North-oriented rasters. It is recommended that you use<br />

ximage instead.<br />

• ximage will crash if you use it together with ciainfo or widget olh.<br />

• Using mosaics, fit isopsf and photom psf will crash for point-sources close to the edge<br />

of the mosaic<br />

• corr flat will fail to flat correct a PDS that contains data with an optical configuration<br />

that is not constant.<br />

• There has been reports from users that MIDAS has problems reading CIA generated FITS<br />

files. It appears that MIDAS does not implement the full FITS standard, and therefore<br />

can not read CIA astrometry.<br />

• There is a known problem with the CIA routine sscd del. Deleting an SSCD may corrupt<br />

those SSCDs which have been derived or extracted from the original. For example:<br />

CIA> spdtoscd, ’cisp02600506.fits’, sscd, dir=’$cia_vers/test’, /nowrite<br />

CIA> cleaned_sscd=sscd_clean(sscd)<br />

CIA> sscd_del, sscd

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!