Change request #1013
Make `ctbin` less strict for the input event lists it accepts?
Status: | New | Start date: | 12/03/2013 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assigned To: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Duration: |
Description
I’d like to use `ctbin` to create a count cube for an event list I have and am annoyed by the things I have to “fake” to make it work (see attached script).
It still doesn’t work because `ctbin` requires a `GTI` extension:
*** ERROR encounterted in the execution of ctbin. Run aborted ... *** ERROR in GCTAEventCube::set_time(): No Good Time Intervals (GTIs) have been found. Every CTA event cube needs associated GTIs to allow the computation of the ontime.
In principle I think having an event list format verification is good, but it would be nice if some things were declared optional about the CTA event list format and if the ctools printed warnings for missing things instead of aborting with an error.
Some suggestions:
- Event list columns like 'EVENT_ID’, 'MULTIP’, 'DIR_ERR’, 'AZ’, 'COREX’, 'COREY’, 'CORE_ERR’, 'XMAX’, 'XMAX_ERR’, 'ENERGY_ERR’ should be optional.
Not all CTA event lists will have these columns filled and filling the hard disk with zeros e.g. when running large-scale simulations with `ctobssim` is bad.
- Having 'TSTART’, 'TSTOP’, 'MJDREF’, 'RA_PNT’, 'DEC_PNT’ as header keywords is problematic. In my case I have 10,000 runs with ~ 100 events each. Do I really have to write 10,000 files, i.e. is there no way to create combined event lists for several runs?
- `ctbin` could print a warning, but still run if the `GTI` extension is not present?
Recurrence
No recurrence.
History
#1 Updated by Knödlseder Jürgen over 10 years ago
Good Time Intervals are mandatory. You have to know the effective observing time that was used for data taking.
#2 Updated by Knödlseder Jürgen over 10 years ago
- Tracker changed from Bug to Change request