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.
34 CHAPTER 5. <strong>BAT</strong> ANALYSIS PROCEDURES<br />
5.4.5 Retrieve Known Problematic Detectors<br />
<strong>The</strong> <strong>BAT</strong> team maintains a list of known bad detectors, which is stored in the Calibration Database<br />
(CALDB). <strong>The</strong>se maps only contain detectors (usually detector modules) which were known for<br />
operational reasons to have issues which affect science analysis. <strong>The</strong> user is still responsible for<br />
filtering the data for noisy detectors (see the next section) or other obvious problems. <strong>The</strong> ‘batdetmask’<br />
task is used to retrieve the appropriate detector quality map from CALDB.<br />
batdetmask date=total.dpi outfile=master.detmask clobber=YES \<br />
detmask=../hk/swt0142921337bdecb.fits.gz<br />
• date tells batdetmask to retrieve the observation date from the detector plane image you just<br />
created<br />
• outfile is the output master quality map for the observation<br />
• detmask is the detector enable/disable map (usually in the bat/hk directory)<br />
We use the detmask parameter to combine the existing flight enable/disable map with the<br />
quality map based on ground analysis.<br />
5.4.6 Find Noisy Detectors<br />
Noisy detectors are found with the bathotpix task.<br />
bathotpix infile=total.dpi outfile=total.qmap \<br />
detmask=master.detmask clobber=YES<br />
• infile is the detector plane image you just created<br />
• outfile is the resulting quality map<br />
• detmask is the quality map we made in the previous step<br />
5.4.7 Where to Use the Quality Map<br />
<strong>The</strong> quality map should be used in all subsequent analysis. In particular, it should be used during<br />
the mask weighting process (using the batmaskwtevt task), and in the generation of all light curves<br />
and spectra (using the batbinevt task) and images (using the batfftimage) task. All of these tasks<br />
have an input parameter called detmask= which accept a detector quality map. This information<br />
is used to exclude noisy detectors, and to properly normalize the resulting output fluxes.<br />
5.4.8 <strong>The</strong> Difference Between the Enable/Disable Map and the Quality Map<br />
<strong>The</strong>re is a difference between the enable/disable map and the quality map we just produced. <strong>The</strong><br />
enable/disable map is produced by the flight software, and records which detectors were disabled<br />
at the time. Thus, this map indicates which detectors were noisy in the past, were disabled, and<br />
now have zero counts. <strong>The</strong> quality map contains that information, but also excludes any currently<br />
noisy detectors, i.e. detectors with too many counts. <strong>The</strong> <strong>BAT</strong> flight software does not catch all<br />
noisy detectors. Some detector noise is sporadic, or below the count rate threshold for disabling.<br />
Thus, the best quality map is a combination of both the disabled detectors and the currently noisy<br />
ones.