From 47ba7cc40dc91618b61700450d3be7afcb5eb838 Mon Sep 17 00:00:00 2001
From: Bob Coecke <coecke@cs.ox.ac.uk>
Date: Fri, 15 Feb 2019 11:01:16 +0000
Subject: [PATCH] bits in 3.1
---
NEWPROPOSAL/FULLPROP.tex | 40 ++++++++++++++++++++--------------------
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/NEWPROPOSAL/FULLPROP.tex b/NEWPROPOSAL/FULLPROP.tex
index a11cea6..70432ea 100644
--- a/NEWPROPOSAL/FULLPROP.tex
+++ b/NEWPROPOSAL/FULLPROP.tex
@@ -1054,7 +1054,7 @@ open-source basis with a permissive license (See \S~\ref{sec:cons-agre}.) \e
%%provide an HPC simulator with a publicly accessible front end, which
%%will also be incorporated into the project website.
-Beyond online self-publishing we will also pitch articles to magazines
+Beyond online self-publishing we will also pitch articles to magazines
aimed at a general audience in several languages. We will
specifically target:
\begin{itemize}
@@ -1099,8 +1099,7 @@ this document.}
\section{IMPLEMENTATION}
\label{sec:impl-2-pages}
-\subsection{Work plan \REM{(2 pages)}}
-\label{sec:work-plan-work}
+\subsection{Work plan \REM{(2 pages)}} \label{sec:work-plan-work}
\REM{Provide a brief presentation of the overall structure of the work plan.
Clearly define the intermediate targets.
@@ -1110,24 +1109,27 @@ Provide a graphical representation of the work packages components
showing how they inter-relate (Pert chart or similar).
}
-\oldt{The work plan has four major scientific work packages, each focusing
-on a different \emph{theme} within the project. The work packages
-will proceed in parallel, and all will have at least some activities
+The work plan has four major scientific work packages,
+%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
work package grouping administrative and organisational activities.)
\begin{description}
-\item[\ref{wp:frontend}] is focussed on translating from HLLs into
- \azx, reflecting higher level programming constructs into \azx, and
- building a test suite of programs.
-\item[\ref{wp:backends}] is about modelling the properties of
- different machines in \azx, and translating \azx to hardware.
-\item[\ref{wp:theory}] develops the theory behind \azx and algorithms
- to realise the logical ideas.
-\item[\ref{wp:usefulstuff}] applies these advances to the
-creation of useful quantum software, specifically focusing on
-optimisation and error correction.
+\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.
+\item[\ref{wp:backends}] \newt{is focussed on the further development of zx calculus, its axiomaic 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.}
+%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.}
+%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
+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
@@ -1135,9 +1137,8 @@ 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]
+\oldt{\begin{figure}[th]
\centering
\makebox[\textwidth][c]{\input{ganttchart.tex}}
@@ -1145,7 +1146,6 @@ early outputs of each WP will be used in later outputs of other WPs.
\label{fig:gantt}
\end{figure}
-\oldt{
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
--
GitLab