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.

274 CHAPTER 21. USING SLICE WITHIN CIA<br />

A detailed description of the algorithms in SLICE can be found in M. A. Miville-Deschênes’<br />

paper (2000, A&A 146, 519), while the package has it own user’s manual available at in the doc<br />

directory of the SLICE delivery.<br />

An important note for SLICE V1.2: Although optical distortion has been computed<br />

for all <strong><strong>ISO</strong>CAM</strong> configurations and can be corrected in CIA, SLICE V1.2 incorporates an older<br />

correction scheme. As a result only the most widely used optical configurations can be corrected<br />

for distortion in SLICE. This limitation is known to M. A. Miville-Deschênes and should be<br />

uplifted in subsequent releases of SLICE.<br />

21.3 Organization of data in SLICE<br />

In CIA, data are either stored in hidden structures (the SCD, SSCD, SAD, SSAD) that you<br />

access through pointers, or in standard IDL structures (the so-called PDS) that you manipulate<br />

directly.<br />

In SLICE this is different: data are stored in IDL variables (i.e. you can manipulate them<br />

directly) but these also belong to common blocks that are accessed by SLICE routines. As a<br />

result, their names are defined once and for all, and you cannot use them for other purposes.<br />

This is why SLICE is not loaded by default when you start CIA.<br />

Although you can do it in SLICE, we assume here that dark correction, de-glitching and<br />

transient correction are performed in CIA. You will generally start the SLICE processing after<br />

these three steps, i.e. where, in a more standard reduction session, you would have made the<br />

flat-field correction.<br />

To start SLICE, the first step is to initialize its common blocks as well as place its directories<br />

in your IDL path. This is simply done with:<br />

CIA> @cia slice init<br />

This creates variables that will be used to store your data, any variable with the same<br />

name is therefore erased. Their names and content are listed in Table 21.1.<br />

You need now to transfer your data into these variables. This is done with the CIA routine<br />

raster2slice, therefore type:<br />

CIA> raster2slice,data<br />

The next section will describe the processing that you can do in SLICE. For completeness<br />

reasons, let us see here also how to transfer data back from SLICE into a CIA structure. This<br />

is also very simple as you just have to type:<br />

CIA> new raster = slice2raster()<br />

This function requires no argument as all the required data are already in the SLICE<br />

commons. You will see that the content of the output raster structure is different from that<br />

of the input one. In particular, the raster field that contains the final map is generally larger.<br />

This is due to the SLICE convention of only building maps with North up and East left (the<br />

astronomical convention). This in general results in larger raster maps. Note however that<br />

this new raster structure is fully compatible with CIA. In particular it can be examined with<br />

isocont.

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

Saved successfully!

Ooh no, something went wrong!