diff options
Diffstat (limited to 'Smoke/report/chapter2.tex')
| -rw-r--r-- | Smoke/report/chapter2.tex | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/Smoke/report/chapter2.tex b/Smoke/report/chapter2.tex index be2ccca..be36f5c 100644 --- a/Smoke/report/chapter2.tex +++ b/Smoke/report/chapter2.tex @@ -7,10 +7,10 @@ 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. Using different techniques, these attributes can be visualized. Each and every
+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,
+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 hight plots. \\
\begin {center}
@@ -23,8 +23,9 @@ 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. That 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 new file for every new technique we implemented. The second thing we
+able to add additional functionality without losing sight of what we were doing, we created a file for every new technique we implemented. The second thing we
did is we split up the calculations, the rendering functions and user interactions from each other. \\
-With this new structure we were able to manage the code and add additional functionality. We also used SVN to manage our project. 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. We chose C as our programming language and used the GTK+ library to create
+the graphical user interface. We also used SVN to manage our project. This was very useful since we both had different development environments and also did a lot
+of work at home. \\
|