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

D.11. BATHOTPIX 151
(keepfract = 0.98) [real ]
Fraction of non-zero detectors to select as good, initially.
(guardfract = 0.25) [real ]
Fractional amount to enlarge initially selected detectors, relative to the median value. A
value of 0.25 indicates an enlargement of 0.25 x the median on both sides of the distribution.
(guardval = 5.0) [real ]
Further amount to enlarge the selection window, this time in counts. This keyword is present
for the case of an image with very small dynamic range, where guardfract may be too small
to be effective.
(applygaps = yes) [boolean ]
If yes, then positions of BAT detector gaps are excised.
(mergemask = yes) [boolean ]
If yes, then the input mask is merged with the result before writing to the output. If no, then
only the pixels adjusted within this run of bathotpix are written.
(zerothresh = 20.0) [real ]
Threshold value. If the median is above zerothresh, then pixels with zero are considered to
be COLD. If the median is below zerothresh, i.e. the total number of counts is very low, then
pixels with zero are considered to be okay.
(goodval = 0) [integer ]
Value to be used in detector mask maps to indicate a good pixel.
(badval = 1) [integer ]
Value to be used in detector mask maps to indicate a bad pixel, such as a detector gap.
(hotval = 1) [integer ]
Value to be used in detector mask maps to indicate a hot pixel.
(coldval = 1) [integer ]
Value to be used in detector mask maps to indicate a cold pixel.
(clobber = NO) [boolean ]
If the output file already exists, then setting “clobber = yes” will cause it to be overwritten.
(chatter = 1) [integer, 0 - 5 ]
Controls the amount of informative text written to standard output. Setting chatter = 1
produces a basic summary and image statistics; chatter = 2 (default) additionally prints a
summary of input parameters; chatter = 3 prints detailed information on which hot and cold
detectors; chatter = 5 prints debugging information.
(history = YES) [boolean ]
If history = YES, then a set of HISTORY keywords will be written to the header of the
specified HDU in the output file to record the value of all the task parameters that were used
to produce the output file.