Use Case: GetOffLineObservation


This Use Case describes how the Caibration Pipeline gets off-line data and metadata to be processed.

The Observer selects data to be processed from the Archive. The data and metadata are read one observation at the time and both are saved in memory in order to be processed in the same way as with on-line calibration, according to Observation Intents, as available in the metadata.

Role(s)/Actor(s):
Primary: Observer
Secondary: Archive

Priority: Major

Performance: from seconds (such as pointing/focus measurements) to minutes for array calibrations (baseline, pointing model).

Frequency: minutes

Preconditions:

  1. One or a a set of calibration scans are available in the Archive.

Basic Course:

  1. The Observer selects one or a set of calibration scans in the Archive, using available archive functionality (data selector, data extractor).

    For each observation, the System looks for the ObservationIntent, in the metadata.
    Exception Course:The ObservationIntent is not regognized by the System: the observation is ignored and the problem is logged.



  2. The System then gets input: metadata and data, filters them according to the specified Observation Intent, and saves them in memory.


Alternate Course:

  1. ...


Postconditions:

  1. Metatadata and data relevant to the observation are saved in memory according the relevant ObservationIntent


Issues to be Determined or Resolved:

Notes:

Owner: Robert Lucas
Last modified by $Author: telcal $ on $Date: 2002/10/22 11:53:18 $