fly motor being read in wrong from the spec.log

[kenygren]

Describe the bug

In the spec log, the motor went to the correct positions - see pymca for correct motor positions in z
in the map.nxs file the fly_labz motors are not reading in correctly - see image from nexpy readout

The config yaml looks right

To Reproduce
Provide a minimal pipeline configuration in which the bug appears:

pipeline: /nfs/chess/aux/cycles/current/id1a3/thom-levy-4181-b/reduced_data/mapscan-p5-minigrid-1504-1

if you look in the output folders those are from the dev version. The prod version also does this and is the output_prod

Expected behavior
I expect the fly_labz to produce the same motor positions as the spec.log (rsampZ in this case)

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Station computer id1a3
• CHAP dev and prod on 06/20/2026

Additional context
This prevented on the fly assessment of the data