@@ -890,99 +890,60 @@ showing how they inter-relate (Pert chart or similar).
}
The work plan has four major scientific work packages (WPs),
%each focusing on a different \emph{theme} within the project. The work packages
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.)
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[\ref{wp:frontend}] is focussed on \newt{the \dzxc interface with known high-level quantum programming languages}
\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 \newt{for benchmarking}.
\item[\ref{wp:representation}]\newt{is focussed on the further development of zx calculus, its axiomatic formulation, and its status as a theory of resources.}
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[\ref{wp:theory}]
\newt{focusses on resource optimization, such as gate reduction in circuit representations, efficient intelligent error-correction, and other deep algorithms.}
\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[\ref{wp:usefulstuff}]
\newt{applies all the previous to specific quantum hardware.}
\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. Broadly speaking,
the tasks are sequenced in order of technical difficulty so that
experience gained on earlier tasks can be applied to the more
difficult ones. There are strong interactions between the tasks, and
early outputs of each WP will be used in later outputs of other WPs.
(Details about the tasks are found in \S~\ref{sec:work-packages}.)
\begin{figure}[th]
\centering
\makebox[\textwidth][c]{\input{ganttchart.tex}}
\caption{Approximate timings and durations of tasks (months)}
\label{fig:gantt}
\end{figure}
%%%%%%%%%%%%%%%%%%%%
%% Overall structure
%%%%%%%%%%%%%%%%%%%%
The project is a single integrated whole, so there are many linkages
between the work packages; these are displayed in
Figure~\ref{fig:pert}. As discussed in
\TODOb{I don't think this is actually discussed in \S~\ref{sec:manag-struct-milest}}
\S~\ref{sec:manag-struct-milest}, only some of these linkages are true
dependencies, where later tasks rely on results of earlier ones. On the other hand, many tasks can influence and enhance each other as they run in parallel.
Our work plan consists of a balance of short tasks with concrete software deliverables (e.g. \ref{task:circuit-model}, \ref{task:mbqc-model}) and longer term, more ambitious and open-ended tasks (e.g. \ref{task:algorithms} and \ref{task:opt-machine}) which can offer significant, but less predictable, step-changes in the state of the art.
Several tasks of \ref{wp:frontend} are ``long and thin'': that is, they are intended to work in parallel with the other WPs, with new features being integrated as they are developed.
Similarly, much of the theoretical work in \ref{wp:representation} and \ref{wp:theory} is intended to be developed alongside the more implementation-oriented WPs.
These theory-oriented WPs will draw inspiration from the practical ones and feed back into them in turn.
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 \ref{wp:frontend} are quite
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 \ref{wp:representation} build on a significant existing body of results and techniques for the \zxcalculus and quantum information theory.
Similarly, several tasks of \ref{wp:theory} are based on known results and techniques for the \zxcalculus and rewrite theory in general.
Hence, they can begin immediately.
This will provide an ample source of theoretical work to do until the more implementation-oriented tasks \ref{task:circuit-model} and \ref{task:mbqc-model} provide enough examples and use cases to feed into tasks \ref{task:resourcesagain}, \ref{task:annotate1} and \ref{task:annotate2}.
The more challenging machine models of \ref{task:qdot-model},
\ref{task:NQIT-model} and \ref{task:IBM-model} are scheduled to begin in parallel with the more challenging theoretical tasks in \ref{wp:theory}, 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}
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 (\ref{del:qudits}), developing representations for recursion and control (\ref{del:recursion}), and expressing topological and causal constraints (\ref{del:topology}).
Throughout the project, we will check the performance of our methods against competitors (\ref{del:outperform}) and benchmark our software using the open test-suite we will develop (cf.\ \ref{task:testBench}).
%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.
\TODOb{is this paragraph needed/needed here?}
The allocation of staff to work packages is discussed in
\S~\ref{sec:consortium-as-whole} and \S~\ref{sec:descr-cons}.
However, 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
receive attention from the personnel of several sites. This degree of
collaboration is a strong point of this project.
collaboration is a strong point of this project.\e}
