XGitUrl: https://git.ucc.asn.au/?p=ipdf%2Fsam.git;a=blobdiff_plain;f=chapters%2FProposal.tex;h=f8e1ed07805c6f9460ab2c3af44aa0edc4370e0a;hp=dd2f8e675c867d24672adb049b8136befd3418ac;hb=747a93660e5c5784f9f76b6c4f2a60bb92f7bdf3;hpb=b1c5fe49ec552755fd19073c3f91c8e9866d6938
diff git a/chapters/Proposal.tex b/chapters/Proposal.tex
index dd2f8e6..f8e1ed0 100644
 a/chapters/Proposal.tex
+++ b/chapters/Proposal.tex
@@ 6,13 +6,13 @@
\section{Aim}
In this project, we will explore the state of the art of current document formats including PDF, PostScript, SVG, HTML, and the limitations of each in terms of precision.
We will consider designs for a document format allowing graphics primitives at an arbitrary level of zoom with no loss of detail. We will refer to such a document format as ``infinite precision''. A viewer and editor will be implemented as a proof of concept; we adopt a low level, ground up approach to designing this viewer so as to not become restricted by any single existing document format.
+We will consider designs for a document format allowing graphics primitives at an arbitrary level of zoom with no loss of detail. A viewer and editor will be implemented as a proof of concept; we adopt a low level, ground up approach to designing this viewer so as to not become restricted by any single existing document format.
There are many possible applications for documents in which precision is unlimited. Several areas of use include: visualisation of extremely large or infinite data sets; visualisation of high precision numerical computations; digital artwork; computer aided design; and maps.
\subsection{Clarification of Terms}
It may be necessary to clarify what we mean by the terms ``infinite precision'' and ``document formats''. Regarding the latter, we consider a document format to be any representation of visual information which is capable of being stored indefinitely. Regarding the former, we do not propose to be able to contain an infinite amount of information within such a document. The goal is to be able to render a primitive at the same level of detail it is specified by a document format, regardless of how precise this level is. For example, the precision of coordinates of primitives drawn in a graphical document editor will always be limited by the resolution of the display on which they are drawn, but not by the viewer.
+It may be necessary to clarify what we mean by the terms ``arbitrary precision'' and ``document formats''. Regarding the latter, we consider a document format to be any representation of visual information which is capable of being stored indefinitely. Regarding the former, we do not propose to be able to contain an infinite amount of information within such a document. The goal is to be able to render a primitive at the same level of detail it is specified by a document format, regardless of how precise this level is. For example, the precision of coordinates of primitives drawn in a graphical document editor will always be limited by the resolution of the display on which they are drawn, but not by the viewer.
\section{Methods}
@@ 25,17 +25,15 @@ At this stage we have identified two possible areas for individual research:
\item {\bf Arbitrary Precision real valued numbers}  Sam Moore
 We plan to investigate the representation of real values to a high or arbitary degree of precision. Such representations would allow for a document to be implemented
 using a single global coordinate system. However, we would expect a decrease in performance with increased complexity of the data structure used to represent a real value. \rephrase{Both software and hardware techniques will be explored.} We will also consider the limitations imposed by performing calculations on the GPU or CPU.
+ We plan to investigate the representation of real values to a high or arbitary degree of precision. Such representations would allow for the coordinates of primitives to be relative to a single global coordinate system. We would expect a decrease in performance with increased complexity of the data structure used to represent a real value. \rephrase{Both software and hardware techniques will be explored.} We will also consider the limitations imposed by performing calculations on the GPU or CPU.
 Starting points for research in this area are Priest's 1991 paper, ``Algorithms for Arbitrary Precision Floating Point Arithmetic''\cite{priest1991algorithms}, and Goldberg's 1992 paper ``The design of floating point data types''\cite{goldberg1992thedesign}. A more recent and comprehensive text book, ``Handbook of Floating Point Arithmetic''\cite{HFP}, published in 2010, has also been identified as highly relevant.
+Starting points for research in this area are Priest's 1991 paper, ``Algorithms for Arbitrary Precision Floating Point Arithmetic''\cite{priest1991algorithms}, and Goldberg's 1992 paper ``The design of floating point data types''\cite{goldberg1992thedesign}. A more recent and comprehensive text book, ``Handbook of Floating Point Arithmetic''\cite{HFP}, published in 2010, has also been identified as highly relevant.
\item {\bf Local coordinate systems}  David Gow \cite{proposalGow}
An alternative approach involves segmenting the document into different regions using fixed precision floats to define primitives within each region. A quadtree or similar data structure could be employed to identify and render those regions currently visible in the document viewer.\rephrase{Say more here?}
\end{enumerate}
\pagebreak
We aim to compare these and any additional implementations considered using the following metrics:
\begin{enumerate}
@@ 70,36 +68,6 @@ We aim to compare these and any additional implementations considered using the
Due to the relative immaturity and inconsistency of graphics drivers on mobile devices, our proof of concept will be developed for a conventional GNU/Linux desktop or laptop computer using OpenGL. However, the techniques explored could easily be extended to other platforms and libraries.
\pagebreak

\section{Timeline}

Deadlines enforced by the faculty of Engineering Computing and Mathematics are \emph{italicised}.\footnote{David Gow is being assessed under the 2014 rules for a BEng (Software) Final Year Project, whilst the author is being assessed under the 2014 rules for a BEng (Mechatronics) Final Year Project; deadlines and requirements as shown in Gow's proposal\cite{proposalGow} may differ}.

\begin{center}
\begin{tabular}{lp{0.5\textwidth}}
 {\bf Date} & {\bf Milestone}\\
 \hline
 $1^{\text{st}}$ May & Testbed Software (basic document format and viewer) completed and approaches for extending to allow infinite precision identified. \\
 \hline
 ? May & Draft Progress Report and Literature Review \\
 \hline
 $26^{\text{th}}$ May & \emph{Progress Report and Literature Review due.}\\
 \hline
 $9^{\text{th}}$ June & Demonstrations of limitations of floating point precision in the Testbed software. \\
 $1^{\text{st}}$ July & At least one implementation of infinite precision for basic primitives (lines, polygons, curves) completed. Other implementations, advanced features, and areas for more detailed research identified. \\
 \hline
 $1^{\text{st}}$ August & Experiments and comparison of various infinite precision implementations completed. \\
 \hline
 $1^{\text{st}}$ September & Advanced features implemented and tested, work underway on Final Report. \\
 \hline
 TBA & \emph{Conference Abstract and Presentation due.} \\
 \hline
 $10^{\text{th}}$ October & \emph{Draft of Final Report due.} \\
 \hline
 $27^{\text{th}}$ October & \emph{Final Report due.}\\
 \hline
\end{tabular}
\end{center}
+