[Tpe] ready to cook?
Puneet Khetarpal
puneetk at jlab.org
Mon Jun 27 14:26:20 EDT 2011
Hi All,
I was going through some of the output files and logs for some of the
cooking and found some stuff that may be relevant to our cooking.
Please take a look:
1. The beam position and target positions seem to be inconsistent,
could someone please check? See snippet below:
clastpe at ifarm1101> more
.farm_out/tpe_pass0_v8_clastpe_runs67282-67282.9556771.err
...
WARNING, no target position available in the database, take value=0.0000000.0000
00-30.000000 for run 66000 instead
Target Z -30.000000
WARNING, no beam position available in the database, take value=0.0000000.000000
-20.000000 for run 66000 instead
Beam offset (x,y) 0.000000 0.000000
using beam position: 0 0 -20 from run: 66000
Target position initialized to: x=0.000000 y=0.000000 z=-30.000000
...
2. Are we removing events that fall during the beam trips? see snippet
from same file below:
cp: cannot stat `clas_067282.A46.trip': No such file or directory
3. Are we happy with the cuts on the chi squares for TBT, etc.. for RECSIS?
clastpe at ifarm1101> more
.farm_out/tpe_pass0_v8_clastpe_runs67282-67282.9556771.out
...
TRK_STATI L: Cut# Description Value Passed %
TRK_STATI L: 1 trk_evnt: Ntrig (Nevt) > 0.0 519495 100.0
TRK_STATI L: 2 ana_segm: Nevt w. segm = 5.0 500095 96.3
TRK_STATI L: 3 trk_link: Nevt w. link = 5.0 460693 88.7 100.0
TRK_STATI L: 4 ana_prfit: Nevt PR chi2 < 700.0 444889 85.6 96.6
TRK_STATI L: 5 SEB_eid: Nevt SEB = 0.0 416044 80.1 90.3
TRK_STATI L: 6 trk_dcam: Nevt w. LRseg= 4.0 411665 79.2 89.4
TRK_STATI L: 7 trk_dcam: Nevt w. LRseg= 5.0 402286 77.4 87.3
TRK_STATI L: 8 ana_fit: Nevt FF1 chi2 < 700.0 400365 77.1 86.9
TRK_STATI L: 9 ana_fit: Nevt in TBT > 0.0 400365 77.1 86.9
...
4. What cuts/code are we going to use to make preliminary cuts to skim
our data during the cook?
Puneet
"No word is true until it is eaten" - 36 Lessons of Vivec, Sermon 27
More information about the Tpe
mailing list