There are no Operator screens per say for the M&C system. Operators monitor the status and state of the M&C as reflected by CLEO screen elements.
The Status display provides a text description of the status (health) of a manager. The background color of the text will turn colors depending upon the severity of the status of the device. The posible messages that would be displayed are; Clear, Info, Notice, Warning, Error, Fault, and Unknown.
The State display reports what the manager is currently doing. The background of the text will turn colors depending upon the state of the device. The possible messages that would be displayed are; Not In Service, Off, Standby, Ready, Activating, Committing, Running, Stopping, Aborting, and Not Connected.
The three "lights" following the status and state indicate the connection state of the display to the M&C system. These are either green "up" or red "down". There is one light each for the Manager, the Accessor, and the Transporter. The time stamp at the far right of the display ticks away while the system is functioning properly and if not will indicate a very obvious time error.
For more information and detailed explanation of this display, refer to the Cleo documentation at web adress: http://www.gb.nrao.edu/~rmaddale/GBT/CLEOManual/statestatus.html
A user starts up a YGOR program called messageWindow to view the messages. To start messageWindow, you must specify the computer on which the messageMux is running. For example:
sample% messageWindow -h vega
will use the messageMux found on vega. The messageWindow currently being used is a curses program.
In addition to messages being displayed in a messageWindow, the level of the severest messages from a manager is stored in the manager's status parameter. There are six levels of messages and manager status parameters:
Merely provides a means of logging expected events or for debugging purposes.
Examples:
A scan is in progress.
This level reports any unexpected events that are not reported at the more severe levels. This level includes illegal actions by users, therefore, it may not reflect system failures.
Examples:
The user enters an illegal value for a control parameter.
The one pps in the timing center has drifted past a threshold value.
This level provides a description of an unexpected or possible problem-causing event which requires more careful monitoring or investigation by the operator.
Examples:
An attenna surface panel's temperature has an unreasonable reading.
The cryo temperatures have climbed beyond a specified threshold.
The antenna is pointing within a specified distance from the sun.
An event has occurred which requires a specific action by the operator, such as notifying the contact engineer.
Examples:
An off-line receiver is warming up.
A cryo compressor has failed and a spare should be connected.
The A Rack of the Spectral Processor fails to start a scan on time.
This level describes events, which will cause the system to generate bad observational data or prevents the completion of actions.
Examples:
The cryo temperatures of the active receiver have climbed to the point there is little hope of detecting a signal.
The tracking LO has gotten out of sync with the sig/ref signal.
The antenna is more than N beamwidths off the commanded track.
A failure of a digital interface.
The A Rack of the Spectral Processor fails to start.
An LO repeatedly fails to stay in lock.
Description of an unexpected and problem-causing event which the system took some action as a result of, or requires some action by telescope personnel, i.e., equipment or personnel are in danger. An event from which the software cannot recover and must be restarted.
Examples:
The commanded track has driven the telescope into a limit.
The active surface is shutting down because an emergency stop was initiated.
The temperature in a rack of equipment is high enough that the equipment needs to be powered down.
The wind speed is high enough to cause the automatic stowing of the antenna.
Some sub-task of a system has crashed.
An "impossible" software condition occurs, a la assertion.