Change request #2677
Do no longer interpolate for background cube
| Status: | Closed | Start date: | 09/12/2018 | |
|---|---|---|---|---|
| Priority: | Immediate | Due date: | ||
| Assigned To: |  Knödlseder Jürgen | % Done: | 100% | |
| Category: | - | |||
| Target version: | 1.6.0 | |||
| Duration: |
Description
Interpolation of a stacked background cube is problematic when combining various energy thresholds. The background cube should be exactly in the same binning as a counts cube since both live in the same space. The same energy layer selection should be implemented in ctbin and GCTACubeBackground so that both cubes are compatible. The m_energies member in GCTACubeBackground should be changed into a m_ebounds member. ctbkgcube should be changed accordingly.
Recurrence
No recurrence.
History
#1
Updated by Knödlseder Jürgen about 6 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
The interface to GCTACubeBackground was changed. The energies of the background cube are now defined using a GEbounds instance, before they were defined using a GEnergies instance. This means that the background cube can now be defined in exactly the same way as a counts cube.
The evaluation of the background cube values is done by integrating the background rate over the energy bins assuming a power law. This should make the evaluation relatively insensitive to the exact number of energy bins.
The test data files were updated so that they are compliant with the new format. Specifically, an energy boundary extension is now stored in the FITS file instead of an energies extension.
The changes were merged into devel.