GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Bugs, Fixes, Releases » TPC MVD and GEM correlators
TPC MVD and GEM correlators [message #12013] Thu, 16 June 2011 02:30 Go to previous message
Felix Boehmer is currently offline  Felix Boehmer
Messages: 149
Registered: May 2007
Location: Munich
first-grade participant

From: *gsi.de
Hi all,

I checked in correlator tasks for MVD and GEM in tpc/tpcreco. Also, there is a testing macro: macro/run/tdrct/run_reco_tpc.C

The scheme is easy: First comes real TPC PR, the fit, then the MVD correlator, another fit, then the correlation with the GEM and the final fit.

Please go ahead and try.


One observation, though: I still have trouble with GEANE, especially when extrapolating in forward direction into the GEMs (floating point exceptions). I can't do anything about it right now. There is an option in the PR (useGeane()) which is the default in the macro. By disabling it, the track representation will change to RKTrackRep, which shows no such problems, but seems to have inferior material effect calculations.

So please try the stability of the channel in question first.
Also, I would be helpful if people start using the macro also off the grid in private small runs and share their experience with me.

Be sure to update your

tpc/tpcreco
GenfitTools
genfit
recotaks
macro

folders to have the lates reconstruction algorithms in place.

Cheers

Felix
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [FIXED] Bug in EvtGenDirect
Next Topic: Bug in parameter handling?
Goto Forum:
  


Current Time: Thu Mar 28 10:53:59 CET 2024

Total time taken to generate the page: 0.01125 seconds