From 679bf90646759d0bcc7e58c11f7bb5c77ef8aded Mon Sep 17 00:00:00 2001
From: Ross Duncan <ross.duncan@strath.ac.uk>
Date: Fri, 15 Feb 2019 22:54:51 +0000
Subject: [PATCH] Updated risks
---
NEWPROPOSAL/FULLPROP.tex | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/NEWPROPOSAL/FULLPROP.tex b/NEWPROPOSAL/FULLPROP.tex
index dcc5cd2..783f167 100644
--- a/NEWPROPOSAL/FULLPROP.tex
+++ b/NEWPROPOSAL/FULLPROP.tex
@@ -1677,6 +1677,7 @@ Complete deep-\zx compiler stack with open APIs. \\\hline
\end{tabular}}
\end{center}
+\e
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -1694,7 +1695,7 @@ mitigation measures.\textbf{Please provide a table with critical risks
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 may (or even most) of
+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
@@ -1702,7 +1703,7 @@ 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.
-\ref{wp:backends} is the most critical; here we mitigate the risk by
+\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
@@ -1718,14 +1719,16 @@ problems. Due to its high dependence on other tasks, we consider
& \textbf{Proposed mitigation measures}\\\hline
%
Can't hire suitable post-docs&
-Low&
+Medium&
All&
-We have already identified several suitable candidates for each role.
+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 Delft machine info unavailable or not detailed enough&
+NQIT or Grenoble machine info unavailable or not detailed enough&
Low&
-\ref{wp:backends}&
+\ref{wp:usefulstuff}&
(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
@@ -1746,14 +1749,13 @@ 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 developers in the consortium (Allouche,
-Kissinger, Valiron) to act as ``integration triumvirate'' and ensure
+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
+\\\hline
\end{tabular}
\end{center}
-\e
+
\newpage
\subsection{Consortium as a whole} %\REM{(1 page)}
--
GitLab