Hi, I do not think reconsctruction is skipping any events. it is rather a
Fortran vs. C++ numbering convetion. Here s the proof:
the very 1st event registered by DGen in a session:
************************************************************
* Row * EEP.N * EEP.theta * EEP.theta * EEP.theta *
************************************************************
* 0 * 1 * 48.155574 * 124.80790 * 46.928245 *
The first event nsed reconstructed:
Event Number: 1
mc 0 -1 : 0.622640 48.155499 -10.127000 -13.361400 | 3 electron
mc 1 1 : 0.057730 124.807899 31.708000 -13.361400 | 14 proton
mc 2 0 : 0.684690 46.928200 173.498001 -13.361400 | 13 neutron
All scattering angles match. However, TBLRaw number the events from 1
rather than from 0.
TBLRaw::nEvent is synchronized with TCodaRead::eventNo which is plainly
rawData[4] which is read out by TCodaEvio from the codafile. So I suspect,
it s simply the way blastmc counts events.
Chi
On Fri, 25 Apr 2003, Tancredi Botto wrote:
>
> chi, pardon me, but please make sure that the (physics) event number in
> nsed is the same for mc, data. We had a problem (was skipping one) once.
> The problem was actually in TBLRaw (I think) where the first physics event
> was lost due to a while loop
> -- t
> ________________________________________________________________________________
> Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124
> research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST