Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Better "to short delay" error message #43

Open
philipstarkey opened this issue Jul 21, 2017 · 0 comments
Open

Better "to short delay" error message #43

philipstarkey opened this issue Jul 21, 2017 · 0 comments
Labels
enhancement New feature or request major

Comments

@philipstarkey
Copy link
Member

Original report (archived issue) by Jan Werkmann (Bitbucket: PhyNerd, GitHub: PhyNerd).

We often get the "Commands have been issued to devices attached to X at t= ...s s and ... s. This Pseudoclock cannot support update delays shorter than ... sec." when rewriting experiment scripts. This is mostly caused by shutters that just happen to get to close to some other pulse.
This is hard to debug, as we can't just view the file in runviewer since it didn't compile.
It would be really helpful to get the names of the colliding outputs as this would make things a lot easier.
@philipstarkey philipstarkey added major enhancement New feature or request labels Apr 5, 2020
Loki27182 pushed a commit to Loki27182/labscript that referenced this issue Oct 9, 2023
@chrisjbillington
Merge with pstarkey/GatedClocks-bugfix (Pull request labscript-suite#43)
957af93
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request major
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@philipstarkey