Docker-in-Docker (DinD) capabilities of public runners deactivated. More info

Commit 6a8248a1 authored by Maude Le Jeune's avatar Maude Le Jeune
Browse files

missing .tex

parent aafa7211
\title[Pipelet]{The Pipelet software}
\author[Betoule, Le Jeune]{Marc \textsc{Betoule}, Maude \textsc{Le Jeune}}
\date[2010/09/04]{september, 4th, 2010}
% {\@dblarg{\@unnumberedcaption\@captype}}
\section{From the user point of view}
\begin{frame}{The pipelet big scheme}
\subsection{Building a pipeline}
\begin{frame}[fragile]{Building a pipeline}
\begin{verbatim}P = Pipeline(pipedot, codedir='./', prefix='/data/...')
\item \verb pipedot is the string description of the pipeline
\begin{verbatim}pipedot = """
\item \verb codedir is the path of the processing code files (.py)
\item \verb prefix is the path of the processed data repository
\subsection{Writing segment scripts}
\begin{frame}[fragile]{Writing segment scripts}
The default segment environment provides utilities to:
\item control the pipe parallelization scheme;
\item save and load I/O's and provide filenames;
\item save and load parameters;
\item execute or include sub processings
\subsection{Running a pipeline}
\begin{frame}[fragile]{Running a pipeline}
The pipe engine converts each pair of (processing code, data to
process) into a \textcolor{blue}{task list}.
One can empty the \textcolor{blue}{task list} in different modes:
\item the interactive mode (or debugging mode)
\item the process/thread mode
\item the batch mode
\subsection{Browsing a pipeline}
\begin{frame}[fragile]{Browsing a pipeline}
The web interface includes:
\section{From the developper point of view}
\subsection{The pipelet actors}
\begin{frame}{The pipelet actors}
\subsection{The pipeline object}
\subsection{The task object}
\ No newline at end of file
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