From stat boxes one can estimate total efficiency of compositing space points for FTD which is ~ 82.7 %
I wanted to check the position of digitized strips in the event display, but it is not so trivial to show for the FTD that the position is biased if it is...
Just to show some example case for the thought:
Strips radially exceed the boundaries is expected behaviour...
Ideally all disks should have different strip length, but as it is currently implemented, we assume equal strip lengths for all disks for simplicity and reject space points if they are reconstructed outside of surface boundaries
However, one needs to pay attention to the middle position of the strips...
I assume we expect them to be radially on the middle of the sensors.
However if they as well as SET strips are digitized to be with V = 0 coordinate, then they also deviate from the middle sensor position as V is perpendicular to the strips which are tilted by the 5 degrees..
I will try to put them on the middle the same as SET hits and cross check how efficiency changes...
This most probably also affects FTD strip disks:
I wanted to check the position of digitized strips in the event display, but it is not so trivial to show for the FTD that the position is biased if it is...
Just to show some example case for the thought:
Strips radially exceed the boundaries is expected behaviour... Ideally all disks should have different strip length, but as it is currently implemented, we assume equal strip lengths for all disks for simplicity and reject space points if they are reconstructed outside of surface boundaries
However, one needs to pay attention to the middle position of the strips... I assume we expect them to be radially on the middle of the sensors. However if they as well as SET strips are digitized to be with
V = 0coordinate, then they also deviate from the middle sensor position asVis perpendicular to the strips which are tilted by the 5 degrees..I will try to put them on the middle the same as SET hits and cross check how efficiency changes...
Originally posted by @dudarboh in https://github.com/iLCSoft/MarlinTrkProcessors/issues/50#issuecomment-946936450