This package maintains and provides access to an online archive of many Chandra operational events, including:
The contents of the Kadi archive will be accessible on the HEAD and GRETA networks in any of four ways:
http://occweb.cfa.harvard.edu/twiki/Aspect/StarWorkingGroupMeeting2012x03x21
Envision multiple tables (maneuvers, BSH, NSM, etc), each of which has "default" times that can be used for filtering data.
Maneuver events ^^^^^^^^^^^^^^^^^
===== =========================================================================== Event Sequence for Maneuvers: ===== =========================================================================== t0 previous AOFATTMD = STDY t1 previous NMAN --> NPNT transition time t2 NPNT --> NMAN transition time tref1 AOFATTMD = MNVR (AOMANUVR time) tref2 AOFATTMD = STDY t3 NMAN --> NPNT transition time (first CEBR check passes or times out) t4 AOPSACPR changes from INIT to ACT (second CEBR check passes or times out) t5 AOACASEQ changes from ACQ to GUID / 1-shot (acquisition star success) t6 AOACASEQ changes from GUID to KALM (guide star success) t7 NPNT --> NMAN transition time t8 AOFATTMD = MNVR (AOMANUVR time) ===== ===========================================================================
MSIDs of Interest
- AOPCADMD
- AOFATTMD
- AOACASEQ
- AOPSACPR
- AOUNLOAD
Maneuver Attributes
Other telemetry event tables ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SSM
NSM
BSH
SCS 107 runs
SCS 107 execution start and stop time
Return to science time
Cause? (may be too difficult)
Should this only include SCS 107 "only" safing events (e.g. Radmon)? Or all (e.g. SSM, NSM)?
Momentum dumps
PCAD mode (AOPCADMD)
1-shot (RSS of AOATTERx)
System momentum (AOSYMOMx)
Pulse counts (AOTHRSTx)
VDE used (AOVDESEL)
Thruster temps (PMxTHV1T and PMxTHV2T)
Slightly-more detailed calculations:
Thruster efficiency
Duty cycles
Warm start count
Fuel flow rate
Fuel used
Tank pressure
Flag for anomalous
Eclipses
SIM motion
Grating motion
Dark Current Cals
Start and stop time
But will split replicas show up as two? Is this preferable, or should each replica be called out indiv?
IRU calibration uplink
CCD set point temperature changes
Gyro holds
Meteor showers
Certain iFOT tables will be synced into the Kadi event archive:
The information within many other iFOT tables will be available in Kadi, but with an intent for a higher degree of completeness. For instance the iFOT radiation zone table is missing times when there was no RADMON commanding, and the ACA dark calibration is missing events in 2005 and 2006.
There are two major event tables that are maintained and available on OCCweb:
Kadi merges these two into a common format and makes them available for query.
Using the history of load segment runtimes maintained in the Ska commanded states processing, Kadi maintains a database of all commands that were run via weekly load commanding since 2002. (Prior to that the data for precisely which load segments were run over which times is not available in the commanded states history). This database can be quickly loaded and searched by time-based or attribute-based queries.
List of updates to key thermal G_LIMMON limits (e.g. TEPHIN). To the extent that it is practical and value-added, a more comprehensive list of limit updates could be included.