Action #553
Feature #903: Implement a sky region class
Define interface for region classes.
| Status: | Rejected | Start date: | 10/09/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned To: |  Deil Christoph | % Done: | 100% | |
| Category: | - | |||
| Target version: | HESS sprint #1 | |||
| Duration: |
Description
As first step, the interface for the region classes should be defined.
I think it would be best to start from a minimal case, defining only the methods that are really needed.
Recurrence
No recurrence.
History
#1
Updated by Knödlseder Jürgen over 11 years ago
- Description updated (diff)
#2
Updated by Knödlseder Jürgen over 11 years ago
To start get the ball rolling I started a Wiki page on regions: https://cta-redmine.irap.omp.eu/projects/gammalib/wiki/GRegion
#3
Updated by Knödlseder Jürgen over 11 years ago
- Status changed from New to In Progress
#4
Updated by Deil Christoph over 11 years ago
- Assigned To set to Deil Christoph
#5
Updated by Deil Christoph over 11 years ago
Jürgen Knödlseder wrote:
To start get the ball rolling I started a Wiki page on regions: https://cta-redmine.irap.omp.eu/projects/gammalib/wiki/GRegion
Thanks.
I’m trying to write down an API proposal and simplified code for the most important region use cases at the moment.
One thing I wanted to mention is that I don’t think there is an XML region file format, so I would propose to use the ds9 / CIAO ascii format instead.
#6
Updated by Knödlseder Jürgen over 11 years ago
I asked our VO gurus, and so far I got no response. I agree, let’s use ds9 for the moment. We can always add an XML format if required.
#7
Updated by Martin Pierrick almost 11 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Parent task changed from #535 to #903
#8
Updated by Knödlseder Jürgen almost 11 years ago
- Status changed from Resolved to Rejected
- Remaining (hours) set to 0.0