NPS Online analysis (Fall 2023)

If you have any questions or comments, please email - Zheng Huang zhuang@jlab.org, or call cell # on whiteboard

• We would like the detector check replay to be done on first 50,000 events of every run, and compare plots with the standard ones in the binder (coming up). In addition, we want physics replay to be done on every run in its entirety.
• Do not start the full analysis until after the run ends!
• The standard.kinematics file should update automatically. If you notice a dramatic change in plots, the background process may have terminated. See the appropriate section below.

• Shift leaders are asked to keep a running total of the number of e- events; This will help us better estimate when to move to the next setting.

ANALYSIS of coincidence (NPS+HMS) runs (this is the standard setting)

• ssh to cdaql1 or cdaql2 as cdaq user
• go_analysis_nps
• ./run_nps_hms_coin.sh 718 50000 (to replay the first 50k event in run 718)' <- this is what you do for the standard configuration 50k online replay'
• ./run_hms_coin.sh 718 -1 (to replay all the events in the run) <- this is what you should use if only the HMS data is needed, 10x replay speed
• ./run_hms_coin.sh 718 50000 (to replay the first 50k in run 718 but only the HMS part of these data)

• Note you can do any # of events, for numbers other than 50000, the root files will be saved under the Production folder.
• Inputs:
  • COIN coda file : nps_coin_run#.dat.0
  • HMS standalone coda file: hms_all_run#.dat.0
• Outputs (For COIN script ./run_nps_hms_coin.sh)
  • ROOTfiles: ./ROOTFiles/COIN/*
  • OnlineGUI PDFs: ./HISTOGRAMS/COIN/PDF/*
  • HCANA report output: ./REPORT_OUTPUT/COIN/*
  • Terminal messages: ./REPORT_OUTPUT/COIN/replayreport/*
• Outputs (For HMS coin script ./run_hms_coin.sh)
  • ROOTfiles: ./ROOTFiles/HMS/hms50k/*
  • OnlineGUI PDFs: ./HISTOGRAMS/HMS/PDF/*
  • HCANA report output: ./REPORT_OUTPUT/HMS/ for the cut summary, ./REPORT_OUTPUT/HMS/hms50k/ for the replay summary*
  • Terminal messages: ./REPORT_OUTPUT/HMS/REPORT_OUTPUT/*

• New Fast split analysis
  • ssh cdaq@cdaql1 if you are not logged in already
  • do : go_analysis
  • do : cd ../replay_scripts
  • launch : ./run_gen.sh [run number] [number of events in k events] 72000 [number of events per job]
  • example : ./run_gen.sh [run number] [number of events in k events] 72000 1000
  • avoid submitting more than 40 jobs at a time, increase the last parameters if there are too many jobs

• ./run_hms.sh 718 50000 (to replay a run taken with the HMS single daq) <- highly NOT RECOMMENDED, only use when run plan asked for HMS standalone DAQ

ANALYSIS of the NPS standalone runs

• ssh to cdaql1 or cdaql2.
• ./hcana
• .x SCRIPTS/NPS/eel108_replay.C(718,50000)

Information for runsheets(From old archive, need to be changed)

• Tracking efficiency: will appear in emacs window after 50k: "E SING SING FID EFF"
• Computer live time: will appear in emacs window after 50k: "Pre-scaled PsX HMS/SHMS Computer Live Time", where X is the trigger leg enabled for that run (1,2, or 3).

• • Use the good electron fraction ("good electrons"/50,000) to estimate the total number of good electrons for a given run using the total number of events in that run.

• If you forget to write down the total number CODA events (needed to extrapolate the total number of events) you can find it in the end of run logbook entries ("Event number")
• The tracking efficiency and computer live time can also be found in MON_OUTPUT/HMS/REPORT/summary_output_xxxx.txt (or the equivalent SHMS directory)

Automated script that writes to database (coming up shortly)

• This script should always be running, and is typically seen running on the 2nd desktop of the SHMS DAQ.
• To run, ssh to cdaql1 or cdaql2, type go_analysis and then launch_runinfod
• This script will need to be restarted any time the cdaql6 machine is power-cycled.

To add the previous run when a run has already started

caput hcSHMSRunInProgress 0 followed by caput hcSHMSRunInProgress 1

Repeat for the HMS if needed.

Carbon Hole Runs

• See the instructions on the beam checkout page
• Broad instructions are included below
• Adjust the prescale settings accordingly, set a target rate of ~1kHz for the HMS 3/4 triggers (PS3)
  • The rates you'll see will depend heavily upon setting, the step above is just to get reasonable rates to disc
• Once the prescale values are set, start a run
• When you have 50-100k events, run a HMS 50k
  • Check the HMS Fast Raster page of the output plots, check the hole position. If it looks off, ask MCC to adjust the position.
  • You will need to stop and start a new run when they adjust the position
  • This may take some trial and error to correctly centre the beam
  • You can also try running more than 50k events in the replay if needed (see above)
  • More information is located here

Debugging - General

If any of the plots look odd/not as described:

• The standard.kinematics file should update automatically, but you can double-check that standard.kinematics has been updated and is CORRECT.
• Watch out for silly typos, e.g. gbeam rather than gpbeam.
• Note that standard.kinematics affects things you think it really shouldn't! If things look wrong this is absolutely the first thing you should check.
• Make sure you have the correct particles going into each spectrometer

You should not -

• Panic
• Start editing scripts and deleting things without knowing what you are adjusting
• Delete ANYTHING in the scripts without also leaving a comment explaining what you have deleted or changed

If you cannot run the replay and see things about not being able to get gpbeam, for example, you might need to restart the script that writes to the database.

• See instructions above for running the launch_runinfod script.