Open nsjarvis opened 1 day ago
Similar csv files for the other run period REST files are linked below
There's a script to extract a column here , use it like this python extract_col.py monitoring_data_2019-11_verREST1.csv Triggers/random_trig > randoms.csv
Something must have been wrong during the production or copying of this file. The converted random trigger file produced during the REST production is nearly 500x larger:
cat /mss/halld/RunPeriod-2019-11/recon/ver01/converted_random/merged/converted_random_073070.hddm | grep size
size=3349506500
cat /mss/halld/gluex_simulations/random_triggers/recon-2019_11-ver01/run073070_random.hddm | grep size
size=7866066
The random trigger file at /cache/halld/gluex_simulations/random_triggers/recon-2019_11-ver01/run073070_random.hddm contains only 1882 events. Peter confirmed that that's what the MCWrapper database indicates for this run.
One can see even from the monitoring histogram which only sees a fraction of the events that there should be at least 100 x more than this.
According to the monitoring plots made along with the REST production, there should be 670692 random triggers for that run.
It's possible that the random trigger files could be too short for other runs as well. I ran demon over the REST production files to count the randoms in the monitoring histogram. The plots are on this page and the CSV data file is here and also attached: monitoring_data_2019-11_verREST1.csv