Skip to content

Commit 36dad35

Browse files
committed
First pass at getting new files included in the docs
1 parent ba082c1 commit 36dad35

File tree

2 files changed

+8
-1
lines changed

2 files changed

+8
-1
lines changed

docs/source/api/index.rst

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,5 +7,12 @@ API Reference
77
:template: autosummary-module.rst
88
:recursive:
99

10+
labscript.core
11+
labscript.outputs
12+
labscript.remote
13+
labscript.constants
1014
labscript.labscript
1115
labscript.functions
16+
labscript.base
17+
labscript.compiler
18+
labscript.utils

docs/source/connection_table.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ The connection table maps out the way input/output devices are connected to each
55
.. image:: img/connection_diagram.png
66
:alt: Example wiring diagram.
77

8-
Here we see two :py:class:`PseudoclockDevice <labscript.PseudoclockDevice>` instances in the top tier of the diagram. They do not have a parent device that tells them when to update their output (this is true for all :py:class:`PseudoclockDevice <labscript.PseudoclockDevice>` instances). However, all but one (the master pseudoclock device) must be triggered by an output clocked by the master pseudoclock device.
8+
Here we see two :py:class:`PseudoclockDevice <labscript.core.PseudoclockDevice>` instances in the top tier of the diagram. They do not have a parent device that tells them when to update their output (this is true for all :py:class:`PseudoclockDevice <labscript.PseudoclockDevice>` instances). However, all but one (the master pseudoclock device) must be triggered by an output clocked by the master pseudoclock device.
99

1010
Each :py:class:`PseudoclockDevice <labscript.PseudoclockDevice>` instance should have one or more :py:class:`Pseudoclock <labscript.Pseudoclock>` children. Some :py:class:`PseudoclockDevice <labscript.PseudoclockDevice>` instances may automatically create these children for you (check the device specific documentation). In turn, each :py:class:`Pseudoclock <labscript.Pseudoclock>` will have one of more :py:class:`ClockLine <labscript.ClockLine>` instances connected to it. These :py:class:`ClockLine <labscript.ClockLine>` instances generally refer to physical outputs of a device which will be used to clock another device. However, in some cases, one or more :py:class:`ClockLine <labscript.ClockLine>` instances may be internally created for you (check the device specific documentation).
1111

0 commit comments

Comments
 (0)