Add track state at target

[alspellm]

Extrap track to target and make new track state where track params ref = (trackX,trackY,0), therefore d0 = 0.
trackY position may replace d0 if using this track state in analysis.

Track reference point is set to (trackX, trackY, trackZ), so track position at target is saved.

May want to change track param reference point to ref = (trackX,0,0), so that d0 != 0.

These track states only exist if target position is set in steering-file KalmanPatRecDriver.

[cbravo135]

I think you want to change -4.3 to target_z

[alspellm]

Ah you are correct, whoops

…

On Thu, Jun 8, 2023, 6:00 PM Cameron Bravo ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In tracking/src/main/java/org/hps/recon/tracking/TrackUtils.java <#996 (comment)> : > + double dx = dz * mom.x() / mom.z(); + Hep3Vector dPos = new BasicHep3Vector(dx, dy, dz); + finalPos = CoordinateTransformations.transformVectorToTracking(VecOp.add(dPos, RKresults.getFirstElement())); + } + bFieldY = fM.getField(CoordinateTransformations.transformVectorToDetector(finalPos)).y(); + //params are calculated with respect to ref = {trackX, trackY, z=0) + double[] params = getParametersFromPointAndMomentum(finalPos, momTrans, (int) charge, bFieldY); + BaseTrackState bts = new BaseTrackState(params, bFieldY); + //reference point is set to track position in X Y Z + bts.setReferencePoint(finalPos.v()); + //Consider shifting reference point to (trackX, 0, 0)...otherwise d0=0 + boolean case2 = false; + if (case2){ + double [] paramsRefPoint = {finalPos.x(), finalPos.y(), 0.0}; + bts.setReferencePoint(paramsRefPoint); + double[] newRef = {-4.3, 0.0, 0.0}; I think you want to change -4.3 to target_z — Reply to this email directly, view it on GitHub <#996 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALKJUAVYERXF6YNS4FFFX43XKJYT7ANCNFSM6AAAAAAY75AKSI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[normangraf]

Instead of having magic code triggered by the addition of the targetPosition variable please add a boolean which explicitly states what is going to happen followed by the target location, such as

<createTrackStateAtTargetPosition>true</createTrackStateAtTargetPosition>
<targetPosition>-4.3</targetPosition>