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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

106 CHAPTER 13. DATA CALIBRATION<br />

automatically whenever a flat-field correction is required. Chapter 20 gives a more detailed<br />

description the various calibration methods and their impact on the PDS.<br />

It is possible to correct data for dark current and glitches only, save the result in an IDL<br />

file, and then try different methods for transient and flat-field corrections (reloading the dark<br />

and glitch corrected data before each new try). So the user must take care of what corrections<br />

have been performed on a data set – including the order in which they have been performed –<br />

before trying any other correction. It is possible to perform the same correction more then once<br />

on a data set, though novice users are strongly discouraged from doing so. It is recommended<br />

that you carefully read Chapter 20 if you really want to try this. The DATA STATUS window<br />

displays some useful information about the number of times that each calibration was performed<br />

on the data set. If the data set is loaded from an IDL restore command, then all indices start<br />

at 900 instead of zero in order to indicate that the data status is unknown.<br />

A data history has been designed in order to help the user to keep a track of all processes<br />

which have been applied to the data set. This history can be displayed on the screen at any time<br />

(using Data / Display History). The file data history.txt is then created in the current directory.<br />

A log file of the whole x cia session can also be displayed on the screen (using CIA / Log<br />

File). This log file contains all commands, warning and error messages of the current x cia<br />

session. The default name of the log file is cia log.txt. This file is automatically overwritten at<br />

the beginning of a x cia session unless the /noinit keyword is used. The user can also choose<br />

another name by typing:<br />

CIA> x_cia, logfile=’my_name.txt’<br />

13.3.3.4 Example 2: testing several methods for flat-field correction<br />

Let’s assume that the user wants to correct data from dark current, glitches and transient effects,<br />

and then try several methods for the flat-field correction. Assuming that a user input frame (an<br />

IDL 32×32 array called my flat in the following) is used as flat-field, it is necessary to load it<br />

using the INFLAT keyword.<br />

Hence, the sequence of commands would be the following:<br />

1. Start a CIA session.<br />

2. Start x cia with the following:<br />

CIA> x_cia, inflat=my_flat<br />

3. Choose AOT Type (default is raster scan).<br />

4. Data / Load / SSCD<br />

5. Data / AOT Info<br />

6. Process / None<br />

7. Dark / User Input<br />

8. Deglitch / Spatial<br />

9. Transient / SAP Model Fitting<br />

10. Process / Selected

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

Saved successfully!

Ooh no, something went wrong!