InfoVis:Wiki - User contributions [en]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 4

2010-01-07T23:03:57Z

UE-InfoVis0910 0825628:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]

==Point A: Description of application area, data, target group and tasks==

===Application area and data===
A family tree is a chart representing family relationships in a conventional tree structure. The tree shows the parents-children connection. The tree should show detail information of a person as well as important events and emotions (happiness). The family tree should visualize hierarchical structures. In our case we will add some additional information as hereditary diseases.

===Target group===
The target audience of this visualization would be:

- family members of the Simpsons

- characters of the Simpsons-Universe

- cast and crew of 'The Simpsons'-Television-Show

No, seriously:

- just folks who are interested - the family tree data is fictional anyway. Laymen, no prior knowledge needed.

Target group for family trees are usually people, who would like to know more about specified family relationships. It serves as well for next family generations who would like to know more about their family members. The family tree is also very useful for medical matter because hereditary diseases are shown (epilepsy).In our case the target group is each person who would like to know more about The Simpsons characters.

===Goals===
- The tree should be made very simple so everybody could be able to read the most important information about each person listed on the tree.

- For the visualization of the data we will use miscellaneous visual attributes and high data-per-ink ratio. The goal is to keep the reader focused on the important information and give him maximum information about the persons and their relationships among each other on the tree.

==Point B: Concept==

[[ Image:Gesamt2.jpg]]

[[ Image:Vergleich2.jpg]]

===Type of Visualization===
The family tree is visualized by the use of a graph - in our case not to be mistaken for a tree since we have more than one higher-ranking node (= two parents) for each node.

===Visual mapping===

====Blood relationship -> Annulus (around portrait)====
Blue Annulus = existence of blood relationship

Red Annulus = no existence of blood relationship

====Marriage -> dual wedding ring symbol (between two parents of a child)====
dual wedding ring symbol = the parents are/were married with each other

====Relationship -> Black persistent lines====
Horizontal black persistent lines between persons indicate relationship based on partnership.

Vertical black persistent lines between persons indicate relationship between parents and their child/children.

====Relationship -> Black dashed lines====
Horizontal black dashed lines in Comparison Mode indicate not shown siblings (due to eg. zoom level).

Vertical black dashed lines in Comparison Mode indicate indirect parent-child-relationship - meaning one or more generations inbetween the dashed lines are left out.

===Interaction===

====Navigation====
Navigation takes place via mouse controls. A modifier key on the keyboard is also used ('Control'-key). The program starts in the Overview mode showing the whole family tree.

Mouse-hovering over a person brings up a popup window revealing all kinds of person-related information (name, gender, birth date, profession, events, satisfaction graph). Selecting an event item in this popup-window causes highlighting the corresponding time-section in the satisfaction graph.

Selecting more than one person via 'Control'+Left-Mouse-Button-clicking several persons or drawing a selection frame around several persons (- via holding Left-Mouse-Button and moving the Mouse). Via 'Enter'-key on the keyboard the selected persons are shown in the Comparison Mode - non-selected persons are left out by dashed black lines (- see text on Visual Mapping).

====Zooming and Panning====
In the Comparison Mode the program allows for each split side (left and right) a separately adjustable zoom level and area by panning. A change of the zoom level is accomplished by the use of holding the 'Control'-key on the keyboard and turning the mouse wheel. Panning is accomplished by holding the left mouse button and moving the mouse in direction of desire.

====Split Screen Mode====
The Comparison Mode splits the window into two separate sub-windows to allow for separately adjusting (by zooming and panning) the region of interest for each side (= lisa as well as bart) of the family tree.

====Dynamic Queries====
There are several search queries the user can choose from - they are accessible in the Comparison Mode.

One filter in the comparison mode allows the user for filtering with the help of regular expressions - this searches for matching strings in all data fields in the family tree and highlights the corresponding persons.

More filters:

- filter by gender

- filter by sex

- filter by Blood relationship (- blood related? Yes/ No.)

- filter by time range (- see section 'Range Slider' below)

====Range Slider====
The user can choose an arbitrary range of time to show the family tree only in the corresponding range.

====Details on Demand====
On user demand the information of a person in the family tree is shown in a separate popup window. This window is divided into three different parts. One third shows the name, gender, date of birth and profession. The second one shows all mentionable events in the lifetime of the person - the last third of the window visualizes the 'satisfaction-over-time'-graph.

====Focus and Context====
Usage of the Dynamic Queries causes the program to focus on the matching search results. The search results are visualized by adding a mask layer on top of the family tree, allowing only for the resulting persons to be shown clearly through the mask layer - the non-matching persons are overlaid by the dark but opaque layer.

===How are the users supported in their tasks?===
A top priority for the team was to create a great experience for the user by making the controls as intuitive and easy to use as possible. Many of the Navigation Methods (left-clicking / zooming and panning) are commonly known from surfing the internet. Moreover an extensive help documentation is supplied with the family tree software package.

===What special features are there?===
Dynamic query search with regular expression engine, range slider for time filtering, intuitive easy-to-use-interface, clear design (with priority on data-ink-ratio)

==Sources==

- Miksch, S. 'Begriffsabgrenzung, Definition und Ziele/ Knowledge Crystallization/ Interaktionen: Filtering, Zooming etc'.

- Miksch, S. 'Focus + Context/ Verzerrungstechniken'.

- Aigner, W. 'Hierachische Techniken'.

File:Vergleich2.jpg

2010-01-07T23:03:18Z

UE-InfoVis0910 0825628: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

File:Gesamt2.jpg

2010-01-07T23:03:08Z

UE-InfoVis0910 0825628: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 4

2010-01-07T23:01:02Z

UE-InfoVis0910 0825628:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]

==Point A: Description of application area, data, target group and tasks==

===Application area and data===
A family tree is a chart representing family relationships in a conventional tree structure. The tree shows the parents-children connection. The tree should show detail information of a person as well as important events and emotions (happiness). The family tree should visualize hierarchical structures. In our case we will add some additional information as hereditary diseases.

===Target group===
The target audience of this visualization would be:

- family members of the Simpsons

- characters of the Simpsons-Universe

- cast and crew of 'The Simpsons'-Television-Show

No, seriously:

- just folks who are interested - the family tree data is fictional anyway. Laymen, no prior knowledge needed.

Target group for family trees are usually people, who would like to know more about specified family relationships. It serves as well for next family generations who would like to know more about their family members. The family tree is also very useful for medical matter because hereditary diseases are shown (epilepsy).In our case the target group is each person who would like to know more about The Simpsons characters.

===Goals===
- The tree should be made very simple so everybody could be able to read the most important information about each person listed on the tree.

- For the visualization of the data we will use miscellaneous visual attributes and high data-per-ink ratio. The goal is to keep the reader focused on the important information and give him maximum information about the persons and their relationships among each other on the tree.

==Point B: Concept==

[[ Image:Gesamt.jpg]]

[[ Image:Vergleich.jpg]]

===Type of Visualization===
The family tree is visualized by the use of a graph - in our case not to be mistaken for a tree since we have more than one higher-ranking node (= two parents) for each node.

===Visual mapping===

====Blood relationship -> Annulus (around portrait)====
Blue Annulus = existence of blood relationship

Red Annulus = no existence of blood relationship

====Marriage -> dual wedding ring symbol (between two parents of a child)====
dual wedding ring symbol = the parents are/were married with each other

====Relationship -> Black persistent lines====
Horizontal black persistent lines between persons indicate relationship based on partnership.

Vertical black persistent lines between persons indicate relationship between parents and their child/children.

====Relationship -> Black dashed lines====
Horizontal black dashed lines in Comparison Mode indicate not shown siblings (due to eg. zoom level).

Vertical black dashed lines in Comparison Mode indicate indirect parent-child-relationship - meaning one or more generations inbetween the dashed lines are left out.

===Interaction===

====Navigation====
Navigation takes place via mouse controls. A modifier key on the keyboard is also used ('Control'-key). The program starts in the Overview mode showing the whole family tree.

Mouse-hovering over a person brings up a popup window revealing all kinds of person-related information (name, gender, birth date, profession, events, satisfaction graph). Selecting an event item in this popup-window causes highlighting the corresponding time-section in the satisfaction graph.

Selecting more than one person via 'Control'+Left-Mouse-Button-clicking several persons or drawing a selection frame around several persons (- via holding Left-Mouse-Button and moving the Mouse). Via 'Enter'-key on the keyboard the selected persons are shown in the Comparison Mode - non-selected persons are left out by dashed black lines (- see text on Visual Mapping).

====Zooming and Panning====
In the Comparison Mode the program allows for each split side (left and right) a separately adjustable zoom level and area by panning. A change of the zoom level is accomplished by the use of holding the 'Control'-key on the keyboard and turning the mouse wheel. Panning is accomplished by holding the left mouse button and moving the mouse in direction of desire.

====Split Screen Mode====
The Comparison Mode splits the window into two separate sub-windows to allow for separately adjusting (by zooming and panning) the region of interest for each side (= lisa as well as bart) of the family tree.

====Dynamic Queries====
There are several search queries the user can choose from - they are accessible in the Comparison Mode.

One filter in the comparison mode allows the user for filtering with the help of regular expressions - this searches for matching strings in all data fields in the family tree and highlights the corresponding persons.

More filters:

- filter by gender

- filter by sex

- filter by Blood relationship (- blood related? Yes/ No.)

- filter by time range (- see section 'Range Slider' below)

====Range Slider====
The user can choose an arbitrary range of time to show the family tree only in the corresponding range.

====Details on Demand====
On user demand the information of a person in the family tree is shown in a separate popup window. This window is divided into three different parts. One third shows the name, gender, date of birth and profession. The second one shows all mentionable events in the lifetime of the person - the last third of the window visualizes the 'satisfaction-over-time'-graph.

====Focus and Context====
Usage of the Dynamic Queries causes the program to focus on the matching search results. The search results are visualized by adding a mask layer on top of the family tree, allowing only for the resulting persons to be shown clearly through the mask layer - the non-matching persons are overlaid by the dark but opaque layer.

===How are the users supported in their tasks?===
A top priority for the team was to create a great experience for the user by making the controls as intuitive and easy to use as possible. Many of the Navigation Methods (left-clicking / zooming and panning) are commonly known from surfing the internet. Moreover an extensive help documentation is supplied with the family tree software package.

===What special features are there?===
Dynamic query search with regular expression engine, range slider for time filtering, intuitive easy-to-use-interface, clear design (with priority on data-ink-ratio)

==Sources==

- Miksch, S. 'Begriffsabgrenzung, Definition und Ziele/ Knowledge Crystallization/ Interaktionen: Filtering, Zooming etc'.

- Miksch, S. 'Focus + Context/ Verzerrungstechniken'.

- Aigner, W. 'Hierachische Techniken'.

File:Gesamt.jpg

2010-01-07T23:00:01Z

UE-InfoVis0910 0825628: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

File:Corrected.pdf

2009-12-09T22:02:09Z

UE-InfoVis0910 0825628: Corrected version of InfoVis Lab2

== Summary ==
Corrected version of InfoVis Lab2
== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 2

2009-12-07T16:46:06Z

UE-InfoVis0910 0825628:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]
=== Zu beurteilende Tabelle ===
[[Image:table2.gif]]

=== Point B : Critics on the given table ===
====1. White space:====
This example shows horizontal white space between rows of data but no white space of vertikal data may cause difficulties for the reader of this table.

====2. Rules and grids:====
As written in the lecture, the delineation of columns and rows is the least effective use of rules and grids. In our example are used thick grids and dots (intermittent lines) without any form what did not even separate the header from body nor any other data. There is a thick line between the body and the header but the problem is that the same thick lines are also used in the body what makes it look like group of data.That reduces the table’s effectiveness.

====3. Header:====
In the header there is the same title written for each group of data what makes the table full of information and reduces the effectivness.There is also no need for unit´s name to be repeated for each data because it is the same name repeated all the time.

====4. Alignment:====
Quantitative values in our table are center aligned.Because of the way numbers are written and read, aligning them to the center makes them difficult to interpret and decimels can be easily ignored.

====5. Number format:====
A comma is not placed to the left of every three whole-number digits.

====6. Font:====
In our table font is "Bold" what does not make the table legible.

=== Point C : Suggested revisions ===
We developed two tables, one print version which is scaled to fit on a page and a second one which is basically designed for larger documents, e.g. look-up tables or electronic documents. The reason why we posted both of them is that we believe that the purpose and the environment of the table have influence on the design of the table.
==== Table 1 ====

[[Image:Tabelle 1.jpg|550px]]

==== Table 2 ====

[[Image:Infovis table2new.png|left|thumb|1000px|Tabelle 2]]

=== Point D : Explanation of improvements ===
==== Ad Table 1 ====
=====1. White space:=====
First thing we did was to delete already existing grids and rows and to replace them with white spaces horizontaly.We did that to make our table look more legible and to increase the table effectivness.

=====2. Rules and grids=====
We deleted all grids and rules except the header line.That is important for the reader to get the idea of the data he is reading.

=====3. Header=====
For better view we deleted all unit names that were repeated for each row and we left only one unit name that values for each one.
We did the same thing with the column names and we left only one colum name "Tk50-HTK" written horizonatly and it is easiy to notice that it values for each subgroup.(E-195-1 etc.)

=====4. Alignment=====
Because numbers in our table represent quantitative values we aligned them to the
right for better legibility.

=====5. Number format=====
For better legibility we changed number format and placed comma to the left of every three whole-number digits.

=====6. Font=====
We changed the font as well because BOLD makes the data less effective.We chose ariel font.

=====7. Fill color=====
Fill colors are less distracting to the eye as it scans across them.Because of that we chose grey grids accros horizontal rows.

==== Ad Table 2 ====
=====1. White Space=====
White space was used between each of the groups (E-195-/E-196-/E-197-).

=====2. Rules and grids=====
Most of the gridlines were dismissed. Only one gridline stayed remaining.

=====3. Header=====
The Header is now consisting of the chemical elements for better comparison of the relevant values in columns instead of in rows.

=====4. Alignment=====
Numbers are aligned on the right side. Mass numbers of the elements are aligned on the left and the element names (one row below) in the middle to make it look like the standard chemical notation of elements.

=====5. Font=====
Google Docs standard font.

=====7. Fill color=====
One fill color is used for the columns in order to help the eyes focus on them.

=====8. Element Order=====
The elements are now ordered according to their position in the periodic table rather than alphabetical.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 2

2009-11-20T19:35:31Z

UE-InfoVis0910 0825628:

File:Tabelle1.jpg

2009-11-20T19:34:18Z

UE-InfoVis0910 0825628: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 2

2009-11-20T19:32:12Z

UE-InfoVis0910 0825628:

User:UE-InfoVis0910 0825628

2009-11-07T20:09:17Z

UE-InfoVis0910 0825628:

Pavol Bauer

[[image:Grins.png|200px]]

add me on fb:
[http://www.facebook.com/people/Pavol-Bauer/603432289]

User:UE-InfoVis0910 0825628

2009-11-07T20:08:51Z

UE-InfoVis0910 0825628:

Pavol Bauer

[[image:Grins.png|200px]]

facebook:
[http://www.facebook.com/people/Pavol-Bauer/603432289]
User IMG follows..

File:Grins.png

2009-11-07T20:05:14Z

UE-InfoVis0910 0825628: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 02 - Aufgabe 1 - Flow Visualization

2009-11-06T18:21:50Z

UE-InfoVis0910 0825628:

Flow visualization is a process of making the physics of fluid flows visible in oder to analyse it.

== Definition ==
{{Quotation|To be able to recognize the motion of the fluid, one must therefore provide a certain technique by which the flow is made visible. Such methods are called flow-visualization techniques.|[Merzkirch, 1987]}}

== Overview ==
Flow visualization is a modern technique to visualize motions and patterns of mostly invisible fluids, e.g. gas, air or water.
Main target is to make flows in a specific context visible so that it can be analyzed.
Application areas for flow visualization are e.g. in aviation, aqua- or aerodynamic.

In fact, there are several ways how to do this. Generally we can divide into two main methods:

[[Image:e398-inflatable.jpg|right|thumb|150px|Figure 1]]
[[Image:2-01-AERO-Papodopoulos.jpg|right|thumb|150px|Figure 2]]
[[Image:HyFish.jpg|right|thumb|150px|Figure 3]]
=== Physical methods===
Physical methods are an experimental approch on flow visualization. Basically these techniques can further be divided into three groups [Löffelmann, 1998]:
* Adding foreign material
:These methods work by adding small particles, e.g. smoke or oil, to the fluid to make it visible. Figure 1 gives an example for using smoke in a wind tunnel.
* Optical techniques
:These methods work e.g. with the refraction of the light or by working with light beams, where images with shadows and caustics indicate flows.
* Adding heat or energy
:These methods use e.g. gas, where the molecules have been exited by shoting electrons at them, to visualize motion patterns.

The main disadvantage of physical methods is that these techniques require a test system (e.g., a wind tunnel) and therefore, may be limited by physic constraints (e.g., the size of the tunnel) and costs.
=== Computational methods ===
In contrast to physic methods, the motion of fluids can also be expressed by mathematical equations which can be estimated numerically. Thus even supercomputers would take a long time to solve the equations and the solution would only be an estimation of the definite problem, more accurate methods needed to be discovered.

One approach is to discretize the spatial domain into small cells so every single cell can be computed separately. Using this method one gets a mesh grid of the definite fluid motion. Figure 2 shows how such a mesh grid looks like in practice. NASA is testing complex scenarios of its space shuttles like return-to-launch-site and transatlantic abort maneuvers by the use of computational fluid dynamics. The image shows the surface pressure distribution at the speed of Mach 15. Figure 3 shows another shape of how computers can be used for flow visualization.

== References ==
*[Merzkirch, 1987] Wolfgang Merzkirch. ''Flow Visualization, Second Edition''. Academic Press Inc. Ltd., London, 1987.
*[Devenport and Hartwell, 2006] W.J. Devenport and W.L. Hartwell, Experiment 1 - Flow Visualization. Last modified at: December 20, 2006. Retrieved at: November 9, 2007. [http://www.aoe.vt.edu/~devenpor/aoe3054/manual/expt1/index.html http://www.aoe.vt.edu/~devenpor/aoe3054/manual/expt1/index.html].
* [Löffelmann, 1998] Helwig Löffelmann , Visualizing Local Properties and Characteristic Structures of Dynamical Systems, Created at: November, 1998. Retrieved at: November 5, 2009 http://www.cg.tuwien.ac.at/~helwig/diss/

== External Links ==
*[http://en.wikipedia.org/wiki/Flow_visualization http://en.wikipedia.org/wiki/Flow_visualization]
*[http://en.wikipedia.org/wiki/Computational_fluid_dynamics http://en.wikipedia.org/wiki/Computational_fluid_dynamics]
*[http://www.ilight.com/ FieldView, a software for simulating, streamlines around a solid surface]

User:UE-InfoVis0910 0825628

2009-11-06T15:24:00Z

UE-InfoVis0910 0825628:

Pavol Bauer

Add me on facebook:
[http://www.facebook.com/people/Pavol-Bauer/603432289]
User IMG follows..

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08

2009-11-06T15:19:38Z

UE-InfoVis0910 0825628:

== Gruppenmitglieder ==
[[User:UE-InfoVis0910_0426516|Olea, Christian]] 
[[User:UE-InfoVis0910_0126013|Saric, Martina]] 
[[User:UE-InfoVis0910_0625209|Schwengerer, Martin]] 
[[User:UE-InfoVis0910_0825628|Bauer, Pavol]]

== Aufgaben ==
[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 0|Aufgabe 0]] 
[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 1|Aufgabe 1]] 
[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 2|Aufgabe 2]] 
[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 3|Aufgabe 3]] 
[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 4|Aufgabe 4]]

Teaching:TUW - UE InfoVis WS 2009/10

2009-11-06T15:18:50Z

UE-InfoVis0910 0825628:

[[Image:Aigner03infovis ue.gif]] <big>WS 2009/10</big>

'''LVA Nr:''' 188.308 ([http://tuwis.tuwien.ac.at/lva/tuwien/188308 TUWIS++ Seite])

'''LVA Homepage:''' http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/index.html

'''Leitung:''' [[Gschwandtner, Theresia|Theresia Gschwandtner]] [gschwandtner (at) ifs.tuwien.ac.at] 
'''Tutorin:''' [[User:Katharina-Anna Wendelin|Katharina-Anna Wendelin]] [e0425160 (at) student.tuwien.ac.at]

== Gruppen ==


[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 02|Gruppe 02 (Feichtinger, Rezaei, Schindelka)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 03|Gruppe 03 (Lang, Hackl, Hasslacher)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 04|Gruppe 04 (Kaiser, Ehsani, Sverak)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05|Gruppe 05 (Paizoni, Wuttej, Hudl)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06|Gruppe 06 (Fried, Fritz, Hiller)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08 (Saric, Olea, Schwengerer, Bauer)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 09|Gruppe 09 (Hubmann-Haidvogel, Kloibhofer, Riederer)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 10|Gruppe 10 (Kickinger, Ramsauer, Wittmann)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 11|Gruppe 11 (Gastecker, Hahn, Leeb)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 12|Gruppe 12 (Bauer, Eigner, Sakai)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 13|Gruppe 13 (Sadauskas, Scheikl, Burger)]]

[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 15|Gruppe 15 (Martin, Stix, Lenzhofer)]]

== News / Bemerkungen ==

Liebe TeilnehmerInnen! 
Die vorläufige Bewertung der Aufgabe 0 ist nun auf eurer Gruppenseite
(unter Aufgabe 0 - discussion page) abrufbar.
Es besteht die Möglichkeit, euren aktuellen Punktestand (Maximum: 5 Punkte)
bis einschließlich Fr., den 06. 11. 2009 23:59 zu verbessern. --[[User:Katharina-Anna Wendelin|Katharina-Anna Wendelin]] 11:42, 30 October 2009

Liebe TeilnehmerInnen! 
Die Links zu Aufgabe 1 (Auszubessernde InfoVis Begriffe) sind nun auf eurer Gruppenseite unter "Aufgabe 1" zu finden.
Achtung: die Aufgabenstellung hat sich im Vergleich zum Vorjahr geändert! (siehe http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe1.html) -- [[User:Katharina-Anna Wendelin|Katharina-Anna Wendelin]] 21:18, 29 October 2009 (CEST)

Liebe TeilnehmerInnen, 
fügt bitte Gruppen mit nur einem oder zwei Mitgliedern selbstständig zusammen,
z.B., Martin Schwengerer geht zur Gruppe 08 und Gruppe 12 verteilt sich auf Gruppe 01 und Gruppe 04. 
Wie ihr euch umverteilt überlasse ich euch. Sollte das nicht funktionieren, bitte ich um
Rückmeldung bis morgen, dann muss ich "nachhelfen" ;). 
Vielen Dank! 
-- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 07:27, 29 October 2009 (CEST)

Liebe TeilnehmerInnen, 
aus Datenschutz-Gründen bitte ich euch eure Martrikelnummer
nicht auf eurer InfoVis:Wiki Userseite anzugeben. 
Vielen Dank! 
-- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 09:40, 27 October 2009 (CEST)

Liebe TeilnehmerInnen! 
Um diese Seite einheitlich zu gestalten (auch bezüglich der Vorjahre), schlage ich vor die Nachnamen
der Gruppenmitglieder in Klammer neben der Gruppe anzugeben, 
z.B.: Gruppe XX (Maier, Müller, Mustermann). 
-- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 10:05, 01 October 2009 (CEST)

User:UE-InfoVis0910 0825628

2009-11-06T15:16:46Z

UE-InfoVis0910 0825628: New page: Pavol Bauer

Pavol Bauer