missing .tex

doc/slideshow.tex

+\documentclass[hyperref={colorlinks=true}]{beamer} 
+\usepackage{graphicx}
+\usepackage{amsmath}
+\usepackage[utf8]{inputenc}
+\usepackage{multicol}
+\usepackage{ulem}
+\usepackage{color}
+\usepackage{listings}
+\usepackage{wasysym}
+\useoutertheme{infolines}
+\usepackage{hangcaption}
+
+\title[Pipelet]{The Pipelet software}
+\author[Betoule, Le Jeune]{Marc \textsc{Betoule}, Maude \textsc{Le Jeune}}
+\institute[CNRS]{}
+\date[2010/09/04]{september, 4th, 2010}
+
+\newcommand{\unnumberedcaption}%
+%	{\@dblarg{\@unnumberedcaption\@captype}}
+
+\begin{document}
+
+\begin{frame}{Pipelet}
+\tableofcontents
+\end{frame}
+
+\section{From the user point of view}
+
+\begin{frame}{The pipelet big scheme}
+\begin{figure}
+\includegraphics[width=0.90\textwidth]{pipelet_scheme.pdf}
+\end{figure}
+\end{frame}
+
+
+\subsection{Building a pipeline}
+\begin{frame}[fragile]{Building a pipeline}
+
+\begin{verbatim}P = Pipeline(pipedot, codedir='./', prefix='/data/...')
+\end{verbatim}
+\begin{itemize}
+\item \verb pipedot   is the string description of the pipeline
+\begin{verbatim}pipedot = """
+1->2->4
+3->4
+"""
+\end{verbatim}
+\item \verb codedir   is the path of the processing code files (.py)
+\item \verb prefix    is the path of the processed data repository
+\end{itemize}
+\begin{figure}
+\includegraphics[width=0.50\textwidth]{pipelet_scheme_small.pdf}
+\end{figure}
+\end{frame}
+
+
+
+\subsection{Writing segment scripts}
+
+\begin{frame}[fragile]{Writing segment scripts}
+
+The default segment environment provides utilities to: 
+\begin{itemize}
+\item control the pipe parallelization scheme;
+\begin{figure}
+\includegraphics[width=0.90\textwidth]{seg_scheme.pdf}
+\end{figure}
+\item save and load I/O's and provide filenames;
+\item save and load parameters;
+\item execute or include sub processings
+\end{itemize}
+\end{frame}
+
+\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}.
+\begin{figure}
+\includegraphics[width=0.80\textwidth]{task_scheme.pdf}
+\end{figure}
+One can empty the \textcolor{blue}{task list} in different modes: 
+\begin{itemize}
+\item the interactive mode (or debugging mode)
+\item the process/thread mode 
+\item the batch mode
+\end{itemize}
+\end{frame}
+
+
+\subsection{Browsing a pipeline}
+
+\begin{frame}[fragile]{Browsing a pipeline}
+The web interface includes: 
+\begin{itemize}
+\item 
+\item
+\end{itemize}
+\href{http://localhost:8080}{http://localhost:8080}
+\end{frame}
+
+
+\section{From the developper point of view}
+
+\subsection{The pipelet actors}
+
+\begin{frame}{The pipelet actors}
+
+\end{frame}
+
+\subsection{The pipeline object}
+
+\subsection{The task object}
+
+
+
+
+\end{document}
\ No newline at end of file