SHORTPROP.tex

%(i) developing experience on easier objectives before addressing more
%demanding ones and (ii) consulting our board of advisors to foresee
%problems.  Due to its high dependence on other tasks, we consider
%\ref{wp:usefulstuff} to be highest risk.}\TODOb{This doesn't seem quite up-to-date, also see below}
%
%
%
%\begin{center}
%  \begin{tabular}{|p{0.25\textwidth}|c|c|p{0.4\textwidth}|}
%    \textbf{Description of risk} 
%    & \textbf{Likelihood}
%    & \textbf{WPs involved}
%    & \textbf{Proposed mitigation measures}\\\hline
%%    
%Can't hire suitable post-docs&
%Medium&
%All&
%While we have already identified several suitable candidates for each
%role, the investigators also collectively supervise a large body of PhD
%students and post-docs who could be channelled to the project.
%\\\hline
%%    
%NQIT or Grenoble machine info unavailable or not detailed enough&
%Low&
%\ref{wp:usefulstuff}&
%\oldt{(i) We have members of the consortium from NQIT, and letters of
%support from DiCarlo who agrees to help.  (ii) We can approach other
%members of our board of advisors, or other friendly
%experimentalists. (iii) We can target an more abstract model of the
%machine} \\\hline
%%    
%Some desired technique or algorithm isn't found&   
%High&
%All&
%All tasks where this is a risk have been structured as a collection of
%related goals; if some part doesn't succeed then the finished system
%will be will have fewer features, or worse performance.  However it's
%very unlikely that an entire task will fail in a way that jeopardises
%the project. \\\hline
%%    
%Software integration issues&
%Medium&
%All&
%(i) We will establish a common API in \ref{del:earlyapi} to allow
%loose coupling of the software components (ii) We appoint the most
%experienced software developer in the  consortium (Valiron) to act as ``integration tzar'' and ensure
%the global design is good. (iii) As noted above, we will integrate
%often and deliver new features more than once a year.  
%\\\hline
%  \end{tabular}
%\end{center}
%
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
%\newpage
\subsection{Consortium} %\REM{(1 page)}
\label{sec:consortium-as-whole}

The team consists of:
\begin{description} 
\item[{\bf Univ.~Grenoble (coordinator):}] Dr Dominic Horsman.
\item[{\bf Univ.~Lorraine; LORIA; LRI:}] Dr Simon Perdrix, Prof.~Emmanuel Jeandel, Dr Beno\^it
      Valiron.
\item[{\bf Univ.~Oxford:}] Prof.\ Bob Coecke, Dr Miriam Backens, Dr Niel de Beaudrap, Dr Quanlong Wang.
\item[{\bf Cambridge Quantum Computing Ltd.:}] Dr Ross Duncan, Mr Will Simmons. 
\item[{\bf Univ.~Gdansk / ICTQT:}] Dr Ana Bel\'en Sainz.
\item[{\bf Radboud Univ.~Nijmegen:}] Dr Aleks Kissinger, (Dr) Kang Feng Ng, Mr John van de Wetering. 
\end{description}
These members include the pioneers of \zxcalculus \cite{Coecke:2009aa}, those who proved its completeness \cite{1367-2630-16-9-093021,Jeandel2017A-Complete-Axio,HFW}, as well as those that proposed the exploitation of \zxcalculus in quantum technologies \cite{Duncan:2010aa, Horsman:2011lr, Chancellor2016Coherent-Parity, BH-2017, DKPdW-2019} (incl.~translations  between different computational models, error-correction/lattice surgery, circuit optimisation).  Hence, the consortium includes all leading researchers on \zxcalculus. CQC is moreover the world-leading quantum computing company on compiler design. Duncan and Kissinger  pioneered automation of diagrammatic reasoning (cf.~{\tt quantomatic} and {\tt PyZX}), which helped in setting the state-of-the-art in circuit optimization \cite{DKPdW-2019}.   We also  include pioneers in quantum
programming languages (Valiron), important contributors to MBQC \cite{Duncan:2010aa} and 
quantum circuits (Jeandel).    
 
Consequently,  members  have a long history of collaboration. Coecke is a member of the International Scientific Committee of ICTQT-Gdansk, the new institute that hosts Sainz' new group.  Several members have ongoing collaborations with Cambridge Quantum Computing Inc. In particular, co-inventor of \zxcalculus Ross Duncan is now the leading researcher at CQC, which clearly demonstrates CQC's commitment to \zxcalculus.   Quantum compilation  is moreover the key focus of CQC. 
The project will be co-ordinated from Grenoble, and integrate with the QuEnG technology project.
Several members are also part of the NQIT Quantum Technologies Hub.   

%The consortium has also been instrumental in community building, for example with the QPL conference series which now attracts well over 100 participants every year and approx.~75 paper submissions on foundational and structural research in the area of quantum computing.  It also has organised several schools e.g.~the QiCS School\footnote{www.cs.ox.ac.uk/people/bob.coecke/QICS$\underline{\ }$School.html} and the CAP Spring School,\footnote{www.cs.ox.ac.uk/ss2014/} and a substantial talks archive is maintained.\footnote{www.youtube.com/user/OxfordQuantumVideo} \newt{More recently, the several members are 
%involved in the Compositionality community, which has diagrammatic/categorical reasoning as its core focus, with a new journal, a new conference series, and a new workshop series.}

%\TODOb{Keeping any of this? Introducing anything else?}
%\bR Of utter importance is the alignment with Networked Quantum Information Technologies Hub (NQIT) at the Oxford site, which means that several members of the consortium have already direct expertise with interacting with quantum hardware (de Beaudrap, Horsman).  The NQIT is the largest of the four Hubs in the UK National Quantum Technology Programme, a 270 GBP million investment by the UK government to establish a quantum technology industry in the UK. %We are working towards building a quantum computer demonstrator, the Q20:20 engine, which demonstrates a networked, hybrid light-matter approach to quantum information processing.
%Concretely, the most important aspect is the fact that the modular architecture motivated using lattice surgery on surface codes for the logical operations, and that these are in effect \zx-operations \cite{{BH-2017}}. This will certainly make the ambition here much more achievable. \e

%\REM{From cyril to address industrial/commericial}
%Bull brings expertise in high performance simulation as well as
%industrial guidances in software. \REM{more}



%\newpage%\TODOb{This needs to be done urgently}
 \subsection{Financial plan}
\label{sec:financial-plan} 

\REM{The resources to be committed for each project partner have to be
  described in the Electronic Submission System by the
  coordinator. These resources include: Personnel, Consumables,
  Equipment, Travel, Subcontracting, Provisions, Licensing fees,
  other. Justify them here. Both the justification and the information
  in the system will be communicated to the Evaluation Panel.}

We request 30 months of salary
  for post-docs at Oxford, 36+18 months at Gdansk, and 18 months at each of Grenoble and LORIA. The Oxford post-doc will also engage in co-operation with industrial partners at CQC.  The post-docs
  will be hired as soon as possible by the site leads at each site.
%\item \emph{Coordinator}: We request 10\% contribution the
%  Duncan's salary at Strathclyde to cover the time spent managing
%  the project. This is reduced from 20\% upon negotiation with
%  Stratclyde.  (Duncan will contribute an additional 8.4 months of
%  time as a researcher, see below.)

Spread
  across the sites, more than 110 person-months of time
  will be contributed by the named staff on the project, all of which
  is supported by other sources.  

At LORIA and Grenoble, one PhD student will contribute
  approx 9 months to the project, at Gdansk, one will contribute 12 months, and at Oxford, two PhD students will be fully dedicated, all funded from other sources.

At CQC, a Senior Scientist and a Research Software Developer will contribute, funded from elsewhere.

We plan one workshop each year, in
Oxford, Nijmegen, and Grenoble.  We plan to invite significant figures from the experimental and software industrial communities to supplement the project reach and expertise.  We have
budgeted
\euro 15k for each, through the co-ordinating site budget.

We request substantial budget for travel, for quantERA
reporting meetings, for formal project meetings, smaller more frequent
WP meetings, and also to present our work at conferences.

We  request laptop computers for each of the postdocs, and
  replacement laptops for some staff.  
  
\newpage\section{ETHICAL ISSUES \REM{1/2 page}}
\label{sec:ethical-issues}

\REM{Describe any foreseeable ethical issue that may arise during the
  course of the research project. Describe all mitigation strategies
  employed to reduce ethical risk, and justify the research
  methodology with respect to ethical issues.}

No ethical issues foreseeable.

\REM{max 30 references - OK AT THE MOMENT SINCE KEVIN-ROSS ONLY IN COMMENTS}
\bibliographystyle{plain}
\bibliography{quantera} 

\end{document} %%% -- uncomment to throw away notes

\newpage
\section{IMPLEMENTATION \REM{(2 pages total -- shorter than long proposal)}}
\label{sec:impl-2-pages} 

\subsection{Work plan} \label{sec:work-plan-work}

\REM{Provide a brief presentation of the overall structure of the work plan.
Clearly define the intermediate targets. 
Provide a timing of the different work packages and their components
(Gantt chart or similar). 
Provide a graphical representation of the work packages components
showing how they inter-relate (Pert chart or similar).
}

\TODOb{Put some more here from actual WP descriptions.}
The work plan has four major scientific work packages (WPs),
which will proceed in parallel:
%All will have at least some activities throughout the length of the project, with the exception of \ref{wp:usefulstuff} which builds on earlier work in the other WPs and thus only begins one year into the project. (There is also a fifth
%work package grouping administrative and organisational activities.)
\begin{description} 
\item[{\bf WP 1}] is focussed on the \dzxc interface with known high-level quantum programming languages 
%translating from HLLs into \azx, reflecting higher level programming constructs into \azx, 
and building a test suite of programs for benchmarking.
\item[{\bf WP 2}] is focussed on the further development of zx calculus, its axiomatic formulation, and its status as a theory of resources.
%is about modelling the properties of different machines in \azx, and translating \azx to hardware.
\item[{\bf WP 3}] 
focusses on resource optimization, such as gate reduction in circuit representations, efficient intelligent error-correction, and other deep algorithms.
%develops the theory behind \azx and algorithms  to realise the logical ideas.
\item[{\bf WP 4}]
applies all the previous to specific quantum hardware.
%applies these advances to the
%creation of useful quantum software, specifically focusing on
%optimisation and error correction.
\end{description}
Each work package is divided into more specific tasks, each of which 
is designed to deliver a particular piece of the project: some are
theoretical results, some are software functions.  
Our work plan consists of a balance of short tasks with concrete software deliverables and longer term, more ambitious and open-ended tasks which can offer significant, but less predictable, step-changes in the state of the art.

The early tasks of {\bf WP 1} are quite
practical and don't require much preparation to begin. They will provide
useful experience for the later tasks.
The first three tasks of {\bf WP 2} build on a significant existing body of results and techniques for the \zxcalculus and quantum information theory.
Similarly, several tasks of {\bf WP 3} are based on known results and techniques for the \zxcalculus and rewrite theory in general. Hence, they can begin immediately.  The more challenging machine models of {\bf WP 4} are scheduled to begin in parallel with the more challenging theoretical tasks in {\bf WP 3}, anticipating a great deal of back-and-forth interaction between these two aspects of the project.
%\ref{wp:usefulstuff} requires integrating and generalising many of the 
%ideas of \ref{wp:representation} and \ref{wp:theory}, so it is mostly
%scheduled toward the end of the project.
%
%\TODOb{update pert chart}
%\begin{figure}[h]
%  \centering
%  \input{pertchart.tex}
%  
%  \caption{Dependencies and interactions between tasks} 
%\label{fig:pert}
%\end{figure}

%%%%%%%%%%%%%%%%%%%%%%%
%% Intermediate targets
%%%%%%%%%%%%%%%%%%%%%%%
%Our intermediate targets are described in the deliverables of each WP and in the milestones in \S~\ref{sec:manag-struct-milest}, with the latter focussed towards providing working pieces of software.
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}

%\newpage

\def\partnerref#1{{\hypersetup{hidelinks}\ref{#1}}}
  


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%\input{old-wps.tex}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%\newpage
%\paragraph{Work package overview}
%\label{sec:work-pack-overv}
%
%\newt{\begin{center}
%  \begin{tabular}{|p{0.2\textwidth}|c|c|c|c|c|c|}
%    \hline
%    \textbf{Partner} 
%    & \ref{wp:frontend} 
%    & \ref{wp:representation} 
%    & \ref{wp:theory}
%    & \ref{wp:usefulstuff} 
%    & \ref{wp:admin} 
%    & \textbf{TOTAL} \\\hline
%1. Grenoble   &  12 & 2 & 12 & 20 & 3  & 49 \\\hline
%2. LORIA      & 20 & 12 & 9  & 9  & 3  & 53 \\\hline
%3. Oxford     & 32 & 14 & 30 & 12 & 2  & 90 \\\hline
%4. CQC        &  4 & 0  & 6 &  2 & 0  & 12 \\\hline
%5. Gdansk     &  12& 42 & 12 & 6 & 4  & 76 \\\hline
%6. Nijmegen   &  3 & 6  & 12 & 0 & 0  & 21 \\\hline
%\textbf{TOTAL}& 83 & 76 & 81 & 49 & 12 & 301   \\\hline 
%  \end{tabular}
%\end{center}}
%
%\REM{(total effort per WP and partner in person.months)}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%\newpage
\subsection{Management structure, milestones, risk assessment}
\label{sec:manag-struct-milest}

\REM{Describe the organisational structure and the decision-making. 
\textbf{including a list of milestones (template provided). A
  milestone is a major and visible achievement. It should be SMART:
  Specific, Measurable, Attainable, Relevant, Time-bound.}
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 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.  
To assist in monitoring and evaluating progress, as well as to collaborate on WP4,
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.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%\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
%%
%\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



\paragraph{Critical risks for implementation}
\label{sec:crit-risks-impl}


\REM{Describe any critical risks, relating to project implementation, that
the stated project's objectives may not be achieved. Detail any risk
mitigation measures.\textbf{Please provide a table with critical risks
  identified and mitigating actions (template provided).}
}


The project is overall quite high-risk, in the sense that what we
propose is in the most part entirely novel, and might fail.  The
rewards for success would be correspondingly great.  However, we have
designed the project to survive the failure of many (or even most) of
its tasks and still deliver value.

We mix low and high risk activities.  Success in low
risk activities (\ref{task:trans1}, \ref{task:basic-opt}, \ref{task:ECC},
%\ref{task:axioms}, THIS IS NOT REAALY LOW RISK
\ref{task:circuit-model}, \ref{task:mbqc-model})
will still deliver significant progress towards our overall objective.
\oldt{\ref{wp:theory} is the most critical; here we mitigate the risk by
(i) developing experience on easier objectives before addressing more
demanding ones and (ii) consulting our board of advisors to foresee
problems.  Due to its high dependence on other tasks, we consider
\ref{wp:usefulstuff} to be highest risk.}\TODOb{This doesn't seem quite up-to-date, also see below}



\begin{center}
  \begin{tabular}{|p{0.25\textwidth}|c|c|p{0.4\textwidth}|}
    \textbf{Description of risk} 
    & \textbf{Likelihood}
    & \textbf{WPs involved}
    & \textbf{Proposed mitigation measures}\\\hline
%    
Can't hire suitable post-docs&
Medium&
All&
While we have already identified several suitable candidates for each
role, the investigators also collectively supervise a large body of PhD
students and post-docs who could be channelled to the project.
\\\hline
%    
NQIT or Grenoble machine info unavailable or not detailed enough&
Low&
\ref{wp:usefulstuff}&
\oldt{(i) We have members of the consortium from NQIT, and letters of
support from DiCarlo who agrees to help.  (ii) We can approach other
members of our board of advisors, or other friendly
experimentalists. (iii) We can target an more abstract model of the
machine} \\\hline
%    
Some desired technique or algorithm isn't found&   
High&
All&
All tasks where this is a risk have been structured as a collection of
related goals; if some part doesn't succeed then the finished system
will be will have fewer features, or worse performance.  However it's
very unlikely that an entire task will fail in a way that jeopardises
the project. \\\hline
%    
Software integration issues&
Medium&
All&
(i) We will establish a common API in \ref{del:earlyapi} to allow
loose coupling of the software components (ii) We appoint the most
experienced software developer in the  consortium (Valiron) to act as ``integration tzar'' and ensure
the global design is good. (iii) As noted above, we will integrate
often and deliver new features more than once a year.  
\\\hline
  \end{tabular}
\end{center}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\newpage
\subsection{Consortium as a whole} %\REM{(1 page)}
\label{sec:consortium-as-whole}

%%\REM{The individual members are described in section 3.5, there is no
%  need to repeat that information there.  
%Describe the consortium. How will it match the project's objectives
%and bring together the necessary expertise? How do the members
%complement one another? 
%In what way does each of them contribute to the project? Show that
%each has a valid role and adequate resources in the project to fulfil
%that role. 
%If applicable, describe the industrial/commercial involvement in the
%project and explain why this is consistent with and will help to
%achieve the specific measures which are proposed for exploitation of
%the results of the project.  
%}

\newt{The members  of the consortium are chosen to provide the best 
combination of skills to deliver this project, including the fathers of  \zxcalculus, those who established it as a universal and complete calculus, those who have developed applications of \zxcalculus to quantum technologies, and those who have outperformed all other methods using \zxcalculus.      
%They also contributed greatly to community building. 
 
\TODOb{Do we think it's really good to say we are the Oxford mafia?
  Also i had two other positions between Oxford and CQC -rd}
Many members also have a long history of collaboration, and in fact have been at different consortium sites at some point of their career, for example Wang was a postdoc at Nancy before moving to  Oxford and CQC. Duncan,  Horsman, Kissinger and Perdrix were postdocs at Oxford before moving to CQC, Grenoble, Nijmegen and Nancy respectively. Sainz has a long-standing collaboration with members of the Oxford Group, and organised Quantum Physics and Logic X, the main conference for \zxcalculus alike research, while at Barcelona.  Coecke is a member of the International Scientific Committee of ICTQT-Gdansk, the new institute that hosts Sainz' new group.

Several members have ongoing collaborations with Cambridge Quantum Computing Inc. In particular, co-inventor of \zxcalculus Ross Duncan is now the leading researcher at CQC, which clearly demonstrates CQC's commitment to \zxcalculus.  Quantum compilation  is moreover the key focus of CQC. Several members are  part of the NQIT Quantum Technologies Hub.\footnote{nqit.ox.ac.uk}   

%We now provide details on each of these.

Expertise on the
{\bf theoretical aspects} underpinning the project is provided by Oxford site leader Coecke and CQC research leader Duncan 
 who jointly invented the \zxcalculus\  \cite{Coecke:2009aa}. Backens, Perdrix, Jeandel and  Wang are the key  contributors to establishing universal completeness of \zxcalculus \cite{1367-2630-16-9-093021, Jeandel2017A-Complete-Axio, HFW}. Coecke pioneered general categorical and diagrammatic methods in quantum computing \cite{AbrCoe:CatSemQuant:2004}, and with Kissinger co-authored the textbook of the field \cite{Coecke2017Picturing-Quant}.
 
Expertise on {\bf quantum technology applications} is provided by those who pioneered these applications.  Duncan, Perdrix and Horsman  pioneered zx-based translations  between different computational models \cite{Duncan:2010aa, Horsman:2011lr}, Horsman and Kissinger pioneered zx-based error-correction  \cite{Chancellor2016Coherent-Parity}, and Horsman and de Beaudrap  demonstrated the equivalence of zx-rules and lattice surgery \cite{BH-2017}. 
 
Duncan and Kissinger  pioneered {\bf automation} of diagrammatic reasoning (cf.~{\tt quantomatic} and {\tt PyZX}), which also will play a key role in this project, as they already have in setting the state-of-the-art in circuit optimization \cite{DKPdW-2019}.    

We also  include pioneers in {\bf quantum
programming languages} (Valiron), important contributors to the 
theory of {\bf MBQC} (Perdrix, de Beaudrap, and Duncan) and 
{\bf quantum circuits} (Jeandel).  }  

The consortium has also been instrumental in community building, for example with the QPL conference series which now attracts well over 100 participants every year and approx.~75 paper submissions on foundational and structural research in the area of quantum computing.  It also has organised several schools e.g.~the QiCS School\footnote{www.cs.ox.ac.uk/people/bob.coecke/QICS$\underline{\ }$School.html} and the CAP Spring School,\footnote{www.cs.ox.ac.uk/ss2014/} and a substantial talks archive is maintained.\footnote{www.youtube.com/user/OxfordQuantumVideo} \newt{More recently, the several members are 
involved in the Compositionality community, which has diagrammatic/categorical reasoning as its core focus, with a new journal, a new conference series, and a new workshop series.}

\TODOb{Keeping any of this? Introducing anything else?}
\bR Of utter importance is the alignment with Networked Quantum Information Technologies Hub (NQIT) at the Oxford site, which means that several members of the consortium have already direct expertise with interacting with quantum hardware (de Beaudrap, Horsman).  The NQIT is the largest of the four Hubs in the UK National Quantum Technology Programme, a 270 GBP million investment by the UK government to establish a quantum technology industry in the UK. %We are working towards building a quantum computer demonstrator, the Q20:20 engine, which demonstrates a networked, hybrid light-matter approach to quantum information processing.
Concretely, the most important aspect is the fact that the modular architecture motivated using lattice surgery on surface codes for the logical operations, and that these are in effect \zx-operations \cite{{BH-2017}}. This will certainly make the ambition here much more achievable. \e

%\REM{From cyril to address industrial/commericial}
%Bull brings expertise in high performance simulation as well as
%industrial guidances in software. \REM{more}



\newpage%\TODOb{This needs to be done urgently}
 \subsection{Financial plan}
\label{sec:financial-plan} 

\REM{The resources to be committed for each project partner have to be
  described in the Electronic Submission System by the
  coordinator. These resources include: Personnel, Consumables,
  Equipment, Travel, Subcontracting, Provisions, Licensing fees,
  other. Justify them here. Both the justification and the information
  in the system will be communicated to the Evaluation Panel.}

\paragraph{Personnel} 
\label{sec:personnel}

This is a large and multifaceted project, which will require
significant work to deliver.  A full-time post doc at each contributing academic
site is needed, under supervision of the site lead.  In addition, At
all the academic sites there is a large amount of time donated to the
project by senior scientists with relevant expertise.  At CQC, our
industrial partner, a Senior Scientist and a Research Software Developer will contribute to the project.

\begin{itemize}
\item \emph{Post-doctoral researchers}: We request 30 months of salary
  for post-docs at Oxford, 36+18 months at Gdansk, and 18 months at each of Grenoble and LORIA. The Oxford post-doc will also engage in co-operation with industrial partners at CQC.  The post-docs
  will be hired as soon as possible by the site leads at each site.
%\item \emph{Coordinator}: We request 10\% contribution the
%  Duncan's salary at Strathclyde to cover the time spent managing
%  the project. This is reduced from 20\% upon negotiation with
%  Stratclyde.  (Duncan will contribute an additional 8.4 months of
%  time as a researcher, see below.)
\item \emph{Principle investigators and other named staff}: Spread
  across the sites, more than 110 person-months of time
  will be contributed by the named staff on the project, all of which
  is supported by other sources.  This means that almost 40\% of the
  research effort of the project is funded from elsewhere.
\item \emph{PhD Students}: at LORIA, Titouan Carette will contribute
  approx 9 months to the project; this is funded from other sources.
  At Grenoble, Richard East will contribute
  approx 9 months to the project; this is funded from other sources.
  At Gdansk, a PhD student will contribute
  approx 12 months to the project; this is funded from other sources. \newt{At Oxford, at least two PhD students will contribute to the project, as well as several MSc students}.
\item \emph{Engineers}: At CQC, a Senior Scientist and a Research Software Developer will contribute, funded from other sources.
\end{itemize}

\paragraph{Workshops}
\label{sec:workshops}

Project workshops serve a key role in intra-project communication,
dissemination, and outreach.  We plan one workshop each year, in
Oxford, Nijmegen, and Grenoble.  We plan to invite significant figures from the experimental and software industrial communities to supplement the project reach and expertise, which increases the cost beyond
the usual expenses of venue hire and speakers' expenses.  We have
budgeted
\euro 15k for each, through the co-ordinating site budget.

\paragraph{Travel and subsistence} 
\label{sec:travel-subsistence}

Since many of the personnel have expertise relevant to more than one
work package, we request substantial budget for travel, for quantERA
reporting meetings, for formal project meetings, smaller more frequent
WP meetings, and also to present our work at conferences.

\paragraph{Equipment}
\label{sec:equipment}

\begin{itemize}
\item We  request laptop computers for each of the postdocs, and
  replacement laptops for some staff.  These are necessary
  because of the frequent need to travel and work at another site
  and/or present work at conferences or workshops.
\end{itemize}

%%% Local Variables:
%%% mode: latex
%%% TeX-master: t
%%% End: