Home » PANDA » PandaRoot » Tracking » WirepointHitPolicy detplane implementation
Re: WirepointHitPolicy detplane implementation [message #8096 is a reply to message #8080] |
Mon, 16 March 2009 23:25 |
Anonymous Poster
|
|
From: *pool.einsundeins.de
|
|
Hi again,
I have a very simple solution for your distance cut: Put a
protected:
double _maxDistance
in WirepointHitPolicy. Then make a WirepointHitPlicy which loks something like this
const DetPlane&
SpacepointHitPolicy::detPlane(AbsRecoHit* hit, AbsTrackRep* rep)
{
TMatrixT<double> rawcoord = hit->getRawHitCoord();
//I dont know which of the 8 params is for the wire points
TVector3 point1(rawcoord[0][0],rawcoord[1][0],rawcoord[2][0]);
TVector3 point2(rawcoord[3][0],rawcoord[4][0],rawcoord[5][0]);
int dimension = rep->getDim();
TMatrixT<double> statePred(dimension,1);
TMatrixT<double> covPred(dimension,dimension);
//note that _plane is defined in AbsTrackRep
TVector3 poca=rep->extrapolateToLine(point1,point2,statePred,covPred,_plane);
/*C. Hoeppner, March 09: I am not entirely sure that these two calls
are needed, but they dont hurt for sure. Something happens here
to the orientation of u and v, so keep it.*/
TVector3 m=_plane.getNormal();
_plane.setNormal(m);
//now calculate distance of poca to line between point1 and point2
double distance;
if(distance>_maxDistance) {
cout << "vpf greater than maxValue" << endl;
FitterException exc("distance vpf-wire larger than maxValue", __LINE__,__FILE__);
throw exc;
}
return _plane;
}
For the DCH where you dont want this distance cut, just set the _maxDistance (do this in the contructors of the recoHits) to a very large value. Or you can use a bool flag to deactivate this feature. This you would also be set in the ctors.
About the origin of the plane: can you come to a common solution? Is Lia's solution OK for you Ola?
Thanks for your support!
Christian
|
|
|
|
|
WirepointHitPolicy detplane implementation
By: Anonymous Poster on Mon, 16 March 2009 13:55
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Mon, 16 March 2009 14:16
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Mon, 16 March 2009 15:54
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Mon, 16 March 2009 16:49
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Mon, 16 March 2009 18:46
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
new in AbsTrackRep: extrapolateToLine and consequences on WirepointHitPolicy
By: Anonymous Poster on Mon, 16 March 2009 23:10
|
|
|
Re: new in AbsTrackRep: extrapolateToLine and consequences on WirepointHitPolicy
|
|
|
Re: new in AbsTrackRep: extrapolateToLine and consequences on WirepointHitPolicy
By: Anonymous Poster on Tue, 17 March 2009 18:23
|
|
|
Re: new in AbsTrackRep: extrapolateToLine and consequences on WirepointHitPolicy
By: Anonymous Poster on Wed, 18 March 2009 11:51
|
|
|
Re: new in AbsTrackRep: extrapolateToLine and consequences on WirepointHitPolicy
|
|
|
Re: new in AbsTrackRep: extrapolateToLine and consequences on WirepointHitPolicy
By: Anonymous Poster on Wed, 18 March 2009 13:37
|
|
|
Re: new in AbsTrackRep: extrapolateToLine and consequences on WirepointHitPolicy
|
|
|
Re: new in AbsTrackRep: extrapolateToLine and consequences on WirepointHitPolicy
By: Anonymous Poster on Wed, 18 March 2009 15:26
|
|
|
Re: new in AbsTrackRep: extrapolateToLine and consequences on WirepointHitPolicy
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Mon, 16 March 2009 23:25
|
|
|
changes in PndDchKalmanQA
By: Anonymous Poster on Wed, 18 March 2009 15:32
|
|
|
Re: changes in PndDchKalmanQA
By: Anonymous Poster on Wed, 18 March 2009 16:13
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Wed, 18 March 2009 17:21
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Thu, 19 March 2009 14:11
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Thu, 19 March 2009 16:54
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Thu, 19 March 2009 16:56
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Thu, 19 March 2009 16:57
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Fri, 20 March 2009 14:36
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Fri, 20 March 2009 18:18
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Fri, 20 March 2009 20:28
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Mon, 23 March 2009 13:32
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Mon, 23 March 2009 15:33
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Mon, 30 March 2009 16:21
|
|
|
Re: WirepointHitPolicy detplane implementation
|
|
|
Re: WirepointHitPolicy detplane implementation
By: Anonymous Poster on Wed, 01 April 2009 12:34
|
|
|
Re: WirepointHitPolicy detplane implementation
|
Goto Forum:
Current Time: Fri Dec 06 20:05:31 CET 2024
Total time taken to generate the page: 0.00890 seconds
|