@@ -877,7 +877,7 @@ Beyond online self-publishing we will also pitch articles to magazines aimed at
...
@@ -877,7 +877,7 @@ Beyond online self-publishing we will also pitch articles to magazines aimed at
\newpage
\newpage
\section{IMPLEMENTATION \REM{(2 pages total -- shorter than long proposal)}}
\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}
\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
...
@@ -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.
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.
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
%{\bR Because of the integrated nature of the project, and the high
degree of past collaboration among the consortium members, most tasks
%degree of past collaboration among the consortium members, most tasks
receive attention from the personnel of several sites. This degree of
%receive attention from the personnel of several sites. This degree of
collaboration is a strong point of this project.\e}
%collaboration is a strong point of this project.\e}
%\newpage
%\newpage
...
@@ -994,107 +994,102 @@ Explain why the organisational structure and decision-making
...
@@ -994,107 +994,102 @@ Explain why the organisational structure and decision-making
mechanisms are appropriate to the complexity and scale of the
mechanisms are appropriate to the complexity and scale of the
project.}
project.}
\paragraph{Coordinator}
%\paragraph{Coordinator}
\label{sec:overall}
%\label{sec:overall}
Coordination between sites and between work packages will be overseen
Coordination between sites and work packages will be done
by D. Horsman at the Grenoble site, which will also handle the
by Horsman/Grenoble, which will also handle project administration. The project will be managed by a senior scientist from each site:
Perdrix (LORIA), and Kissinger (Nijmegen). They will track
\paragraph{Sites}
global progress to ensure milestones are reached.
\label{sec:sites}
Each work package will be lead by a responsible PI
%who will coordinate
The project will be managed by a senior scientist from each site:
%research activity between sites to
B. Coecke (Oxford), R. Duncan (CQC), D. Horsman (Grenoble), A. B. Sainz (Gdansk),
who ensures that deliverables are met:
S. Perdrix (LORIA), and A. Kissinger (Nijmegen). They will track
%achieve WP-specific objectives, and organise collaboration meetings as needed.
global progress to ensure milestones are reached, and facilitate
{\bf WP 1}: Perdrix (LORIA),
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.
{\bf WP 2}: Sainz (Gdansk),
{\bf WP 3}: Coecke (Oxford),
\paragraph{Work packages}
{\bf WP 4}: Horsman (Grenoble),
\label{sec:work-packages-1}
%\textbf{\ref{wp:admin}}: D. Horsman (Grenoble).
%
Each work package will be lead by a responsible PI who will coordinate
%\paragraph{Experimental and integration advisory board}
research activity between sites to ensure that deliverables are met,
%\label{sec:monit-advis-board}
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}
Every six months there will be a meeting of both the work package leaders
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
and the site leaders, either electronically (\eg via Skype) or at a
project event. At these meetings progress towards research objectives
project event.
will be evaluated, and any new opportunities will also be discussed. These
%At these meetings progress towards research objectives
meetings will be organised by the coordinator.
%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,
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
we have recruited Prof. ~Auffeves, Lead of the
Grenoble Quantum Engineering project, and Prof.Vinet is the head of the silicon spin qubit experimental team.
Grenoble Quantum Engineering project, and Prof.~Vinet, head of the silicon spin qubit experimental team, as external advisors.
The entire project and advisory board (see \S\ref{sec:impact-2-pages})
%Prof. Auffeves is the , and Prof. Vinet is the head of the silicon spin qubit experimental team.
will meet once a year to evaluate progress, set priorities, and plan
%The entire project and advisory board (see \S\ref{sec:impact-2-pages})
next steps.
%will meet once a year to evaluate progress, set priorities, and plan
\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.
reduce risk and improve communication across the consortium.
