summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorWilrik de Loose <wilrik@wilrik.nl>2008-01-11 03:22:25 (GMT)
committerWilrik de Loose <wilrik@wilrik.nl>2008-01-11 03:22:25 (GMT)
commit9d43af2c4e96e6132cb02079207a007eeb62820e (patch)
tree8fd46309b2f0d0760860507c72cdf95ceb02a6f9
parent1efa2c021e48ee3356936404448b6cbaecddd70f (diff)
download2iv35-9d43af2c4e96e6132cb02079207a007eeb62820e.zip
2iv35-9d43af2c4e96e6132cb02079207a007eeb62820e.tar.gz
2iv35-9d43af2c4e96e6132cb02079207a007eeb62820e.tar.bz2
verslag update (spelfouten)
-rw-r--r--Smoke/report/2IV35-Report.log34
-rw-r--r--Smoke/report/2IV35-Report.pdfbin1072199 -> 1072372 bytes
-rw-r--r--Smoke/report/chapter1.tex3
-rw-r--r--Smoke/report/chapter2.tex18
-rw-r--r--Smoke/report/chapter7.tex2
-rw-r--r--Smoke/report/chapter8.tex16
6 files changed, 43 insertions, 30 deletions
diff --git a/Smoke/report/2IV35-Report.log b/Smoke/report/2IV35-Report.log
index 9ae0b4e..e7b0c5c 100644
--- a/Smoke/report/2IV35-Report.log
+++ b/Smoke/report/2IV35-Report.log
@@ -1,4 +1,4 @@
-This is pdfeTeX, Version 3.141592-1.21a-2.2 (MiKTeX 2.4) (preloaded format=latex 2007.9.5) 11 JAN 2008 04:03
+This is pdfeTeX, Version 3.141592-1.21a-2.2 (MiKTeX 2.4) (preloaded format=latex 2007.9.5) 11 JAN 2008 04:16
entering extended mode
**2IV35-Report.tex
(2IV35-Report.tex
@@ -569,27 +569,27 @@ Underfull \hbox (badness 10000) in paragraph at lines 80--25
[23] (chapter8.tex
Chapter 8.
-Underfull \hbox (badness 10000) in paragraph at lines 3--5
+Underfull \hbox (badness 10000) in paragraph at lines 3--4
[]
-Underfull \hbox (badness 10000) in paragraph at lines 8--11
+Underfull \hbox (badness 10000) in paragraph at lines 7--9
[]
-Underfull \hbox (badness 10000) in paragraph at lines 12--14
+Underfull \hbox (badness 10000) in paragraph at lines 10--12
[]
-Underfull \hbox (badness 10000) in paragraph at lines 15--17
+Underfull \hbox (badness 10000) in paragraph at lines 13--15
[]
-Underfull \hbox (badness 10000) in paragraph at lines 20--22
+Underfull \hbox (badness 10000) in paragraph at lines 18--20
[]
@@ -600,46 +600,46 @@ Underfull \hbox (badness 10000) in paragraph at lines 20--22
] <streamtubes.png, id=127, 847.165pt x 629.35126pt>
File: streamtubes.png Graphic file (type png)
<use streamtubes.png>
-Underfull \hbox (badness 10000) in paragraph at lines 28--30
+Underfull \hbox (badness 10000) in paragraph at lines 26--28
[]
<volume.png, id=128, 847.165pt x 629.35126pt>
File: volume.png Graphic file (type png)
<use volume.png> [25 <streamtubes.png>])
-Underfull \hbox (badness 10000) in paragraph at lines 38--26
+Underfull \hbox (badness 10000) in paragraph at lines 36--26
[]
[26 <volume.png>] (chapter9.tex
Chapter 9.
-Underfull \hbox (badness 10000) in paragraph at lines 3--5
+Underfull \hbox (badness 10000) in paragraph at lines 3--4
[]
-Underfull \hbox (badness 10000) in paragraph at lines 6--7
+Underfull \hbox (badness 10000) in paragraph at lines 5--6
[]
-Underfull \hbox (badness 10000) in paragraph at lines 10--12
+Underfull \hbox (badness 10000) in paragraph at lines 9--10
[]
-Underfull \hbox (badness 10000) in paragraph at lines 13--15
+Underfull \hbox (badness 10000) in paragraph at lines 11--12
[]
-Underfull \hbox (badness 10000) in paragraph at lines 16--19
+Underfull \hbox (badness 10000) in paragraph at lines 13--14
[]
-Underfull \hbox (badness 10000) in paragraph at lines 22--24
+Underfull \hbox (badness 10000) in paragraph at lines 17--18
[]
@@ -648,12 +648,12 @@ Underfull \hbox (badness 10000) in paragraph at lines 22--24
]
-Underfull \hbox (badness 10000) in paragraph at lines 25--27
+Underfull \hbox (badness 10000) in paragraph at lines 19--20
[]
)
-Underfull \hbox (badness 10000) in paragraph at lines 28--27
+Underfull \hbox (badness 10000) in paragraph at lines 21--27
[]
@@ -741,4 +741,4 @@ esky\cm\cmtt12.pfb><C:\MiKTeX\texmf\fonts\type1\bluesky\cm\cmsy10.pfb><C:\MiKTe
X\texmf\fonts\type1\bluesky\cm\cmmi12.pfb><C:\MiKTeX\texmf\fonts\type1\bluesky\
cm\cmbx12.pfb><C:\MiKTeX\texmf\fonts\type1\bluesky\cm\cmr12.pfb><C:\MiKTeX\texm
f\fonts\type1\bluesky\cm\cmr17.pfb>
-Output written on 2IV35-Report.pdf (31 pages, 1072199 bytes).
+Output written on 2IV35-Report.pdf (31 pages, 1072372 bytes).
diff --git a/Smoke/report/2IV35-Report.pdf b/Smoke/report/2IV35-Report.pdf
index dfa7181..dfd956f 100644
--- a/Smoke/report/2IV35-Report.pdf
+++ b/Smoke/report/2IV35-Report.pdf
Binary files differ
diff --git a/Smoke/report/chapter1.tex b/Smoke/report/chapter1.tex
index 192f53b..5d35a93 100644
--- a/Smoke/report/chapter1.tex
+++ b/Smoke/report/chapter1.tex
@@ -1,6 +1,7 @@
\chapter{Introduction}
-The visualization course focuses on techniques and algorithms used to visualize large data sets. The code of a 2D fluid simulator was supplied to implement such techniques on. \\
+The visualization course focuses on techniques and algorithms used to visualize large data sets. The code of a 2D fluid simulator was supplied to implement such
+techniques on. \\
\begin {center}
\includegraphics[width=120mm]{practical.png} \\
diff --git a/Smoke/report/chapter2.tex b/Smoke/report/chapter2.tex
index 7e3a1a8..9d5fdc1 100644
--- a/Smoke/report/chapter2.tex
+++ b/Smoke/report/chapter2.tex
@@ -1,13 +1,17 @@
\chapter{The skeleton code}
-The provided code for the course contains an implementation of a real-time fluid flow simulation. The fluid flows under the influence of a user-controlled force field. The simulation follows the Navier-Stokes equations for fluid flow. These equations describe how the velocity, pressure, temperature and density of a moving fluid are related. \\
+The provided code for the course contains an implementation of a real-time fluid flow simulation. The fluid flows under the influence of a user-controlled force
+field. The simulation follows the Navier-Stokes equations for fluid flow. These equations describe how the velocity, pressure, temperature and density of a moving
+fluid are related. \\
\section{Grid-based smoke}
The visualization is done using a two dimensional grid as opposed to particle-based smoke visualization techniques. At every vertex a number of fluid attributes are
-stored. The skeleton program keeps track of the density, velocity and force. These attributes can be visualized with different techniques. Each and every attribute has its own 'preferred' visualization technique. \\
+stored. The skeleton program keeps track of the density, velocity and force. These attributes can be visualized with different techniques. Each and every attribute
+has its own 'preferred' visualization technique. \\
-Using these values at the cell's vertices, all sorts of techniques, additional values and other useful info can be used. The values are used in colormap techniques, calculation of the divergence and the rendering of the height plots. \\
+Using these values at the cell's vertices, all sorts of techniques, additional values and other useful info can be used. The values are used in colormap techniques,
+calculation of the divergence and the rendering of the height plots. \\
\begin {center}
\includegraphics[width=70mm]{flow_vis.png} \\
@@ -18,6 +22,10 @@ The above screenshot shows us the fluid movement using a grey colormap. This sim
\section{Internal structure}
-The first assignment was to simply compile the code. This was fairly easy. However, the code was a bit unstructured. Everything was put into one big file. To be able to add additional functionality without losing sight of what we were doing, we created a file for every new technique we implemented. Furthermore the calculations, rendering functions and user interaction code was split from eachother. \\
+The first assignment was to simply compile the code. This was fairly easy. However, the code was a bit unstructured. Everything was put into one big file. To be
+able to add additional functionality without losing sight of what we were doing, we created a file for every new technique we implemented. Furthermore the
+calculations, rendering functions and user interaction code was split from each other. \\
-With this new structure we were able to manage the code and add additional functionality. The programming language of our choice was C and for the graphical user interface we took the GTK+ library with the OpenGL extension. For project managment SVN was used. This was very useful since we both had different development environments and also did a lot of work at home. \\
+With this new structure we were able to manage the code and add additional functionality. The programming language of our choice was C and for the graphical user
+interface we took the GTK+ library with the OpenGL extension. For project management SVN was used. This was very useful since we both had different development
+environments and also did a lot of work at home. \\
diff --git a/Smoke/report/chapter7.tex b/Smoke/report/chapter7.tex
index 58412e5..5fb859e 100644
--- a/Smoke/report/chapter7.tex
+++ b/Smoke/report/chapter7.tex
@@ -66,7 +66,7 @@ the center. \\
\subsection{Height strips}
When first implementing the height plots a third dimension was simply added when rendering the triangle strips for the smoke visualization. This had as an effect
-that the different rows of each of the triangle strips in the simulation where not connected. In stead of a height plots we implemented height strips. \\
+that the different rows of each of the triangle strips in the simulation where not connected. In stead of a height plots, height strips were implemented. \\
This problem was countered first calculating the height for each vertex and storing it in an array. When rendering a vertex, the correct value is then retrieved
from the array to correctly display the height. \\
diff --git a/Smoke/report/chapter8.tex b/Smoke/report/chapter8.tex
index 511b5cc..e5ebf91 100644
--- a/Smoke/report/chapter8.tex
+++ b/Smoke/report/chapter8.tex
@@ -4,15 +4,19 @@ The last of the non-optional assignments, just as the height plots, a 3-dimensio
\section{Description}
-Imagine dropping of bit of ink into the fluid and let it flow for a while. This will result in a line that shows the path a ink particle has taken. Such a path is called a streamline. A streamtube is a 3D variant of a streamline. It consists of a number of consecutive tubes that together form a thick 3-dimensional tube. \\
+Imagine dropping of bit of ink into the fluid and let it flow for a while. This will result in a line that shows the path a ink particle has taken. Such a path is
+called a streamline. A streamtube is a 3D variant of a streamline. It consists of a number of consecutive tubes that together form a thick 3-dimensional tube. \\
-Each streamtube has a begining and an end. The starting point of a streamtube is called a seedpoint. From this seedpoint the tube will begin flowing with the fluid. It ends after a number of frames. \\
+Each streamtube has a beginning and an end. The starting point of a streamtube is called a seedpoint. From this seedpoint the tube will begin flowing with the
+fluid. It ends after a number of frames. \\
-The implemented streamtubes initially were not actually flowing trough the fluid but through a frame history. Each frame's velocity or force vector components are stored in a history array and the streamtubes take a path trough this history. The 2D grid became a 3D grid with this new feature. \\
+The implemented streamtubes initially were not actually flowing trough the fluid but through a frame history. Each frame's velocity or force vector components are
+stored in a history array and the streamtubes take a path trough this history. The 2D grid became a 3D grid with this new feature. \\
\section{Implementation}
-Firstly the seedpoint placement was implemented. The user is able to pick an exact position for a seedpoint by with the mouse. A seedpoint is rendered as a small sphere. \\
+Firstly the seedpoint placement was implemented. The user is able to pick an exact position for a seedpoint by with the mouse. A seedpoint is rendered as a small
+sphere. From such a seedpoint either a streamline or streamtube is rendered. This is shown on figure 12. \\
\begin {center}
\includegraphics[width=\textwidth]{streamtubes.png} \\
@@ -20,7 +24,7 @@ Firstly the seedpoint placement was implemented. The user is able to pick an exa
\end {center}
The simulation also has a history array that stores up to 80 frames. The user can go back and forth in this frame history or render all 80 frames at once to get
-some sort of volumetric effect of the smoke. \\
+some sort of volumetric effect of the smoke. This effect is shown in the image below (figure 13). \\
\begin {center}
\includegraphics[width=\textwidth]{volume.png} \\
@@ -29,4 +33,4 @@ some sort of volumetric effect of the smoke. \\
\section{Difficulties}
-Since time was becoming an issue, the implementation of streamtubes is most likly still buggy and might not be fully correct. \\
+Since time was becoming an issue, the implementation of streamtubes might not be fully correct. \\