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

Spectroscopic Detector #368

Open
MarcusZuber opened this issue May 20, 2015 · 3 comments
Open

Spectroscopic Detector #368

MarcusZuber opened this issue May 20, 2015 · 3 comments

Comments

@MarcusZuber
Copy link
Member

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?

@matze
Copy link
Contributor

matze commented May 21, 2015

I think this would be suitable. In fact the only guarantee about grab()s return value is that it is an ndarray. I think most important is that the dimensions are image dimensions (rows and colums mean x and y) not matrix dimensions (y and x).

@tfarago
Copy link
Contributor

tfarago commented May 21, 2015

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 std used by focus function) must have a special implementation for this. This can be avoided if you think of every channel as a separate 2D camera. In this case you can use the rest of Concert without a single change. Or, maybe even better, one can have both, let's say I have a SpectroscopicCamera and I want to do CT on some channel, then one can implement SpectroscopicCamera.get_camera_for_channel(50 * q.keV) which returns (surprisingly 😄 ) a Camera, so you can use it normally by further processing.

@MarcusZuber
Copy link
Member Author

@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.
My idea for the processing was to use the Specroscopic camera that returns these image stacks in experiment classes and then to attach consumers for each energy channel. To split the results I would use this slice-selcting coroutine.

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

3 participants