"Per run" data for all runs are integrated in the
To have a hint what scalers entries (names) mean you may look into some scaler page file, e.g.
/usr/products/trigger/scaler/*.pgIt is seen there that beam=S_log_8 (output #8 of S_logic) and gbeam=T0srs_8 (gated beam was output #8 of SRS control logic). Names S_log_8 and T0srs_8 are scalers names, same as ntuple entries. We used in the trigger definition
Beam = S_log_8 = s1*s2*s3*~v1*~v2*~v3 gbeam = T0srs_8 = s1*s2*s3*~v1*~v2*~v3 * ~BUSYTry the following procedure:
PAW++  cuts $1 10876<=run<=11313 * -- select runs range PAW++  cuts $2 mod(int(type),10)==1 * -- trigger type "Interaction" PAW++  cuts $3 type>1000 * -- Filter ON PAW++  nt/pl 102.t0srs_8%run $1.and.$2.and.$3 * -- plot gated beam for conditions * above PAW++  h/pri 1000000 s =====> ID = 1000000 T0SRS_8 ENTRIES = 173 ALL CHANN = 173.0000 MEAN VALUE =0.3525434E+09 R . M . S =0.2526585E+09Total gbeam = 0.352543*173=60.989939e+9 = 6.10e10
Check the shape of the distribution, sometimes scalers get overflow and it's need make cut like
nt/pl 101.t0srs_8 $1.and.1e6<t0srs_8<1e7 * -- spill scalers may have overflowKeep in mind that this is number of events taken, hope this is the same number as the amount of data processed.