\documentclass[xcolor=dvipsnames]{beamer}

\setbeamertemplate{navigation symbols}{}
% \setbeamertemplate{background}[grid][step=1cm]
\useoutertheme{infolines}
\usecolortheme[named=violet]{structure}
\setbeamertemplate{items}[circle]

\usepackage{tikz}
\usetikzlibrary{arrows,shapes,backgrounds}
\usepackage{listings}
\usepackage{graphicx}
\usepackage{color}
\usepackage{hyperref}

\author[Brett Viren]{Brett Viren}
\institute[BNL]
{
  Physics Department
  
  \includegraphics[height=1.5cm]{bnl-logo}
}
\title[LBNE Install]{LBNE Software Installation System Status and Issues}
%\date[Short Date/Event]{Long Date/Event}

\newcommand{\fixme}[1]{\textbf{FIXME:} \textit{#1}}

\begin{document}


\lstset{%
  emphstyle=\color{red},
  keywordstyle=\color{black}\bfseries,
  basicstyle=\footnotesize,
  identifierstyle=\color{DarkOrchid}\ttfamily,
  commentstyle=\color{Brown}\ttfamily,
  stringstyle=\color{blue}\ttfamily,
  showstringspaces=false}

\begin{frame}
  \titlepage
\end{frame}


\begin{frame}[fragile]
  \frametitle{LBNE Software Installation Problem Space}

  \begin{itemize}
  \item $\sim$40 externals, $\sim$5 LBNE sub-suites
    \begin{itemize}
    \item build tools: CMake and bleeding edge GCC (!)
    \item large HEP packages (Geant4, ROOT, GENIE)
    \item Python, Boost both PostgreSQL and MySQL, gccxml, ...
    \item A large framework: art + larsoft (+artdaq for online)
    \item LBNE: FD/ND/Beam/Fast simulation, detector reconstruction projects
    \end{itemize}
  \item Multi-national, distributed collaboration
  \item Multiple platforms: at least Sci. Linux, Deb/Ubu, Mac OS X
  \item Require, roughly in order of decreasing importance:
    \begin{enumerate}
    \item Control versions independently from other experiments.
    \item Facilitate any collaborator building all relevant software
      from pristine sources on all supported platforms.
    \item Provide pre-built binaries.
    \end{enumerate}
  \end{itemize}
 
\end{frame}

\begin{frame}
  \frametitle{LBNE Software Installation System}

  \begin{center}
    ``worch = waf + orchestration''     
  \end{center}

  \begin{itemize}
  \item Meta-build system using a package's native build mechanisms \
    (eg. autoconf, cmake, etc)
  \item Flexible (meta) configuration system
    \begin{itemize}
    \item installation directory layout patterns
    \item manages package versioning and overall build versioning
    \item organization: groups of packages, suites of groups
    \item express inter-package dependencies
    \item details of build flags, environment.
    \end{itemize}
  \item fine grained, sub-package parallel building (beyond
    ``\texttt{make -jN}'')
  \item Installation requires downloading a single file and running two commands.

  \item Being used outside of LBNE (ORKA and collaborating with ATLAS)
  \end{itemize}

  Development at: \url{https://github.com/brettviren/worch}

\end{frame}

\begin{frame}
  \frametitle{User Environment with ``worch''}
  \begin{itemize}
  \item Unified installation and environment configuration file set
  \item Multiple environment setup systems supported.  So far:
    \begin{description}
    \item[UPS] FNAL-centric system for user environment setup
      \begin{itemize}
      \item Used for user environment setup on fnal.gov machines
      \item Somewhat cryptic configuration language
      \item Sprinkled dependencies in FNAL installation ``system''
      \item Essentially is required to build Art.
      \end{itemize}
    \item[modules] Environment modules (\url{http://modules.sf.net/}
      \begin{itemize}
      \item Free Software, community supported
      \item Uses a ``real'' language (well, at least TCL)
      \item Already in use by some LBNE collaborators (PDSF)
      \end{itemize}
    \end{description}
  \end{itemize}

  Worch does not require a user environment system to build.  They are
  added as just another build ``feature''.

  \textbf{However....}
\end{frame}

\begin{frame}
  \frametitle{The problem with UPS and Art}
  \begin{itemize}
  \item Art is the de facto software framework for LBNE offline (and
    online/DAQ?) at this time.
  \item It is built with CMake.  That's great, however:
  \item Its CMake files require UPS.
  \item This greatly hampers building it outside of FNAL
  \item Building Art, itself, has posed more problems than all other externals combined.
  \end{itemize}
  Possible solutions:
  \begin{itemize}
  \item Rewrite Art's native build system to be independent from UPS
    \begin{itemize}
    \item Art developers are not interested
    \item Large effort for an outsider, always needing to chase differences 
    \end{itemize}
  \item ``Fake'' UPS and Art is non-the-wiser.  
    \begin{itemize}
    \item Probably more effort than the next solution:
    \end{itemize}
  \item Provide for UPS to be used by worch installation elements
    \begin{itemize}
    \item \textbf{This is the approach I'm talking now.}
    \end{itemize}
  \end{itemize}
\end{frame}

\begin{frame}
  \frametitle{Expected Time Line}

  \begin{itemize}
  \item Worch ``works'' now.  
    \begin{itemize}
    \item It builds non-art, LBNE sub-suites.
    \item It builds ORKA's Geant4/ROOT simulation/analysis application
    \end{itemize}
  \item Building Art and Larsoft will take more effort.
  \item If this can't be done in 1-2 months I may give up.
    \begin{itemize}
    \item If I give up, I fully expect that we must rely on FNAL to
      provide binary-only.
    \item We loose the ability to just fix things ourselves.
    \item A single person is currently doing this spread across Nova,
      Mu2e, Darkside50 and other FNAL neutrino experiments.  LBNE
      would need to compete for attention.
    \end{itemize}
  \end{itemize}
  Of course, help wanted.

  \begin{itemize}
  \item Try building non-art suites.
  \item Try new platforms (so far SL6 and Debian)
  \item Get involved in solving ``The Art/UPS problem''
  \item Help incorporate building LArSoft (its current build system and repository location are changing and I've not ``gone there'' yet).
  \end{itemize}
\end{frame}

\end{document}
