Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
O
OHR Meta Project
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Projects
OHR Meta Project
Commits
743b66f5
Commit
743b66f5
authored
Jul 06, 2018
by
Erik van der Bij
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added Physics meets blockchain.
https://indico.cern.ch/event/736583/
parent
3f152e3a
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
932 additions
and
0 deletions
+932
-0
2018_OH_ph_meets_blockchain.tex
.../2018_ph_meets_blockchain/2018_OH_ph_meets_blockchain.tex
+932
-0
No files found.
presentations/2018_ph_meets_blockchain/2018_OH_ph_meets_blockchain.tex
0 → 100644
View file @
743b66f5
\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} % is included in mathtools
\usepackage
{
mathtools
}
% use for symbols: $\Phi$
% \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
[polish,english]
{
babel
}
\usepackage
[utf8]
{
inputenc
}
\usepackage
{
multirow
}
%%%%%%%%%%%%5
%\usepackage{geometry}
%\geometry{verbose,letterpaper}
%\usepackage{movie15}
%\usepackage{hyperref}
\graphicspath
{
{
../../figures/
}
}
% natively .png and .jpg images are accepted
\title
[Open source software and hardware\hspace{10em}\insertframenumber/\inserttotalframenumber]
{
Open source software,
\\
Open source hardware
}
%\subtitle{A CERN perspective}
\author
{
Erik van der Bij
}
% - 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
[Open X event]
%(optional, should be abbreviation of conference name)
{
Physics Meets Blockchain
\\
2nd Discussion Workshop
\\
Geneva, 11 July 2018
}
% - 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}
}
% 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}{Thanks for the opportunity}{Many of us depend on good
% Urban Drainage without knowing it}
% \begin{center}
% \includegraphics[height=0.75\textheight]{misc/floods_in_benicasim.png}
% \end{center}
%\end{frame}
\begin{frame}
{
Outline
}
\tableofcontents
% You might wish to add the option [pausesections]
\end{frame}
% Structuring a talk is a difficult task and the following structure
% may not be suitable. Here are some rules that apply for this
% solution:
% - Exactly two or three sections (other than the summary).
% - At *most* three subsections per section.
% - Talk about 30s to 2min per frame. So there should be between about
% 15 and 30 frames, all told.
% - A conference audience is likely to know very little of what you
% are going to talk about. So *simplify*!
% - In a 20min talk, getting the main ideas across is hard
% enough. Leave out details, even if it means being less precise than
% you think necessary.
% - If you omit details that are vital to the proof/implementation,
% just say so once. Everybody will be happy with that.
\section
[Intro to 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
[Intro to OSHW]
{
Introduction to Open Source Hardware
}
\subsection
{}
%\begin{frame}{A basic question}
% Could hardware design be as easy to share as software?
%\end{frame}
%\begin{frame}{A basic question}
% Why is this important?
%\end{frame}
%
%\begin{frame}{Why we use Open Hardware}
%
% \begin{block}{Get a design just the way we want it}
% \begin{itemize}
% \item We specify fully the design.
% \end{itemize}
% \end{block}
%
% \begin{block}{Peer review}
% \begin{itemize}
% \item Get your design reviewed by experts all around the world.
% \end{itemize}
% \end{block}
%
% \begin{block}{Healthier relationship with companies}
% \begin{itemize}
% \item No vendor-locked situations. Companies selected solely on the basis of technical excellence, good support and price.
% \end{itemize}
% \end{block}
%
%\end{frame}
%
%
%
%\begin{frame}{Why we use Open Hardware}
%
% \begin{block}{Spend money where you or your funding agencies want}
% \begin{itemize}
% \item Makes life easier for public institutions.
% \item Opens the door to smaller companies \\ with good local support.
% \end{itemize}
% \end{block}
%
% \begin{block}{Design re-use}
% \begin{itemize}
% \item When it's Open, people are more likely to re-use it.
% \item When it's Open, people are much more likely to contribute.
% \end{itemize}
% \end{block}
%
% \begin{block}{Dissemination of knowledge}
% \begin{itemize}
% \item One of CERN's key missions!
% \end{itemize}
% \end{block}
%
%\end{frame}
\begin{frame}
{
Why we use Open Hardware
}
\begin{block}
{
Design re-use
}
\begin{itemize}
\item
When it's Open, people are more likely to re-use it.
\item
When it's Open, people are much more likely to contribute.
\end{itemize}
\end{block}
\begin{block}
{
Peer review
}
\begin{itemize}
\item
Get your design reviewed by experts all around the world.
\item
Therefore the designs will become better.
\end{itemize}
\end{block}
\begin{block}
{
Dissemination of knowledge
}
\begin{itemize}
\item
One of CERN's key missions!
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
Why we use Open Hardware
}
\begin{block}
{
Get a design just the way we want it
}
\begin{itemize}
\item
We specify fully the design.
\end{itemize}
\end{block}
\begin{block}
{
Healthier relationship with companies
}
\begin{itemize}
\item
No vendor-locked situations. Companies selected solely on the basis of technical excellence, good support and price.
\end{itemize}
\end{block}
\begin{block}
{
Spend money where you or your funding agencies want
}
\begin{itemize}
\item
Makes life easier for public institutions.
\item
Opens the door to smaller companies
\\
with good local support.
\end{itemize}
\end{block}
\end{frame}
%\begin{frame}{Empowerment}
% \begin{center}
% \includegraphics[height=0.85\textheight]{misc/fwatch-full-side.jpg}
% \end{center}
%\end{frame}
%
%\begin{frame}{Empowerment}
% \begin{center}
% \includegraphics[height=0.85\textheight]{misc/ben_with_talon_beast.jpg}
% \end{center}
%\end{frame}
%
%%\begin{frame}{Empowerment}
%% \begin{center}
%% \includegraphics[height=0.85\textheight]{misc/momo-installation.jpg}
%% \end{center}
%%\end{frame}
%
%\begin{frame}{Empowerment}
% \begin{center}
% \includegraphics[height=0.85\textheight]{misc/safecast.jpg}
% \end{center}
%\end{frame}
%
\begin{frame}
{
There is an Open Source Hardware 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
\textit
{
study, modify, distribute, make
and sell
}
designs or hardware based on those designs.
\item
Now we know exactly what we mean when we say OSHW!
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
CERN Open Hardware License
\href
{
http://ohwr.org/cernohl
}{
-- ohwr.org/cernohl
}}
\begin{block}
{
Provides a solid legal basis
}
\begin{itemize}
\item
Developed by Knowledge and Technology Transfer Group at CERN.
\item
Open Software licences not usable (GNU, GPL,
\dots
).
% \item Defines conditions of using and modifying licenced material
\end{itemize}
\end{block}
\begin{block}
{
Practical: makes it easier to work with others
}
\begin{itemize}
% \item Makes it easier to work with others
\item
Upfront clear: anything you give is available to everyone.
\item
Everyone can use it for free.
\item
No strings attached.
\textit
{
Really!
}
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
CERN Open Hardware License
\href
{
http://ohwr.org/cernohl
}{
-- ohwr.org/cernohl
}}
\begin{block}
{
Same principles as Open Software
}
\begin{itemize}
\item
Anyone can see the source (design documentation).
\item
Anyone is free to study, modify and share.
\item
Any modification and distribution under same licence.
\item
Persistence makes everyone profit from improvements.
\end{itemize}
\end{block}
\begin{block}
{
Hardware production
}
\begin{itemize}
\item
When produce: licensee is invited to inform the licensor.
\end{itemize}
\end{block}
\end{frame}
%\begin{frame}{CERN Open Hardware License \href{http://ohwr.org/cernohl}{-- ohwr.org/cernohl}}
% \begin{block}{Provides a solid legal basis}
% \begin{itemize}
% \item Developed in collaboration with Knowledge Transfer Group at CERN.
% \item Better suited than non-HW licenses (GNU GPL, Creative Commons\dots)
% \item Defines conditions for using and modifying licensed material.
% \end{itemize}
% \end{block}
%
%\pause
%\begin{block}{Provides a clear legal environment}
% \begin{itemize}
% \item Written in a clear, concise style.
% \item Easy for licensors to evaluate if it is good for them.
% \end{itemize}
%\end{block}
%\end{frame}
\section
[OSHW in practice]
{
Open Source Hardware in practice
}
\subsection
{}
\begin{frame}
{
Example: SPEC - Simple PCI Express FMC carrier
}
{
Made in Spain, The Netherlands, Greece
\&
Poland
}
\begin{center}
\includegraphics
[height=6.5cm]
{
../pictures/ohwr/SPEC
_
top
_
high
_
res.jpg
}
\end{center}
\end{frame}
\begin{frame}
{
Example of a project in the
\\
Open Hardware Repository
\href
{
http://ohwr.org
}{
-- ohwr.org
}}
\begin{center}
\includegraphics
[height=6cm]
{
../pictures/ohwr/ohr
_
spec
_
overview.png
}
\end{center}
\end{frame}
\begin{frame}
{
Be Open
}
\begin{block}
{
Use OHR to the fullest
}
\begin{itemize}
\item
Document everything on OHR:
\begin{itemize}
\item
schematics, mechanics, status.
\end{itemize}
\item
Discuss over mailing list. Already from start of project.
\item
Document design review results.
\item
Track Issues and detected bugs.
\end{itemize}
\end{block}
\begin{block}
{
Don't be afraid to show mistakes!
}
\begin{itemize}
\item
E.g. SPEC: 86 Issues documented, 40 still 'Open'.
\item
Issues may help others when adapting a design.
\item
OHR becomes a teaching tool.
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
White Rabbit -- Innovation with Open approach
}
\begin{itemize}
\item
Hardcore innovation.
\item
An enabling technology.
\item
Started at CERN and GSI high-energy physics labs.
\item
Everything Open: hardware, gateware, software.
\item
Made extensive use of small companies to develop.
\item
Companies develop and sell products based on it.
% \item And still anyone can join and build upon it.
\end{itemize}
\end{frame}
\begin{frame}
{
White Rabbit -- is Ethernet
}
\begin{columns}
[c]
\column
{
.47
\textwidth
}
\begin{itemize}
% \item Few thousands nodes
\item
Bandwidth: 1 Gbps
\item
Single fiber medium
\item
Up to 10 km links
\item
WR Switch: 18 ports
% \item Allows non-WR Devices
\item
Ethernet features (VLAN)
\&
protocols (SNMP)
\item
\color
{
blue!90
}{
Synchronization:
}
\begin{itemize}
\item
accuracy better
\\
than 1 ns
\item
precision (tens of ps sdev skew max)
\end{itemize}
\end{itemize}
\column
{
.6
\textwidth
}
\begin{center}
\includegraphics
[width=1.0\textwidth]
{
../../figures/network/wr
_
network-ethernet.jpg
}
\end{center}
\end{columns}
\end{frame}
\begin{frame}
{
WR time transfer performance: lab tests
}{
3 cascaded switches
}
\begin{center}
\includegraphics
<1>[height=7.0cm]
{
../../figures/switch/wrSwitchV3.jpg
}
\pause
% \includegraphics<2>[height=7.0cm]{../../figures/measurements/meas_setup.jpg} \pause
\includegraphics
<2>[height=6.0cm]
{
../../figures/measurements/meas
_
results.pdf
}
\end{center}
\end{frame}
%\begin{frame}{White Rabbit applications }
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
%\begin{columns}[c]
%
% \column{0.65\textwidth}
% \begin{itemize}
% \setlength{\itemindent}{-0.3em}
% \item<1-> Particle accelerators
% \begin{itemize}
% \setlength{\itemindent}{-1.3em}
% \small
% \item<2-> \textbf<2>{CERN (Switzerland/France)}
% \item<3-> \textbf<3>{GSI (Germany)}
% \end{itemize}
% \item<1-> Cosmic ray \& neutrinos detectors
% \begin{itemize}
% \setlength{\itemindent}{-1.3em}
% \small
% \item<4-> \textbf<4>{LHAASO (China)}
% \item<5-> \textbf<5>{HiSCORE (Siberia)}
% \item<6-> \textbf<6>{KM3NET (Mediterranean)}
% \end{itemize}
% \item<1-> Metrology laboratories
% \begin{itemize}
% \setlength{\itemindent}{-1.3em}
% \small
% \item<7-> \textbf<7>{MIKES (Finland)}
% \item<8-> \textbf<8>{VSL (Netherlands)}
% \end{itemize}
% \end{itemize}
% \column{0.5\textwidth}
% \begin{center}
% \only<1>{\color{white}{First application:\\ CERN Neutrinos to Gran Sasso}}
% \only<2>{European Organization for Nuclear Research}
% \only<3>{GSI Helmholtzzentrum fur Schwerionenforschung GmbH}
% \only<4>{The Large High Altitude Air Shower Observation}
% \only<5>{Gamma-Ray and Cosmic Ray Detector}
% \only<6>{European deep-sea research infrastructure }
% \only<7>{Centre for metrology and accreditation}
% \only<8>{Dutch Metrology Institute\\ \color{white}{ble}}
% \end{center}
% \begin{center}
% \includegraphics<1>[height=0.44\textheight]{p1588/PTPv3_blank.jpg}
% \includegraphics<2>[height=0.44\textheight]{applications/CERN/accelerators-stripped.jpg}
% \includegraphics<3>[height=0.44\textheight]{applications/gsi.pdf}
% \includegraphics<4>[height=0.44\textheight]{applications/lhaaso.pdf}
% \includegraphics<5>[height=0.44\textheight]{applications/HiSCORE.jpg}
% \includegraphics<6>[height=0.44\textheight]{applications/KM3NeT.pdf}
% \includegraphics<7>[height=0.44\textheight]{applications/mikes.pdf}
% \includegraphics<8>[height=0.44\textheight]{applications/netherlands.jpg}
% \end{center}
% \column{0.6\textwidth}
%\end{columns}
% \begin{center}
% \small
% \textbf{All users:} \url{www.ohwr.org/projects/white-rabbit/wiki/WRUsers}
% \end{center}
%\end{frame}
\begin{frame}
{
White Rabbit applications
}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{columns}
[c]
\column
{
0.65
\textwidth
}
\begin{itemize}
\setlength
{
\itemindent
}{
-0.3em
}
\item
<1-> Particle accelerators
\begin{itemize}
\setlength
{
\itemindent
}{
-1.3em
}
\small
\item
<1->
\textbf
<1>
{
CERN (Switzerland/France)
}
\item
<1->
\textbf
<1>
{
GSI (Germany)
}
\end{itemize}
\item
<2-> Cosmic ray
\&
neutrinos detectors
\begin{itemize}
\setlength
{
\itemindent
}{
-1.3em
}
\small
\item
<2->
\textbf
<2>
{
LHAASO (China)
}
\item
<2->
\textbf
<2>
{
HiSCORE (Siberia)
}
\item
<2->
\textbf
<2>
{
KM3NET (Mediterranean)
}
\end{itemize}
\item
<2-> Metrology laboratories
\begin{itemize}
\setlength
{
\itemindent
}{
-1.3em
}
\small
\item
<2->
\textbf
<2>
{
MIKES (Finland)
}
\item
<2->
\textbf
<2>
{
VSL (Netherlands)
}
\end{itemize}
\end{itemize}
\column
{
0.5
\textwidth
}
\begin{center}
\only
<1>
{
\color
{
white
}{
First application:
\\
CERN Neutrinos to Gran Sasso
}}
\only
<1>
{
European Organization for Nuclear Research
}
\only
<1>
{
GSI Helmholtzzentrum fur Schwerionenforschung GmbH
}
\only
<2>
{
Dutch Metrology Institute
\\
\color
{
white
}{
ble
}}
\end{center}
\begin{center}
% \includegraphics<1>[height=0.44\textheight]{p1588/PTPv3_blank.jpg}
\includegraphics
<1>[height=0.44
\textheight
]
{
applications/CERN/accelerators-stripped.jpg
}
% \includegraphics<3>[height=0.44\textheight]{applications/gsi.pdf}
\includegraphics
<2>[height=0.44
\textheight
]
{
applications/netherlands.jpg
}
\end{center}
\column
{
0.6
\textwidth
}
\end{columns}
\begin{center}
\small
\textbf
{
All users:
}
\url
{
www.ohwr.org/projects/white-rabbit/wiki/WRUsers
}
\end{center}
\end{frame}
\begin{frame}
{
How can this map to your project?
}
\begin{center}
{
What could be your ``killer app''?
}
\end{center}
\end{frame}
%
%\begin{frame}{Open source and the unexpected}
% \begin{center}
% \includegraphics[width=\textwidth]{../../figures/applications/wr_other_apps.jpg}
% \end{center}
%\end{frame}
\begin{frame}
{
Business models
}{
Dispelling the commercial vs open myth
}
\begin{center}
\includegraphics
[width=\textwidth]
{
../pictures/ohwr/commercial
_
and
_
open.pdf
}
\end{center}
\end{frame}
\begin{frame}
{
Where the rubber meets the road
}{
Eight years
of experience at CERN
}
\begin{center}
\includegraphics
[height=6.5cm]
{
../pictures/ohwr/ohr
_
companies.png
}
\end{center}
\end{frame}
\begin{frame}
{
Free-as-in-freedom design tools
}{
The last hurdle to
efficient sharing -
\href
{
http://kicad-pcb.org/
}{
kicad-pcb.org
}}
\begin{center}
\includegraphics
[width=\textwidth]
{
misc/kicad
_
screenshot.png
}
\end{center}
\end{frame}
\begin{frame}
{
Free-as-in-freedom design tools
}{
Example: similar case in the
Quantum Engineering community?
}
\begin{block}
{
Tools should be free and open to be able to share
}
\begin{itemize}
\item
Simulation tools
\item
Control software
\item
Data processing tools
\item
Quantum Information Software
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
Hardware for quantum engineering projects
}{
Duplication of effort: different labs build similar equipment
}
\begin{center}
\includegraphics
[width=\textwidth]
{
quantum/quantum
_
electronics.png
}
\\
slide courtesy of G.Kasprowicz
\end{center}
\end{frame}
\begin{frame}
{
Quantum engineering project: Sinara
}{
Open source hardware for quantum applications
}
\begin{block}
{
Sinara -
\href
{
https://github.com/m-labs/sinara/wiki
}{
github.com/m-labs/sinara/wiki
}}
\begin{itemize}
\item
Open-source hardware ecosystem designed for use in quantum physics experiments running ARTIQ control software.
\item
All design files, sources, mechanics, documentation published.
\item
Project shared under OHL, managed using github.
\end{itemize}
\end{block}
\begin{block}
{
International collaboration
}
\begin{itemize}
\item
Institutes: NIST Boulder, UMD, ARL, Warsaw WUT, Oxford University, Uni Hannover, PTB
\item
Industry: Mlabs, Quartiq, Creotech, Technosystem
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
Sinara hardware
}{
Licenced under CERN OHL
}
\begin{center}
\includegraphics
[width=\textwidth]
{
quantum/sinara
_
hw.png
}
\end{center}
\end{frame}
\begin{frame}
{
Quantum engineering project: Easy
$
\Phi
$}{
Open source hardware for quantum applications
}
\begin{block}
{
Easy
$
\Phi
$
-
\href
{
http://easy-phi.ch
}{
easy-ph.ch
}}
\begin{itemize}
\item
Easy
$
\Phi
$
is a platform aiming at physicists.
\item
Developed for the needs of quantum optics, usable for applications in physics or biology.
\item
Open standard platform.
\end{itemize}
\end{block}
\begin{block}
{
Single institute, but Open
}
\begin{itemize}
\item
University of Geneva
\\
- Group of Applied Physics in Optics
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
Easy
$
\Phi
$
hardware
}{
Licenced under CERN OHL
}
\begin{columns}
[c]
\column
{
.47
\textwidth
}
\begin{itemize}
\item
Dual High-Speed Universal Input
\item
Dual High-Speed Universal Output
\item
Dual High-Speed Delay Line
\item
High speed coincidence
\item
Thermocouple temperature measurement
\item
Optical amplitude modulator
\item
...
\end{itemize}
\column
{
.6
\textwidth
}
\begin{center}
\includegraphics
[width=1.0\textwidth]
{
quantum/easy-phi
_
crate.png
}
\end{center}
\end{columns}
\end{frame}
% \begin{frame}{Other perceived benefits}
% \begin{block}{Motivation and recognition}
% \begin{itemize}
% \item Designers prefer collaboration rather than work in isolation.
% \item Easy to gain a reputation based on one's work.
% \item Easier hiring.
% \item Part of the commercial strategy of many companies.
% \end{itemize}
% \end{block}
% \pause
% \begin{block}{For small and medium-size companies}
% \begin{itemize}
% \item Lower barriers to market.
% \item Easier to bring in extra talent, even from the client!
% \end{itemize}
% \end{block}
% \end{frame}
% \begin{frame}{Perceived issues}
% \begin{block}{Where does this stop?}
% \begin{itemize}
% \item Layers of openness.
% \item ASIC design slowly becoming more accessible (e.g. lowRISC).
% \item Commodity hardware not so critical.
% \end{itemize}
% \end{block}
% \pause
% \begin{block}{Will I find providers if I specify OSHW?}
% \begin{itemize}
% \item For better or worse, it's a free market out there.
% \item Nothing specific to OSHW.
% \end{itemize}
% \end{block}
% \end{frame}
% \begin{frame}{Perceived issues}
% \begin{block}{The expectation management department}
% \begin{itemize}
% \item Can I really control all manufacturing and distribution
% of an OSHW design I release?
% \item Comparing apples-to-apples: how much has been invested
% in a given OSHW solution?
% \item I published and I did not get any bug fix!
% \end{itemize}
% \end{block}
% \pause
% \begin{block}{Will people steal my design and make money off it?}
% \begin{itemize}
% \item Yes, even if it's not OSHW (unless it's very complicated
% and you have a large legal department).
% \item But hey, Arduino survives! Why?
% \end{itemize}
% \end{block}
% \end{frame}
% \begin{frame}{Perceived issues}
% \begin{block}{I can't afford the initial investment}
% \begin{itemize}
% \item OSHW designs are often a show case for a group,
% institution or company.
% \item Can't cut corners on quality. Should not be bad in principle.
% \item May not be adequate given the context. OSHW is not for
% everyone all the time.
% \end{itemize}
% \end{block}
% \end{frame}
% \begin{frame}{Recipes for success}
% \begin{block}{Common sense!}
% \begin{itemize}
% \item Identify the problem that needs solving, prepare plan,
% get good team, track progress, document\ldots
% \item Nothing OSHW-specific here.
% \end{itemize}
% \end{block}
% \pause
% \begin{block}{Enlarge your scope}
% \begin{itemize}
% \item Use standards.
% \item Be flexible if you want to attract talent.
% \end{itemize}
% \end{block}
% \pause
% \begin{block}{Choose good partners}
% Your interests do not need to align completely, just enough
% to walk a part of the path together.
% \end{block}
% \end{frame}
\section
[Getting organised]
{
How to get organised
}
\subsection
{}
\begin{frame}
{
Public institutions
}
\begin{block}
{
They serve the interests of a whole society
}
\begin{itemize}
\item
Try to maximise positive impact of decisions.
\item
Not always easy.
\end{itemize}
\end{block}
\pause
\begin{block}
{
Can be ``tractor'' institutions
}
\begin{itemize}
\item
To help take projects to a mature state where they can
be sustained commercially.
\item
Liaising with other public institutions to reach
critical mass.
\item
Also with their procurement hat.
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
The funding agencies conundrum
}
\begin{center}
\includegraphics
[height=0.8\textheight]
{
misc/flags.jpg
}
\end{center}
\end{frame}
\begin{frame}
{
Issues with ``coopetition''
}
Research groups sometimes end up behaving as private
companies (but with public money!) because of wrong incentives by
funding agencies.
\end{frame}
\begin{frame}
{
The power of getting organised
}
Look at Open Hardware, Open Access
\ldots
even CERN itself! These
things looked highly improbable before people got organised to make
them happen.
\end{frame}
\begin{frame}
{
Check out
\href
{
https://www.zenodo.org
}{
zenodo.org!
}}
\begin{block}
{
Why?
}
\begin{itemize}
\item
Science cannot be open without open data ...
\begin{itemize}
\item
... and software and hardware
\end{itemize}
\item
Avoid double pay for tax payers
\item
Makes sharing research very easy!
\end{itemize}
\end{block}
\pause
\begin{block}
{
How?
}
\begin{itemize}
\item
Open attitude from day 1
\item
Communities of interest in Zenodo
\item
Involving key commercial and non-commercial actors from the start
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
OpenX
}{
How to get organised
}
\begin{columns}
[c]
\column
{
.47
\textwidth
}
\begin{itemize}
\item
Open Hardware
\item
Open Software
\item
Site to collaborate
\item
Coordination
\item
Need for a
\\
``Tractor" institution?
\end{itemize}
\column
{
.6
\textwidth
}
\begin{center}
\includegraphics
[height=6.5cm]
{
misc/Tuxoid
_
OHWR-logo
_
RC
_
V1.png
}
\end{center}
\end{columns}
\end{frame}
\begin{frame}
{
So, how can the
\\
OpenX Community get organised?
}
\begin{center}
\includegraphics
[height=6.5cm]
{
misc/Tuxoid
_
OHWR-logo
_
RC
_
V1.png
}
\end{center}
\end{frame}
\end{document}
\ No newline at end of file
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment