On 10/26/2015 12:14 AM, Joe Britton wrote: > A (key binding) way to > "clear the queue" (in some meaningful way without removing the default > experiment) or maybe to "dequeue all instances" would do it. Then you > can fire two shortcuts. > > > Good point. An alternative approach that requires no change to ARTIQ is > the following. > > a) Start a program that plots some observable in the GUI. > b) Repeatedly call (CTRL-ENTER) a short-lived program that steps an > experiment parameter. > c) Observe the impact in to the plot. > > Experiment (a) can be marked Flush if the parameter changed by (b) > modifies the state of (a). In the case that experiment (a) modifies > something physical about the experiment no Flush (eg mirror position > change).
The flush flag only affects the startup of an experiment, and as far as I can tell, experiment (a) would keep running and never terminate. So a flush flag on (a) won't have any effect on its interaction with (b). If I understand this correctly, what you can do is have (a) pause, make (b) higher priority than (a), and communicate through broadcasted datasets: (b) would modify the value of a dataset that (a) reads after its pause. Sébastien _______________________________________________ ARTIQ mailing list https://ssl.serverraum.org/lists/listinfo/artiq
