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.

202 CHAPTER 17. IMPORTING <strong>ISO</strong> DATA PRODUCTS TO CIA<br />

17.1.2 SADs from AAR: aa2sad<br />

To convert AAR data products to SADs in memory or on disk we use the procedure aa2sad.<br />

Note that this routine is a command line version of the high-level widget program sad display<br />

– see Section 10.2. Using the assigned variables of Section 17.1.1 an example call is:<br />

CIA> aa2sad, tdtosn, ssad_origin, ssad_future, scd_dir=scd_dir, $<br />

CIA> sad_dir=sad_dir, arc_dat=product_dir, ack=ack, /noscd<br />

Two SSADs are created, one being the origin and the other the future SSAD (see Section<br />

15.2.4). The keyword ack returns a logical value, 1 for a successful call and 0 for a failure.<br />

Other useful optional keywords to aa2sad are nowrite and noscd. Setting nowrite will inhibit<br />

writing of SADs to disk. Setting noscd, as in the example, inhibits the default creation of SCDs<br />

along with the SADs.<br />

17.1.3 SCDs from SPD: spdtoscd<br />

To convert SPD data products to SPD SCDs in memory or on disk we use the procedure<br />

spdtoscd. Using the assigned variables of Section 17.1.1, an example call is:<br />

CIA> spdtoscd, ’cisp14300601.fits’, sscd, dir=product_dir, $<br />

CIA> scd_dat=scd_dir, ack=ack<br />

The output parameter sscd will contain the name of the created SSCD. Only one SSCD<br />

exists for a single CISP file. The SSCD and its SCDs will be written to scd dir (permission to<br />

write on this directory is required). The keyword ack returns a logical value, 1 for a successful<br />

call and 0 for a failure. For more advanced users, the UTK start time and end time of required<br />

SCD records can be passed as keywords to spdtoscd (see the on-line help or cia help).<br />

In addition the keyword bs may be of interest to observers with beam-switch data. Beamswitch<br />

observations have an intermediate step which occurs while slewing and data accrued<br />

in this step may appear in an SCD. Normally this SCD is considered to contain invalid data.<br />

Setting /bs will make spdtoscd merge this SCD with the previous SCD and users can later<br />

manually unmask this ‘invalid’ data for inclusion in the finally MOSAIC image.<br />

17.1.4 SCDs from ERD: erdtoscd<br />

With the exception that erdtoscd creates ERD SCDs from ERD data products, everything in<br />

the description of spdtoscd in Section 17.1.3 also applies here. An example call might be:<br />

CIA> erdtoscd, ’cier14300601.fits’, sscd, dir=product_dir, $<br />

CIA> scd_dat=scd_dir, ack=ack<br />

17.1.5 CDSs from CAL-G files: calg2cds<br />

To convert CDS data products from files on the CD-ROM to CDSs in memory or on disk we<br />

use the function calg2cds 1 . Using the assigned variables of Section 17.1.1 an example call is:<br />

1 Remember that since the CDSs in CIA are more recent then the distributed CAL-G files (Section 9.4.3) it is<br />

unlikely that you will frequently use this routine.

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

Saved successfully!

Ooh no, something went wrong!