Level 2 cleaned event-lists (see the directory structure thread for an explanation of the different "levels" of data) are routinely generated by the SDC processing for the Quick Look site and archive. However, it is recommended that the users run the pipeline on the Level 1 files themselves, to ensure the most recent version of the processing scripts is being run or to change the level of filtering performed.
To run the pipeline, the command is simply
xrtpipeline; however, other
selections can be included on the command line to make subsequent analysis
easier. For a full list of these, type
plist xrtpipeline. Alternatively,
fhelp xrtpipeline will reveal the help file, which could also be useful to read.
clobber=no is the default, so files will not
Here we use GRB 091029 as an example:
> xrtpipeline [createexpomap=yes cleanup=no] &> log > Source RA position [ ] 60.17793 > Source DEC position [ ] -55.95425 > Target Archive Directory Path [ ] 00374210000 > Stem for FITS input files [ ] sw00374210000 > Directory for outputs [ ] 00374210000-xrt
Many files are created by the pipeline, with the most important one being the cleaned event-file (sw[obsid]x<mode><window><type>_cl.evt - see the files and directory structure thread for an explanation of the naming convention).
The commands within the square brackets are not required, but can be useful.
createexpomap=yescreates an exposure map corresponding to each event-list; this is the default from version 3.7 of the software. See the exposure map thread for more details.
cleanup = nokeeps the temporary files created by the pipeline. Of most use are the region files centred on the position given, which will have names of the form sw[obsid]x<mode><window><type>.reg.
The target directory path must include the
Note that files produced by xrtpipeline cannot be written inside this target directory (that is, the directory of downloaded files - 00374210000 in the above example); the output directory must be at the same level or higher than the input one in the directory structure.
The stem for the input files is
sw followed by the 11 digit concatenation of the target ID (8 digits) and observation segment number (3 digits).
For version 2.8 and later of the Swift software, the default screening criteria (for data collected since September 2007) are:
Note that the substrate voltage (Vsub) was raised from 0V to 6V on 7th August 2007. Previous data are (automatically) processed with
The default CCD temperatures should, in general, be acceptable. However, should the observation be particularly hot, and the data are still required, a GTI expression needs to be included; i.e.:
xrtpipeline gtiexpr="<required expression>"
<required expression> is a list of boolean commands. As an example, to remove all temperature and angular filtering, simply typing
xrtpipeline gtiexpr="SAA==0" would work. See
xrtscreen for more details.