@@ -1093,15 +1093,15 @@ Provide a graphical representation of the work packages components
showing how they inter-relate (Pert chart or similar).
}
The work plan has four major scientific work packages,
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, and all will have at least some activities
throughout the length of the project. (There is also a fifth
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}
%translating from HLLs into \azx, reflecting higher level programming constructs into \azx,
and building a test suite of programs.
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.}
%is about modelling the properties of different machines in \azx, and translating \azx to hardware.
\item[\ref{wp:theory}]
...
...
@@ -1122,42 +1122,46 @@ 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}.)
\oldt{\begin{figure}[th]
\begin{figure}[th]
\centering
\makebox[\textwidth][c]{\input{ganttchart.tex}}
\caption{Approximate timings and durations of tasks (months)}
\label{fig:gantt}
\end{figure}}
\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}) 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.
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.
The 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.
The early tasks of \ref{wp:frontend} and \ref{wp:representation} are quite
The early tasks of \ref{wp:frontend} 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 first two tasks of \ref{wp:theory} build on a significant existing body of results and techniques for the \zx-calculus and rewrite theory in general. Hence, they can begin straight away. 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:annotate1} and \ref{task:annotate2}.
The more challenging machine models of \ref{task:qdot-model} and
\ref{task:NQIT-model} are scheduled to begin in parallel with the more challenging theoretical tasks in WP3, anticipating a great deal of back-and-forth interaction between these two aspects of the project.
% delayed until sufficient theory has been
% developed to attempt them.
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}
...
...
@@ -1166,6 +1170,15 @@ scheduled toward the end of the project.
\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}).
\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
...
...
@@ -1331,12 +1344,12 @@ We will use the existing graph re-writing and automated theorem proving tools of
\end{WPtasks}
\begin{WPdeliverables}
\WPdeliverable{M9}{Preliminary assessment of the comparative study of the axiomatizations of paradigms of quantum computation}
\WPdeliverable{M14}{Completeness of qudit \zxcalculus}
\WPdeliverable{M18}{\zx formalism for recursion and control}
\WPdeliverable[\label{del:qudits}]{M14}{Completeness of qudit \zxcalculus}
\WPdeliverable[\label{del:recursion}]{M18}{\zx formalism for recursion and control}
\WPdeliverable{M20}{Preliminary assessment of nonclassicality of re-writing processes}
\WPdeliverable{M24}{\zx representation and explanation of the result that promotes magic states as a resource of quantum computation}
\WPdeliverable{M30}{\zx formulation of contextuality (Kochen--Specker and/or Spekken's)}
\WPdeliverable{M36}{Characterisation of set of generic non-classical resources for quantum speed-up}
\WPdeliverable{M24}{\zx representation and explanation of the result that promotes magic states as a resource of quantum computation}
\WPdeliverable{M30}{\zx formulation of contextuality (Kochen--Specker and/or Spekken's)}
\WPdeliverable[\label{del:non-classicality}]{M36}{Characterisation of set of generic non-classical resources for quantum speed-up}
\end{WPdeliverables}
\end{WP}
...
...
@@ -1410,13 +1423,13 @@ We develop practical logical and algorithmic techniques for transforming ``abst
%\WPdeliverable{M18}{\zx language constructs for basic control flow, repetition and recursion}
\WPdeliverable{M36}{\newt{Generalisations of PyZX and other general-purpose techniques and
algorithms + software for simplifying \zx terms}.}
\WPdeliverable{M18}{An extended \zx language which expresses
\WPdeliverable[\label{del:topology}]{M18}{An extended \zx language which expresses
topological and quantitative properties, with associated
reasoning techniques.}
\WPdeliverable{M24}{\newt{Setting the state-of-the-art for all forms of circuit optimization}.}
\WPdeliverable[\label{del:outperform}]{M24}{\newt{Setting the state-of-the-art for all forms of circuit optimization}.}
\WPdeliverable{M24}{\newt{Optimization techniques for a variety of computational models}.}
% \WPdeliverable{M24}{Routines for adding error-correction to \zx programs}
\WPdeliverable{M36}{Routines for adding error-correction to ZX programs.}
\WPdeliverable{M36}{Routines for adding error-correction to \zx programs.}
