KVROOT: /afs/in2p3.fr/throng/indra/.kvroot-1.8.6_gcc-4.1.2_x86_64_root-5.33.01
The problem is always persisting. See this extract of the log file obtained during the raw->recon analysis: ----------------log file --------------------------------------------------------------------------------- : : Finished reading 165008 events from file root://ccxroot.in2p3.fr:1999//hpss/in2p3.fr/group/indra/e494s/raw/run_0081.dat.07-May-07.18:23:02 +++ INDRA events : 204858 +++ INDRA gene events : 1393164288 +++ Other (non-INDRA) events : 909296543 *** Number of reconstructed INDRA events : 8250 *** : : ----------------------------------------------------------------------------------------------------------- -- You received this bug notification because you are a member of KaliVeda Development Team, which is subscribed to KaliVeda. https://bugs.launchpad.net/bugs/807444 Title: Event counters are wrong for analysis of INDRA-VAMOS raw data Status in KaliVeda data analysis framework: Fix Committed Status in KaliVeda 1.8 series: Fix Committed Bug description: When performing analysis of raw INDRA-VAMOS data, the event counters printed at the end of the analysis are totally bizarre: Finished reading 203545 events from file root://ccxroot.in2p3.fr:1999//hpss/in2p3.fr/group/indra/e494s/raw/run_0023.dat.04-May-07.19:33:47 +++ INDRA events : 796580064 +++ INDRA gene events : 1882353257 +++ Other (non-INDRA) events : 1919341557 Normally they are initialised in KVINDRARawDataAnalyser::postInitRun() but KVIVRawDataAnalyser::postInitRun() overrides this method and the initialisation is lost To manage notifications about this bug go to: https://bugs.launchpad.net/kaliveda/+bug/807444/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~kaliveda-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~kaliveda-dev More help : https://help.launchpad.net/ListHelp
