Introduction to Log Entries

It is important to establish some definitions before proceeding into the different Log Entries.  OPSLOG uses a mode or state to allow and disallow editing or adding new data.  This is discussed in this section as well. The topics discussed are:

 

Type of Log Entries

There are formally 12 different types of Log Entries.  Their definition reflects when these entries should be made.  All log types are entered directly by the operator with the exception of Operator Login and Operator Logout.

  1. Failure This entry is used to indicate whenever there has been hardware, software or other failure that results in either lost observing time or may have an impact on the quality of data collected.  ALL lost time is tracked using a Failure entry in the system, even when lost time is associated directly with weather (eg stow due to high winds, too much snow/rain/sleet, ....).

  2. Information This is basically the catch all in that if events happen during the shift which do NOT fall under one of the other Log Entry Types this type should be used.

  3. Maintenance Activity During maintenance day there are some maintenance activities that need to be tracked in the log.  For example, inspecting brakes, greasing bearings, installed a ladder, repairing HVAC, ... These activities are essentially the major tasks being accomplished by the groups signing the access log for the antenna during maintenance days.  Although these entries would reflect the major maintenance tasks on the GBT during maintenance days when NRAO gets into the situation of performing some inspections while observing those activities would be entered into the log under this log type.

  4. Observer arrival is used to indicate which observers are present for their observations and when they arrived.  This is usually used in conjunction with the Observer departure type to keep track of observers.

  5. Observer departure is used to indicate which observer have left the control room and when.

  6. Operator Login / Operator Logout These log entries are made automatically by the program when the operator logs in and out respectively.

  7. Project change This type of log entry is used whenever the type of observing changes OR the formal proposal code changes for Astronomical and Test observing types.  It is NOT used to indicate receiver changes (see the next type). This is an important entry since these entries along with Failure, Receiver change, Restore to Operation,  Operator login and Operator logout types are used to determined lost time requirements.

  8. Receiver change would be created whenever a receiver is changed.  It is also used to indicate if either the prime focus boom, sub reflector or turret is moved.  This is an important entry since these entries along with Failure, Receiver change, Restore to Operation,  Operator login and Operator logout types are used to determined lost time requirements.

  9. Restore to Operation is used to indicate that a Failure entry type is no longer in effect.  It is effectively used to close Failure entry.  This is an important entry since these entries along with Failure, Receiver change, Restore to Operation,  Operator login and Operator logout types are used to determined lost time requirements.

  10. Scan information is used to record information on observing scans.

  11. Weather is used to record weather information.

 

Note
The log entry type is selected at the time the log entry is created by the operator.  It cannot be changed later.

 

Types of Observing

 

There are formally 8 types of 'observing' states.  These are important because they determine some of the observing statistics required by NRAO management.  The Observing type is set at initial shift log in and by Project change log entries

  1. Astronomical observations As the name suggests these are the formally scheduled and approved astronomical observations (the GBT observing schedule indicates these by a proposal code).  These do NOT include activities covered by the other observing types.  Lost time is tracked ONLY for this type of observing.

  2. Maintenance This type indicates scheduled maintenance days or periods.  

  3. Test Observations or systems tests These are the scheduled test (this includes tests as indicated on the graphical schedule or tests scheduled during commissioning). See Note below.

  4. Calibration This type indicates observations used to calibrate the telescope (see Note below).

  5. Commissioning These are all the activities that fall under Commissioning on the graphics schedule (see Note below).

  6. Shutdown This indicates that the telescope is scheduled for shutdown.  It does NOT include periods when observing is stopped due to high winds or snow.  Formal shutdowns will occur three times a year (Thanksgiving, Christmas and New Years).

  7. Not scheduled These are periods when there is no observing or scheduled maintenance.  It does NOT include periods when observing is stopped due to high winds or snow.

  8. Observation setup  There is now a practice to schedule some extra time prior to the startup of scheduled Astronomical observing to check out the system in readiness for the observing.  This is usually an hour in advance of the formal astronomy observing.

Note
The distinction between Tests, Calibration, and Commissioning types has not been clearly defined in the past.  I propose that we attempt to make this distinction more meaningful beginning with the use of OPSLOG.  It is not critical to be exact amongst these three types.

 

Fields common to log entries

There are some fields which are common to ALL log entries.  These include:

There are some other common fields that are important which are not common to ALL log entry types.  These include:

 

Program Mode or State

OPSLOG uses a mode or state to indicate if the user is allowed to change or add data.  The current state or mode (mode indicator) of OPSLOG is displayed in the upper right of the screen.  The user changes mode by: