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

PyDM image processing #1106

Open
peroame opened this issue Aug 22, 2024 · 0 comments
Open

PyDM image processing #1106

peroame opened this issue Aug 22, 2024 · 0 comments
Assignees

Comments

@peroame
Copy link

peroame commented Aug 22, 2024

I have the impression the modern waveform record offers itself to be dynamically changed for both its length (through the NORD field) and its type (through the FTVL field) and it would be nice to see the client adapting. What I noticed, though, is the following:

  1. If FTVL is USHORT, pydm will use 32-bit ndarray instead of 16-bit (note: this is the case when using ca:// while pva:// uses 16-bit ndarrays instead and that feels the correct behavior).
  2. If FTVL is UCHAR, pydm will use 8-bit array but the display then doesn't seem to work correctly with ca:// (note: the display looks ok when using pva:// with 8-bit arrays).
  3. Nor ca:// or pva:// seem to be able to adapt dynamically when FTVL changes and they maintain the data type they found when the connection was established.

Do you think it would be appropriate for pydm to be able to dynamically adapt to a changing FTVL or, for cameras, to a changing pixel format? Does areadetector change FTVL on the fly?

Thank you for looking at this,
Amedeo

@nstelter-slac nstelter-slac self-assigned this Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants