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:
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.
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, ....).
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.
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.
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.
Observer departure is used to indicate which observer have left the control room and when.
Operator Login / Operator Logout These log entries are made automatically by the program when the operator logs in and out respectively.
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.
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.
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.
Scan information is used to record information on observing scans.
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.
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
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.
Maintenance This type indicates scheduled maintenance days or periods.
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.
Calibration This type indicates observations used to calibrate the telescope (see Note below).
Commissioning These are all the activities that fall under Commissioning on the graphics schedule (see Note below).
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).
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.
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.
There are some fields which are common to ALL log entries. These include:
Log Date This is the date and time (always Eastern Time Zone) of the action or state to which the log entry refers to. Some examples: the date and time the receiver failed, the date and time when observations XXXXX began, date and time when the weather was sampled and so on. It does NOT necessarily refer to the date and time the log entry was created (in most cases it will not). Exception: The date and time used for Operator login and logout are the formal shift change times.
Comment The comment field is used to enter any information pertinent to log entry that is not covered in other fields. This is in principal a field whose size is not limited (other than by disk space).
Log Key There is a unique number assigned to each log entry. It is used by OPSLOG to 'tie' information together between different tables. It is sometimes useful to the user of OPSLOG.
Parent This is the log key of any log entry that the current one is related to. For example a Restore to Operation log entry will have the parent key referencing the original failure entry. Comment log entry types will also have the log key of the entry to which it refers to stored in the parent key.
There are some other common fields that are important which are not common to ALL log entry types. These include:
Proposal This is the formal proposal code for approved Astronomical observations. These codes can be constructed from the GBT graphics schedule and are listed in the Astonomical Summary for each graphics schedule. Is IMPORTANT to get these codes correct since they are used for many of the statistics calculated for NRAO management. The form of the proposal code is
GBT01A-011 for GBT proposals: 01A is the trimester and it refers to the first trimester of 2001; -011 is running number for the trimester
AB123 for VLA proposals: A is VLA; B is the first letter of last name of PI; 123 is running number
BU345 for VLBA proposals: B is VLBA; U is the first letter of last name of PI; 345 is running number
GL026 for global proposals: G is Global L is the first letter of last name of PI; 026 is running number
EVN113 for EVN proposals: 113 is running number
(GO) Project id is the project id established in GO. Among other things it refers to the sub directory (within home/gbtdata) that contains the data for the current observations.
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:
Adding a new log entry from the Menu Edit / New Log Entries and selecting the type of Log entry from the list OR from the popup menu (right mouse click) Add new log Entry and choosing the type from the list (Append shows in the mode indicator)
Selecting from the Menu Edit / Edit current data OR the popup (right mouse click) menu (Edit shows in the mode indicator)
selecting the Menu Edit / Save Changes OR the Save Changes from the popup menu OR the edit toolbar icon (View shows in the mode indicator)
selecting the Menu Edit / Abandon Changes OR the Abandon Changes from the popup menu OR the cancel toolbar icon (View shows in the mode indicator)