Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pilx] scanning motor ranges are not used when displaying the image #2383

Closed
kif opened this issue Jan 20, 2025 · 2 comments · Fixed by #2394
Closed

[pilx] scanning motor ranges are not used when displaying the image #2383

kif opened this issue Jan 20, 2025 · 2 comments · Fixed by #2394
Assignees
Labels
bug Serious issue, to be addressed in priority !

Comments

@kif
Copy link
Member

kif commented Jan 20, 2025

diffmap generates the 2 arrays with the scan motor name containing their position but this information is not used for the display.

reported by ID27.

@kif kif added the bug Serious issue, to be addressed in priority ! label Jan 20, 2025
@kif
Copy link
Member Author

kif commented Jan 22, 2025

Update as well how units are handled in diffmap.py : there are still a lot of unit.split("_")[0]

@kif
Copy link
Member Author

kif commented Jan 27, 2025

Silx is now able to recognize the axis names and motor position and display them properly:
Image
In pilx, it is not yet the case ...
Image

The screenshots were taken with the branch kif/diffmap, PR #2394

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Serious issue, to be addressed in priority !
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants