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.

21.5. A WORKED EXAMPLE 283<br />

Table 21.4: Our choice of parameters for the DivSky method.<br />

Filter tdt size filter flat thresh nplanes<br />

LW3 65801627 15 10 60<br />

LW2 65801627 15 10 30<br />

• size filter: this is an integer whose meaning is rather similar to the flat smooth window<br />

of the previous method. Here also the data are filtered and removed from the readouts<br />

before computing the flat-field. However, it is the sky image (in map) that is smoothed and<br />

then divided out. Note that contrary to flat smooth window, the size of the smoothing<br />

box is really size filter. It is rather hard to determine aprioriwhat should be the value<br />

of this parameter. One way to proceed is to try different values and judge from the results,<br />

from a size slightly larger than the PSF to one larger than the raster step. Remember to<br />

inspect not only the resulting map, but also the flat-field: it is generally in the flat-field<br />

that you can judge the success of your parameter choice. If features reminiscent of your<br />

source appear in the flat-field cube, then size filter is wrong (see section 21.4.1 to see<br />

how to recover the flat-field cube).<br />

Table 21.4 summarizes our choice of parameters for the DivSky method while figure 21.3<br />

shows the results for the two filter. For this particular method, and in the LW3 case, the<br />

command lines are:<br />

CIA> red param=set red param(tdt=’65801627’,flat thresh=10,nplanes=60,$<br />

CIA> size filter=15,/divsky)<br />

CIA> act=set act(/make map)<br />

CIA> slice pipe<br />

An obvious improvement is seen here: the gradient of “emission”, which is in fact the longterm<br />

transient, is much smoother now, and pointing imprints have disappeared. In your data<br />

reduction session, we suggest that you play around with both flat-field methods, before you<br />

select the one to use in the first pass. It is also important that you check that your choice of<br />

flat-field method is compatible with the long-term transient determination (see sec. 21.5.3).<br />

21.5.3 Long-term transient determination<br />

Now that we have seen how to derive the flat-field in our data, we are going to try and determine<br />

the long-term transient which is assumed to be a global (i.e. pixel independent) additive time<br />

drift of the signal.<br />

It is important to understand that the long-term transient determination is made by comparing<br />

the data cube to an estimation of the sky. Thus a flat-fielding method is necessary, and,<br />

among the parameters to set for this step, we will find again those which have been encountered<br />

in the previous section. It is extremely important that a good flat-fielding method is chosen,<br />

otherwise you will see very strong artifacts appearing in the long-term transient curves. These<br />

artifacts are quite characteristic: they form an oscillating signal with a number of peaks equal<br />

to half the number of raster legs. An example of such artifacts is shown in figure 21.4. If that is<br />

your case, try and tune the flat-field parameters better or select another flat-field method (this<br />

is why we do that exercise in sec. 21.5.2).

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

Saved successfully!

Ooh no, something went wrong!