The SWIFT BAT Software Guide Version 6.3 30 ... - HEASARC - Nasa

146 APPENDIX D. BAT SOFTWARE TOOL REFERENCE
NOTE: the scripts batgrbproduct and bat-burst-advocate are identical. The first name has
been preserved for historical reasons, and the second name for consistency with the product scripts
of the UVOT and XRT.
By default it is assumed that the TDRSS position message is present. This message provides
information about the position of the burst and the initial time interval of the burst. However, the
user can override these values using command line parameters. If the RA and Dec values are set
to BLIND, then sky images are made, but no further analysis is done, and it is up to the user to
search the image to find new sources.
PREREQUISITES - the user must have the standard FTOOLS (6.0.5 or later) installed and
set up. Also, the CALDB must be installed and set up. It is assumed that the input directory
structure is the same as that produced by the Swift Data Center (SDC). The event by event data
should already be energy-calibrated by either the SDC or running bateconvert manually (i.e. the
PI and ENERGY columns should be filled).
D.10.4 SUMMARY OUTPUTS
Upon finishing, the output directory contains a text file calledprocess.log. This file contains all
the commands executed and detailed output transcripts. Users can check this file to: (a) diagnose
problems; and (b) to get ideas on how to use the software to make their own custom science
products.
The output directory also contains report.txt, which is text file with a summary report giving
basic statistics and factual information about the trigger that was analyzed.
The task concludes by printing to the console a detailed inventory of files it created, including
the name and a brief description for each file.
D.10.5 OUTPUT DIRECTORIES
The output files are arranged by type into several directories. The following list describes each
directory. Each file name contains code phrases which are also described.
outdir/lc Light curves. File names with “1chan” and “4chan” have 1 and 4 energy bins respectively.
Time binnings can be 1 second (“1s”), 64 millisecond (“64ms”) and 4 millisecond
(“4ms”). The light curves cover the full range of event data.
outdir/pha Spectra and response matrices. Spectra are computed for the total burst interval,
the T50/T90 intervals, the peak flux interval (1 second), and also for the pre-slew, slew, and
post-slew intervals. Response matrices are computed for the pre-slew and post-slew intervals.
outdir/dpi Detector images. Detector images are made in the pre-burst, pre-slew and post-slew
time intervals. Pre-burst means an image created before any detectable emission. Images
with 1 and 4 energy bins are created.
outdir/img Sky and partial coding images. Sky images are made in the same time intervals as
detector images, but only for the 1-channel images. Small “postage-stamp” images are also
created (suffix “.postimg”), centered on the burst position. Partial coding maps are made for
the pre-slew and post-slew intervals.
outdir/gti Duration information. Various good time interval files are generated. Files with “acs”
are spacecraft-attitude related (“acs 10am”, “acs sett”, “acs slew” corresponding to the 10arcmin,
settled, and slewing flags, respectively). Files with “grb” select events near the GRB