Skip to content

Commit 59757a4

Browse files
committed
Added note about not using generic classes directly
1 parent 9a9e205 commit 59757a4

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/source/connection_table.rst

+2
Original file line numberDiff line numberDiff line change
@@ -13,3 +13,5 @@ If a device is not a :py:class:`PseudoclockDevice <labscript.core.PseudoclockDev
1313

1414
If a :py:class:`PseudoclockDevice <labscript.core.PseudoclockDevice>` also has outputs that are not used for a :py:class:`ClockLine <labscript.core.ClockLine>`, then an :py:class:`IntermediateDevice <labscript.core.IntermediateDevice>` is internally instantiated, and should be made available through the ``PseudoclockDevice.direct_outputs`` attribute (for example see the :py:class:`PulseBlaster <labscript_devices.PulseBlaster.PulseBlaster>` implementation).
1515

16+
.. note::
17+
Most user's will not need to use :py:class:`PseudoclockDevice <labscript.core.PseudoclockDevice>`, :py:class:`Pseudoclock <labscript.core.Pseudoclock>`, and :py:class:`IntermediateDevice <labscript.core.IntermediateDevice>` directly. These are generic classes that are subclassed by device implementations in :doc:`labscript-devices <labscript-devices:index>`. It is these device implementations that you are most likely to use.

0 commit comments

Comments
 (0)