Revision as of 17:04, 15 February 2017

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.

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.

[HV instructions for users]

[HV for experts]

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].

Links

Ar(ee'p) DAQ

@@ Line 122: / Line 122: @@
 [[https://hallaweb.jlab.org/wiki/index.php/HV_HowTo_for_Experts HV for experts]]
-<b>Troubleshoot</b>
-<pre>
- If you start HV-GUI but get error "initialization"
-In this case,
->login: a-onl@aonl2
-> ps -ef | grep -i hvs  (make sure you are not Killing HRS HV ~!!)
-> kill -9 PROCESS#
-> cd ~/slowc/
-> .hvs DVCS
-</pre>
-== <b> How to start DVCS ADC readout through EPICS</b> ==
-== IOC iochacs boot parameters==
- boot device          : dc
- unit number          : 0
- processor number     : 0
- host name            : opsfs
- file name            : /cs/op/iocs/iochacs/vx/vxWorks.st
- inet on ethernet (e) : 129.57.242.13:fffffc00
- host inet (h)        : 129.57.236.40
- gateway inet (g)     : 129.57.240.1
- user (u)             : vxwrks
- flags (f)            : 0x80
- target name (tn)     : iochacs
- startup script (s)   : /cs/op/iocs/iochacs/startup
-<pre>
-Login as "opsll.acc.jlab.org" that is accelerator computer. You need an accelerator computer account.
-I have tested thorugh this:
-> ssh -X parkkj@opsll.acc.jlab.org
-> setenv EPICS_CA_ADDR_LIST 129.57.255.11
-> edmRun /a/opsuser/mccops/edm/HALLA/DVCS/dvcsCalorimeter-new.edl
-</pre>
-<b> How to read DVCS Calo HV/Anode current and record Start_Run_Log</b>
-<pre>
-<b>MAKE SURE HV GUI IS RUNNIGN ONLINE</b> because hvcli uses TCP/IP protocol only
-Login as "adaq" on the "adaq1" or "adaq2" computers.
-> /adaqfs/home/adaq/scripts/epicsRunStart
-make sure you call current version of "hv_proc_dvcs.com" in the "epicsRunStart"
-look at the line# 1507, 1510: They should:
-/adaqfs/home/adev/dvcs3/slowc/hv_proc_dvcs.com -D DVCS -c GET -P MV -m 0:12,0:15 >> $epicsfile
-/adaqfs/home/adev/dvcs3/slowc/hv_proc_dvcs.com -D DVCS -c GET -P MC -m 0:12,0:15 >> $epicsfile
-</pre>
-<b> DVCS Calo Anode current Alarm</b>
-<pre>
-For a moment, we have only an alarm related with VME server status (129.57.242.13). If lost connection, there is an audible alarm.
-Reaction:
-(1) ping 129.57.242.13 to make sure it is a connection issue.
-(2) if there is no ping result, you should reboot the VME by remote power-cycle.
-</pre>
-please see the step [https://hallaweb.jlab.org/wiki/index.php/How_to_HRS_/_DVCS#Reboot_calorimeter_HV_crates.2F_Port_Server.2F_VME_ADCs_crate_.2810.2F28.2F2016.29 How-To-Reboot]
-== DVCS Temperature Monitor ==
-We installed the heat sensor (TEMPer1f which Charles bought) inside of DVCS calorimeter dark-box.
- The motivation is to investigate the pedestal oscillation (possibly temperature dependence, air condition run cycle...)
-At lease this allows us to monitor the temperature inside of dark-box
-The sensor installation is shown in the attached figure. (top of calorimeter frame)[[https://logbooks.jlab.org/files/2014/12/3309738/photo.JPG Picture]]
-We used the 33ft x 2 USB extension cables for the connection between sensor and dvcsdaq2 computer(down the hall).
-<pre>
-ssh -X dvcs@dvcsadq2.jlab.org
-cd /home/dvcs/DVCS_Temp/temper/usb-thermometer/
-pcsensor
-dvcs@dvcsdaq2> pcsensor
-/12/01 17:28:43 Temperature 99.61F 37.56C
-</pre>
-** <b> How to install Driver </b>
-<pre>
-(1) make sure you have "libusb-dev"
-how to check ?
-> rpm -qa | grep -i libusb
-libusb1-1.0.9-0.6.rc1.el6.x86_64
-libusb-0.1.12-23.el6.x86_64
-If you don't have it, please
-obtain "libusb-devel-0.1.12-23.el6.x86_64.rpm"
-from " web" or
-ifarm "/lustre/expphy/volatile/clas/claseg3/parkkj/DVCS/DVCS_Temp/temper/"
-(2) install
->su
->rpm -Uvh ibusb-devel-0.1.12-23.el6.x86_64.rpm
-> rpm -qa | grep -i libusb
-libusb-devel-0.1.12-23.el6.x86_64
-libusb1-1.0.9-0.6.rc1.el6.x86_64
-libusb-0.1.12-23.el6.x86_64
-(3) copy directory: "usb-thermometer"
-from
-from " web" or
-ifarm "/lustre/expphy/volatile/clas/claseg3/parkkj/DVCS/DVCS_Temp/temper/"
-(4) cd /home/dvcs/DVCS_Temp/temper/usb-thermometer
-> cp 99-tempsensor.rules /etc/udev/rules.d/
-> make
-> scp pcsensor /usr/local/bin/
-should be working....as long as USB-cable is connected...
-(reboot machine if necessary...)
-</pre>
-** <b>Where is Script</b>
-script is running under on DVCS@DVCSDAQ2.jlab.org
-/home/dvcs/temp/
-cat temp2.log
-(DVCS HV on @17:51)
-** <b>How to Monitor </b>
-<pre>
->> ssh -X a-onl@aonl1
->> cd /adaqfs/home/a-onl/parkkj/temper/
->> ./GetDVCSTempTime.exe  (If password asked (usually NOT but in case), type same as one of adaq1)
->> display tempNow.png  (You can post this figure on HALOG if it needs.)
-</pre>
-* This plot shows the temperature history between -8hrs and Now.
-== DVCS HV alarm ==
-If you hear about DVCS HV alarm (either Red flashing rectangular box on screen .OR. Voice),
-please look at the DVCS HV GUI which is running on aonl2.jlab.org machine then figure out the what the problem is.
 Alarm Detail
@@ Line 291: / Line 165: @@
 or contact to Kijun Park <mailto:parkkj@jlab.org>
-==LED table control==
-The LED driver is located in the DVCS IOC. To access it:
-* open a terminal, and type the command: "telnet iochacs"
-* load the LED control library by typing: "ld < NewLedLib.o"
-Then it is possible to control the led. Few commands:
-* SetFrequency(prescalefactor1,prescalefactor2), to turn off the LED put a large prescale factor SetFrequency(0xffff,0xffff)
-* To switch ON the LED corresponding to a particular block: SetBlock(columnNbr, rowNbr)
-* To scan several blocks of the calo with the LEDs: ScanCalo(MaxColumnNbr, MaxRowNumber, Number)
-* SetDelayTrig(Step)
-* SetDelayLed(Step)
-* To turn the Led Off  LedOff()
-* To turn the Led On  LedOn()
-== Reboot calorimeter HV crates/ Port Server/ VME ADCs crate (10/28/2016)==
-If the DC current are not read out ( ie GUI frozen and time out in the end of run )
-that could mean that the IOC iochacs (129.57.242.13) is down.
-<pre>
-If the DVCS CALO ADC readback is frozen, here is the detailed procedure for IOC reboot:
-. open a terminal on adaq1
-. telnet src2 (username: adaq and password same as for hacweb8)
-. menu option 1- Device Manager
-. menu option 2- Outlet Management
-. menu option 1- Outlet Control/Configuration
-. menu option 10-  DVCS ADC VMECrate  (*Note that now you see correct name on console !)
-. menu option 1- Control Outlet
-. option 3 immediate reboot
-exit: use <ESC>
-</pre>
-Alternative way, You need a hardware reboot by pushing the reset button in the hall
-VME module is in the middle size black rack beside DVCS HV rack.
-You see the "reset" button on the top-front panel of module.
-<pre>
-The IOC is plugged on a remoter control power strip which is using the hostname src2
-The plug assignements are
-hatsv17(port server)
-DVCS Bottom HV
-GEM Test HV
-DVCS ADC VMECrate
-DVCS Top HV
-</pre>
-End CODA run first (see modified instructions in halog 342245 [[http://www.jlab.org/~adaq/halog/html/1012_archive/101201143439.html]])
-Login on the src2 host ( use the username and password for hacweb8 ) and go outlet control and select reboot immediate on the selected plug.
-Here is a detailed procedure in halog 341127 [[http://www.jlab.org/~adaq/halog/html/1011_archive/101121081830.html]]
 == How to reboot iocs and the Ethernet/GPIB converters for the Unser and BCMs ==

Difference between revisions of "Ar(ee'p)"