You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some DST files, we find that evnumMax of DST file N is larger than evnumMin of DST file N+1 (more correctly, of N+5, since these are 5-files). Thus the boundary between files N and N+1 becomes blurred: events in the "overlap" of DST files will be associated to two DST files, since QADB finds the DST file by checking event number ranges. In practice:
QADB queries by (runnum,evnum) will return the first matching DST file that contains the event
Accumulated charge calculation may be slightly overestimated for runs that have such files
To determine which runs and DSTs have this issue, use util/syncCheck.groovy:
source env.sh
run-groovy util/syncCheck.groovy # prints all the overlap info
run-groovy util/syncCheck.groovy | grep 'SYNC ERROR' | cut -d= -f2 | sort -n | uniq -c
The third command prints two columns, shown in the list below: the number of problematic DST files, together with the run number.
In some cases, only one run has an issue; sometimes the difference evnumMax - evnumMin in a DST file is very large, causing that DST file to be associated to all events of a run. In other cases, the entire run has overlapping DST files.
It is not clear how to fix this issue from the QADB side. A possible upstream solution is to ensure during cooking that the events do not get "mixed" between DST files.
Note: util/printSummary.cpp marks some DST files as Golden, but they do not appear in text/listOfGoldenFiles.txt. This is likely related to this issue. The runs and filenums are:
Newer QAs have been using time bins, which do not have this issue. We will not be going back and fixing old Pass 1 QAs for run groups A, B, or K, since their Pass 2 QAs will be done with time bins.
For some DST files, we find that
evnumMax
of DST fileN
is larger thanevnumMin
of DST fileN+1
(more correctly, ofN+5
, since these are 5-files). Thus the boundary between filesN
andN+1
becomes blurred: events in the "overlap" of DST files will be associated to two DST files, since QADB finds the DST file by checking event number ranges. In practice:(runnum,evnum)
will return the first matching DST file that contains the eventTo determine which runs and DSTs have this issue, use
util/syncCheck.groovy
:The third command prints two columns, shown in the list below: the number of problematic DST files, together with the run number.
In some cases, only one run has an issue; sometimes the difference
evnumMax - evnumMin
in a DST file is very large, causing that DST file to be associated to all events of a run. In other cases, the entire run has overlapping DST files.It is not clear how to fix this issue from the QADB side. A possible upstream solution is to ensure during cooking that the events do not get "mixed" between DST files.
The text was updated successfully, but these errors were encountered: