% TEXINPUTS=.:$HOME/git/bvtex: latexmk  -pdf <main>.tex
\documentclass[xcolor=dvipsnames]{beamer}

\input{defaults}
\input{beamer/preamble}

\setbeamertemplate{navigation symbols}{}
% \setbeamertemplate{background}[grid][step=1cm]

\usepackage{siunitx}
\usepackage{xmpmulti}
\usepackage[export]{adjustbox}
\usepackage{ulem}
\usepackage[outline]{contour}
\usepackage{tikz}
\usetikzlibrary{shapes.geometric, arrows}
\usetikzlibrary{positioning}

\definecolor{bvtitlecolor}{rgb}{0.98, 0.92, 0.84}
\definecolor{bvoutline}{rgb}{0.1, 0.1, 0.1}

\renewcommand{\bvtitleauthor}{Brett Viren}
\renewcommand{\bvtit}{sim \& reduc}
\renewcommand{\bvtitle}{\LARGE Drift Signal Simulation and \\Data Reduction\\{\small (double feature)}}
\renewcommand{\bvevent}{\Large FD Sim/Reco\\DUNE Collaboration Meeting\\24 Jan 2017}
\renewcommand{\bvbeamerbackground}{}


\def\Put(#1,#2)#3{\leavevmode\makebox(0,0){\put(#1,#2){#3}}}


\begin{document}
\input{beamer/title.tex}
\input{beamer/toc.tex}

\section{Full TPC Drift and Signal Simulation}
\input{simdrift.tex}


\section{Proposal for Initial Data Reduction Process}

\begin{frame}
  \tableofcontents[currentsection,hideothersubsections]
\end{frame}

\input{reduc.tex}

\begin{frame}[fragile] 
  \frametitle{Implications for Reco}

  Validate Gaussian Hit Finder is okay with rebinning.
  \begin{columns}
    \begin{column}{0.6\textwidth}
      \begin{itemize}\footnotesize
      \item \textbf{Must be okay or Nyquist is wrong!}
      \item We do better than Nyquist by summing instead of resampling.
      \item Simple Gaussian fit check (thanks Xin) $\longrightarrow$
        \begin{itemize}\scriptsize
        \item $\mu=10, \sigma=2$, rebin: 1, 2, 4, 8$\times$
        \item \textbf{Recommend RB3} as safe.
        \end{itemize}
      \item Gaussian hit finder ``erases'' any signs of reduction for downstream algorithms.
      \end{itemize}
    \end{column}

    \begin{column}{0.4\textwidth}
      \begin{center}\footnotesize
        \begin{tabular}{l|r|r|r}
          \texttt{RBn} & const & $\mu$ & $\sigma$ \\
          \hline
          1 & 10.0 & 10.0 & 2.00 \\
          2 & 19.8 & 10.0 & 2.02 \\
          4 & 38.5 & 10.0 & 2.08 \\
          8 & 68.9 & 10.0 & 2.31 \\
        \end{tabular}
      \end{center}
    \end{column}
  \end{columns}

  \vfill
  Need modest development for:
  \begin{itemize}\footnotesize
  \item \textbf{Art input module} to read in reduced data
    \begin{itemize}\scriptsize
    \item[$\to$] needed for raw data in any case, reduced data will be similarly packed
    \end{itemize}
  \item \textbf{Art service interface} to the reduction code
    \begin{itemize}\scriptsize
    \item[$\to$]  ``keep up'' process uses either plain-art or stand-alone to conserve RAM.
    \item[$\to$] will run in LArSoft for applying to simulated data.
    \end{itemize}
  \end{itemize}

\end{frame}

\begin{frame} 
  \frametitle{Summary}
  \begin{description}
  \item[simulation] Technical progress on implementation for an
    \textbf{improved drift signal simulation} which allows for
    long-range induction effects and intra-wire field variations has
    been made
  \item[reduction] A \textbf{data reduction process} can give us a
    much smaller data set while keeping all useful signal.  It can be
    used by the rest of the processing chain, enable easy data sharing
    and can allow all collaborators their own copy of the entire set
    of protoDUNE signals.
  \end{description}

  \vfill

  \footnotesize
  $\rightarrow$ later, need to understand how these ideas might apply to DUNE FD.

\end{frame}


\end{document}

%%% Local Variables:
%%% mode: latex
%%% TeX-master: t
%%% End:
