Difference between revisions of "Instructions for monitoring and analysis during shift"
From HallCWiki
Jump to navigationJump to searchLine 29: | Line 29: | ||
<target> = h or c | <target> = h or c | ||
− | This will spit out the Number of Good events in the Run | + | This will spit out the Number of Good events in the Run and two pages of histograms |
Update the counts in the file [https://docs.google.com/spreadsheets/d/1iAb4nu7ph_Da_ewDQV-ycxMtoWpcT3ENutVMsJMPf3c/edit#gid=0 [on Google docs]] | Update the counts in the file [https://docs.google.com/spreadsheets/d/1iAb4nu7ph_Da_ewDQV-ycxMtoWpcT3ENutVMsJMPf3c/edit#gid=0 [on Google docs]] |
Revision as of 16:17, 23 January 2018
Instructions for CT Experiment (E12-06-107)
1. Keep an eye on the Hall C Scaler Data GUI and make sure the rates with beam ON are steady
2. In the middle of the run
for SHMS detector check: ./run_coin_shms.sh <run_number>
for HMS detector check: ./run_coin_hms.sh <run_number>
3. After full run Check the Good events and Update the file on Google docs(
a. Login to cdaql1 machine
b. Update the file " standard.Kinematics " : usually opened in HIGH VOLTAGE Monitor (HCDESK 2 ) path : /net/cdaqfs/home/cdaq/hallc-online/hallc_replay/DBASE/COIN/STD/standard.kinematics
c. Analyze the run with :
./hcana -q "SCRIPTS/COIN/PRODUCTION/replay_production_coin_hElec_pProt.C(<run number>,-1)"
d. Run the script ./run_beancounter.sh <run_number> <target> <target> = h or c
This will spit out the Number of Good events in the Run and two pages of histograms
Update the counts in the file [on Google docs]
Compare with golden histograms found at : [CT analysis page]