FC charge in the data differs from that in the QADB

[c-dilks]

Some datasets, e.g., RG-A Spring 2018, required additional fixes to the Faraday Cup (FC) charge, which is

• used in the QA procedure to normalize, e.g., the number of trigger electrons
• stored in the QADB, to provide user access to the FC charge per QADB bin, so they can obtain the correct FC charge for the QADB filter they are using

In the case of RG-A Spring 2018, we produced the QADB on data that have been "reheated" using the following prodedure:

1. start with fully cooked data
2. run rebuild-scalers -c X, which corrects clock rollover
3. run postprocess -q 1, which includes the recharge option
4. produce the QADB based on the resulting output

Therefore, if you compare the FC charge that is stored in the QADB with that obtained directly from skim or DST files, you may notice they are different.

Important

The QADB stores what we believe to be the correct charge, please use that in your analysis.

Note

This GitHub issue is for information only, and is linked from the main README.md dataset tables.