Commit 1c95a62e authored by Javier Serrano's avatar Javier Serrano

OpenChain Webinar presentation

parent 896d7aa3
all : js_open_chain_2021_07.pdf
.PHONY : all clean
js_open_chain_2021_07.pdf : js_open_chain_2021_07.tex
pdflatex $^; \
pdflatex $^
clean :
rm -f *.vrb *.eps *.pdf *.dat *.log *.out *.aux *.dvi *.ps *.toc *.snm *.nav *~
\documentclass[compress,red]{beamer}
%\documentclass[compress,red, handout]{beamer}
\mode<presentation>
\setbeamertemplate{navigation symbols}{}
\usetheme{Warsaw}
%\hypersetup{pdfpagemode=FullScreen} % makes your presentation go automatically to full screen
% define your own colors:
\definecolor{Red}{rgb}{1,0,0}
\definecolor{Blue}{rgb}{0,0,1}
\definecolor{Green}{rgb}{0,1,0}
\definecolor{magenta}{rgb}{1,0,.6}
\definecolor{lightblue}{rgb}{0,.5,1}
\definecolor{lightpurple}{rgb}{.6,.4,1}
\definecolor{gold}{rgb}{.6,.5,0}
\definecolor{orange}{rgb}{1,0.4,0}
\definecolor{hotpink}{rgb}{1,0,0.5}
\definecolor{newcolor2}{rgb}{.5,.3,.5}
\definecolor{newcolor}{rgb}{0,.3,1}
\definecolor{newcolor3}{rgb}{1,0,.35}
\definecolor{darkgreen1}{rgb}{0, .35, 0}
\definecolor{darkgreen}{rgb}{0, .6, 0}
\definecolor{darkred}{rgb}{.75,0,0}
\xdefinecolor{olive}{cmyk}{0.64,0,0.95,0.4}
\xdefinecolor{purpleish}{cmyk}{0.75,0.75,0,0}
\useoutertheme[subsection=false]{smoothbars}
% include packages
\usepackage{subfigure}
\usepackage{multicol}
\usepackage{amsmath}
% \usepackage{epsfig} % Erik: didn't work with Miktex
\usepackage{graphicx}
\usepackage[all,knot]{xy}
\xyoption{arc}
\usepackage{url}
\usepackage{multimedia}
\usepackage{hyperref}
\usepackage{helvet}
\usepackage[english]{babel}
\usepackage[utf8]{inputenc}
\usepackage{multirow}
%%%%%%%%%%%%5
%\usepackage{geometry}
%\geometry{verbose,letterpaper}
%\usepackage{movie15}
%\usepackage{hyperref}
\graphicspath{ {../../figures/} }
\title[Open Source Hardware at CERN\hspace{10em}\insertframenumber/\inserttotalframenumber]
{Open Source Hardware at CERN}
\subtitle{A quick introduction}
\author
{Javier Serrano}
% - Give the names in the same order as the appear in the paper.
% - Use the \inst{?} command only if the authors have different
% affiliation.
\institute%[Universities of Somewhere and Elsewhere] % (optional, but mostly needed)
{
%\inst{1}%
% BE-CO Hardware and Timing section\\
CERN, Geneva, Switzerland
%\and
%\inst{2}%
%Department of Theoretical Philosophy\\
%University of Elsewhere
}
% - Use the \inst command only if there are several affiliations.
% - Keep it simple, no one is interested in your street address.
\date[OpenChain Bi-Weekly Webinar] %(optional, should be abbreviation of conference name)
{OpenChain Bi-Weekly Webinar\\
6 July 2021
}
% - Either use conference name or its abbreviation.
% - Not really informative to the audience, more for people (including
% yourself) who are reading the slides online
%\subject{Theoretical Computer Science}
% This is only inserted into the PDF information catalog. Can be left
% out.
% If you have a file called "university-logo-filename.xxx", where xxx
% is a graphic format that can be processed by latex or pdflatex,
% resp., then you can add a logo as follows:
%\pgfdeclareimage[height=1cm]{ohr-logo}{ohr_logo.jpg}
%\logo{\pgfuseimage{ohr-logo}}
% Delete this, if you do not want the table of contents to pop up at
% the beginning of each subsection:
%% \AtBeginSection[]
%% {
%% \begin{frame}<beamer>{Outline}
%% \tableofcontents[currentsection]
%% \end{frame}
%% }
\AtBeginSubsection[]
{
\begin{frame}
\frametitle{Table of Contents}
\tableofcontents[currentsection,currentsubsection]
\end{frame}
}
% If you wish to uncover everything in a step-wise fashion, uncomment
% the following command:
%\beamerdefaultoverlayspecification{<+->}
\begin{document}
\begin{frame}
\titlepage
\end{frame}
\begin{frame}{Outline}
\tableofcontents
% You might wish to add the option [pausesections]
\end{frame}
\section[CERN]{Introduction to CERN}
\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{center}
\includegraphics[height=0.8\textheight]{misc/cern_council.jpg}
\end{center}
\end{frame}
\begin{frame}{How to interpret one's dissemination mandate in the 21\textsuperscript{st}
century}
\begin{center}
\includegraphics[height=0.8\textheight]{misc/cern_and_openness.jpg}
\end{center}
\end{frame}
\section{Open Source Hardware}
\subsection{}
\begin{frame}{Democratisation}
\begin{center}
\includegraphics[height=0.85\textheight]{misc/ben_with_talon_beast.jpg}
\end{center}
\end{frame}
\begin{frame}{OSHW definition}
\begin{block}{Check out \href{http://www.oshwa.org/definition/}{http://www.oshwa.org/definition/}}
\begin{itemize}
\item Inspired by the Open Source definition for software
\item Focuses on ensuring freedom to study, modify, distribute, make
and sell designs or hardware based on those designs
\end{itemize}
\end{block}
\end{frame}
\begin{frame}{Challenges we saw in Open Hardware ten years ago}
\begin{itemize}
\item Curated repositories of \textbf{high-quality designs} with version control and
forums
\item Discussions with commercial companies on \textbf{business models}
\item \textbf{Free and Open Source Software tools} to design hardware and easily share
those designs
\item A sound legal basis for sharing in the form of a good set of \textbf{Open
Hardware Licences}
\end{itemize}
\end{frame}
\begin{frame}{The importance of FOSS tools for hardware design}
\begin{center}
\includegraphics[width=\textwidth]{misc/sam_smith_kicad_v3.png}
\end{center}
\end{frame}
\section{Open Source Hardware at CERN}
\subsection{White Rabbit}
%% \begin{frame}{The need for synchronisation in a particle accelerator}
%% \begin{center}
%% \includegraphics[height=6.5cm]{misc/synchrotron.jpg}
%% \end{center}
%% \end{frame}
\begin{frame}{White Rabbit (WR): an \emph{extension} of Ethernet}
\begin{columns}[c]
\column{.5\textwidth}
\begin{itemize}
\item Standard Ethernet network with extensions for:
\begin{itemize}
\item Sub-nanosecond synchronisation
\item Guaranteed latency
\end{itemize}
\item Now standardised under IEEE 1588
\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}
\item Central element of WR network
\item 18 port gigabit Ethernet switch with WR features
\item Fully open design, commercially available
\end{itemize}
\end{center}
\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{itemize}
% \item Carrier boards in PCI-Express, VME, PXIe
\item All carrier cards are equipped with a White Rabbit port
\item Mezzanines provide different functions (e.g. ADC)
\end{itemize}
\end{block}
\column{.01\textwidth}
\end{columns}
\end{frame}
\subsection{The CERN Open Hardware Licence}
\begin{frame}{Challenges in hardware licensing}
\begin{block}{Rights for hardware}
Copyright does not generally apply to physical objects
\end{block}
\pause
\begin{block}{Patents}
Much more prevalent in hardware than in software
\end{block}
\pause
\begin{block}{Reciprocity}
What should a reciprocal licence do for a hardware design? What is the scope
of reciprocity?
\end{block}
\pause
\begin{block}{The hardware design ecosystem}
Dominated by proprietary tools, parts of which sometimes go into the design itself
\end{block}
\end{frame}
\begin{frame}{The CERN Open Hardware Licence v2}
\begin{itemize}
\item Based on rights mainly applying to the design sources (e.g. circuit
schematics or CAD drawings)
\pause
\item Specifies conditions for:
\begin{itemize}
\item Copying designs
\item Modifying designs
\item Distributing modified or unmodified designs
\item Making hardware out of those designs
\item Distributing that hardware
\end{itemize}
\pause
\item Drafted by Myriam Ayass, Andrew Katz and Javier Serrano
\pause
\item Comes in three variants:
\begin{itemize}
\item CERN-OHL-P-2.0 (permissive)
\item CERN-OHL-W-2.0 (weakly reciprocal)
\item CERN-OHL-S-2.0 (strongly reciprocal)
\end{itemize}
\end{itemize}
\end{frame}
\begin{frame}{Challenges in hardware licensing}{How CERN OHL v2 deals with them}
\begin{block}{Rights for hardware}
CERN OHL v2 makes no assumption about rights
\end{block}
\pause
\begin{block}{Patents}
Two-way patent licensing clauses
\end{block}
\pause
\begin{block}{Reciprocity}
Have URL travel with object and use concepts of Product and Available
Component to establish limits of reciprocal obligations
\end{block}
\pause
\begin{block}{The hardware design ecosystem}
Components which are shipped with design tools qualify as Available Components
\end{block}
\end{frame}
\subsection{Other}
\begin{frame}{Ongoing developments and discussions}
\begin{block}{OSHW as part of a larger Open Science Policy}
\begin{itemize}
\item Creation of an Open Science working group
\item Discussing creation of an OSPO, which would include OSHW support
\item Involving procurement in the discussion from day one
\end{itemize}
\end{block}
\pause
\begin{block}{ASIC design}
\begin{itemize}
\item Following latest developments with interest, e.g. SkyWater PDK,
particularly from a licensing perspective
\item Discussing how to share beyond RTL code, open questions:
\begin{itemize}
\item Dual use and open source
\item Open sourcing of designs and academic tool licences
\end{itemize}
\end{itemize}
\end{block}
\end{frame}
\begin{frame}{Ongoing developments and discussions}
\begin{block}{Public Core: a refinement of Open Core}
\begin{itemize}
\item A way to structure public/private partnerships
\item Hopefully provides good incentives for all actors
\item Looking to apply it to White Rabbit (through a Collaboration
Agreement) in the coming months
\end{itemize}
\end{block}
\end{frame}
\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