\documentclass[presentation,9pt]{beamer}
% Replacing 'presentation' with 'handout' in the above line
% will produce 4 slides per page.
% The hyperref option makes it possible to include hyperlinks.

\mode<presentation> {
\usetheme{Boadilla}
\setbeamercovered{transparent}
}

\usepackage[english]{babel}
\usepackage[latin1]{inputenc}
\usepackage{times}
\usepackage[T1]{fontenc}
%\usepackage{wrapfig}
\usepackage{amsmath}

\mode<handout>{
\usepackage{pgfpages}
\pgfpagesuselayout{4 on 1}[letterpaper,landscape,border shrink=5mm]
\setbeamercolor{background canvas}{bg=black!10} }

\setbeamertemplate{footline}
{
\leavevmode%
\hbox{%
\begin{beamercolorbox}[wd=.333333\paperwidth,ht=2.25ex,dp=1ex,center]{author
	in head/foot}%
	\usebeamerfont{author in head/ foot}\insertshortauthor%&\approx& (\insertshorti
\end{beamercolorbox}%
\begin{beamercolorbox}[wd=.333333\paperwidth,ht=2.25ex,dp=1ex,center]{title
	in head/foot}%
	\usebeamerfont{title in head/foot}\insertshorttitle
\end{beamercolorbox}%
\begin{beamercolorbox}[wd=.333333\paperwidth,ht=2.25ex,dp=1ex,right]{date in
	head/foot}%
	\usebeamerfont{date in head/foot}\insertshortdate\hspace*{2em}
	\insertframenumber / \inserttotalframenumber\hspace*{2ex}
\end{beamercolorbox}}%
\vskip0pt%
}

\newcommand{\backupbegin}{
\newcounter{framenumberappendix}
\setcounter{framenumberappendix}{\value{framenumber}}
}
\newcommand{\backupend}{
\addtocounter{framenumberappendix}{-\value{framenumber}}
\addtocounter{framenumber}{\value{framenumberappendix}} 
}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%\title[GEANT4/EGS5]{GEANT4/EGS5}

\title{MVTX progress report}

\author{Sho Uemura}
%\institute{bumming around}
\date[July 27, 2017]

%\titlegraphic{
%\includegraphics[height=0.1\textheight]{SLAC_Logo}\hspace*{4.75cm}~
%\includegraphics[height=0.1\textheight]{partner_logo_v2}
%}

\begin{document}

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

\begin{frame}{Interface to sPHENIX}
    \begin{itemize}
        \item Goal: understand sPHENIX infrastructures, and build our software and firmware to work with sPHENIX
            \begin{itemize}
                \item We are bridging two systems that have been defined for us: ALICE ITS and sPHENIX. This subtask deals with the sPHENIX side and the ``glue,'' other subtasks deal with work to be done on the ITS/MVTX side (including FELIX).
                \item BNL has promised significant help related to integrating FELIX with sPHENIX (sPHENIX TPC is also using FELIX)
            \end{itemize}
        \item DAQ: Need to get data from FELIX card to sPHENIX DAQ
            \begin{itemize}
                \item Plan: Develop an rcdaq plugin for MVTX (rcdaq is a lightweight DAQ system meant to be compatible with the PHENIX/sPHENIX DAQ), develop file format and analysis/monitoring software
                    \begin{itemize}
                        \item This will be our test beam DAQ
                        \item It is promised that if we have MVTX working with rcdaq, integration work with the ``real'' sPHENIX DAQ will be minimal
                        \item BNL has promised to write a basic rcdaq plugin for FELIX
                    \end{itemize}
            \end{itemize}
        \item Timing, trigger, control (TTC): FELIX must use the sPHENIX system instead of the ATLAS system
            \begin{itemize}
                \item FELIX v2.0 will have a ``timing mezzanine'' card, with ATLAS and sPHENIX options: BNL will take care of this
                \item FELIX can lock its clocks to either the 40 MHz LHC clock or the 10 MHz RHIC clock, so RU and ALPIDE don't see any difference
            \end{itemize}
        \item Detector control system (DCS): need to insert detector status data in DAQ
    \end{itemize}
\end{frame}

\begin{frame}{Readout firmware}
    \begin{itemize}
        \item Goal: develop firmware for RU and FELIX with all necessary functions (DAQ, TTC, DCS)
            \begin{itemize}
                \item Ideally we will not need to make any changes to the RU firmware: the only change to the RU interfaces is that the ALICE CRU and LTU are both replaced by the FELIX
            \end{itemize}
        \item We can compile the provided FELIX firmware
            \begin{itemize}
                \item Given to us: GBT links to communicate with RU, DMA engine to push data out through PCIe
                \item What we need to do: recognize, package, and compress data coming from the RU, configure, control, and trigger the RU
                \item So far we can put fake data on a GBT output, loop it back on a fiber to a GBT input, push it to PCIe and write it to disk using FELIX software
                \item Next step: take all the GBT inputs, mux+pack data so we can read out all links over PCIe
            \end{itemize}
        \item Asked ALICE firmware group for firmware source access so we can start to understand the RU and CRU functions
    \end{itemize}
\end{frame}

\begin{frame}{Detector control system (DCS)}
    \begin{itemize}
        \item FELIX should:
            \begin{itemize}
                \item Monitor and configure the ALPIDE chips (through the RU)
                \item Monitor and control the RU, and remotely program the RU firmware
                \item Monitor and control the power boards (through the RU)
            \end{itemize}
        \item Also: CAEN bulk power supplies, cooling system
        \item RU uses GBT-SCA chip for monitoring, control, and remote programming; FELIX has built-in support for communicating to GBT-SCA, we need to add specific RU support (some combination of firmware and software)
        \item CAEN power supplies are here
    \end{itemize}
\end{frame}

\begin{frame}{FireFly cable test w/ MOSAIC}
    \begin{itemize}
        \item We need to know whether the readout will still work with possible changes to the stave readout (longer twinax cables, extension to the flex circuit)
        \item Key measure of performance is the ``eye diagram'' (see below, from CERN tests of IB HIC)
        \item MOSAIC developers at INFN gave us example code for running eye scans using the MOSAIC test system: this should work for us with minor changes
        \item We can also use an oscilloscope with high-speed differential probe: expected in the next week or two
    \end{itemize}

    \begin{center}
        \includegraphics[width=0.8\textwidth]{ib_eye_wp10-edr.png}
    \end{center}
\end{frame}

%\begin{frame}{Fix vertex fit}
%\begin{columns}
%\column{0.6\textwidth}
%\begin{itemize}
%\item The resolution of the reconstructed mass should be independent of Z but is worse for displaced vertices.
%\item This ad-hoc correction works pretty well: corrM = uncM - 0.15e-3*(elePX/eleP-posPX/posP)*uncVZ/uncM
%\item Hunch: the vertex mass is being calculated using the track directions at $z=0$, or something like that.
%\end{itemize}
%\begin{center}
%\includegraphics[width=\textwidth]{mass_shift_40}
%\end{center}
%\column{0.4\textwidth}
%\includegraphics[width=\textwidth,page=4]{acceptance_40}
%
%\includegraphics[width=\textwidth,page=5]{acceptance_40}
%\end{columns}
%\end{frame}

\end{document}