Just to avoid confusion and make it clear to all:
now the duplicates killing (if switched on) kill ALL the duplicates in the
same seed and does not care about purity!
Ex:
if there are 2 D0 events
1) ts = AAB/PPC pur 87% (sb 1)
2) ts = AAB/PPC pur 23% (sb 3)
all this two events will be removed. This is because the algoritm that
makes the killing does not know anything about purity: it only compares
timestamp.
Of course this problem does not occur for different seeds:
Ex D0 eve AAB/PPC pur 34% (sb 3)
Ex DC eve AAB/PPC pur 75% (sb 2)
running with the right killing table (on D0 with kill_TAB_1 and on
DC with kill_TAB_2) you'll have removed the D0 candidate but you'll keep
the DC one!
This implementation, thus, will be really well_behaved (we don't loose
signal events) only when we'll have collections without duplicates among
the same seed!!!
The mes study that I'm making contains all those duplicated events (even
those that refer to the same seed). In this case (dupli_among_same_seed)
those events will appear twice (or more) in the mes distribution.
Let me know any question/comment.
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 !"
|