|
|
Run_state of service mode runs
(internal documentation)
by Petra Nass
Last update:September 16, 2005.
|
|
Note: this page reflects the situation as of October 2007, may need an update from time to time! Any links will go to an USD internal area which is password protected (you could login to w4 and check that page directly).
Description of run_state of SM runs
A) Default for all newly added runs during the period: OPEN
- The default run_state of all incoming runs is now OPEN.
- The support astronomer has to inform the operations support
scientists if the run_state for a run has to be changed
(e.g. after consulting
the Database Consistency Check Page
which is updated hourly from 9:30 to 17:30, Garching time)
B) Default for all new runs for next period: NEXT
- The default run_state of all SM runs for next period is NEXT.
- By default, all NEXT runs will be set to OPEN at
the start of the new period.
- The support astronomer has to inform the operations support
scientists if the run_state for a run has to be changed from
NEXT, e.g. to HOLD or to CARRYUNDER.
To track service mode runs during PHASE2, we use our
own database, called
phase2 .
In this database, each run has a status which is called
run_state.
Possible values for this run_state are: