-
Notifications
You must be signed in to change notification settings - Fork 4
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
Spectroscopic Detector #368
Comments
I think this would be suitable. In fact the only guarantee about |
What do you do with the images after acquisition? I guess you want to use them just like images from other cameras (3D reconstruction, ...). If that's the case then the processing stages after the acquisition which are not aware of 3D stacks (unlike e.g. numpy's |
@tfarago I already thought about that, but then I get problems with the synchronization. I usually run them in trigger mode 'Auto'. I would need to use the SpectroscopicCamera for the trigger and the "SingelEnergy"-camera for the grab. |
I have a spectroscopic camera that creates multiple images in each acquisition. Each image contains the information of one energy channel.
My idea to implement this camera was that the Camera.grab() function returns a stack of images, each slice containing one energy channel. To use this consistently I would implement a coroutine to select one energy channel and an adjusted ImageWriter addon.
Would this be a suitable implementation? Are there any other dependencies on the grab() function?
The text was updated successfully, but these errors were encountered: