The SWIFT BAT Software Guide Version 6.3 30 ... - HEASARC - Nasa
The SWIFT BAT Software Guide Version 6.3 30 ... - HEASARC - Nasa
The SWIFT BAT Software Guide Version 6.3 30 ... - HEASARC - Nasa
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
96 APPENDIX D. <strong>BAT</strong> SOFTWARE TOOL REFERENCE<br />
be useful, for example, if each DPH row is to be flattened into a detector image, while otherwise<br />
preserving the individual exposures.<br />
<strong>The</strong> “matchlc” binning method will bin the input data to match an existing light curve. <strong>The</strong><br />
light curve, which is passed in the ‘gtifile’ parameter, must be a standard OGIP light curve file<br />
with enough information to determine the time binning. If the light curve file has a GTI extension,<br />
it is ignored. Note that the ‘minfracexp’ parameter is always honored. If it is important to exactly<br />
match the template light curve time bins, even if they have zero exposure, then set minfracexp=0.<br />
For output light curves, the TIME column may refer to the start or the center of the bin,<br />
depending on the setting of the ‘timepixr’ parameter. Output lightcurves also contain the keyword<br />
TIMEPIXR which indicates the reference point for light curve time bins. For all other output<br />
types, TIME refers to the start of the accumulation time. In some cases, a separate keyword or<br />
column named TSTOP or TIME STOP is used to indicate the stop of the accumulation time.<br />
TIME SELECTION<br />
By default, the input file is selected according to its own internal good time intervals, if any are<br />
present.<br />
Crude time selection can be performed using the tstart and tstop parameters to the task, which<br />
give the start and stop times of accumulation.<br />
More refined selections can be performed specifying the gtifile parameter. A good time interval<br />
file (GTI) describes an arbitrary number of intervals by specifying the start and stop times. <strong>The</strong><br />
intersection of the input files’ GTIs, the user-provided gtifile, and the user-provided tstart/tstop<br />
parameters, are used to select input data by time. For input DPH (survey) data, the time interval<br />
of each input DPH must overlap with the total good time intervals by a large enough amount, and<br />
must never straddle more than one output bin.<br />
<strong>The</strong> DPH overlap time required is determined by the min dph frac overlap, min dph time overlap<br />
and max dph time nonoverlap parameters. Care should be taken when altering the overlap parameters,<br />
especially when the properties of the source and the background are not constant with time.<br />
For example, if a source becomes earth-occulted during the DPH, and a corresponding occultation<br />
GTI was input to batbinevt, then the background will have the full exposure, but the source<br />
will only have a fractional exposure, i.e. the exposure is ambiguous. For exposure purposes, batbinevt<br />
records the full exposure of all DPHs that pass the overlap tests, including any non-overlap<br />
intervals. <strong>The</strong> output GTI, however, retains the user-requested good time intervals.<br />
FLUX UNCERTAINTIES<br />
batbinevt assumes that detector counts are Poisson-distributed, and propagates the errors to the<br />
output. However, if the input is a modeled background (e.g. from batclean), then the output<br />
uncertainties will be set to zero. This behavior is governed by the HDUCLAS2 keyword in the<br />
input DPH file: modeled background maps should have HDUCLAS2 = ‘PREDICTED’.<br />
D.1.4 PARAMETERS<br />
infile [filename ]<br />
Input file name or names, containing <strong>BAT</strong> event or DPH data. This may be a commadelimited<br />
list of names, or the name of a text file containing a list of file names, one per line,<br />
preceded by an ‘@’ character.