Skip to content
Snippets Groups Projects
Commit 76f1ce94 authored by Bob Coecke's avatar Bob Coecke
Browse files

More in short 3

parent e10dfeba
No related branches found
No related tags found
No related merge requests found
......@@ -877,7 +877,7 @@ Beyond online self-publishing we will also pitch articles to magazines aimed at
\newpage
\section{IMPLEMENTATION \REM{(2 pages total -- shorter than long proposal)}}
\label{sec:impl-2-pages}
\label{sec:impl-2-pages}
\subsection{Work plan} \label{sec:work-plan-work}
......@@ -939,10 +939,10 @@ Similarly, several tasks of {\bf WP 3} are based on known results and techniques
On the theory side, we aim to augment the \zxcalculus in several directions: by going from qubits to qudits, developing representations for recursion and control, and expressing topological and causal constraints.
Throughout the project, we will check the performance of our methods against competitors and benchmark our software using the open test-suite we will develop.
{\bR Because of the integrated nature of the project, and the high
degree of past collaboration among the consortium members, most tasks
receive attention from the personnel of several sites. This degree of
collaboration is a strong point of this project.\e}
%{\bR Because of the integrated nature of the project, and the high
%degree of past collaboration among the consortium members, most tasks
%receive attention from the personnel of several sites. This degree of
%collaboration is a strong point of this project.\e}
%\newpage
......@@ -994,107 +994,102 @@ Explain why the organisational structure and decision-making
mechanisms are appropriate to the complexity and scale of the
project.}
\paragraph{Coordinator}
\label{sec:overall}
Coordination between sites and between work packages will be overseen
by D. Horsman at the Grenoble site, which will also handle the
overall administration of the project.
\paragraph{Sites}
\label{sec:sites}
The project will be managed by a senior scientist from each site:
B. Coecke (Oxford), R. Duncan (CQC), D. Horsman (Grenoble), A. B. Sainz (Gdansk),
S. Perdrix (LORIA), and A. Kissinger (Nijmegen). They will track
global progress to ensure milestones are reached, and facilitate
collaboration across tasks at their individual sites. They will be in close contact throughout the project to assure coherence and concurrence of the activities at the different sites.
\paragraph{Work packages}
\label{sec:work-packages-1}
Each work package will be lead by a responsible PI who will coordinate
research activity between sites to ensure that deliverables are met,
achieve WP-specific objectives, and organise collaboration meetings as
needed.
\textbf{\ref{wp:frontend}}: S. Perdrix (LORIA),
\textbf{\ref{wp:representation}}: A. B. Sainz (Gdansk),
\textbf{\ref{wp:theory}}: B. Coecke (Oxford),
\textbf{\ref{wp:usefulstuff}}: D. Horsman (Grenoble),
\textbf{\ref{wp:admin}}: D. Horsman (Grenoble).
\paragraph{Experimental and integration advisory board}
\label{sec:monit-advis-board}
%\paragraph{Coordinator}
%\label{sec:overall}
Coordination between sites and work packages will be done
by Horsman/Grenoble, which will also handle project administration. The project will be managed by a senior scientist from each site:
Coecke (Oxford), Duncan (CQC), Horsman (Grenoble), Sainz (Gdansk),
Perdrix (LORIA), and Kissinger (Nijmegen). They will track
global progress to ensure milestones are reached.
Each work package will be lead by a responsible PI
%who will coordinate
%research activity between sites to
who ensures that deliverables are met:
%achieve WP-specific objectives, and organise collaboration meetings as needed.
{\bf WP 1}: Perdrix (LORIA),
{\bf WP 2}: Sainz (Gdansk),
{\bf WP 3}: Coecke (Oxford),
{\bf WP 4}: Horsman (Grenoble),
%\textbf{\ref{wp:admin}}: D. Horsman (Grenoble).
%
%\paragraph{Experimental and integration advisory board}
%\label{sec:monit-advis-board}
%
Every six months there will be a meeting of both the work package leaders
and the site leaders, either electronically (\eg via Skype) or at a
project event. At these meetings progress towards research objectives
will be evaluated, and any new opportunities will also be discussed. These
meetings will be organised by the coordinator.
project event.
%At these meetings progress towards research objectives
%will be evaluated, and any new opportunities will also be discussed. These
%meetings will be organised by the coordinator.
To assist in monitoring and evaluating progress, as well as to collaborate on WP4,
we have recruited Alexia Auffeves and Maud Vinet as external advisors. Prof. Auffeves is the Lead of the
Grenoble Quantum Engineering project, and Prof. Vinet is the head of the silicon spin qubit experimental team.
The entire project and advisory board (see \S\ref{sec:impact-2-pages})
will meet once a year to evaluate progress, set priorities, and plan
next steps.
we have recruited Prof. ~Auffeves, Lead of the
Grenoble Quantum Engineering project, and Prof.~Vinet, head of the silicon spin qubit experimental team, as external advisors.
%Prof. Auffeves is the , and Prof. Vinet is the head of the silicon spin qubit experimental team.
%The entire project and advisory board (see \S\ref{sec:impact-2-pages})
%will meet once a year to evaluate progress, set priorities, and plan
%next steps.
\bR
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{List of milestones}
\label{sec:list-milestones}
The milestones of the project are conceptually simple: at each
milestone we will deliver a functioning piece of software. With each
milestone, we add more, and more advanced, functionality. By
delivering the software incrementally, we follow best practice in the
industry: by regularly integrating parts from all work packages, we
%\paragraph{List of milestones}
%\label{sec:list-milestones}
The milestones are as follows:
\begin{description}
\item[{\bf M1}] Minimal QASM $\to$ QASM circuit optimiser (month 12)
\item[{\bf M2}] Support for one HLL using parametric \zx, with 1WQC and idealized circuit output (month 18)
\item[{\bf M3}] Architecture sensitive, fidelity aware optimiser Error correction support (month 24)
\item[{\bf M4}] Back-end support for Oxford Ion Traps, initial back end API (month 30)
\item[{\bf M5}] Complete deep-\zx compiler stack with open
APIs, and a target compiled protocol demonstrating explicit quantum speed-up. (month 36)
\end{description}
Hence, at each milestone we will deliver a functioning piece of software. With each
milestone, we add more, and more advanced, functionality. By delivering the software incrementally, we follow best practice in the industry: by regularly integrating parts from all work packages, we
reduce risk and improve communication across the consortium.
\begin{center}
\makebox[\textwidth][c]{
\begin{tabular}{|c|c|c|l|}
\hline
\textbf{Milestone} &
\textbf{Delivery Month} &
\textbf{WP involved} &
\textbf{Title} \\\hline
%
\ms \label{ms:qasmqasm}&
12 &
\ref{wp:frontend} &
Minimal QASM $\to$ QASM circuit optimiser \\\hline
%
\ms \label{ms:quippermbqc}&
18&
\ref{wp:frontend},\ref{wp:representation},\ref{wp:theory}&
Support for one HLL using parametric \zx,\\
&&& with 1WQC and idealized circuit output \\\hline
%\begin{center}
%\makebox[\textwidth][c]{
% \begin{tabular}{|c|c|c|l|}
% \hline
% \textbf{Milestone} &
% \textbf{Delivery Month} &
% \textbf{WP involved} &
% \textbf{Title} \\\hline
%%
%\ms \label{ms:qasmqasm}&
%12 &
%\ref{wp:frontend} &
%Minimal QASM $\to$ QASM circuit optimiser \\\hline
%%
%\ms \label{ms:quippermbqc}&
%18&
%\ref{wp:frontend},\ref{wp:representation},\ref{wp:theory}&
%Support for one HLL using parametric \zx,\\
%&&& with 1WQC and idealized circuit output \\\hline
%%
%\ms \label{ms:optimise-ecc}&
%24&
%\ref{wp:representation},\ref{wp:theory},\ref{wp:usefulstuff}&
%Architecture sensitive, fidelity aware optimiser\\
%&&& Error correction support
% \\\hline
%%
%\ms \label{ms:nqitbackend}&
%30&
%\ref{wp:frontend},\ref{wp:theory},\ref{wp:usefulstuff}&
% Back-end support for Oxford Ion Traps,\\
% &&& initial back end API\\\hline
%%
%\ms \label{ms:delftbackend} &
%36&
%All&
%Complete deep-\zx compiler stack with open\\
%&&& APIs, and a target compiled protocol\\
%&&& demonstrating explicit quantum speed-up. \\\hline
% \end{tabular}}
%\end{center}
%
\ms \label{ms:optimise-ecc}&
24&
\ref{wp:representation},\ref{wp:theory},\ref{wp:usefulstuff}&
Architecture sensitive, fidelity aware optimiser\\
&&& Error correction support
\\\hline
%
\ms \label{ms:nqitbackend}&
30&
\ref{wp:frontend},\ref{wp:theory},\ref{wp:usefulstuff}&
Back-end support for Oxford Ion Traps,\\
&&& initial back end API\\\hline
%
\ms \label{ms:delftbackend} &
36&
All&
Complete deep-\zx compiler stack with open\\
&&& APIs, and a target compiled protocol\\
&&& demonstrating explicit quantum speed-up. \\\hline
\end{tabular}}
\end{center}
\e
%\e
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment