From: W. Trevor King Date: Fri, 21 Jun 2013 18:47:38 +0000 (-0400) Subject: pyafm/overview.tex: Remove figure references X-Git-Tag: v1.0~32 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=b049da5615523e6e7d3dc38a5d9f3056ed73d247;p=thesis.git pyafm/overview.tex: Remove figure references Prof. Cruz points out that I don't actually discuss the figures until later sections. If I want to refer forward, I could cite the sections themselves, but it's easier to just remove these references. --- diff --git a/src/pyafm/overview.tex b/src/pyafm/overview.tex index 3930e17..7e8b335 100644 --- a/src/pyafm/overview.tex +++ b/src/pyafm/overview.tex @@ -14,20 +14,19 @@ For those of you thinking, ``Why is he calling this thing a stack?'', software is rarely developed as a single monolithic program. Instead, developers write software as a series of modular components, with each layer in the stack using lower level features from the layers below it -to supply higher level features to the layers above it -(\cref{fig:pyafm:stack}). New high-level programs will contain logic -for the new idea (perform velocity-clamp unfolding experiments) and -leverage pre-existing packages for all the old ideas that you need to -get the job done (open a file, Fourier transform an array, \ldots). A -well structured suite of software breaks up the task at hand into many -sub-components, with a distinct package handling each component. +to supply higher level features to the layers above it. New +high-level programs will contain logic for the new idea (perform +velocity-clamp unfolding experiments) and leverage pre-existing +packages for all the old ideas that you need to get the job done (open +a file, Fourier transform an array, \ldots). A well structured suite +of software breaks up the task at hand into many sub-components, with +a distinct package handling each component. \citet{whitehead11} introduces his claim about civilization and subconscious operations to motivate the utility of symbolism in subconcious reasoning. By encapsulating already established ideas in -a compact form, we can focus on the crux of an issue -(\cref{fig:unfold-protein:unfolder}) without being distracted by the -peripheral boilerplate (\cref{fig:labview}). +a compact form, we can focus on the crux of an issue without being +distracted by the peripheral boilerplate. In this chapter, I will discuss the earlier frameworks and abortive attempts that lead me towards my current architecture