Hi all,
I've just ultimated my first check on timestamps with the new machinery.
This email is intented to let you now how is the full chain now working:
a) It is now possible to run anaRecoil/abcRecoil with the -ts '#' option
In this way timestamp of events falling in the deltaE/mes right box are
dumped to the ts_file.# sampled by integrated purity.

The files with even # are the pure timestamp files (== to those that
CPFramework produces); odd # ones are the files needed in order to remove
the duplicates (they contains the purity information).

For example there are:
1) the file produced by CPFramework:
http://www.slac.stanford.edu/~asarti/recoil/ts_stu/ allDstar0_1
2) the file obtained running abcRecoil on the reduced collections
belongings to the CPFramework timestamp:
http://www.slac.stanford.edu/~asarti/recoil/ts_stu/ ts_file.26

There are some differences: mainly due to the fact that the mes/Delta box
is defined in two different ways in CPFramework and anaRecoil

The strange thing that I observe is the following:
running on superblock1 events I got events with purities < 80% (either
integrated and per mode): How this can happen?

The same is for the other superblocks. Can Daniele or Urs comment on this?

b) obtained the files for D0 and Dstar0 superblock1 I could start the
equal candidates scan:
I found 64 duplicated events on top of
4987 superblock 1 dstar0 eve &
14152 superblock 1 d0

Those duplicated events are assigned to the events with the highest per
mode purity.
I'm going to start the same study for superblocks 1 & 2.

Any question or comment is really welcomed.
Thanks,
Alessio

______________________________________________________
Alessio Sarti
 Universita' & I.N.F.N. Ferrara
 tel  +39-0532-781928  Ferrara

"Quod non fecerunt barbari, fecerunt Berlusconi"

"Che il bianco sia bianco, e che il nero sia nero
 che uno e uno fanno due e che la scienza dice il vero....
 DIPENDE !"