Talley Lambert
Talley Lambert
I believe, (but am not sure/have not tested) that you would need to use [`mmc.setAutoShutter(False)`](https://valelab4.ucsf.edu/~MM/doc/MMCore/html/class_c_m_m_core.html#a4044c7fe6f58db4ca69c0bb4016f3635), and then manually open/close the shutter before/after the Z-stack. https://github.com/pymmcore-plus/useq-schema/issues/38 would simply be the declarative...
Another thing to mention here is that we haven't optimized for "sequenceable" hardware in pymmcore plus's mda engine yet. I'm curious: Are you by chance comparing to the speed you...
Great! I'll take that 😂
`core_widgets` is basically what I imagine breaking out into a new package soon. So, if it simply provides a Qt view onto the core model and could generally be used...
Yes indeed, I meant @fdrgsp sorry. I think core state will go away with better device widgets.
thanks for that context @ptbrown1729 ... Yeah that seems like a very reasonable and potentially common use case. I know that @ianhi also has some hardware that is much easier...
Yeah, let's do 1. 3 is ideal longer term, and I like what you proposed at AICSimagio as well
> while looking at this I noticed that we aren't doing the kind thing of remembering what the user set the exposure to on a per channel basis. This is...
@ianhi, can you make a new PR with _just_ the bit that prevents the displayed value from matching the actual value? then do cache in a different pr?
Yeah, a bare minimum compatibility pr would be good. How does the widget need to change?