<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hello Noémie, Sebastian, Nathan, all,<div class=""><br class=""></div><div class="">I agree with Sebastian that the scaler data can be looked at on a file by file (or even finer grained) level, so you do not have to use the number of files processed. This is also better because you do not know how much of an individual file had beam trips. </div><div class=""><br class=""></div><div class="">An other place where you can be more accurate in your charge calculation is the “duration * run current”. The run current is not a constant over the run, actually it can vary significantly with beam trips etc. I don’t think the RCDB has the properly averaged current, and it also does not take into account the live time of the DAQ. The run scalers, if you used the gated FCUp, do take into account the live time, and take into account the fluctuations in the beam current on time scale of the struck scalers. </div><div class="">If you would like to do a better comparison to the struck scalers, you can take the data from MYA, and use the measurement by measurement beam current and multiply this by the same for the live time. This is done to compute the charge as reported on the graph: <a href="https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge.html" class="">https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge.html</a> I attach a spreadsheet with the same data in tabular form for each run. Charge, sum_charge, and sum_charge_target are in mC. The calculation done in this code is found in the file RGC2022.py in <a href="https://github.com/mholtrop/RunData" class="">https://github.com/mholtrop/RunData</a>. This calculation has been verified by Rafo for the RGA data, where he found generally good agreement with the results from offline reconstruction, though there are still some discrepancies were are trying to iron out. The reconstructed data for RGA had some difficulties because not all the information had gone into the data stream quite as it should.</div><div class=""><br class=""></div><div class="">I hope this helps.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Maurik</div><div class=""><br class=""></div><div class=""> </div><div class=""></div></body></html>