Dear vub-recoilusers,
I finally managed to get the Run1-5 production done - several jobs kept producing
corrupted output, probably a memory swap problem (the next production will be done
on a smaller number of events per tcl). One job kept hanging after processing
36000 events, it required a little tweaking to get it done not spoiling the B
counting.
* Please note that the dataset for Run1 has noticeably changed: since last
February, a lot of collections have been marked bad and removed from the dataset.
* The dataset for Run5 has also changed: now all the bug-free collections have
been skimmed and processed.
You will find the chains in
/afs/slac.stanford.edu/u/br/sacco/vol1/ana-32/workdir/
The generic chains are called, as usual: genChainRun* or, separated per B charge,
genbchChainRun*, genbnuChainRun*.
I also produced chains for resonant and non-resonant signal (modes 6333 and 2575)
separated per run period: mixChainRun*, nreChainRun*.
Some figures for the number of events (skimmed/generated):
mode 1235 Run1: 2508083/36156000;
mode 1235 Run2: 7098889/103124000;
mode 1235 Run3: 3382314/47102000;
mode 1235 Run4: 12536374/168528000;
mode 1235 Run5: 16296050/219758000;
mode 1237 Run1: 2232867/36536000;
mode 1237 Run2: 6254509/103260000;
mode 1237 Run3: 3214425/50556000;
mode 1237 Run4: 10982874/167716000;
mode 1237 Run5: 13559746/208816000;
mode 6333 Run1: 14272/844000
mode 6333 Run2: 41860/2514000
mode 6333 Run3: 22921/1322000
mode 6333 Run4: 74726/4047000
mode 6333 Run5: 98606/5326000
mode 2575 Run1: 18065/844000
mode 2575 Run2: 53313/2514000
mode 2575 Run3: 29593/1322000
mode 2575 Run4: 95512/4047000
mode 2575 Run5: 126871/5326000
Happy vub-ing,
Roberto
|