Bug #2686
ctselect automatically sets RoI if event files have no RoI definition using the user parameters
| Status: | Closed | Start date: | 09/22/2018 | |
|---|---|---|---|---|
| Priority: | Immediate | Due date: | ||
| Assigned To: |  Knödlseder Jürgen | % Done: | 100% | |
| Category: | - | |||
| Target version: | 1.6.0 | |||
| Duration: |
Description
When analyzing the H.E.S.S. files it appeared that ctselect automatically sets the RoI to the values specified by the user parameters when loading the event files. This is due to the fact that the ctool::setup_observations method calls the ctools::set_obs_bounds method. I do not recall why this method is called, but it is clear that we should no do this, at least not for ctselect.
Recurrence
No recurrence.
History
#1
Updated by Knödlseder Jürgen over 5 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
I removed the calls to the ctool::set_obs_bounds method. None of the unit tests got affected, probably because for all test data the boundaries were already set.
The code is merged in devel.