Bug #1926
Tracker z position offset in current recon
Start date:
29 March 2017
Due date:
% Done:
0%
Estimated time:
Workflow:
New Issue
Description
I noticed an almost order-of-magnitude increase in residuals propagating into the target from the DS tracker looking at data reconstructed with MAUS 2.8.4 vs the same data (run 8448) with 2.6.1. It looks like in 2.8.4, the global z position reported by TKD is off by 94mm. In the 2.6.1 dataset TKD z positions range from 18849 to 19950, in the 2.8.4 one from 18755 to 19856. In TKU there is an offset as well, but there it's only 6mm.
Updated by Rajaram, Durga about 6 years ago
- Assignee changed from Kyberd, Paul to Rajaram, Durga
Ao had reported the same thing in his recent CM talk.
This seems to be coming from the geometry.
A few weeks ago I asked Ryan Bayes for clarification on why the TKD geometry changed. Haven't heard back.