In order to acquire experiments I often just use the code equivalent of running MDAs, that is to say SequenceSettings passed to the AcquisitionManager and run a non blocking acquisition.
I think I always observed that the system state cache corresponding to the beginning ot the acquisition is re-applied at the end, meaning if property P is in state 0 at the beginning, it will be set to state 0 at the end (if it has changed during the acquisition).
In the context of localization microscopy, I am now facing a situation in which we automatically change a certain property during acquisition (activation laser pulse length) but want to keep it at the same level for the next acquisition. Any insights on how to prevent the system from rolling back to the initial state?
My only solution would be to not do MDA-like acquisitions but rather snap the images and add them to the datastore. This brings me to another question, I guess that when using the SnapLiveManager the images are not pushed to the core circular buffer? (that’s where our activation thread pulls the frames from)
Finally, one of the reason why I’d rather use the MDA than the snap/store approach is that the latter used to be very slow comparitvely. I must admit I haven’t tested it since MM2-gamma was first out, so I might now be wrong.