Run_state of service mode runs (internal documentation) by Petra Nass Last update:September 16, 2005.
	HOME INDEX SEARCH HELP NEWS

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:

• OPEN or CARRYOVER
  all OBs which have "+" or "M" might be executed at any time
  • OPEN
  • CARRYOVER
  • CARRYUNDER
  • REOPEN

• HOLD
  No OBs will be executed, because all OBs for a HOLD run will not appear in the queues, no matter if they are "+", "M" or any other OB status.
  
  Examples and Further Details about HOLD
  Note: A new status WAIT was added during the transition phase from P70 to P71, to cope with the different period start/end dates for different telescopes/instruments. This status will only be used in exceptional cases!
• COMPLETED or TERMINATED
  No OBs will be executed anymore, all OBs for such runs should either have OB status "C" or "K" (it's the task of the support astronomer to set the OB status to "K"ancelled. Usually this happens mostly at the end of the period and/or for TERMINATED runs)
  • COMPLETED
  • COMPLETED/PRE
    completed pre-imaging run
  • COMPLETED/TOO
    completed TOO run TBD if still needed!
  • COMPLETED/PF
    completed run, however run was only partly feasible
    
  • TERMINATED/LP
    large programme, either all OBs for a certain period completed or terminated because OPC allocated time for that period exceeded
  • TERMINATED/EA
    run started but terminated, Exceeded Allocation
  • TERMINATED/UR
    run started but terminated, User Request
  • TERMINATED/EP
    run started but terminated, End-of-Period
  • TERMINATED/IA
    run started but terminated, targets InAccessible
  • TERMINATED/PO
    run started but terminated, PSO technical decision
  • TERMINATED/NO
    run terminated, PI never submitted any OBs
  • TERMINATED/NS
    run not started, terminated due to end-of-period

  Note: TOOs have "_TOO" appended to the run_state.
  

• TRANSFERRED/..
  No OBs will be executed for such runs. All remaining "+" or "M" OBs need to be "K"ancelled.
  • TRANSFERRED/VM
    run has been transferred to visitor mode
  • TRANSFERRED/SM
    run has been transferred to another service mode run