NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Dynamic > SchedulingData
   Changes | Index | Search | Go

Scheduling Data - Complete, pending testing of selection rules

Overview

Certain data must be collected and managed in order to manually or automatically conduct dynamic scheduling. The data querying software needs to be able to provide complete feedback if requested. (E.g. "Project X was not suggested as it requires 4.5 hours of observing and there is a fixed time project which must be run in 3 hours.") Also, the querying software will only answer the query - it will have no knowledge of individual scheduling blocks and will not begin any observing processes. The system for which the data is entered should be simple enough for all users (investigators, support staff, etc). Additionally, the GBT scheduler needs an easy means to add projects (e.g. maintenance days, TO projects) to the system.

Data determined in advance of the run-time decision

Data determined at the run-time decision point

Data which changes at the end of observing period

Data that can only be used once an observation has been started.

Input Table

Definitions:

Input Originally from Modifiable by
  PST DSS Programs Investigator(s) PSC Scheduler Operator Support
Project
User on site date   DONE DONE Note 1 DONE   DONE   DONE
User unavailable dates DONE DONE PICK   DONE   DONE DONE DONE
User contact info DONE Note 5 PICK   DONE   DONE DONE DONE
Semester assigned DONE PICK       DONE    
Total Time DONE PICK     DONE DONE    
Used Time   DONE PICK       DONE    
Science Grade   DONE     DONE DONE    
Thesis DONE     DONE   DONE    
Proposal Contact DONE PICK       DONE    
Observing Contact(s) DONE PICK   DONE   DONE DONE DONE
Session
LST/UT Range DONE PICK       DONE    
Fixed/Window/Any DONE PICK       DONE    
Minimum Time   DONE PICK   DONE   DONE   DONE
Maximum Time   DONE PICK   DONE   DONE   DONE
Time Between   DONE PICK   DONE   DONE   DONE
Canonical Freq.   DONE PICK       DONE    
Canonical Declination   DONE PICK       DONE    
Max. Wind Speed DONE PICK   DONE Note 3 DONE DONE    
Min. Atm. Eff. DONE PICK   DONE Note 3 DONE DONE    
Instrumentation DONE PICK   DONE Note 4   DONE   DONE Note 4
Total Time DONE PICK       DONE    
Used Time   DONE PICK       DONE DONE  
Night/Work/Any DONE PICK   DONE Note 6   DONE   DONE Note 6
Session Priority   DONE PICK   DONE   DONE   DONE
Max % for Semester   DONE PICK     DONE DONE    
Solar Avoidance/Location   DONE PICK   DONE   DONE   DONE
Success of TP   DONE PICK       DONE DONE  
Start of TP   DONE PICK       DONE DONE  
Stop of TP   DONE PICK       DONE DONE  
NRAO Priority   DONE PICK       DONE    
Other
Sunrise/sunset definition   DONE       DONE   DONE
Current telescope state     DONE       ?  
Current weather     DONE       DONE DONE

Input Table for Fixed Time Sessions needs group approval.

Fixed Time Input Originally from Modifiable by
  PST DSS Programs Investigator(s) PSC Scheduler Operator Support
Session
Start Datetime DONE PICK DONE DONE   DONE   DONE
Repeat Time DONE PICK DONE DONE   DONE   DONE

Input Table for Fixed Window Sessions needs group approval.

Fixed Window Input Originally from Modifiable by
  PST DSS Programs Investigator(s) PSC Scheduler Operator Support
Session
Start Datetime DONE PICK DONE DONE   DONE   DONE
Length DONE PICK DONE DONE   DONE   DONE
Repeat Time DONE PICK DONE DONE   DONE   DONE

Instrumentation Table :

Here are the details that comprise the instrumentation information described in the session:

Name Description Required
Backend The backend to be used DONE
Receiver The frontend to be used DONE
Canonical Frequency The frequency that represents this session DONE
Observing Mode Line vs. Continuum DONE
? ?  
Melinda: bandwidth for backend=spectrometer effects whether an Session is runable because it effects the devices/paths that are routed. For multi beam receivers the beam and the number of beams required effect whether an Session is runable. The number of frequencies for any given configuration effects whether an Session is runable.

Melinda: An session may require more than one instrumentation or backend and receiver should be plural

Notes:

  1. User on site obtainable from reservation system, potentially
  2. RFI group can set window-of-opportunity periods for RFI mitigation
  3. Observer may modify weather grade, but not higher than set by PSC/PST
  4. Instrumentation changes must be made by the GBT scheduler except in the case of switching the SP to the ACS, or vice-versa. There may be other exceptions to this run determined later. See Instrumentation Table for more details.
  5. Technically, the NRAO User Database and associated portal manages this info, not the PST
  6. Night can be switched to any time, but not vice-versa

There are other inputs that don't fit into the columns in the table. These items are in 'green' on the Scheduling Rules page. I think these can be all classified as "viewing/selection filters" chosen by the operator. The operator has the option of turning these selection rules off/on. These are:

Topic SchedulingData . { Edit | Attach | Ref-By | Printable | Diffs | r1.29 | > | r1.28 | > | r1.27 | More }
Revision r1.29 - 27 Apr 2007 - 09:49 GMT - KarenONeil
Parents: WebHome 		Content copyright © 1999-2007 by the contributing authors.
All material on this collaboration platform is the property of the contributing authors.

Dynamic.SchedulingData moved from Dynamic.SchedulingMetadata on 06 Dec 2006 - 11:54 by KarenONeil - put it back