Single molecule force spectroscopy (SMFS) provides an experimental
-window the mechanics and kinetics of individual molecules and domains.
-Single molecule measurements extend bulk measurements, by offering
-insight into the variations within a population of molecules in
-addition to insight into the aggregate behavior of bulk solutions.
+window on the mechanics and kinetics of individual molecules and
+domains. Single molecule measurements extend bulk measurements, by
+offering insight into the variations within a population of molecules
+in addition to insight into the aggregate behavior of bulk solutions.
They also bridge the gap between chemists experimenting at the bulk
level and theorists simulating at the amino-acid level. By providing
data for comparison, SMFS lays the ground work for improving and
Open source experiment control is possible! Even for a small lab,
with a single novice developer\footnote{
- I started this project a bit of LabVIEW and Matlab experience, but
- only a few days of Python from the physics department's ``Welcome to
- Drexel'' boot camp. I stumbled across version control on my own,
- after a year of maintaining a directory full of version-stampted
- tarballs.
-
-}, building reasonable software on top of existing pieces is possible.
+ I started this project with a bit of LabVIEW and Matlab experience,
+ but only a few days of Python from the physics department's
+ ``Welcome to Drexel'' boot camp. I stumbled across version control
+ on my own, after a year of maintaining a directory full of
+ version-stampted tarballs.
+},
+building reasonable software on top of existing pieces is possible.
After a significant investment in developing
\sawsim\ (\cref{sec:sawsim}), the \pyafm\ stack
(\cref{sec:pyafm,sec:calibcant}), and \Hooke\ (\cref{sec:hooke}), we
have a complete experiment control and analysis suite for single
molecule force spectroscopy. All of the software in the
-stack---including the existing libraries and systems layers that I've
-built on---is open source, so other labs are free to use, improve, and
-republish it as they see fit.
+stack---including the existing libraries and systems layer
+dependencies---is open source, so other labs are free to use, improve,
+and republish it as they see fit.
As the body of existing science increases, new researchers must become
at the same time more specialized and more interdisciplinary than
generating their figure. Do you think I'm not calibrating my
cantilevers correctly? Feel free to dig through my code. Let me know
if you find something wrong (or fix it and send me a patch!). Science
-is built on reproducible experiments and analysis, and open sourcce
+is built on reproducible experiments and analysis, and open source
software allows you to explicitly specify your methods. With well
-organized code, the specification should be clear from a high-level,
+organized code, the specification should be clear from high-level,
experiment-design choices down through low-level bit manipulation.
Many researchers have not received formal training in software
tool or workflow, but learning that it exists at all. There are a
number of papers highlighting best practices and tools that are good
surveys for guiding future
-learing\citep{wilson06a,wilson06b,vandewalle09,aruliah12}.
+learning\citep{wilson06a,wilson06b,vandewalle09,aruliah12}.