From dacb026a5d2aa4817b555a8804c4433ca83bc791 Mon Sep 17 00:00:00 2001
From: Miriam Backens <miriam.backens@cs.ox.ac.uk>
Date: Fri, 15 Feb 2019 15:09:29 +0000
Subject: [PATCH] mostly implementing changes from Niel's merge-conflicted
version
---
NEWPROPOSAL/FULLPROP.tex | 33 ++++++++++++---------------------
1 file changed, 12 insertions(+), 21 deletions(-)
diff --git a/NEWPROPOSAL/FULLPROP.tex b/NEWPROPOSAL/FULLPROP.tex
index 7096bd1..adea061 100644
--- a/NEWPROPOSAL/FULLPROP.tex
+++ b/NEWPROPOSAL/FULLPROP.tex
@@ -890,10 +890,10 @@ Modelling error correction in \newt{the annotated \zxcalculus} will thus enable
%doing cool stuff with cool stuff
-The retargetable \newt{\dzxc} system will make it easy to support new quantum
-devices, thus making the latest developments in quantum technology available to all academic and industrial users, and maximising the return on investment in quantum computing.
+\newt{The purpose of the \dzxc system is to form the basis of a retargetable compiler, making it easy to support new quantum devices.
+This will help to make the latest developments in quantum technology available to all academic and industrial users, maximising the return on investment in quantum computing.}
Our consortium includes an industrial partner (\newt{Cambridge Quantum Computing}) to help ensure the industrial relevance of our work.
-We also have experimental figures on the advisory panel.
+We also have \newt{experimentalists} on the advisory panel.
With \newt{the \dzxc system}, high-level quantum languages and protocols can be designed without needing to know the underlying hardware.
This will streamline the production of quantum software, opening it up to individuals and companies with limited prior knowledge of quantum computing.
Quantum hardware will also be more accessible, both in academia and industry. Individual developers will not need to know the entire architecture, as different elements can be \newt{adapted to automatically during compilation}.
@@ -919,15 +919,9 @@ This will accelerate the widespread commercial and academic development and expl
%The inherently interdisciplinary nature of this project will bring a larger community to bear solving problems during the lifetime of the project. The development of the \azx language and compiler stacks themselves will also open up further challenges as the project progresses (and beyond) that are accessible to broader communities.
\newt{The \dzxc system} will connect the entire range of knowledge involved in building quantum technologies, from experimental and theoretical Physics, through to quantum computing theory, and on to formal methods of Computer Science.
All of these are needed to develop the deep compilation system, \newt{so developing the \dzxc system} is a fundamentally interdisciplinary task.
-This \newt{system} opens the prospect of an acceleration in the development of quantum algorithms in a way which can then \newt{easily be adapted} to many different hardware platforms.
-For example, algorithm and protocol designers will not need to interface directly with quantum technologies: the \newt{\dzxc system} does all the compilation and optimisation necessary. This will allow the
-integration of quantum computing into mainstream Computer Science, and so the easy importing of tools (for example, techniques for optimisation or verification) that have been developed over many years.
-By aiding the development of intuitively accessible programming
-languages, \newt{the \dzxc system} will also make quantum technologies
-accessible to a broader range of users and developers. End-users
-outside quantum physics and computer science will be able to build
-protocols for use in their own field that do not require them to
-understand the physical action of the hardware.
+\newt{By aiding the development of intuitively accessible programming languages, the \dzxc system will also make quantum technologies accessible to a broader range of users and developers.
+For example, algorithm and protocol designers will not need to interface directly with quantum technologies in order to test the effectiveness of their work, lowering the bar for development in the field.
+End-users outside of quantum physics and computer science will also be able to build protocols for use in their own field that do not require them to understand the physical action of the hardware.}
The \dzxc system will not be a closed system: our commitment to open
APIs (See \ref{task:trans1} and \ref{task:backendapi}) and our open
@@ -986,7 +980,8 @@ publication venues are conferences with published proceedings.)
(QIP), \emph{Theory of Quantum Computation} (TQC), and \emph{Quantum
Physics and Logic} (QPL).
\item Mainstream computer science venues: the \emph{Journal of the
- ACM} (JACM), \emph{Logic in Computer
+ ACM} (JACM),
+ the \emph{International Conference on Computer-Aided Design} (ICCAD), \emph{Logic in Computer
Science} (LiCS), \emph{Principles of Programming Languages}
(POPL), \emph{Automata, Logic and Programming} (ICALP), \emph{Tools
and Algorithms for the Construction and Analysis of Systems}
@@ -1026,14 +1021,10 @@ post-doc will spend approximately 25\% of their time on site at the
CQC offices in Cambridge.
-\TODOb{Niel/Dom please confirm NQIT role.} \bR With NQIT, we will
-provide a programming framework for the networked quantum computer
-developed as part of that project. As part of this we will present the
-project results at the semi-annual NQIT Industry Forum events and the
-UK Quantum Technologies annual showcase. To further this aim, our
-postdoc in Oxford will spend 10--20\% of their time working closely
-with the NQIT project. In both cases, our work can be exploited
-directly by end-users. \e
+\newt{With NQIT, we will provide a programming framework for the networked quantum computer developed as part of that project (and the quantum computing project which follows afterwards in Phase~II of the UK Quantum Technologies Programme), seek to collaborate with their architectures team, and present the project results at the UK Quantum Technologies annual showcase.
+
+In both cases, our work can be exploited
+directly by end-users.} %% copied from Niel's document so I assume this is up-to-date
\TODOb{This para to be cut.}
\bR In addition, we have also recruited a board of advisers (see below)
--
GitLab