-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It seems that the time sequence cannot be too long. #95
Comments
There was a similar report here: https://groups.google.com/g/labscriptsuite/c/q2sBrLmELn8/m/b4CAIWEcAQAJ I was never able to reproduce the issue myself locally. Do you have a full example script that reproduces it you would be willing to share? |
Thank you Phil!
When I only execute a single time sequence, it works well. Once I start the cycle, the above error will occur. I've tried to shorten the sequence time of my single cycle by about 5 second, and when I cycle it three times, it can run. But my actual experiment can not shorten my sequence time. |
So I haven't had chance to try and compile this yet, but looking at it I think I understand what the issue is. The outputs on It seems like a bit of a deficiency that we don't have a way for pseudoclocks to tell labscript what their maximum clock tick period is. Unfortunately I can't immediately see an easy way to add this into labscript. It has to be done around the Anyway...fortunately there is an easy work around. Which is that you just need to use an output on Please let me know if this fixes the issue! We'll keep this open until we have a proper fix in labscript that covers all pseudoclocks. |
Thanks Phil!Now it can run successfully! |
My initial timing duration is about 25s, and it can run well. But when I tried to cycle my experiment three times, my experiment logic script like this:
I‘ve encountered this error:
Is there any way to solve it?Thanks!
@mjasperse @chrisjbillington @philipstarkey
The text was updated successfully, but these errors were encountered: