occheung/artiq
1
0
Fork 0
forked from M-Labs/artiq
Code Pull Requests Activity

exceptions: clarify RTIOBusy

Browse Source
This commit is contained in:
Robert Jördens 2016-03-09 22:11:32 +01:00
parent 107e5cfbd4
commit 9edaf16735
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
artiq/coredevice/exceptions.py
View File

@ -99,15 +99,14 @@ class RTIOCollision(Exception):
artiq_builtin = True
class RTIOBusy(Exception):
"""Raised when an event could not be executed because the given channel
was already busy executing a previous event. The two events were not
sufficiently spaced on the timeline.
"""Raised when at least one output event could not be executed because
the given channel was already busy executing a previous event.
This exception is raised after the error condition appeared. More
This exception is raised late: after the error condition occurred. More
specifically it is raised on submitting an event on the same channel after
the execution of the faulty event was attempted.
The offending event is discarded and the RTIO core keeps operating.
The offending event was discarded.
"""
artiq_builtin = True