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
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
32 CHAPTER 5. <strong>BAT</strong> ANALYSIS PROCEDURES<br />
Search in the <strong>BAT</strong> trend data by month. See /swift/data/trend/YYYY MM/bat/bgainoffs<br />
on the <strong>HEASARC</strong> FTP site.<br />
You want the next earliest gain/offset map produced before the event data in question. Since<br />
the trend data are not named by time but by observation, this is especially inconvenient. Rather<br />
than searching all the files in the given month, you can narrow your search. In the event file, look<br />
for the LDPGAIN and LDPOFFST keywords,<br />
ftlist sw00145675000bevshsp_uf.evt.gz K | grep LDP | grep Index<br />
which produces the following<br />
LDPGAIN = 171. / LDP Gain Index<br />
LDPOFFST= 478. / LDP Offset Index<br />
<strong>The</strong>se are semi-unique identifiers of which map were used. If you convert these two index values<br />
to hexidecimal, you get gain=0x00ab, offset=0x01de. This tells you which kind of filenames to look<br />
for in the trend data. You would use a wildcard mask like this:<br />
ls sw*bcbo01deg00ab.fits*<br />
Note how the offset index (01de) and gain index (00ab) have been incorporated into the file<br />
name. This command produces the following three files:<br />
sw00067672001bcbo01deg00ab.fits.gz sw00145675000bcbo01deg00ab.fits.gz<br />
sw00145581002bcbo01deg00ab.fits.gz<br />
All of these files should have identical gain/offset contents. However, it is prudent to download<br />
each of them and use the one closest in time to the event data of interest according to its TSTART<br />
keyword.<br />
5.4 Making a Detector Quality Map<br />
Once a <strong>BAT</strong> event list has been cleaned of diagnostic events and the energy calibration has been<br />
applied, the full detector array should be scanned for anomalous detectors. <strong>The</strong>se are detectors that<br />
have too high or too low counts, compared to the expected statistical distribution. This section<br />
describes how to make a detector quality map, which is used in all following steps, including<br />
performing mask weighting (ray tracing), extracting spectra, light curves, and images.<br />
5.4.1 Reasons to Create a <strong>BAT</strong> Quality Map<br />
• If it has not been run before (i.e. missing files).<br />
• To capture improvements in the newer software/ground calibration.<br />
• To focus on a narrow energy or time range where some detectors became noisy.