GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Tracking » GEM tracking
Re: GEM tracking [message #8221 is a reply to message #8220] Wed, 15 April 2009 13:01 Go to previous messageGo to previous message
Anonymous Poster From: *pool.einsundeins.de
Hi Radek and Ralf,

I agree that things like amplitude correlation etc. are very helpful for pattern recognition, i.e. track finding, purposes. However, to my mind that does not mean, that in the track fitting this 2D information should be used. It is just as easy to use the 1D information in genfit. I tested this extensively. Even if the planes are only 300mu apart, this should be taken into account especially in the MVD were the spatial resolution will be much better than that. In the GEMs, it probably doenst matter so much.

Of course this choice is up to you guys. If you need any help in using the 1D info, please let me know and I will be happy to help.

Radek, about your RecoHit implementation in

PndGemRecoHit::PndGemRecoHit(PndGemHit* hit)

you set the hit coordinates and the covariance matrix like:

_hitCoord[0][0] = TMath::Sqrt(hitX*hitX+hitY*hitY);
_hitCoord[1][0] = 0.;

_hitCov[0][0] = hit->GetDr();
_hitCov[1][1] = hit->GetDp();

I dont understand, why one of the two hit dimensions is always 0. This should be the case if the PndGemHit is a 2D info.

Cheers, Christian
 
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: change in genfit exception handling
Next Topic: GEM Tracking inside LHETRACK
Goto Forum:
  


Current Time: Sun Jun 16 23:43:46 CEST 2024

Total time taken to generate the page: 0.01003 seconds