Skip banner and navigation tools.

 |  site map

Skip sidebars of related page links.

Producing cleaned XRT event-files

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. Note that clobber=no is the default, so files will not be over-written.

Step-by-step

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).

Explanations

The commands within the square brackets are not required, but can be useful.

The target directory path must include the auxil and xrt sub-directories.

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 always sw followed by the 11 digit concatenation of the target ID (8 digits) and observation segment number (3 digits).

Attitude files

As explained here, there are three different types of Swift attitude file. You can determine which has been used when running xrtpipeline by looking at the ATTFLAG keyword in the EVENTS extension of the event list. The flags are defined as:

This same attitude file (be it sat, pat or uat) should be used when creating exposure maps and running xrtlccorr.

Additional Information

For version 2.8 and later of the Swift software, the default screening criteria (for data collected since September 2007) are:

 (ELV>=28||BR_EARTH>=120)&&(SUN_ANGLE>=45&&ANG_DIST<=0.15&&MOON_ANGLE>=14)&&
((CCDTemp>=-102&&CCDTemp<=-47)&&(Vod1>=29.8&&Vod1<=30.25)&&(Vod2>=29.30
&&Vod2<=29.80)&&(Vrd1>=16.40&&Vrd1<=16.80)&&(Vrd2>=16.45&&Vrd2<=16.90)&&
(Vsub>=5.67&&Vsub<=6.07)&&(Vbackjun>=5.65&&Vbackjun<=6.05)&&(BaseLin1>=0.1&&
BaseLin1<=0.4)&&(BaseLin2>=-0.1&&BaseLin2<=0.1))&&((STAST_LOSSFCN>=0&&
STAST_LOSSFCN<=5.0E-9)||(STAST_LOSSFCN>=1&&STAST_LOSSFCN<=1.0E+3))&&(STLOCKFL==1)
&&((SETTLED==1&&TEN_ARCMIN==1)||(SETTLED==1&&TEN_ARCMIN==0&&SAFEHOLD==0))

Note that the substrate voltage (Vsub) was raised from 0V to 6V on 7th August 2007. Previous data are (automatically) processed with Vsub>=-0.1&&Vsub<=0.1&&Vbackjun>=-0.1&&Vbackjun<=0.1

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>"

where the <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.

Please note that, if you include a GTI expression, the only additional filtering which will be done by default will be (SETTLED==1&&TEN_ARCMIN==1)||(SETTLED==1&&TEN_ARCMIN==0&&SAFEHOLD==0). Any filtering on the star trackers will be lost unless explictly stated in the gtiexpr input.

Index