I have a feeling that this is a larger project than you may think, really for two reasons.
(1) Robust user authentication is not easy (I am sure it would be easy to hack an insecure solution).
(2) The shared windows drive paradigm labscript uses is really not suitable for a scaleable remote submission solution (i.e., how does the complied h5 file go from the remote user’s computer, to blacs, and when the shot is done where is the final data stored? How does this interact with the whole labscript system in a truly distributed environment?)
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
> You received this message because you are subscribed to the Google Groups "the labscript suite" group.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/CAKBMk%2BfcoxC-XL7SO16wkXxRtCnenB%3DSR8-8Pc3x3b1nyq-9bw%40mail.gmail.com