Action #2152
Make sure that all ctools/cscripts work for non-CTA observations
| Status: | In Progress | Start date: | 07/11/2017 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assigned To: |  Knödlseder Jürgen | % Done: | 10% | ||
| Category: | - | ||||
| Target version: | - | ||||
| Duration: |
Description
The GCTAObservation class handles different instrument types, but not all ctools properly handle non-CTA instruments. For example, ctobssim generates a CTA event list even if the Instrument Response Function used for the simulation is a non-CTA IRF.
The code (probably mainly in GammaLib) should be changed so that proper forwarding of instrument types is guaranteed.
Recurrence
No recurrence.
History
#1
Updated by Knödlseder Jürgen almost 6 years ago
- Target version set to 1.6.0
See also #2140 for an issue with the background model that is generated by ctbkgcube.
#2
Updated by Knödlseder Jürgen almost 6 years ago
- Status changed from New to In Progress
- Assigned To set to Knödlseder Jürgen
- % Done changed from 0 to 10
#3
Updated by Knödlseder Jürgen almost 6 years ago
The GCTAResponseIrf::read method always opens a cta calibration database, which means that we cannot use mission name as instrument name in a CTA observation. This also means that whatever the instrument (H.E.S.S., VERITAS, MAGIC), the IRF needs to be in the cta folder of the response.
The GCTAResponseIrf::read method should be changed so that in case that an instrument attribute is available in the XML file, this attribute is transformed to lower case and used when opening the calibration database.
#4
Updated by Knödlseder Jürgen over 5 years ago
- Target version deleted (
1.6.0)
Do not include in 1.6.0 release