aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBlaise Thompson <blaise@untzag.com>2018-04-10 10:02:48 -0500
committerBlaise Thompson <blaise@untzag.com>2018-04-10 10:02:48 -0500
commit7870759e32cc48fc456f07127e841c8a3f3fa236 (patch)
tree715dd6286b066531ee6b43948be16a93ce81844e
parent628159e39a06da2a75b3b17f8dbf05cfc57de834 (diff)
2018-04-10 10:02
-rw-r--r--acquisition/chapter.tex7
1 files changed, 7 insertions, 0 deletions
diff --git a/acquisition/chapter.tex b/acquisition/chapter.tex
index 5981e22..ab1793d 100644
--- a/acquisition/chapter.tex
+++ b/acquisition/chapter.tex
@@ -474,6 +474,8 @@ They sometimes have an offset, as specified by the autonomic system
Each hardware can be thought of as a dimension of the MR-CMDS experiment, and scans include a
specific traversal through this multidimensional space. %
+In this section I briefly discuss PyCMDS' implementation for each type of hardware. %
+
\subsection{Hardware inheritance} % --------------------------------------------------------------
All hardware classes are children of the parent \python{Hardware} class
@@ -492,6 +494,11 @@ methods:
\item \python{@property units}
\end{ditemize}
+\autoref{aqn:fig:hardware_inheritance} shows the full inheritance tree, including all nine types of
+hardware currently supported by PyCMDS. %
+In general the nesting is type/model, although there can be additional levels of nesting when
+required, as can be seen in the case of OPA/TOPAS/TOPAS-C and OPA/TOPAS/TOPAS-800. %
+
\begin{figure}
\includepython{"acquisition/hardware.py"}
\caption[Parent hardware class.]{