Welcome to g2 group home!
Cooking is over !
Total number of files cooked is 2328. August
part (electron beam energy 2.478 GeV) has 1669
files.
September part (electron beam energy 3.115 GeV) has 659
files.
Follow links below to see details:
Some explanations for those tables.
First column is file status as follows:Now some general comments.
means this file is "good" for the analysis until someone tells otherwise.
means this file should NOT be used in the analysis. They are highlighted also.
Next five columns show presence of the files on the silo:
"01" status of the cooked files:
"+ " means there is only one cooked file runXXXXX_cooked.AYY.00 present
"++" means there is extension file runXXXXX_cooked.AYY.01 also present
"N" SEB Ntuple is present
"D" Deuteron skim file is present
"K" Kaon skim file is present
"P" photo disintegration skim file is present
The rest is obvious.
We considered run as a "good" run if the normalyzed proton yiled per photon per T-counter was stable and consistent with the other runs and other T-counters.
T-counter T55 was not stable during entire August part of the run.
T-counter T53 was not stable during entire September part of the run.
They should be removed from the analysis.
T-counters T33,34 have lower trigger efficiency. They could be recovered via cross normalization between 2.478 and 3.115 GeV.
Runs 20296-20298 had R2S1 drift chambers off. Otherwise they are good
and could be used for the analysis
keeping in mind that acceptance is about 5/6 compared to the rest of
the runs.
Main part of the cooking was finished on March
16. After that I've recooked some of the files.
As a result, some of the files have been replaced on the silo. If you
retrieved data before that, you need to update your files. Check the time
stamps for the silo files. Those with the time stamp between March
18 and April 1 have been recooked/replaced.
There is one bad news. After cooking it was discovered that
nt10maker did not work
with the extension files.
As a result, ntuples produced for the files that have "++"
in "01" column are incomplete!
I fixed the code and put it in CVS. Those of you who wants to
use these ntuples must recreate some of them (those with "++") from the
cooked files and. Make sure you use -k<tripfile.trip>
command line option, with appropriate trip file, to make it
consistent with the calculated photon flux.
If someone finds other files that are "bad" and should be excluded from the analysis, let me know, I'll update tables.
I have not updated caldb with constants from our maps yet, but I definitely will do that and let you all know when it is done. In a mean time use our Maps in /work/clas/production/g2a/pass1.1/PARMS/.
This page is maintained by your friendly chef E.
Pasyuk