I have set things up so I can make FARFALLA DSTs from MUADST.
Comparing the FARFALLA file I made this way with the FARFALLA file I
made the old-fashioned way (with .ZEB file), I see most of the events
are the same. There are a few events where my DREAM executable on
RS6000 found a bogus lateral track -- it really does go through some
stray hits in the lateral view, but when looking at event display it
is obvious that the physical track is the one found by both programs,
and the extra track found by my executable is bogus. I'm not sure why
the two executables are not behaving exactly the same, but I'm not too
worried about it. More disturbing are a couple of events where a hit
is missing from the MUADST. For example, r11731 e236 has 5 strip hits
from off the strip track, but the TDST file contains only 4.
Other Strips differ, event 236:
.ZEB file: There are 5 strip hits.
d: 7078.74 z: 961.30 dd: 3.74 dz: 6202.72
d: 6656.89 z: 1003.70 dd: 7.17 dz: 6102.72
d: 6467.93 z: 225.50 dd: 3.10 dz: 6102.72
d: 7107.23 z: 165.02 dd: 6.81 dz: 6202.72
d: 6983.25 z: 345.21 dd: 6.46 dz: 6202.72
.TDST file: There are 4 strip hits.
d: 7078.74 z: 961.30 dd: 3.74 dz: 6202.72
d: 6656.88 z: 1003.70 dd: 7.18 dz: 6102.72
d: 6467.93 z: 225.50 dd: 3.10 dz: 6102.72
d: 7107.23 z: 165.02 dd: 6.82 dz: 6202.72
As you can see, the extra hit found by my executable appears
legitimate. Anyone have any idea what's going on? I have a copy of
the .ZEB file if anyone wants it.
Bob