...
Once the connection between client and server is made, another GUI pops up that shows the various kinds of logbooks that can be accessed. For the beam test, the one that will be used most often is the shift logbook. There is a button in the upper right hand corner labeled "Access Shift" that allows you to go to the shift of your choice. By default it goes to the current shift in progress. You can also peruse existing shifts or create future shifts (e.g. to populate the Summary/plan section). After clicking on this button, you can hide the logbook selector GUI.
The Summary/Plan window
The The Access Shift button brings up another GUI containing the shift log interface. The Shift Summary/Plan window is used to describe the general shift instructions, goal and plan. It can be modified as many times as necessary. If the goal/plan changes during the course of the shift, this section should be updated.
The Shift Log Sections
The Shift Activies section allows you to enter your activities as you go along with taking data, etc. There is a selector that lets you choose in which kind of log book you want to enter your activities. By default, it comes up with Main logbook. For the beam test, the convention is to enter all shift notes into the Main logbook.
Each logbook has three tabs that are labeled Activities, Problems and Other. Most entries should be entered in the Activities tab. If you want to call out special attention to a problem or other issue, you can use the other two tabs. Note that the tab is easily inadvertantly left in the wrong state, thus causing activies you might want to appear in the log in time order to appear in another section. So always be sure that the Activities tab is selected before you start entering an activity.
What to enter
During I&T, we found that it is beneficial to make a log entry every time you start a run and another one every time a run completes. Note the run number in both cases and any peculiarities that may have shown up during the run. Also note any other activities like the trigger logic being changed in the NIM bins, that a computer rebooted, that you reset the VME crate, accesses to the cave, beam conditions, communications from (S)PS controls, unusual, or outside of your experience, behaviour (both hardware and software) of any part of the system, etc., etc. When in doubt, log it.