Observation blocks

[jschwarz <jschwarz@eso.org>]

Re Steve Scott's comments, observation blocks have been an integral part
of the VLT's dataflow system for several years now. The relevant URL is
http://www.eso.org/projects/dfs

A part of the introduction:

Program Handling

The procedure for proposal preparation in the Data Flow system involves
a Phase I and a Phase II proposal preparation. In
Phase I, proposals are submitted electronically to ESO and evaluated by
the Observing Program Committee (OPC). After
the OPC selection has taken place, Phase II preparation is based on
template forms describing standard instrument modes
and configurations. Observation Blocks are created by specifying the
template parameters, target information, and
user-defined scheduling constraints. The user will be assisted in these
phases by an Instrument Scientist and by observation
preparation tools. These tools include generic systems like finding
chart generators or guide star selection systems, and
instrument related tools like exposure time calculators (ETCs).
Feasibility checks of the proposals are performed by the
observatory and include technical feasibility and exposure time control. 

Observation Handling

During Phase 2 of the proposal preparation process, successful programs
convert their observing programs into structures
which are schedulable and executable by the VLT. These files are called
Observation Blocks (OBs) and combine together
target and instrument data for one or more exposures on typically a
single astronomical object. The description of an
instrument within an OB is called a Template. A subset of instrument
modes and functions supported by ESO is presented as
a template whose input values are set by the astronomer during OB
creation. All ESO instruments under the DFS/VCS
system will be operated via templates and OBs whether in service or
visitor mode. OBs are the quantum of data that flows
within the DFS, collecting state, data and status information as they
flow. When scheduling service mode observations, OBs
represent the smallest schedulable unit of telescope resources. OBs are
submitted to an OB Repository from which a
medium term and short term schedule can be constructed for service mode
observations or from which a visiting astronomer
can schedule his/her nights' observations.