Ar(ee'p)
Contents
- 1 General
- 2 Analysis
- 3 DAQ
- 4 How to taking Data
- 5 Online GUI
- 6 Shift Workers
- 7 Your Responsibilities
- 8 Beam Recovery Procedure
- 9 Slow control
- 10 Miscellaneous
General
Analysis
DAQ
How to taking Data
Start Coda
- How to run DAQ
- From a terminal login as "adaq2" machine (do "ssh adaq@adaq2" without the quotes)
- Password is available on the white board
- After login to adaq2, type "startcoda" to bring up the runcontrol GUI
- The default configuration is "coincidence", if it is not loaded you can choose it from the menu "configurations->Cool", select "coincidence"
- Click "Platform->connect"
- Click on "Download" button
- Click on "Start (>>)" button, and acknowledge "start-of-run" pop-up window
- To end a run click on "End" button
- How to kill coda processes
- At the terminal of adaq2, type "kcoda"
- How to setup the Prescale
- We just use PrescaleR for Ar experiment.
login as "adaq" on "adaq2" machine type "prescaleR &" to open the GUI set desired prescale factors and click "Save" and Exit
Replay data
- From a terminal login as aonl machine ( do "ssh a-onl" without the quotes)
- Password is available on the white board
- After login to a-onl, type gotritium, then Type
analyzer .x replay_coinc.C runnumber (You can see the run number from CODA GUI)
Online GUI
(Last updated: February 15th 2017)
Once the run has been replayed (see instructions above), login to aonl1, aonl2, aonl3, or aonl4 as user a-onl (password on the white board) and do
$ gotritium [] onlineLHRS [] onlineRHRS
The output files are stored under adaq1/data1/Ar40_[run number].root
Shift Workers
Counting house: 5501 & 5507 | Run coordinator: 876-1787 | MCC: 7046 & 7047 & 7048 | Crew chief: 7045 | Guard house: 8522
Your Responsibilities
Before the start of your shift: read, understand and sign the safety documentation of the experiments.
Shift Leader
- Communicate clearly and effectively with shift crews and MCC (7047), and log any status information to the HALOG
- Keep track of beam time accounting
- Consult the daily run plans and communicate with [ run coordinator] whenever problems happen that cannot be solved by shift workers.
- Maintain data taking quality and an efficient use of beam time.
- Follow the directives in the COO
- Log the following in a shift summary in the HALOG:
- run list (describing the goal of this run: eg production on LH2, BMC calibration...) and report main statistic numbers
- any major events, including accesses
Target Operator
- Watch the target, see [Target Info]
- Assist the shift leader and third person with their duties
Third person
- Start and stop the DAQ. Record the purpose for every single run in the "Run list" binders. Read this to create more blank forms.
- Online replay of all production runs (twice), as described in [online data analysis instructions]. First replay the first 50 k events, check online plots (see next bullet), then run a full replay.
- Compare replay histograms with the sample ones and report to shift leader any unexplained differences. Halog them.
- Fill shift checklist once per shift (for guidance, please see the checklist how-to), go here to find blank copies of the shift check list and the shift check list how to
- The shift leader or TO can help.
Beam Recovery Procedure
Update: October 24, 2010.
- Empty target, establish correct beam position</li>
- 5 uA empty target
- BPM4A (X,Y) = ( 0.0, 0.0) mm
- BPM4B (X,Y) = ( 0.0, 0.0) mm
- See white board for updates on these.
- Tolerances on these : +/- 0.3 mm
- In standard configuration we run without the raster (ok on cryotarget if beam current is less than 5uA)
- Put in BeO target, for visual check of spot (if camera still works)
- 10 uA rastered beam on BeO.
Slow control
How to bring up HAC control window (Hall A Tools), Monticello and JTabs
We like to run this display on is hacsbc2. The monitor is located in the Hall A Counting House in rack CH01A02, just below the NMR dipole oscilloscopes. Click here to see the screen.
If the display is not here: log onto the a-onl or the adaq accounts:
- Hall A Tools: 'hlamain'
- JTabs: 'jtabs'
- Monticello" 'monticello'
JTabs is the newest version of the accelerator tools (it replaces monticello) and has some overlap witht he old EDM monticello and hlamain GUIs. It is most likely to be up to date and working, but maybe missing some items from the EDM tools. [Original halog with nice pictures
High Voltage controls (updated: 03/15, K.Park)
LHRS/RHRS : High Voltage controls
Login as "adev" on the "adaql1" or "adaql2" computers. (since I have added voice alarm for LEFT, RIGHT HRS and Compton HV, please note that command is different !)
cd ~adev/slowc
To run the Left HRS alone: ./hvsL LEFT
To run the Right HRS alone: ./hvsR RIGHT
To run the beamline (Compton) crate: ./hvsC BEAMLINE
The following instructions can be used for running the GUI using the vnc server How to open high voltage GUI. This is not how we want to run routinely.
Alarm Detail hapc3.jlab.org (which has HV GUI screen here !, username:adaq, passwd: same as adaq1)
/home/adaq/beep/ -> DVCS_HV_alarm.wav (updated K.Park Feb.08,2016)
adaq1.jlab.org (username:adaq, passwd: same as adaq1)
~/slowc/hvg.bob/hvtools -. VoiceAlarm.java (edit line5) "ssh adaq@hapc3 /usr/bin/play /adaqfs/home/adaq/beep/call_alarm1" (DVCS_HV_Alarm.wav) cd .. havac hvtools/VoiceAlarm.java
- more detail look <a href="https://logbooks.jlab.org/entry/3309179">Elog:3309179</a>
HRS HV alarm
If you hear about Left/Right HV alarm (either Red flashing rectangular box on screen .OR. Voice), please look at either LeftHRS or RightHRS HV GUI which are running on "adev" on the "adaql1" or "adaql2"
- make sure "beepServer" is running on hapc3...If you are not sure run "/home/adaq/beep/start_beepserver"
Alarm Detail hapc3.jlab.org (which has HV GUI screen here !, username:adaq, passwd: same as adaq1)
/home/adaq/beep/ -> LeftHRS_HV_Alarm.wav
adev@adaq1.jlab.org (username:adaq, passwd: NOT same as adaq1: gev instead daq)
/adaqfs/home/adev/slowc/hvg.newAug2014/hvtools -. VoiceAlarm.java "ssh adaq@hapc3 /usr/bin/play /home/adaq/beep/call_alarm3" ==Links to more HV help== These two links provide some <b>old</b> but useful information. <pre> http://hallaweb.jlab.org/equipment/daq/HVhelp.html http://hallaweb.jlab.org/equipment/daq/gen_slow_control.html
For experts
https://hallaweb.jlab.org/wiki/index.php/HV_HowTo_for_Experts
or contact to Kijun Park <mailto:parkkj@jlab.org>
How to reboot iocs and the Ethernet/GPIB converters for the Unser and BCMs
See the link: https://devweb.acc.jlab.org/twiki/bin/view/SWDocs/OnCallSoftIocControlSystem
Low Pressure and Gas Shed Air Flow Alarm
Read [this].
Miscellaneous
Starting HALOG
- For the standalone halog utility: 'ssh adaq@adaqX' ; 'halog'. This will submitt to the new logbook.
- Enter text in the large message area, your name in the User area, and a title in the Subject field. Remember that experiments tend to suffer from too little documentation, not too much. Also, halog entries allow people to remotely check on the experiment progress without bothering you with phone calls. When complete, after pressing the "Make Entry" button, the text in the message center at the top of the window should read 'Entry was saved with lognumber <XXXX>', otherwise something is wrong. It may take a minute or two for the entry to show up in the logbook.
- Making a screen snapshot: Click 'Add Attachment' in the bottom button row of the halog window. The halog window will disappear, and the window the cursor is in will become the active window, its outline flashing. By moving the cursor you can select any window to be selected, by clicking on the left mouse button. You also can select an arbitrary part of the screen by holding down the left mouse button and dragging the cursor along. All the time a rectangle will flash that indicates the selected area. Releasing the mouse button will then cause this screen area to be included into the entry. It will show up as a thumbnail picture in the halog window, where you can discard it or accept it, and then make a second screen grab.
How to bring up the Alarm Handler
From the "toolbox" icon in the taskbar, press the "Alarm Handler" label. Alarms are indicated by a beep and the alarm handler button flashing. The color red indicates values far out of range, while the color white indicates a communication failure. Clicking on the alarm handler button will bring up an alarm handler list. A detailed list is given in the left panel, and clicking on items here brings up a more detailed list in the right panel. The alarm can be acknowledged and silenced by clicking on the button beside the alarm indicator. [This Halog entry] has some more info about the alarm settings. If the alarm is up but there is no sound, check [this halog entry].