Results of Analysis of Offline Monitoring 2018-08

Comments on Launches for Run Period 2018-08

Version Date Comments
01 2018-09-25 Incoming data launch.
02 2018-10-03 7 full runs (50728,50729,50737,50738,50740,50741,50742) for estimation of beam polarization
03 2018-10-15 5 files per run
04 2018-10-18 rho polarization: 51030,51032 (17mum, bad coherent edge), 51038,51039 (47mum, same beam tune), 51046, 51048 (47mum, beam retune)
05 2018-11-02 Test for low-energy running, runs 51229, 51230, 51231 and 51228 for reference
06 2018-11-08 First cycle of low-energy running (51384 - 51392)
07 2018-11-12 Full data set of low-energy running (51384 - 51457)
08 2018-12-01 First 5 files of all run with RCDB query "@is_2018production and status!=0"
09 2018-12-07 Test of runs recorded with cDAQ, processed only 100k events per file due to decoding error in last event
10 2019-01-22 First 5 files of all run with RCDB query "@is_2018production and status!=0"
11 2019-02-14 Test of runs recorded with cDAQ
12 2019-03-21 First 5 files of all run with RCDB query "@is_2018production and status!=0"
13 2019-05-06 First 2 files of all run with RCDB query "@is_2018production and @status_approved"
14 2019-06-17 First 5 files of all run with RCDB query "@is_2018production and @status_approved"
15 2019-07-03 Same 5 files produced with version_4.1.1.xml (2018-01 REST ver02)
16 2019-10-25 Intensity scan runs with halld_recon tag recon-2018_08-ver02: 51643-51682, 51688-51721 (various)
17 2019-12-17 Empty target runs with halld_recon tag recon-2018_08-ver02: 50766, 51011, 51012, 51013, 51556
18 2021-03-17 Empty target runs with version_4.24.0.xml: 50766, 51011, 51012, 51013, 51556
19 2021-03-30 Empty target runs with version_4.24.0.xml: 50766, 51011, 51012, 51013, 51556
20 2021-04-27 Empty target runs with version_4.24.0.xml: 50766, 51011, 51012, 51013, 51556

Plots of Individual Launches for Run Period 2018-08: