30.01.2013 Views

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

158 APPENDIX D. <strong>BAT</strong> SOFTWARE TOOL REFERENCE<br />

D.13.4 IMPORTANT NOTES<br />

<strong>The</strong> mask tagged light curves are invalid during spacecraft slews. Mask tagged data during slews<br />

should be ignored.<br />

<strong>The</strong> generation of the output file will fail if the file is too large to fit the available memory.<br />

D.13.5 PARAMETERS<br />

infile [filename ]<br />

Name of the raw mask tagged rate file, as described above.<br />

quadfile [filename ]<br />

Name of the input quadrant rate file.<br />

maskwt [string ]<br />

Name of mask weight map file. Normally, users should set the value to “INFILE” or “FILE”,<br />

to indicate that the mask weight map is attached to the raw mask tagged light curve.<br />

outfile [filename ]<br />

Output light curve file name.<br />

(detmask = “none”) [string ]<br />

Optional input detector plane mask. This is used to exclude detectors that are disabled<br />

from contributing to the light curves and errors. This file should always be a flight code<br />

generated detector mask which represents only detectors actually turned off, rather than a<br />

mask derived from ground processing. Typically, these files are found in files named like<br />

obsid/bat/hk/swNNNNNNNNNNNbdecb.fits.<br />

(ebounds = “INFILE”) <strong>The</strong> location of the EBOUNDS file describing the energy ranges in<br />

the light curves. <strong>The</strong> default is to use an EBOUNDS extension that is part of the infile (use<br />

“INFILE” or “FILE”). One can also specify “CALDB” if the EBOUNDS extension is not<br />

present.<br />

(corrections = “default”) [string ]<br />

Comma-separated list of corrections to apply to the mask weighting, or “none” if no corrections<br />

are to be applied. Other possible correction types are: “flatfield” (basic flat fielding<br />

correction accounting for both cosine-type and r-squared-type effects); “cosine” (cosine effects<br />

of off-axis illumination only); “pcode” (partial coding effect only); “ndets” (correction<br />

for disabled detectors). <strong>The</strong> “default” correction is pcode,flatfield,ndets.<br />

(detdiv = “YES”) [string ]<br />

Do you want the rate to be per detector (detdiv=“YES”) or for the whole array (detdiv=“NO”).<br />

<strong>The</strong> division is only applied if the corrections parameter includes “ndets”. Note<br />

that if no detector mask is supplied, then the rate will be divided by the total number of<br />

detectors (32768).<br />

(scale = 1.3) [real ]<br />

<strong>The</strong> user is allowed to supply a scale factor to correct for any known errors in how the raw<br />

mask-tagged light curve is calculated. <strong>The</strong> scale factor is multiplicative and scales all output<br />

counts by the same factor. <strong>The</strong> default value of this parameter was determined empirically

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!