Identifying the Input Files (Step=0)

Relevant code

XDpiped.csh ObsIdentifyXD.py mklistXD.csh FindSpectra.py

Relevant options

None

What it does

The first step in the process is to identify the types of files in the user-supplied list, and make sub-lists of each data type. This is done by the Obsidentify.py and mklistXD.csh modules, which create various lists in the LISTS subdirectory (target.lst, QH.lst). At this point, the code also figures out whether the telescope was nodded along the slit or off to blank sky, does a few basic checks on the input data (e.g., checks for changes in exposure time/coadds, non-existent files), and records information about the telescope offsets that will be needed in steps 7 and 13. Some of this relies on the Observation Classes (OBSCLASS) being correct in the headers, which should be the case if the observations were set up following the GNIRS OT library or template observations.

What to look for

This usually works fine. If you are curious or suspect problems, check that the contents of the .lst files in the LISTS directory are what you would expect, based on the files you specified.

Things to most likely go wrong

Usually, the code exits with an intelligible error if problems (missing files, bad headers, …) are encountered. As noted in Data Requirements, XDGNIRS expects the OBJECT keyword to be identical in the acquisition and spectroscopy files for a given object (science target or standard star). If that is not the case, it will think it does not have the data necessary to continue, so you may have to edit the file headers. If the code exits or crashes for reasons you do not understand, maybe you have encountered a subtle feature of the headers that would require the grep (or other) syntax in mklistXD.csh to be changed.