In the end, the big picture idea would be to extend most static output devices to be able to accept ZMQ triggers during the sequence so they could behave as triggerable devices, subject to the latency of ZMQ triggering an the accuracy of a software clock.
* The clock itself would be started like any other device by labscript and would start ticking as soon as blacs sent a start signal. Then it would dispatch ZMQ messages as per its internal table of events.
* The biggest issue I see right now is interfacing with waits since this clock would need to respect labscript time, not wall time. My first idea here was going to be to use a digital input to learn the status of wait, but Chris Billington had some idea of having the device monitoring waits dispatch start-wait and end-wait signals over ZMQ to all listeners.
Like I said, I soft clock would be a great addition to labscript, but it could be a time sink.
Ian B. Spielman
Fellow, Joint Quantum Institute
National Institute of Standards and Technology and the University of Maryland
----- WEB -----
----- EMAIL -----
----- ZOOM -----
----- PHONE -----
----- MAIL -----
2207 Computer & Space Sciences Bldg.
College Park, MD 20742
100 Bureau Drive, Stop 8424
Gaithersburg, MD 20899-8424 USA
----- OFFICE -----
UMD: Physical Sciences Complex, Room 2153
NIST: Building 216, Room B131
> To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/540d7691-1c9c-4c21-a8aa-3060dd2fd289n%40googlegroups.com