Difference between revisions of "Instructions for monitoring and analysis during shift"

From HallCWiki
Jump to navigationJump to search
m
Line 41: Line 41:
 
     <target> = h, c, or d for hydrogen, carbon, or dummy
 
     <target> = h, c, or d for hydrogen, carbon, or dummy
  
     This will update a database (SCRIPTS/COIN/MONITOR/coin_monitor.root) that keeps track of
+
     This will update a database (ROOTfiles/coin_monitor.root) that keeps track of
 
     PS6 live time, yield, PID&tracking efficiency, and 3/4 trigger efficiency for each run.
 
     PS6 live time, yield, PID&tracking efficiency, and 3/4 trigger efficiency for each run.
 
     Plots of these quantities will pop up, and you should make sure that they have not fluctuated.
 
     Plots of these quantities will pop up, and you should make sure that they have not fluctuated.

Revision as of 17:43, 6 February 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] and on the whiteboard
 Compare with golden histograms found at : 
 [CT analysis page]
e. Run the script
  ./run_coin_monitor.sh <run_number> <target>
   <target> = h, c, or d for hydrogen, carbon, or dummy
   This will update a database (ROOTfiles/coin_monitor.root) that keeps track of
   PS6 live time, yield, PID&tracking efficiency, and 3/4 trigger efficiency for each run.
   Plots of these quantities will pop up, and you should make sure that they have not fluctuated.
   You can press the up arrow and changes the arguments of 'coin_monitor_graph.C(runMin,runMax)'
   if you want to see a different range of runs. For example:
   .x SCRIPTS/COIN/MONITOR/coin_monitor_graph.C(2040, 2070)