Project

General

Profile

YOUR SHIFT: Important notes for shifters:

You should have a pair of shoes with you because you may need to go underground. Sandals, flip-flops, high heels, etc are not appropriate footwear for underground access.

  • Has it expired? Then renew it immediately.
  • Is it about to expire? Then renew it so it won't lapse.

You should have been here at least 15 minutes early to:

  • Talk to either the previous shift physicist or a crew member and discuss what happened during their shift
  • Note any new problems found or old ones fixed.
  • Inquire whether there were any hardware changes, special activities etc.
  • Inquire if anyone is underground.
  • Ask if there are any requests for special data taking and remind them to release DAQ control before they leave
  • Make sure the Minerva shifters are away of these, and explain what they should do if the problem arises.
  • Wish the previous shifter a safe drive home.

Where to go for help

  • CRATE-MASTER-MINDER-CHANNEL map for ND
CRATE
0 1
2 3
4 5
6 7
MASTER
09 10 11 12
13 14 15 16
17 18 19 20
21 22 23 24
MINDER
0 1 4 5
2 3 6 7
CHANNEL
00 01 02 03
04 05 06 07
08 09 10 11
12 13 14 15

FD CRATE-VARC-VMM-VADC-CHIP map

CRATE

CRATE
0 1 2 3
4 5 6 7
8 9 10 11
12 13 14 15
VARC-VMM
0-5 1-5 2-5
0-4 1-4 2-4
0-3 1-3 2-3
0-2 1-2 2-2
0-1 1-1 2-1
0-0 1-0 2-0
VADC-CHIP
1-0 1-1 1-1
0-0 0-1 0-1

Shifter's ToDo List

  • ensure the highest uptime of both Far and Near detectors
  • diagnose and fix problems quickly and efficiently
  • alert the system experts and work with them in case of problems
  • perform regular inspections of the data taken
  • monitor detector systems and environment conditions
  • Regularly check DAQ, DCS status webpages
  • Spend time looking at the real time events using the event display
  • READ the previous CRL entries entered in the last 24 hours
  • RECORD anything anomalous in the CRL
  • Enter new problems into the JIRA issue tracking system
  • fill out shifter's checklists

Shifter's Checklist Forms

It's important to let the online statistics accumulate, so make sure that the data run has been running for at least two hours before proceeding with the checklist.

  • Start_Shift
  • DCSChecklist_Near
  • DCSChecklist_Far
  • OMCheckListNear
  • OMCheckListFar
  • Beam
  • End_Shift

Please click "Update" or "Latest" (or "Current") on NuMI elog before inserting plots

Job List

  • The 'Big Green button' has been replaced by the A9 Event Monitoring Web page .The top portion should be green and always be up to date, updating once per second. Please restart the page promptly if it gets stuck, and note the time in the ECL.
  • The Far Detector needs to be notified of beam downtime as follows.
    If the beam will be down for long enough from 07:30-17:30, please notify the mine crew.
    • If there is downtime of at least half an hour notify Soudan.
    • If you learn of an all-day shutdown coming in the near future, inform the Run Coordinator and Soudan.
  • Please stop and restart OM Gui at the beginning of your shift, it leaks memory.
  • When filling in the Near Detector OM check-list please make sure that the socket is "open", and that the status canvas gives a current time stamp.
    • When the MINERvA shifter completes their ND OM checklist and shuts down their monitoring window it closes our connection.
  • ( this is obsolete: will be updated asap) The 'Big Green Button' shows file write latency. It flashes orange if this goes over 3 seconds, and turns red if the file is badly out of date. In this case, restart the Beam data logger, as described at BEAMDATA
  • You need to post the Beam Shift Plots using NUMI Elog and Minos CRL sessions on minos-acnet, from the files in /home/minos/BeamPlots . The NFS server which made these available in /misc/mcr/... has been retired,
  • If G:RD1224 comes into alarm at 14:30, this is expected. If the alarm won't clear after 14:45, call MCR and ask them to remove multiwire 112 from the NuMI beamline. An alert box will pop up on minos-om console to remind you.
  • If Firefox starts giving errors, then restart it.
  • Please check the Run Control GUI, DCS status pages, and JAS regularly for warnings. The shifter is the 1st responder to these error conditions and should notice alarms on the time scale of minutes (not hours).
  • If you need to stop/start a run, please always start RH24Hour sequence, unless instructed otherwise. This will take care that all the necessary OM plots are filled.
  • Please watch the LCW output temperature on the ND DCS Magnet Status section. We have had problems with a water filter clogging up, which will take down both the ND and the NuMI absorber if it stopped up. If the temperature gets very high (>75) or increases quickly (so that it will reach 80 F in less than a day) call the Run Coordinator, then John Voirin or Bill Moorhouse. The temperature regulation is set at 67 F.
    • This will also restrict cooling to the NuMI absorber. Please let the NuMI Beam Coordinator (Sam Childress or Peter Lucas) that there is a problem so they can watch that temperature.
  • Due to budget cuts, we are able to access the far detector only during regular hours (weekend days are still ok) except in emergencies, where loss of data doesn't count as an emergency.
  • The Soudan On Call Phone number will not work at night. Instead, call Bill Miller or Jerry Meier, plus the run coordinator (Greg or Chris) and we will figure out if it's a real emergency or if budget cuts will be costing us data.
    • If Bill doesn't answer his cell, try his home number. If he's at home, his land line works and cell coverage doesn't dip down next to the lake.
  • The ND magnet can now be controlled remotely (E:NDMAG on ACNET). This includes changing polarity, turning the power supply on and off, and setting the current (a setting value of 4990 produces a current readback of 4973 amperes). The setting is an unsigned number; the current readback is a negative number. There is a status bit that indicates polarity. For further information see [this link|http://www-numi.fnal.gov/Minos/ControlRoom/nd_magnet.html].
  • Answering the telephone
    • Please let people know where they've called and who you are! E.g.
    • "MINOS Control Room, this is Fred Jones" would suffice.
    • Please try to always answer the telephone in a timely manner. If you need to step out for a few minutes check the caller ID on the phones when you get back. Call back all numbers that went unanswered.
  • Put a note in the logbook when you call experts or the run coordinator, at least the first time in a thread.

Swing and Owl shifts are again being covered by Minerva

The swing and owl shifts are currently being run by the Minerva shifters. Here are the instructions that apply in that situation:

The MINOS shifters should arrive at the control room at the start of their shifts, and should:

  • Deal with any problems they find
  • Go through the checklists with the previous MINOS shifters (except there won't be one)
  • Bring themselves up-to-date on any outstanding issues or problems likely to occur during the shift.

Since there is now no overlap between MINOS shifters, it is vital that regular use is made of the CRL to pass on information, and ensure the following shifter knows the status of the detectors.

The MINOS on-call shifter should make a logbook entry from home any time they are called. They should log:
  • What caused the call to be made
  • What action they took
  • Any action they told the Minerva shifter to take
  • Any phonecalls with MINOS experts they made or received.

Minerva currently doesn't have access to the MINOS CRL. They should use the blue electronic post-it note on the minos-om. They should log in this any interventions with the MINOS systems, or relevant information such as phonecalls with MINOS experts. The MINOS day shifter should transfer this information to the MINOS CRL at the start of their shift.

  • Congratulations you made it this far! Please note in the CRL logbook that you actually read the memopad and know what to do on shift.