summaryrefslogtreecommitdiffstats
path: root/report
diff options
context:
space:
mode:
authorchris.sutcliffe <ctd.sutcliffe@gmail.com>2021-12-15 01:19:05 +0000
committerchris.sutcliffe <ctd.sutcliffe@gmail.com>2021-12-15 01:19:05 +0000
commit2ec06a08a0a544fc9151481b1cefc78a95f3913b (patch)
tree3e00e72cd5988b820d7f8ec47a722b89114c42fb /report
parent902aebba31a4a01a6d43e6ee38c5ad5414e98e34 (diff)
downloadesotericFORTRAN-2ec06a08a0a544fc9151481b1cefc78a95f3913b.tar.gz
esotericFORTRAN-2ec06a08a0a544fc9151481b1cefc78a95f3913b.zip
remove useless sections of report
Diffstat (limited to 'report')
-rw-r--r--report/esoteric_project_report.pdfbin320097 -> 293516 bytes
-rw-r--r--report/esoteric_project_report.tex71
2 files changed, 0 insertions, 71 deletions
diff --git a/report/esoteric_project_report.pdf b/report/esoteric_project_report.pdf
index 7d70c58..2156a5d 100644
--- a/report/esoteric_project_report.pdf
+++ b/report/esoteric_project_report.pdf
Binary files differ
diff --git a/report/esoteric_project_report.tex b/report/esoteric_project_report.tex
index 82c4e2c..8ab54d3 100644
--- a/report/esoteric_project_report.tex
+++ b/report/esoteric_project_report.tex
@@ -561,77 +561,6 @@ hello6 world
\section{Final implementation}
-\section{Figures, tables, etc.}
-\label{Figures}
-
-The purpose of this section is to just show you how to integrate figures, tables, etc.\ and should disappear in the final report. Figures and tables should be distributed across the document wherever they are needed but you should use an appendix if they are many figures/tables of the same kind. Fig.\ \ref{Pelvis_BVH} shows a bony pelvis.
-
-\begin{figure}[htb]
-%\begin{center}
-\caption{The bony pelvis model with octree based AABBs (Axis Aligned Bounding Boxes).}
-\label{Pelvis_BVH}
-%\end{center}
-\end{figure}
-
-Fig.\ \ref{class} shows a UML class diagram (class, sequence and state diagrams are the most frequently used UML diagrams):
-
-\begin{figure}[htb]
-%\begin{center}
-\caption{A UML class diagram.}
-\label{class}
-%\end{center}
-\end{figure}
-
-Algorithms can be either used in this chapter or alternatively in Chapter \ref{MethLab} if it is a more generic algorithm:
-
-\begin{algorithm}[th]
-\caption{ The projection based contact method algorithm }
-\begin{algorithmic}[1]
-\STATE Retrieve current node displacement $u$
-\\ \texttt{float3 u = m\_U\_new[nodeIndex].xyz;}
-\STATE Retrieve constraint plane equation
-\\ \texttt{float4 plane = m\_constraintMagnitude[nodeIndex];}
-\STATE Calculate dot product with plane normal
-\\ \texttt{float d = dot(u, plane.xyz);}
-\STATE Find node penetration into the plane's negative half-space
-\\ \texttt{float penetration = plane.w - d;}
-\IF {penetration is greater than zero}
- \STATE Find projection onto the plane surface
-
- \texttt{float3 proj = u + plane.xyz * penetration;}
- \STATE Prescribe new nodal position to be on the surface
-
- \texttt{m\_U\_new[nodeIndex] = (float4)(proj, 0.0f);}
-\ENDIF
-\end{algorithmic}
-\end{algorithm}
-
-Tables such as Table \ref{Res01} can also be useful here or in Chapter \ref{MethLab}.
-
-\begin{table}[h]
-\caption[]{Original diameters and diametral strains as reported by
- Sorbe and Dahlgren \cite{Sorbe:1983} (columns 1-2), from a previous
- experiment by Lapeer and Prager and reported in \cite{Lapeer:2001}
- (columns 3-4), and from the current experiment (columns 5-6).}
-\begin{center}
-\begin{tabular}{|l|c|c||c|c||c|c|}\hline
-& \multicolumn{2}{c||}{S-D} & \multicolumn{2}{c||}{L-P old} & \multicolumn{2}{c|}{L-P new} \\ \hline
-Diameter & length & strain & length & strain & length & strain \\ \hline
-$\mi{MaVD}$ & 140.5 & +1.90 & 129.3 & +0.30 & 129.3 & +1.43 \\
-$\mi{OrOD}$ & 131.4 & +0.10 & - & - & 119.9 & +1.85 \\
-$\mi{OrVD}$ & 126.9 & +2.20 & 119.3 & +0.25 & 119.3 & +1.24 \\
-$\mi{OFD}$ & 134.0 & +0.40 & - & - & 119.7 & +1.82 \\
-$\mi{SOFD}$ & - & - & - & - & 113.2 & -0.85 \\
-$\mi{SOBD}$ & 117.1 & -1.70 & 88.7 & -1.07 & 88.7 & -2.52 \\
-$\mi{BPD}$ & 105.0 & 0.00 & 89.7 & -0.21 & 89.7 & -0.83 \\ \hline
-\end{tabular}
-\label{Res01}
-\end{center}
-\end{table}
-
-Note that code snippets or lists of crucial programming code or large UML diagrams should go in the Appendix/Appendices.
-
-
\chapter{Testing}
The testing was done in two main stages, first unit tests after each sprint were done in order to check correctness of the additions made, then large scale tests in order to check the compiler works as expected, is Turing complete and can handle any inputs.