Justin,
I am sorry to say that such a feature is currently not supported. The reason is that the worker running the function runner needs to be aware of the experiment timing (including any waits). So the only times that are known for sure are the time before the sequence starts and the time after it ends.
In the current framework, the basic way this would be implemented would to create a software pseudoclock that sends “ticks” (zmq messages) to whatever software timed devices need updates. It also would need to be synced with the wait infrastructure, meaning the wait monitor device would also have to send signals to the software pseudoclock wherever a wait had ended.
An alternate way to do this is to make a device, say with a real raspberry pi, that either (1) sends zmq messages to the function runner worker every time it is triggered, or (2) if it is fast enough, just locally runs the function.
— Ian
Ian B. Spielman
Fellow, Joint Quantum Institute
National Institute of Standards and Technology and the University of Maryland
----- WEB -----
http://ultracold.jqi.umd.edu
----- EMAIL -----
spie...@jqi.umd.edu
----- ZOOM -----
https://umd.zoom.us/j/7984811536
----- PHONE -----
(301) 246-2482
----- MAIL -----
UMD:
2207 Computer & Space Sciences Bldg.
College Park, MD 20742
NIST:
100 Bureau Drive, Stop 8424
Gaithersburg, MD 20899-8424 USA
----- OFFICE -----
UMD: Physical Sciences Complex, Room 2153
NIST: Building 216, Room B131
> --
> You received this message because you are subscribed to the Google Groups "the labscript suite" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
labscriptsuit...@googlegroups.com.
> To view this discussion on the web, visit
https://groups.google.com/d/msgid/labscriptsuite/acbfe6e0-2e8d-4bcb-a1d5-f2687cbf904fn%40googlegroups.com.