, view all tags

Shift Duties - MuSun Run 3 DRAFT


The primary responsibility of the shift crew is to maintain safe experimental conditions and take efficient and high quality data.
The shift crew can leave the experimental barrack temporarily.

Main routine tasks:

  • Familiarize yourself with the manuals.
    The latest version is maintained in electronic form (user musun, standard musun password) . Caution, not all parts are updated. The old MuCap pdf manual is posted here.
  • Read the recent elogs and the ShiftCheckList_Run3.xls on zurban.
  • Follow measurement plan (verbal, white board or from log book)
  • Make sure that DAQ is running. This is monitored on the MidasWebpage .
  • Make sure that when runs are manually started, all the information on the info page is correctly updated.

Main monitoring tasks:

In addition to the MIDAS status page you should monitor the experimental equipment.You must do more than look at every item listed here throughout the shift. Read the numbers and think about them. Do the graphs and values make sense? We keep the checklist so you have a reference for what the numbers should be. If you don't know what a number should be or what a plot should look like, ask someone!

  • Monitor cryo TPC and CHUPS, it is essential for the safe operation of the experiment. Instructions
  • observe online display (section 2.2 in Manual).
  • observe trend plots. Rates, kicker extinction, exp. fits, DAQ lifetime are good indicators of stability vs. troubles.
  • check HV and currents of chambers [zurban desktop:1]
  • observe VisualScalers
  • observe separator HV, [zurban desktop: 3].
  • make sure that the alarm monitor is running, get help if it is not.
  • Once per shift fill out the checklist on zurban:/home/l_data/Desktop/Checklists, see desktop:5 on zurban
  • Shift Report : Each shift should have a log with notes about what happened during the shift. Significant changes or happenings should get their own elog entry. For an example, see elog:run3/575
  • The RunDatabase is on dolphin. By clicking on the run number a specific run can be edited.
    • Flag the run quality as 'N' if there is reason to believe the run is bad.
    • Add any special short comment in the comment box.
  • The wire chamber gas flow is monitored as part of the check list. There must always be pressure in the ePC gas bottle to guarantee gas flow and safe ePC operating conditions.

Usual procedures:

  • Setting changing beam polarity
    • General instructions are in section 5.7 of Manual.
    • For up-to-date instructions search the elog. As of 11/6/2010 the latest is elog:596
  • Moving chambers:
    • Turn off HV, coordinate with chamber experts
  • Area access (Michael)

Usual trouble procedures:

  • DAQ troubles (see section 4 of Manual).If it get's too serious call Volodya (4917).
  • Beam troubles
    • see section 3.4.20 of Manual.
    • Recently, SEP was unstable, readjust by hand (elog:626)
  • ePC troubles
    • in case of major issues and ramping call Michael, Peter (see elog:1 for tel)
    • conc wire masking see section 5.10.41 in Manual.
  • Other troubles
    • Often a search in the run elog might find a similar situation with advice.

Emergency procedures ( PeterW please check).

  • Cryo or Chups alarm or serious disturbance: call Marat 4667, 4930, +7-921-326-60-40.
  • Chamber or hydrogen gas alarm
    • Procedure: Call Marat, Michael (4924) and/or Peter (4998)
    • Turn off all chambers in electronic barrack (switch off).
    • Turn off main TPC HV.
    • Check wire chamber bubbler. If bubbling stopped, turn off ePC gas bottle. Turn main bottle valve clockwise to close.
  • Alarm interlock system
Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r8 - 2010-11-09 - PeterKammel
  • Edit
  • Attach
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback