Navigator Shifter Overview

The navigator shifter has three main duties:
To improve data quality by getting problems attended to as soon as they crop up.
To flag data of questionable quality for offline consideration, and
To help out the rest of the shift crew. Here is a checklist of activities which should be done:

Before your first shift:

1. Go to IR2 and get a feel for data-taking operations:
   1. Understand where the navigator and pilot shifters sit.
   2. Understand the various screens and monitors - most importantly, the DQM screens and run monitor.
   3. Understand how data-taking works. Understand the concept of a run, and the concept of injections/fills.
   4. Understand how to answer the phone, and telalert/page experts
   5. Look at the electronic logbook and learn how to perform the QA for each run.
2. Understand the Live Fast Monitoring system:
   1. Understand what the LiveFastMon script does. Learn how to start LiveFastMon and cleanup LiveFastMon.
   2. Understand what the IR2LiveL3 server/histograms are.
   3. Understand where the reference server/histograms come from.
   4. Understand how to start JAS and cleanup JAS and how it interacts with the histograms servers listed above.
   5. Understand the histograms and content in the JAS pages.
   6. Understand automated monitoring.
   7. Understand what to do in the event of problems with Live Fast Monitoring.
   8. Look over the troubleshooting section.

Before every shift:

1. Talk to the previous navigator shifter - see if there are detector problems or Live Fast Monitoring problems.
2. Look at the logbook entries for the previous shift to see what problems might have occurred during the previous shift.
3. Read the short-term navigator instructions for information and insight into current and potential problems.

At the start of your shift:

1. If the run continues from the previous shift, you must also still continue to perform the QA for that run, even though it appears in the logbook for the previous shift.
2. Check to see that JAS is running. If not, follow the instructions and to cleanup JAS (just in case), then restart JAS.
3. Check to see that the LiveFastMon-ref and IR2LiveL3-ref folders are available in JAS. If not, restart the reference servers.
4. If data-taking is in progress, check to see that the LiveFastMon script is running and that the LiveFastMon folder is available in JAS. If not, start LiveFastMon.

During your shift:

1. Talk to your pilot shifter/look at the run monitor and be aware of BaBar/DAQ status. Be aware of running conditions - full detector, cosmics, etc.
2. VERY IMPORTANT! Start LiveFastMon when a run starts, and cleanup LiveFastMon when a run ends. Check all JAS pages and histograms at least once during each run. (recommanded twice, once at the beginning of run, once near the end of run)
3. Make sure that IR2LiveL3 folder is available in JAS if DAQ is at or past CONFIGURED state. Immediately alert pilot shifter if this is not the case.
4. Use the histograms in the JAS pages to spot detector problems. If there are problems, talk to the pilot shifter and make a decision about whom to contact.
5. Check to see that automated monitoring is running in the CMLOG browser, by checking to see that the time of the messages is current. The explanations of the messages are in the subsystem automated monitoring pages in JAS. Use automated monitoring messages to supplement your monitoring.
6. If you lose histograms during a particular run, for some reason and need to go back to the histograms of the prebvious run, click on button PRIOR RUN. You can come back to the original JAS page by resfreshing the page.
7. Perform the QA in the electronic logbook for each run of your shift. If data is not OK, give reasons why. Also, a subsystem (check their JAS data quality flag page) might ask you to write comments for minor flaws, even though the data is OK.
8. The Global Flag will be set from the least selection of the Subsystem Flags. e.g; If one of the Subsystem Flag is set Flawed and the rest of the Subsystem Flags are set OK, The Global Flag is set to be Flawed and so on.
9. Make sure you do the checklist (gas hut, DIRC water system, etc.) once during your shift.
10. Check the OPR physics plots page and mark the quality of several runs. Send email to Eugenio Paoloni if plots look suspicious.
11. Reset the reference server if someone asks you to (if there is a new reference HBOOK file).
12. Cleanup JAS and then restart JAS if it crashes or appears to slow down significantly.
13. Send email to Saleem and/or the appropriate expert if there are any questions about any JAS pages or automated monitoring. For example - does a reference histogram need to be updated? Is the wording in a particular JAS page unclear? Use the Hypernews Shifter Chat Forum as a possible alternative.

At end of your shift:

1. Tell the next navigator shifter about any problems.