Hi, BANAPP updated. CVS: ------------ Many small bugfixes and other minor changes: accpetancemaps/geometry: fixed SetRichFidCutX() function to set the X value not the Y value. Changes to the Print() function. Now giving more meaningfull output. Moved EfficiencyCalculator into correction/efficiency/ as this is where it should be. It deals with correction factor and not with particle selection. It is now avaliable in correction/efficiencylibEfficiency.la library. All affected Makefile/Linkdef have been changed. Small changes in method2/hadronAnalyse.cxx, to deal with PID. Fixed typo "BRAT"-> "BANAPP" in util/banapp-config/banapp-config.in -------------- IMPORTANT: So if you use EfficiencyCalulcator in some other program, you now need to link against the libEfficiency library, as it is no longer in the libSelection library!!! A hack was also introduced into dst2tree, with regards to the connection to the geometry DB. If the program uses too long time figuring out which files it can analyse from the filecatalog (response from the filecatalog is always very slow) the connection to the geometry times out. So when the init of some geometry volumes (for diagnostics) starts, the connection is gone and you get a SEGMENTATION VIOLATION. Hopefully this hack will prevent it. It just reads the TPM1 volume every 10th time it has checked a run number with the filecatalog DB... (Asking the filecatalog about the existence/location for more than 200 run numbers can take more than 30 min!!!) Banapp 1.3.0 commited and tagged! Reminder: If you commit a bug, remember to at least update the revision number! and to tag banapp. Its not good to have two versions of banapp with the same version number, one having a bug and the other not... Cheers, Truls On Mon, 2007-03-12 at 16:33 +0100, i.c.arsene_at_fys.uio.no wrote: > Hi, > > I found a small bug in banapp in functions > MicroTreeReader::GoodTofHit(), MrsTreeReader::GoodTfw2Hit(), > FsTreeReader::GoodH2Hit(). These functions make some conditions on > the tof slats. I found that the condition regarding the number of > multiple hits was: > "multi > 1" > This condition has no effect on removing slats with multiple hits since > all or almost all of the "multi slats" have the flag = 1. As i know, > the convention is to have the "multi" flag set to zero if the slat has > only one hit and >0 for multiple hits. I changed the condition to > "multi > 0" > The effect on the data is not big (~0.5 %). > I made the modifications in the above named functions and submitted > them to CVS. > > Cheers, > Ionut > > _______________________________________________ > Brahms-dev-l mailing list > Brahms-dev-l_at_lists.bnl.gov > http://lists.bnl.gov/mailman/listinfo/brahms-dev-l > -- *---------------------------------* |http://www.nbi.dk/~trulsml / |Truls Martin Larsen / |trulsml_at_nbi.dk . |The Niels Bohr Institute // |Work Address: / \0 |Blegdamsvej 17 /\_/ |DK-2100 Copenhagen / / |Tel: +45 353 25269 / -- | /_/ | |Home address: / \ |Holger Danskes Vej 28H| ' |DK-2000 Frederiksberg | |Denmark | |Mob: +45 20974802 | *----------------------* _______________________________________________ Brahms-dev-l mailing list Brahms-dev-l_at_lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/brahms-dev-lReceived on Tue Mar 13 2007 - 04:39:02 EDT
This archive was generated by hypermail 2.2.0 : Tue Mar 13 2007 - 04:39:24 EDT