M&TA Data Processing

An earlier form of this plan from 1997 is also available.
Back to the MTA home page

Outline of processing

Act on and output Raw or standard data products.

1. ACORN/MTA-RT - This is an MTA specialty tool for monitoring the Real-time data. Limits are sensed based on the ODB.
   • Input - The UDP real-time stream from DSN.
   • Output - Messages to the Notifier.
2. SDP - This is the SDP version of AP. It contains the following:
   • DECOM Flight DECOM. I would prefer relatively large engineering files (~1 hour in formats 1 & 2)
   • L0.5 This creates setup for L1.
   • L1 Based on the L0 event products and L0.5 OBI products. This pipeline runs on a per/OBI basis. Archival L1 event files are created.
   • L1.5 - Gratings MTA has a specific suite of procedures be executed against gratings L1 or L1.5 files.
   • L2 - Sources MTA has no use for SDP L2 sources since they may represent different time slices.
3. MTA special AP (MTA/SAP) - This is the MTA version of AP running under separate instantiation than the flight pipeline. It contains the following:
   • DECOM - We need to create L0 event lists based on only the dumps worth of data. This should be achieved by running ADE and HDE under a separate instantiation of the data extractor. These files should time out at the end of the playback. We should also run a limited version of the EDE only to produce the on board aspect solution. Question: Are the ACIS/HRC event files produced this way cumulative or just data from the last pass?
   • L1/OBIBased on the L0 event product and L0 OBC aspect solution, MTA should use something like the SI-pipe to generate a per pass events list. Question: Can the SI-PIPE use the OBC aspect data?

Act on standard data products and output an MTA product.

1. Static Monitor - This is the MTA Standard Monitoring.
   • Primary Input - L0 engineering like data of msids which are not context or state dependent. OR L1 data from ASPECT or other pipes which calculate static values useful to monitor.
   • Secondary Input - Group.list, process.list, Limits.db, Email.list.
   • Output - Data for use by notifier, fits file for use by Summary page maker, fits file for use by DB ingest.
2. Dynamic/State Monitor - This is the MTA State sensitive monitoring. Really this is a front end to the static pipe which updates the limits database with time variability information. This pipeline is designed to monitor those values which are sensitive to the actual state of the spacecraft. Whether or not the spacecraft was in the expected state requires comparison against the OBSCAT. Therefore we consider that test a V&V task.
   • Primary Input - L0 engineering like data of msids which are context or state dependent.
   • Secondary Input - Group_list, process_list, Var_Limits.db, Email_list.
   • Output - Data for use by notifier, fits file for use by Summary page maker, fits file for use by DB ingest.
3. Photon_mon/ACIS_CCD_mon - These tools have similar goals.
   • Photon_mon creates a quick look at the focal plane and certain PHA data and hot pixels..
   • ACIS_CCD_mon looks more carefully at the PHA distributions node by node/FEP by FEP as a precursor to CTI.
   • Primary Input - L0 or L1 event lists. The tools run separately on both products. So When the L0 Archival event list Is created Photon_mon (and if ACIS ACIS_CCD_mon) are executed and write to the DB tables and web pages. When the L1 Archival event list is created Photon_mon (and if ACIS ACIS_CCD_mon) are executed and write to the DB tables and update web pages. Note - when I use the term archival quality I mean data in or scheduled to go in the archive, I intend that the process run off the cache data .
   • Output - Data for use by notifier, fits file for use by html page maker (done internally), fits file to be archived (except in the case of Photon_mon - no archive).
4. ACA_MON - This is an MTA specialty tool to monitor the output of the aspect Level 1 pipe.
   • Primary Input - Archival quality L1 FIDPROPS, ACACENT and GSPROPS FILES.
   • Secondary Input - Limits.db, Email_list.
   • Output - Data for use by notifier, data for internal Summary page maker, possible data for DB (probably handled by ACA_TRD)
5. Grat_mon - This is an MTA specialty tool (specification due 3/31 - pseudo-code (IDL) is available) to monitor the Gratings data.
   • Primary Input - Archival quality L1.5 tg events file.
   • Output - Data for use by notifier, data for internal summary page maker, possible data for DB (unspecified).
6. Src_mon - This is an MTA specialty tool (specification due 3/31) to monitor the focus. We will apply our own version of cell detect to the L1 data and act on the result.
   • Primary Input - Archival quality L1 events file.
   • Output - Data for use by notifier, data for internal summary page maker, possible data for DB (unspecified).