Skeleton is the right word.
A festering, zombified corpse of a thesis, with it's eyes picked out by crows.
But soon the Valkyries will arrive and escort it to the halls of Valhalla where it will be immortalised forever.
Although it will probably not enjoy it, because being a thesis it will be embarressingly nerdy and always
get beaten up by the Tom Clancy novels, and be picked last for the teams in the daily epic battles.
But despite that it will grow strong with age and the citation count will grow and one day if it is very, very lucky, someone may actually read it
Whoops, there goes my suspension of disbelief.
--- /dev/null
+\chapter{Approach}
+
+Repeat the plans as outlined in the project proposals\cite{proposalMoore,proposalGow}\footnote{Sam Moore's proposal has not been assessed but was submitted jointly with David Gow's to CSSE}.
+
+Explain changes from the original proposal.
+\begin{itemize}
+ \item No mention of hardware considerations in proposal, but Sam Moore's topic ``how can we increase the precision of real number representations'' was in the original scope, and can't be answered without considering hardware.
+\end{itemize}
+
--- /dev/null
+\chapter{Physical Limitations on Precision}\label{BackgroundHardware}
+
+This chapter will focus on the physical limitations on precision due to hardware. It will describe the traditional approaches to working with real numbers and the current state of the art.
+
+NOTE: Depending on how much I get into the VHDL stuff, this chapter may seem less relevant to the actual research we are doing and it might be very short.
+However I think even if I do not actually do any hardware designs, a literature review about precision of numbers would not be complete if it only mentioned software algorithms.
+
+
+
+\section{Real Number Representations}
+
+This section will discuss representations of real numbers in hardware, including the trivial: fixed point, IEEE floating points, and anything else I find that is interesting.
+
+
+\section{Floating Point Units}
+
+This section will give an overview of FPUs, focusing on IEEE.
+
+\section{Graphical Processing Units}
+
+This section will discuss anything relevant we can find on GPUs, but will probably be very short.
+
--- /dev/null
+\chapter{Virtual Representations of Real Numbers}\label{BackgroundSoftware}
+
+SoftFloat libraries (fixed precision)
+
+boost library for increased (but still fixed) precision.
+
+Algorithms for arbitrary precision?
+Mathematica uses arbitrary precision numbers. Will they have a reference or report on this anywhere?
+
--- /dev/null
+\chapter{Conclusion}\label{Conclusion}
+
+We will have hopefully done the following:
+
+\begin{itemize}
+ \item Demonstrated precision issues due to traditional (Select one or more of the following!)
+ \begin{itemize}
+ \item Physical representation of real numbers
+ \item Algorithms
+ \item Document formats
+ \end{itemize}
+ \item Demonstrated something better
+ \item Written a less shitty report than this one.
+\end{itemize}
--- /dev/null
+\chapter{Implementation Notes}\label{Implementation}
+
+This will be the easiest and also least important chapter to write.
--- /dev/null
+\chapter{Introduction}\label{Introduction}
+
+The introduction will be witty and engaging and a joy to read.
+
+I hope.
+
+Points to address:
+\begin{enumerate}
+ \item What this is.
+ \item Why we should care
+ \item Most recent development
+ \item Do we really mean ``infinite''? (No. Sorry. We lied)
+ \item Foundational papers. Historical notes.
+\end{enumerate}
+
+See also: The Abstract.
+See also: The Conclusion.
+
+The remainder of this report will be organised as follows: Chapters \ref{BackgroundHardware} and \ref{BackgroundSoftware} will discuss approaches to representation of numbers in both Hardware and Software respectively; Chapter \ref{Approach} will outline the approach [reword] considering <insert fuzzy list of faculty dependent requirements here (Safety, Ethics, Group Work Process, etc)>. Chapter/Appendices \ref{Implementation} will provide implementation notes. Chapter \ref{Results} will describe our results. Chapter \ref{Conclusion} will be the conclusion.
+
+
+
+NOTE: Given that I don't actually need a full thesis, change from Chapters to Sections?
+NOTE2: Will treat as a full thesis but if it gets too big, submit a condensed version as the MCTX "report".
+
+NOTE3: In final version, put the Approach at the end and/or in appendices before the Implementation notes rather than the start (?)
+What we will be doing and why.
+
+See also the Introduction.
+See also the Conclusion.
+
+\begin{itemize}
+ \item Research into document formats is mostly focusing on embedding dynamic content in the document
+ \item TODO: Desperately try to find research into increasing precision in documents
+ \begin{itemize}
+ \item I suspect the reason it is hard to find references saying ``We increased the precision you can get in this graphics format'' is because the real research is into ``how to get more precision out of a number'' and increasing the precision in a graphics format is just an application.
+ \item Talk about why precision in itself is a good thing?
+ \begin{itemize}
+ \item Reduced error in computations
+ \end{itemize}
+ \item Somehow manage to link this to graphics formats.
+ \begin{itemize}
+ \item Increased precision means you can have more zoom, you can have more range
+ \item This is useful because the view of a document as a sheet of paper is increasingly outdated
+ \end{itemize}
+ \item Precision in itself is necessary in order to address the document format issue.
+ \end{itemize}
+ \item In particular we are looking into increasing precision vs IEEE floats because:
+ \begin{itemize}
+ \item Such research is important in its own right; eg: Doing numerical calculations requires high accuracy results
+ \end{itemize}
+ \item
+\end{itemize}
+
+I guess what I am trying to say very badly is:
+
+We want to be able to do more things with documents.
+We are currently limited by the precision of floating point operations. This is a fundamental and physical limit on what can be done.
+
+Even things like postscript are already turing complete. All the fancy papers about putting dynamic content and javascript and things in documents
+are not addressing a physical limitation, merely one of convenience for the document creator.
+
+So it is worth looking into how we can reduce or eliminate the physical limitations on what can be done with a document due to floating point precision.
+
+
%---------------------------------------------------------
%Include the chapters!
-%\include{chapters/Introduction}
+\include{chapters/Introduction}
-%\include{chapters/Overview} % This is chapter 1
+\include{chapters/BackgroundHardware}
+\include{chapters/BackgroundSoftware}
-%\include{chapters/Techniques} % This is chapter 2
+\include{chapters/Approach} % This is chapter 2
+\include{chapters/Implementation}
-%\include{chapters/Results} % etc.
+\include{chapters/Results} % etc.
-%\include{chapters/Conclusion}
+\include{chapters/Conclusion}
%\newpage
%---------------------------------------------------------
\renewcommand{\bibname}{References}
git.ucc.asn.au / ipdf / sam.git / commitdiff
UCC git Repository :: git.ucc.asn.au