Action #497
Feature #490: Avoid casts for derived classes
Rework GPointing interface
| Status: | Closed | Start date: | 09/20/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned To: |  Knödlseder Jürgen | % Done: | 100% | |
| Category: | - | |||
| Target version: | 00-07-00 | |||
| Duration: |
Description
It should be verified if the GPointing base class is really needed. Is there anything common to a pointing definition that needs really be exposed globally?
For many cases, a pointing is simply a constant sky direction, and it would be sufficient for a GObservation implementation to keep this sky direction information locally. For other cases, such as Fermi/LAT, the pointing changes rapidly with time, hence the pointing is a time dependent sky direction.
Again, the main question is: do we need to expose the pointing direction on a general level, or is it sufficient for the derived class GObservation to handle the pointing internally.
Recurrence
No recurrence.
History
#1
Updated by Knödlseder Jürgen about 12 years ago
- Description updated (diff)
#2
Updated by Knödlseder Jürgen about 12 years ago
- Start date set to 09/20/2012
due to changes in a related task
#3
Updated by Knödlseder Jürgen about 12 years ago
- Assigned To set to Knödlseder Jürgen
#4
Updated by Knödlseder Jürgen almost 12 years ago
All casts in the instrument specific classes have been removed. No rework has been done on the GPointing interface. Not clear whether we really need a rework, as long as we don’t have the need for a cast.
#5
Updated by Knödlseder Jürgen almost 12 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
- Remaining (hours) set to 0.0