Willi L Stepp

Are there any updates on this? Might become relevant for us in July.

No, no hardware sequencing I think. Let me know if there is something I can help with.

Sounds good to me. 1. Yes, only predefined formats or would it make sense to enable passing specific keys? 2. Looks very sound to me. But I think most of...

Thanks. So on the scope I run into the problem that the live feed stops when I move the stage with this. I'm not 100% sure, but it seems like...

> For the implementation, a slightly simpler pattern (and one similar to what we do with properties) might be to block any upstream signals, and always check (though maybe you...

I came across the problem mainly here: https://github.com/LEB-EPFL/iSIM/blob/48026a2e9ba89e8c5b2e88066d65600d2737108b/control/src/isim_control/gui/position_history.py#L85C9-L85C73 This makes an overview of the sample, not really crucial, but people have come to like it and I would like to...

Here is my stab at a custom MDAEngine for our iSIM: [iSIM MDAEngine](https://github.com/LEB-EPFL/iSIM/blob/d1685a0a8bda9913930e8d894240d6d86fadc70e/control/src/isim_control/ni/acquisition.py) For a SnapEngine, I think this part would be relevant: ```python def setup_event(self, event: MDAEvent): try: next_event...

> Solution 2 is here as written by @ptbrown1729 and is much cleaner. This is a custom implementation of an "MDAEngine" (not generic) for a complicated DAQ driven instrument with...

I see, thanks for the information! I will think about it. My first feeling would be to go for option 1 and wrap the calls, then the event would also...

A very crude first try here: #295