From: W. Trevor King <wking@tremily.us>
Date: Thu, 16 May 2013 01:58:40 +0000 (-0400)
Subject: pyafm/stack.tex: Reference fig:calibcant:stack from fig:pyafm:stack
X-Git-Tag: v1.0~186
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=4f023dc55398d912ebf2e2b46a79c9720cbcf4c5;p=thesis.git

pyafm/stack.tex: Reference fig:calibcant:stack from fig:pyafm:stack

And mention that unfold-protein holds the control logic.
---

diff --git a/src/pyafm/stack.tex b/src/pyafm/stack.tex
index c7a6ffb..93be6d8 100644
--- a/src/pyafm/stack.tex
+++ b/src/pyafm/stack.tex
@@ -15,12 +15,15 @@ spectroscopy (\cref{fig:pyafm:stack}).
 \begin{figure}
   \tikzstack{}{black!20}
   \caption{Dependency graph for my modular experiment control stack.
-    The dashed line (\tikzline{black!20,dashed}) separates the
-    software components (on the left) from their associated hardware
-    (on the right).  The data flow between components is shown with
-    arrows.  For example, the \stepper\ package calls \pycomedi, which
-    talks to the DAQ card, to write digital output that controls the
-    stepper motor (\tikzline{blue,->}, \cref{sec:pyafm:stepper}).  The
+    The \unfoldprotein\ package controls the experiment, but the same
+    stack is used by \calibcant\ for cantilever calibration
+    (\cref{fig:calibcant:stack}).  The dashed line
+    (\tikzline{black!20,dashed}) separates the software components (on
+    the left) from their associated hardware (on the right).  The data
+    flow between components is shown with arrows.  For example, the
+    \stepper\ package calls \pycomedi, which talks to the DAQ card, to
+    write digital output that controls the stepper motor
+    (\tikzline{blue,->}, \cref{sec:pyafm:stepper}).  The
     \pypiezo\ package, on the other hand, uses two-way communication
     with the DAQ card (\tikzline{red,<->}), writing driving voltages
     to position the piezo and recording photodiode voltages to monitor