I have looked at what tracks are found by ProductionExe when run with the standard tcl files on the tight Z sample (farms used release 4.3.1) and Z->ee MC in 4.4.0int4. The default process, I think, is to do
mod talk DHInput dropList add CdfTrackIdManager CdfTrackColl CdfEmObjectColl dropList add CdfTrackHits CdfTrackView exit # Need to enable PVFinder to do standalone tracking??? mod enable PVFinder mod talk PVFinder SAS3DPVFinder set t TrueVertices set f exit mod disable CT_TrackingModule mod enable SiPatternRecModule mod talk SiPatternRecModule PerformOutsideInTracking set f PerformOIZTracking set f PerformKalSvxStandaloneTracking set t exit mod enable CdfEmObjectModule
_x0("BeamX0",this,0.0,-1,1), _y0("BeamY0",this,0.0,-1,1),And now I can run with BeamX0=-.17, BeamY0=.42.
BeamX0 set -0.1181 BeamY0 set 0.4130It is talking to a different module but presumably for the same purpose. Why the difference in the X offset?
AlignmentSource set "ofotl_prd_read 100021 3 TEST"we get: