Commit a8786ab1 authored by Turnhout, M.C. van's avatar Turnhout, M.C. van
Browse files

typo

parent 5c3e0e3d
......@@ -4,12 +4,13 @@ Feel it in the one drop; And we'll still find time to rap; \qauthor{Bob Marley \
\end{savequote}
\chapter{Under the hood}\label{hood}
As mentioned in chapter \ref{workflow}, a image-stack analysis consists of four steps: droplet tracing (\texttt{BF}), fluorescence image pre-processing (\texttt{fluo}), cell counting (\texttt{ncel}) and events parsing (\texttt{dcel}). These steps are taken care of by \DMA{analyseFoV}:
As mentioned in chapter \ref{workflow}, an image-stack analysis consists of four steps: droplet tracing (\texttt{BF}), fluorescence image pre-processing (\texttt{fluo}), cell counting (\texttt{ncel}) and events parsing (\texttt{dcel}). These steps are taken care of by \DMA{analyseFoV}:
\vspace*{-.4em}\begin{lstlisting}[language=DMAlab, numbers=none]
[BF, fluo, ncel, dcel] = DMA_analyseFoV;
\end{lstlisting}
where \DMA{analyseFoV} calls \DMA{analyseevents} after the stack analysis to get \texttt{dcel}.
In addition, it is possible to get an overview of the \texttt{ncel} and \texttt{dcel} results for the entire directory with image-stacks. This overview is created by \DMA{collectdir}.\\
In this chapter, we will briefly describe what \dmalab\ actually `does' in each step.\\
......@@ -184,5 +185,5 @@ The area is assumed to be a circle with a certain radius so that the circles are
\noindent \DMA{analyseevents} writes its results to the \texttt{dcel} file in \param{odir} (section \ref{outputdcel}).
\section{Directory summary}
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment