Observation Component Editor

The observation component editor is accessed in the usual manner, by selecting the observation component in your science program, and is shown below.

The relative priority of this observation, compared with other observations in the same science program, is set using the high/medium/low buttons. See more details on how the priority affects execution and to add observations into groups. If not already defined, you can edit the observation name to make the science program viewer more understandable (normally this will be the science target name). 

The save button accepts the latest changes and stores the program to the local database, the undo/redo button (and, transiently, the edit pencil) toggles pending and saved changes and the close button closes the science program editor (saving any changes to the local database).

The other fields in the observation component editor are for status information added at the observatory during program execution. The history field will contain narrative text information added by the Gemini staff e.g. verification details, execution problems. The observation status can have values:

• Phase II - observation is in Phase II prep. It is not ready to be executed. This is the default when the observation is created.
• For review - PI has finished Phase II prep. Observation is ready for review. Output of review is "Ready" or back to "Phase II" for more work.
• Ready - observation has been 'verified' (at present this means it has been checked manually) and is ready to be scheduled/executed.
• Observed - observation has been executed; data awaiting Quality Assessment (see more details of the QA process).
• QA (Meets) - quality assessment has been performed on the data. It meets the science needs and has therefore passed QA.
• QA (Useable) - quality assessment has been performed on the data. It does not meet the PI's science needs but might be useable by someone else (via the archive).
• QA (Bad) - quality assessment has been performed on the data. It has failed QA and will not be archived.
• Repeat - observation has resulted from a previously incomplete or incorrect execution. This is the default state when a 'clone' of an observation is made (it is analogous to Phase II for a new observation). The observation is not ready to be executed.

Last update October 11, 2001; Phil Puxley