Skip to content

O
OHR Meta Project
Commit 2019ba3d authored by Javier Serrano's avatar Javier Serrano
Browse files
Options

First two sections

parent d6efe3ff
Show whitespace changes
Inline Side-by-side
Showing with 60 additions and 146 deletions
presentations/cern_ospo_2023/cern_ospo_2023_11.tex
View file @ 2019ba3d
...@@ -48,6 +48,7 @@ ...@@ -48,6 +48,7 @@
\usepackage[english]{babel} \usepackage[english]{babel}
\usepackage[utf8]{inputenc} \usepackage[utf8]{inputenc}
\usepackage{multirow} \usepackage{multirow}
\usepackage{xcolor}
%\usepackage{pgfpages} %\usepackage{pgfpages}
%%%%%%%%%%%%5 %%%%%%%%%%%%5
%\usepackage{geometry} %\usepackage{geometry}
...@@ -63,11 +64,11 @@ ...@@ -63,11 +64,11 @@
\graphicspath{ {../../figures/} } \graphicspath{ {../../figures/} }
\title[The CERN OSPO\hspace{15em}\insertframenumber/\inserttotalframenumber] \title[Open Source at CERN: our OSPO\hspace{9em}\insertframenumber/\inserttotalframenumber]
{Open Source at CERN: our OSPO} {Open Source at CERN: our OSPO}
%\subtitle{} %\subtitle{}
\author \author[CERN OSPO Team]
{Javier Serrano on behalf of the CERN OSPO Team} {Javier Serrano on behalf of the CERN OSPO Team}
% - Give the names in the same order as the appear in the paper. % - Give the names in the same order as the appear in the paper.
...@@ -134,21 +135,9 @@ ...@@ -134,21 +135,9 @@
\end{frame} \end{frame}
\section[Intro to CERN]{Introduction to CERN} \section[Introduction]{Introduction}
\subsection{} \subsection{}
\begin{frame}{Accelerators}
\begin{center}
\includegraphics[height=0.85\textheight]{misc/accelerator_map.jpg}
\end{center}
\end{frame}
%% \begin{frame}{Detectors}
%% \begin{center}
%% \includegraphics[height=0.85\textheight]{misc/atlas.jpeg}
%% \end{center}
%% \end{frame}
\begin{frame}{Dissemination} \begin{frame}{Dissemination}
\begin{center} \begin{center}
\includegraphics[height=0.8\textheight]{misc/cern_council.jpg} \includegraphics[height=0.8\textheight]{misc/cern_council.jpg}
...@@ -162,155 +151,80 @@ ...@@ -162,155 +151,80 @@
\end{center} \end{center}
\end{frame} \end{frame}
\begin{frame}{The CERN OSPO}
The CERN OSPO is an open and inclusive service, working internally across
departments with and for the entire CERN community, and externally as a
visible interface to potential partners and the interested public. It is a
consultation body providing advice.\\See {\color{blue}
\href{https://cds.cern.ch/record/2879995}{https://cds.cern.ch/record/2879995}}
for its abridged mandate.
\section[OSHW at CERN]{Open Hardware at CERN} \end{frame}
\subsection{}
%% \begin{frame}{The need for synchronisation in a particle accelerator} \begin{frame}{Our mandate in a nutshell}
%% \begin{center} \begin{block}{Internally}
%% \includegraphics[height=6.5cm]{misc/synchrotron.jpg}
%% \end{center}
%% \end{frame}
%% \begin{frame}{White Rabbit: an \emph{extension} of Ethernet}
%% \begin{columns}[c]
%% \column{.5\textwidth}
%% \begin{itemize}
%% \item Standard Ethernet network
%% \item Ethernet features (VLAN) \& protocols (SNMP)
%% \end{itemize}
%% \begin{itemize}
%% \item \color{Blue}{Sub-ns synchronisation}
%% \item \color{Red}{Guaranteed (by design) upper bound in frame latency}
%% \end{itemize}
%% \column{.6\textwidth}
%% \begin{center}
%% \includegraphics[height=1.05\textwidth]{network/wr_network-enhanced_pro.jpg}
%% \end{center}
%% \end{columns}
%% \end{frame}
\begin{frame}[t,fragile]{White Rabbit Switch}
\begin{center}
\includegraphics[width=\textwidth]{switch/wrSwitch_v3_3.jpg}
\begin{itemize} \begin{itemize}
\item Central element of WR network \item Consult, advise, train on Open Source best practices,
\item 18 port gigabit Ethernet switch with WR features tools, licenses, etc.
\item Advise on open-sourcing CERN software, gateware and hardware.
\item Fully open design, commercially available \item Identify/track FOSS dependencies for critical services.
\item Advise CERN management on Open Source matters.
\end{itemize} \end{itemize}
\end{center} \end{block}
\end{frame}
\begin{frame}{WR Node: SPEC board}
\begin{center}
\includegraphics[width=7cm]{node/spec.jpg}
\end{center}
\begin{columns}[c]
\column{.01\textwidth}
\column{.98\textwidth}
\begin{block}{Carrier/mezzanine Hardware Kit} \begin{block}{Externally}
\begin{itemize} \begin{itemize}
% \item Carrier boards in PCI-Express, VME, PXIe \item Showcase CERN contributions to Open Source.
\item All carrier cards are equipped with a White Rabbit port \item Facilitate partnerships with external entities.
\item Mezzanines provide different functions (e.g. ADC) \item Promote CERN as an Open Source lab.
\end{itemize} \end{itemize}
\end{block} \end{block}
\column{.01\textwidth}
\end{columns}
\end{frame}
%% \begin{frame}{White Rabbit application examples}
%% \begin{columns}[c] \end{frame}
%% \column{0.7\textwidth}
%% \begin{itemize}
%% \item<1-> \color<2->{black!50}{CERN and GSI}
%% \item<2-> \color<3->{black!50}{The Large High Altitude Air Shower Observatory}
%% \item<3-> \color<4->{black!50}{KM3NET: European deep-sea neutrino telescope}
%% \item<4-> {MIKES: Centre for metrology and accreditation}
%% \end{itemize}
%% \column{0.45\textwidth} \section[Why]{Why an OSPO}
%% \begin{center} \subsection{}
%% \includegraphics<1>[width=0.80\textwidth]{applications/gsiANDcern.pdf}
%% \pause
%% \includegraphics<2>[width=1\textwidth]{applications/lhaaso.pdf}
%% \pause
%% \includegraphics<3>[width=1\textwidth]{applications/KM3NeT.pdf}
%% \pause
%% \includegraphics<4->[width=.5\textwidth]{applications/mikes.pdf}
%% \end{center}
%% \end{columns} \begin{frame}{To answer recurrent questions}
%% \pause \begin{block}{From designers/developers}
%% {\small Now also finance, telecom, energy distribution\ldots} ``I want to open-source my work. How should I do it? How to
%% \end{frame} find the time to open-source right? How to create and nurture a thriving
community around my project?''
\end{block}
\begin{frame}{Open source and standardisation} \end{frame}
White Rabbit is now standardised under IEEE 1588 \begin{frame}{To answer recurrent questions}
\begin{block}{Benefits} \begin{block}{From management}
\begin{itemize} ``How are we
\item Inertia! fulfilling our Open Science mandate as regards software and hardware? What pieces of open-source software do we
\item Impact strategically depend on? How are we making sure they are sustainable?''
\end{itemize}
\end{block}
\pause
\begin{block}{Issues}
\begin{itemize}
\item It takes a lot of effort
\item There is a fundamental tension between standard-essential patents and
reciprocal (or all?) open source licences
\end{itemize}
\end{block} \end{block}
\end{frame} \end{frame}
\begin{frame}{To answer recurrent questions}
\section{Some thoughts on public-private partnerships} \begin{block}{From outside CERN}
\subsection{} ``What is CERN's contribution to the world in software and hardware? What
is the position of CERN on issue xyz related to Open Source?''
\end{block}
\begin{frame}{Public-private partnerships}
\begin{block}{Business models}
\begin{itemize}
\item For this type of hardware, selling support (as often happens in
software) does not seem to be a sucessful model so far
\item Proprietary customisation is
\item Issues with patents
\item Should imitate Open Silicon efforts on two fronts:
\begin{itemize}
\item Get organised through a non-profit (foundation, consortium,
collaboration\ldots)
\item Involve commercial actors who are \emph{users} of the technology
\end{itemize}
\end{itemize}
\end{block}
\end{frame} \end{frame}
\begin{frame}{Public-private partnerships}
\begin{block}{Roles}
\begin{itemize}
\item Partnerships work best when actors are expected to do things which
are ``natural'' for them
\item Need to work more on the public side
\end{itemize}
\end{block}
Referring to the title of this presentation: you are \emph{already} \section[Interlude]{Interlude: some CERN examples of Open Source}
funding these labs and universities with public money. Ask them (and \subsection{}
make it easier for them) to open-source their work.
\end{frame} \section[How]{How the OSPO will operate}
\subsection{}
\section[Who]{The team}
\subsection{}
\end{document} \end{document}
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