Shift Duties

From tigwiki

Jump to: navigation, search

Contents

[edit] General Comments on Duties

  • More information can be found at the TIGRESS Experiment Home page.
  • Shift duties may change throughout the run. Review this page frequently, especially at the beginning of your shift.
    • If you yourself edit this page, make sure you put a sensible description of what you changed in the E-Log and in the Summary at the bottom of the edit page.

[edit] Beginning of Shift

  • Review shift duties, and if there are any changes or new duties you don't understand, ask the previous shift.
  • Read previous shift's E-log.
  • Introduce yourself to the ISAC operator.

[edit] Beginning and Middle of Shift

  • Create an e-log entry noting drifts in zero-degree germanium gains and a snapshot of the Gain Corrected Ge Sum spectrum.
  • On the morning mid-shift, a qualified person should refill the zero-degree detector.

[edit] Half-past Each Hour

  • Record the following data in as an e-log entry:
    • Event rate per second, on MIDAS status page
    • Silicon leakage current.
      • This is the number in the top display of the yellow Mesytec NIM module, downstairs in the Bambino electronics rack.
      • If this is going up faster than 0.050 uA/hour, contact Ching-Yen Wu immediately.
    • Aries Blue Ge Rate.
      • This is recorded in EPICS (e.g. on the striptool) as 8PI:SCLR:VAR13, and in MIDAS as /Equipment/Scaler/MCS2[28].
    • Quadrant and Inner Ring Si Rates.
      • These are recorded as 8PI:SCLR:VAR9 to 13, or /Equipment/Scaler/MCS2[24...28].
    • Counts in 1274, 2225, 2561, 2614, and 1398 keV lines as viewed in Maestro.
  • Record all of the above in the written log book too.
  • Every few times you do this, save the Maestro spectrum as My Documents/tigress/TIGRESS Experiment/xxxx_y.spe, where xxxx is the run number and y is incremented so you don't overwrite any previous ones. Make a note that you saved it.

[edit] Throughout Your Shift

  • On the status page, check that:
  • There are no yellow or red panels -- all green.
    • Note: The Run Status panel (top left) will be RED when the run is stopped.
    • The following Clients are listed in pale purple boxes at the bottom: mhttpd, Analyzer, FeTigCol, Logger, Epics, femcs.
  • Check the Striptool on lynx (the computer next to midtig02). The legend is taped to the monitor. If the light green curve drops and stays low, call the operator as they are unable to see this.
  • Keep an eye on the Maestro session (a VNC session on Lynx). Make sure it's still running.

[edit] If There Are Massive Problems With The Beam

  • NOTE: Massive problem does NOT include short-term sparks, cyclotron trips, etc.
  • Anything that affects beam delivery for less than 15 minutes should just be ignored.
  • Make note of last Si leakage current entry (with beam of course).
  • Ask the operator to put the last Faraday cup in.
  • Wait for operator to say he or she is ready to deliver beam again.
  • Tell the operator to wait for a phone call from downstairs.
  • If you are on shift alone, find an assistant and bring him/her with you; otherwise, both shift experimenters go downstairs.
  • One person calls the control room (7500) ; other person watches leakage current.
  • Ask operator to remove Faraday cup.
  • If leakage current:
    • jumps by more than 0.300 uA
    • jumps to more than 0.100 uA beyond last beam-on leakage current
    • rises steadily by 0.001 uA per second for more than 10 seconds
  • then:
    • ask the operator to put the Faraday cup back in
    • call Ching-Yen Wu for assistance
  • Otherwise, go back upstairs and start a new run to collect data again.

[edit] What to do at the end of a run of Run

  • As soon as you have ended a run and before you start another one:
  • Make an e-log entry of:
    • the just-finished run number
    • why you stopped (loss of beam, shift duties, etc.)
    • start and end time
    • the number of Trigger events
    • whether or not this run was written to disk
    • what the trigger number was (/Equipment/Trigger/settings/Trigger Mode)..
    • if you haven't already done so, all the hourly information
  • NOTE: There is an automatic e-log entry generator that is supposed to be run at the end of each run. Check to see if an elog entry has already been generated for this run. If so, edit it and add any new information as needed. DOUBLE NOTE: Don't necessarily count on the automatic e-logger to run. It is well known that MIDAS's automatic end-of-run functionality is kinda spotty. In particular, it may not make this entry for you when you are running in "automatic restart" mode. (Automatic restart is highly discouraged anyway.)
  • Save the Maestro spectrum as described in the half-past-each-hour session. Clear it. MAKE A NOTE IN THE E-LOG AND IN THE WRITTEN LOG BOOK THAT YOU HAVE DONE THIS.

[edit] If the operator calls requesting readings

  • Find the ODB entry /Equipment/MCS/Common/Period
  • Change it from 100000 (one hundred thousand) to 1000 (one thousand).
  • When the operator is done taking readings, change it back to 100000.

[edit] End of Shift

  • Review any anomolies, beam losses, changes in instructions, etc. with incoming shift.
Personal tools
Experiment Pages