TELESCOPE OPERATIONS

OPS LOG PROGRAM

General

The Ops Log program is used to record various types of information related to activities occurring during an operator's shift. The types of information include major hardware or software failures, observing projects, the overall progress of astronomical observations and other details determined significant by the operator.

Info

Only one operator can log into Ops Log at a time!

The character " ^ " is used below to emphasize spaces between dialog elements.

Running Ops Log from a PC

STEP	ACTION
1	Select the Citrix ICA Client from the START menu (the Custom ICA Connections window will pop up).
2	From the Custom ICA Connections window, select the GBT Citrix Server; window pops up with a login screen).
3	Login with the gbtops or your normal Windows username/password.
4	Start OpsLog: Double click the Ops Log icon or select if from the START menu. Select the shift to log into. Enter user name and password. The shift selected will now appear.

Running Ops Log from a Unix/Linux machine

STEP	ACTION
1	Open an xterm window and enter wfcmgr& (launches Citrix ICA Client window)
2	From the Citrix ICA Client window, select GBT Citrix Server; a window pops up with a login screen).
4	Login as gbtops or with your normal Windows username/password.
5	Start OpsLog: Double click the Ops Log icon or select if from the START menu. Select the shift to log into. Enter user name and password. The shift selected will now appear.

Closing Ops Log and Logging Off the Citrix Rome Server (PC or Unix/Linux)

STEP	ACTION
1	Exit OpsLog by selecting the exit icon or exit option under the file menu. Ensure any other program running on the Citrix server are closed as well.
2	Select the Log Off option from the START menu to log off the Citrix server.
NOTE	DO NOT just disconnect or exit out of the client window. You must logout properly.
3	Close or exit from the Custom ICA Connections window.

Closing Failures From a Previous Shift

Email Pete if you close any open failure that did not start and end on your current shift. Helps him keep track of prolonged failures that he'll need to reprint a log from.

Tracking Lost Time

Lost time begins when a failure stops observing and does not end until the failure is corrected AND and any other actions needed to get back to observing (re-setup of a device, unstowing the telescope and getting back on source, etc.).

Lost time can only be tracked on one failure at a time.

Comments to Assist Debugging/Isolating Problems

Log error messages from Cleo, Astrid, and the OCT to assist in later analysis of problems.

Depending on the failure, consider logging the AZ/EL position, direction of antenna movement, slewing vs. tracking/guiding, device states, repeated occurrences, etc. If it may help isolate a problems cause, log it.

-- DavidRose - 6 Feb 2008

Topic OpsLogProgram . { Edit | Attach | Ref-By | Printable | Diffs | r1.8 | > | r1.7 | > | r1.6 | More }

Revision r1.8 - 06 Feb 2008 - 20:41 GMT - DavidRose Parents: WebHome > TelescopeOperations	Content copyright © 1999-2007 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.


NRAO Home > Green Bank \| Wiki Topic: GB > Operate > TelescopeOperations > OpsLogProgram

Changes \| Index \| Contents \| Search \| Go