InfoVis:Wiki - User contributions [en]

User:UE-InfoVis0708 0425163

2013-08-08T06:19:56Z

UE-InfoVis0708 0425163:

<table>
<tr>
<td>

</td>
<td>
==PLANINC Rainer==
 
</td>
</tr>
</table>
 
letzte Änderung: [[User:UE-InfoVis0708 0425163|UE-InfoVis0708 0425163]] 23:00, 22 October 2007 (CEST)

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 4

2007-12-30T13:34:01Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==

Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration (des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. sollen von Euch selbst festgelegt und beschrieben werden.

[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]

=== Beispiele für derartige Datensätze ===

[[Image:20061115_blutuntersuchung.jpg]]

[[Image:20070920_blutuntersuchung.jpg]]

== Target exploration ==

=== Target and dataset description ===
==== field of appliation ====
This visualization is used in a medical environment to show the different results of blood examinations over time. It's important to highlight values, which are not in the "normal" range, so that you can recognize those values at a glance. It's possible to measure different values at every blood test. Thereby the structure of the datasets can be different for every blood test. The datasets are usually very big and are very complex to analyze.

==== Datasetanalysis ====
# The measured values (Cholesterin, Glucose,...) are ordinal and continuous. Those values are numbers. The reference values "date of birth" and "date of examination" are ordinal as well, but discrete. The reference value "patient's name" is nominal and discrete (because you can only choose from 26 letters).
# The dataset is multidimensional. There are many different datasets over time, thus the datasets are temporal as well. There is no hierarchy within the datasets, all measured values in one dataset are independent of each other (but the measured values are dependent over time!).

=== target group analysis ===
The target group of our visualisation are doctors, who need the results of blood tests for their daily work. So the visualisation should be very intuitive and easy to understand and you should get the most important information at a glance. The medical knowledge about the visualised data is very high and the users (doctors) are familiar with these kind of data. It's not necassary to explain the different values in detail, because they know all of them. But they have to interprete these datasets to draw the right conclusion. Visualization techniques, which are commonly used in this field are stardinates and parallel coordinates (e.g. MediChart: http://www.symposion.com/MediChart/k03a.htm). These visualization techniques are used because they can display multidimensional datasets in a very effective way.

=== goals of visualization ===
With our visualization abnormal blood values should be detected at a glance within the context of all blood examination results over time. It's also possible to highlight one dataset (from one specific date) and detect the detect the tendency of values. The changes over time can also be visualized. You can specify the ranges for the normal values and all values, which are not in this range are highlighted! The data in our visualization should be clearly arranged and so it is easier to predict values and the future state of health. With our visualization it's easier than to predict something from tables.

== Concept ==
=== kind of visualization ===
We use the parallel coordinates technique for our visualization.

=== visual mapping ===
All data dimensions are mapped as points. The higher the value, the higher the points. Only the "reference values" (name, DOB, date of examination) are NOT mapped as points (this wouldn't make sense ;-).

=== description of parallel coordinates ===
{{Quotation|Parallel coordinatesis a common way of visualizing high-dimensional geometry and analyzing multivariate data. To show a set of points in an n-dimensional space, a backdrop is drawn consisting of n parallel lines, typically vertical and equally spaced. A point in n-dimensional space is represented as a polyline with vertices on the parallel axes; the position of the vertex on the i-th axis corresponds to the i-th coordinate of the point.|Wikipedia, http://en.wikipedia.org/wiki/Parallel_coordinates}}

=== interaction ===
* highlight single data sets (e.g. specific date)
* zoom in (to specific axis), to show the differences between the values
* specify the time range, from which the datesets should be used
* data values: if you select a data set, the corresponding values are shown
* change the range of "normal" values for every axis
* add/remove displayed axis

=== Fake Screenshots ===
We made the assumption that the arrangement of the axis make sense from a medical point of view (e.g. Eisen, latex, Glucose and Harnsäure belongs together for a certain health state).

<gallery caption="" perrow="3">
Image:gruppe5_normal.jpg|standard view for one patient (abnormal values highlighted)
Image:gruppe5_highlight.jpg|values from one specific blood examination are highlighted and detailed information are shown
Image:gruppe5_zoom.jpg|zoom in to specific axis (name of patient should be shown)
</gallery>

=== support for doctors ===
It's very intuitiv and the tool must not be learned. You get an overview over the health state of one patient over time. It also allows you to predict future health states and allows you to go against bad consequnces.

=== pros and cons ===
+ high dimensional overview 
+ intuitive 
- temporal history could be better shown in other visualization techniques (e.g. time axis) 
- distinction between lines may be hard (improvement is possible) 

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 4

2007-12-30T13:32:45Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==

Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration (des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. sollen von Euch selbst festgelegt und beschrieben werden.

[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]

=== Beispiele für derartige Datensätze ===

[[Image:20061115_blutuntersuchung.jpg]]

[[Image:20070920_blutuntersuchung.jpg]]

== Target exploration ==

=== Target and dataset description ===
==== field of appliation ====
This visualization is used in a medical environment to show the different results of blood examinations over time. It's important to highlight values, which are not in the "normal" range, so that you can recognize those values at a glance. It's possible to measure different values at every blood test. Thereby the structure of the datasets can be different for every blood test. The datasets are usually very big and are very complex to analyze.

==== Datasetanalysis ====
# The measured values (Cholesterin, Glucose,...) are ordinal and continuous. Those values are numbers. The reference values "date of birth" and "date of examination" are ordinal as well, but discrete. The reference value "patient's name" is nominal and discrete (because you can only choose from 26 letters).
# The dataset is multidimensional. There are many different datasets over time, thus the datasets are temporal as well. There is no hierarchy within the datasets, all measured values in one dataset are independent of each other (but the measured values are dependent over time!).

=== target group analysis ===
The target group of our visualisation are doctors, who need the results of blood tests for their daily work. So the visualisation should be very intuitive and easy to understand and you should get the most important information at a glance. The medical knowledge about the visualised data is very high and the users (doctors) are familiar with these kind of data. It's not necassary to explain the different values in detail, because they know all of them. But they have to interprete these datasets to draw the right conclusion. Visualization techniques, which are commonly used in this field are stardinates and parallel coordinates (e.g. MediChart: http://www.symposion.com/MediChart/k03a.htm). These visualization techniques are used because they can display multidimensional datasets in a very effective way.

=== goals of visualization ===
With our visualization abnormal blood values should be detected at a glance within the context of all blood examination results over time. It's also possible to highlight one dataset (from one specific date) and detect the detect the tendency of values. The changes over time can also be visualized. You can specify the ranges for the normal values and all values, which are not in this range are highlighted! The data in our visualization should be clearly arranged and so it is easier to predict values and the future state of health. With our visualization it's easier than to predict something from tables.

== Concept ==
=== kind of visualization ===
We use the parallel coordinates technique for our visualization.

=== visual mapping ===
All data dimensions are mapped as points. The higher the value, the higher the points. Only the "reference values" (name, DOB, date of examination) are NOT mapped as points (this wouldn't make sense ;-).

=== description of parallel coordinates ===
{{Quotation|Parallel coordinatesis a common way of visualizing high-dimensional geometry and analyzing multivariate data. To show a set of points in an n-dimensional space, a backdrop is drawn consisting of n parallel lines, typically vertical and equally spaced. A point in n-dimensional space is represented as a polyline with vertices on the parallel axes; the position of the vertex on the i-th axis corresponds to the i-th coordinate of the point.|Wikipedia, http://en.wikipedia.org/wiki/Parallel_coordinates}}

=== interaction ===
* highlight single data sets (e.g. specific date)
* zoom in (to specific axis), to show the differences between the values
* specify the time range, from which the datesets should be used
* data values: if you select a data set, the corresponding values are shown
* change the range of "normal" values for every axis
* add/remove displayed axis

=== Fake Screenshots ===
We made the assumption that the arrangement of the axis make sense from a medical point of view (e.g. Eisen, latex, Glucose and Harnsäure belongs together for a certain health state).

<gallery caption="" perrow="3">
Image:gruppe5_normal.jpg|standard view for one patient (abnormal values highlighted)
Image:gruppe5_highlight.jpg|values from one specific blood examination are highlighted and detailed information are shown
Image:gruppe5_zoom.jpg|zoom in to specific axis (name of patient should be shown)
</gallery>

=== support for doctors ===
It's very intuitiv and the tool must not be learned. You get an overview over the health state of one patient over time. It also allows you to predict future health states and allows you to go against bad consequnces.

=== pros and cons ===
- temporal history could be better shown in other visualization techniques (e.g. time axis)
+ high dimensional overview
+ intuitive
- distinction between lines may be hard (improvement is possible)

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 4

2007-12-30T13:19:13Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==

Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration (des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. sollen von Euch selbst festgelegt und beschrieben werden.

[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]

=== Beispiele für derartige Datensätze ===

[[Image:20061115_blutuntersuchung.jpg]]

[[Image:20070920_blutuntersuchung.jpg]]

== Target exploration ==

=== Target and dataset description ===
==== field of appliation ====
This visualization is used in a medical environment to show the different results of blood examinations over time. It's important to highlight values, which are not in the "normal" range, so that you can recognize those values at a glance. It's possible to measure different values at every blood test. Thereby the structure of the datasets can be different for every blood test. The datasets are usually very big and are very complex to analyze.

==== Datasetanalysis ====
# The measured values (Cholesterin, Glucose,...) are ordinal and continuous. Those values are numbers. The reference values "date of birth" and "date of examination" are ordinal as well, but discrete. The reference value "patient's name" is nominal and discrete (because you can only choose from 26 letters).
# The dataset is multidimensional. There are many different datasets over time, thus the datasets are temporal as well. There is no hierarchy within the datasets, all measured values in one dataset are independent of each other (but the measured values are dependent over time!).

=== target group analysis ===
The target group of our visualisation are doctors, who need the results of blood tests for their daily work. So the visualisation should be very intuitive and easy to understand and you should get the most important information at a glance. The medical knowledge about the visualised data is very high and the users (doctors) are familiar with these kind of data. It's not necassary to explain the different values in detail, because they know all of them. But they have to interprete these datasets to draw the right conclusion. Visualization techniques, which are commonly used in this field are stardinates and parallel coordinates (e.g. MediChart: http://www.symposion.com/MediChart/k03a.htm). These visualization techniques are used because they can display multidimensional datasets in a very effective way.

=== goals of visualization ===
With our visualization abnormal blood values should be detected at a glance within the context of all blood examination results over time. It's also possible to highlight one dataset (from one specific date) and detect the detect the tendency of values. The changes over time can also be visualized. You can specify the ranges for the normal values and all values, which are not in this range are highlighted! The data in our visualization should be clearly arranged and so it is easier to predict values and the future state of health. With our visualization it's easier than to predict something from tables.

== Concept ==
=== kind of visualization ===
We use the parallel coordinates technique for our visualization.

=== visual mapping ===
All data dimensions are mapped as points. The higher the value, the higher the points. Only the "reference values" (name, DOB, date of examination) are NOT mapped as points (this wouldn't make sense ;-).

=== description of parallel coordinates ===
{{Quotation|Parallel coordinatesis a common way of visualizing high-dimensional geometry and analyzing multivariate data. To show a set of points in an n-dimensional space, a backdrop is drawn consisting of n parallel lines, typically vertical and equally spaced. A point in n-dimensional space is represented as a polyline with vertices on the parallel axes; the position of the vertex on the i-th axis corresponds to the i-th coordinate of the point.|Wikipedia, http://en.wikipedia.org/wiki/Parallel_coordinates}}

=== interaction ===
* highlight single data sets (e.g. specific date)
* zoom in (to specific axis), to show the differences between the values
* specify the time range, from which the datesets should be used
* data values: if you select a data set, the corresponding values are shown
* change the range of "normal" values for every axis
* add/remove displayed axis

=== Fake Screenshots ===
We made the assumption that the arrangement of the axis make sense from a medical point of view (e.g. Eisen, latex, Glucose and Harnsäure belongs together for a certain health state).

[[Image:gruppe5_normal.jpg]]
[[Image:gruppe5_highlight.jpg]]
[[Image:gruppe5_zoom.jpg]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

File:Gruppe5 zoom.jpg

2007-12-30T13:14:20Z

UE-InfoVis0708 0425163: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

File:Gruppe5 highlight.jpg

2007-12-30T13:13:52Z

UE-InfoVis0708 0425163: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

File:Gruppe5 normal.jpg

2007-12-30T13:13:28Z

UE-InfoVis0708 0425163: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 4

2007-12-30T13:12:28Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==

Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration (des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. sollen von Euch selbst festgelegt und beschrieben werden.

[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]

=== Beispiele für derartige Datensätze ===

[[Image:20061115_blutuntersuchung.jpg]]

[[Image:20070920_blutuntersuchung.jpg]]

== Target exploration ==

=== Target and dataset description ===
==== field of appliation ====
This visualization is used in a medical environment to show the different results of blood examinations over time. It's important to highlight values, which are not in the "normal" range, so that you can recognize those values at a glance. It's possible to measure different values at every blood test. Thereby the structure of the datasets can be different for every blood test. The datasets are usually very big and are very complex to analyze.

==== Datasetanalysis ====
# The measured values (Cholesterin, Glucose,...) are ordinal and continuous. Those values are numbers. The reference values "date of birth" and "date of examination" are ordinal as well, but discrete. The reference value "patient's name" is nominal and discrete (because you can only choose from 26 letters).
# The dataset is multidimensional. There are many different datasets over time, thus the datasets are temporal as well. There is no hierarchy within the datasets, all measured values in one dataset are independent of each other (but the measured values are dependent over time!).

=== target group analysis ===
The target group of our visualisation are doctors, who need the results of blood tests for their daily work. So the visualisation should be very intuitive and easy to understand and you should get the most important information at a glance. The medical knowledge about the visualised data is very high and the users (doctors) are familiar with these kind of data. It's not necassary to explain the different values in detail, because they know all of them. But they have to interprete these datasets to draw the right conclusion. Visualization techniques, which are commonly used in this field are stardinates and parallel coordinates (e.g. MediChart: http://www.symposion.com/MediChart/k03a.htm). These visualization techniques are used because they can display multidimensional datasets in a very effective way.

=== goals of visualization ===
With our visualization abnormal blood values should be detected at a glance within the context of all blood examination results over time. It's also possible to highlight one dataset (from one specific date) and detect the detect the tendency of values. The changes over time can also be visualized. You can specify the ranges for the normal values and all values, which are not in this range are highlighted! The data in our visualization should be clearly arranged and so it is easier to predict values and the future state of health. With our visualization it's easier than to predict something from tables.

== Concept ==
=== kind of visualization ===
We use the parallel coordinates technique for our visualization.

=== visual mapping ===
All data dimensions are mapped as points. The higher the value, the higher the points. Only the "reference values" (name, DOB, date of examination) are NOT mapped as points (this wouldn't make sense ;-).

=== description of parallel coordinates ===
{{Quotation|Parallel coordinatesis a common way of visualizing high-dimensional geometry and analyzing multivariate data. To show a set of points in an n-dimensional space, a backdrop is drawn consisting of n parallel lines, typically vertical and equally spaced. A point in n-dimensional space is represented as a polyline with vertices on the parallel axes; the position of the vertex on the i-th axis corresponds to the i-th coordinate of the point.|Wikipedia, http://en.wikipedia.org/wiki/Parallel_coordinates}}

=== interaction ===
* highlight single data sets (e.g. specific date)
* zoom in (to specific axis), to show the differences between the values
* specify the time range, from which the datesets should be used
* data values: if you select a data set, the corresponding values are shown
* change the range of "normal" values for every axis
* add/remove displayed axis

We made the assumption that the arrangement of the axis make sense from a medical point of view (e.g. Eisen, latex, Glucose and Harnsäure belongs together for a certain health state).
== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 4

2007-12-30T12:32:26Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==

Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration (des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. sollen von Euch selbst festgelegt und beschrieben werden.

[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]

=== Beispiele für derartige Datensätze ===

[[Image:20061115_blutuntersuchung.jpg]]

[[Image:20070920_blutuntersuchung.jpg]]

== Target exploration ==

=== Target and dataset description ===
==== field of appliation ====
This visualization is used in a medical environment to show the different results of blood examinations over time. It's important to highlight values, which are not in the "normal" range, so that you can recognize those values at a glance. It's possible to measure different values at every blood test. Thereby the structure of the datasets can be different for every blood test. The datasets are usually very big and are very complex to analyze.

==== Datasetanalysis ====
# The measured values (Cholesterin, Glucose,...) are ordinal and continuous. Those values are numbers. The reference values "date of birth" and "date of examination" are ordinal as well, but discrete. The reference value "patient's name" is nominal and discrete (because you can only choose from 26 letters).
# The dataset is multidimensional. There are many different datasets over time, thus the datasets are temporal as well. There is no hierarchy within the datasets, all measured values in one dataset are independent of each other (but the measured values are dependent over time!).

=== target group analysis ===
The target group of our visualisation are doctors, who need the results of blood tests for their daily work. So the visualisation should be very intuitive and easy to understand and you should get the most important information at a glance. The medical knowledge about the visualised data is very high and the users (doctors) are familiar with these kind of data. It's not necassary to explain the different values in detail, because they know all of them. But they have to interprete these datasets to draw the right conclusion. Visualization techniques, which are commonly used in this field are stardinates and parallel coordinates (e.g. MediChart: http://www.symposion.com/MediChart/k03a.htm). These visualization techniques are used because they can display multidimensional datasets in a very effective way.

=== goals of visualization ===
With our visualization abnormal blood values should be detected at a glance within the context of all blood examination results over time. It's also possible to highlight one dataset (from one specific date) and detect the detect the tendency of values. The changes over time can also be visualized. You can specify the ranges for the normal values and all values, which are not in this range are highlighted! The data in our visualization should be clearly arranged and so it is easier to predict values and the future state of health. With our visualization it's easier than to predict something from tables.

== Concept ==
=== kind of visualization ===
We use the parallel coordinates technique for our visualization.

=== visual mapping ===
All data dimensions are mapped as points. The higher the value, the higher the points. Only the "reference values" (name, DOB, date of examination) are NOT mapped as points (this wouldn't make sense ;-).

=== description of parallel coordinates ===
{{Quotation|Parallel coordinatesis a common way of visualizing high-dimensional geometry and analyzing multivariate data. To show a set of points in an n-dimensional space, a backdrop is drawn consisting of n parallel lines, typically vertical and equally spaced. A point in n-dimensional space is represented as a polyline with vertices on the parallel axes; the position of the vertex on the i-th axis corresponds to the i-th coordinate of the point.|Wikipedia, http://en.wikipedia.org/wiki/Parallel_coordinates}}

=== interaction ===
* highlight single data sets (e.g. specific date)
* zoom in (to specific axis), to show the differences between the values
* specify the time range, from which the datesets should be used
* data values: if you select a data set, the corresponding values are shown
* change the range of "normal" values for every axis

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 4

2007-12-30T12:13:44Z

UE-InfoVis0708 0425163:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 4

2007-12-30T11:10:07Z

UE-InfoVis0708 0425163:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 4

2007-12-30T11:00:01Z

UE-InfoVis0708 0425163:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 4

2007-12-30T10:42:52Z

UE-InfoVis0708 0425163:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 2

2007-12-16T21:34:34Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_loan_rates.png]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

== Lösung der Aufgabe ==

=== Animadversion on the given table ===
# Absolutley no fill color
# No subdivisions i.e. loan type (there are only 2 types) or term (also 2 types). The information adjustable/fixed or 15/30 is used too often.
# The table is sorted by points. Maybe it would be better, if it´s sort by rate or term
# The word ‘mortgage’ is used to often in the column ‘lender’, it´s not necessary to repeat it so often
# In the column ‘points’ the numbers should have the same amount of digits before and after the decimal point
# The numbers in the column ‘rate’ should all have 3 digits after the decimal point
# The title “effective September 1, 2003” isn´t clear. Is this a date or something else? (because only 1,2003 is bold, why is september not bold?)
# Due to the use of white spaces the reader scans the table column by column but it would make more sense, if there is less white space between the columns but more white space between the rows. This would make it easier to read the table row by row.
=== The improved table ===
This table is the right one, if the value "points" is very important (for more details please go to "The improved table v2" below).
 
<table width="866" border="0" cellspacing="10">
<tr>
<td width="91" valign="top"> </td>
<td colspan="3" align="center">Loan Type: Adjustable <hr/></td>
<td colspan="3" align="center">Loan Type: Fixed <hr/></td>
</tr>
<tr>
<td align="right">Points</td>
<td width="104" align="right">Rate</td>
<td width="149">Lender(Mortgage)</td>
<td width="110" align="right">Term</td>
<td width="135" align="right">Rate</td>
<td width="200">Lender(Mortage)</td>
<td width="47" align="right">Term</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="right">0.0</td>
<td align="right">6.000%</td>
<td>ABC</td>
<td align="right">15</td>
<td align="right">7.000%</td>
<td>CDE</td>
<td align="right">15</td>
</tr>
<tr>
<td align="right">6.000%</td>
<td>BCD</td>
<td align="right">15</td>
<td align="right">6.750%</td>
<td>BCD</td>
<td align="right">15</td>
</tr>
<tr>
<td height="39" valign="top" align="right">6.000%</td>
<td valign="top">CDE</td>
<td valign="top" align="right">15</td>
<td valign="top" align="right">6.250%</td>
<td valign="top">ABC</td>
<td valign="top" align="right">15</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="right">0.5</td>
<td align="right">6.500%</td>
<td>CDE</td>
<td align="right">30</td>
<td align="right">7.250%</td>
<td>CDE</td>
<td align="right">30</td>
</tr>
<tr>
<td align="right">6.250%</td>
<td>BCD</td>
<td align="right">30</td>
<td align="right">7.000%</td>
<td>BCD</td>
<td align="right">30</td>
</tr>
<tr>
<td height="38" valign="top" align="right">6.125%</td>
<td valign="top">ABC</td>
<td valign="top" align="right">30</td>
<td valign="top" align="right">6.500%</td>
<td valign="top">ABC</td>
<td valign="top" align="right">30</td>
</tr>
<tr>
<td rowspan="5" valign="top" align="right">1.0</td>
<td align="right">5.750%</td>
<td>CDE</td>
<td align="right">15</td>
<td align="right">7.000%</td>
<td>CDE</td>
<td align="right">30</td>
</tr>
<tr>
<td align="right">5.675%</td>
<td>ABC</td>
<td align="right">15</td>
<td align="right">6.500%</td>
<td>ABC</td>
<td align="right">30</td>
</tr>
<tr>
<td align="right">5.675%</td>
<td>BCD</td>
<td align="right">15</td>
<td align="right">6.500%</td>
<td>BCD</td>
<td align="right">30</td>
</tr>
<tr>
<td align="right">5.675%</td>
<td>ABC</td>
<td align="right">15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td align="right">5.675%</td>
<td>BCD</td>
<td align="right">15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
</table>
'''Why is this table better than the original one?'''
* It's primary sorted by points.
* It's easier to follow one row, because of smart use of whitespace.
* All numbers are aligned to the left
* Now every Number of Rate has 3 digits on the right side of the decimal point
* "Mortgage" is not in every row but once in the header.
* We broke up the table in 2 parts: the "fixed" one and the "adjustable" one. This gives you a faster overview of your possibilites if you're going to lend money.

=== The improved table v2 ===
We were not sure, what the value "points" is. In the first version (above) we sorted the table by points, because it's also sorted by points in the original one. But afterwards we thought, that the value "points" is not so important, maybe it's just the commission. If it is so, it doesn't make sense to sort the table by commission. So we created a new version of the table (this version is better, if "points" is not important).
[[Image:Table v3.jpg]]
 
'''Why is this table better than the original one?'''
* It's sorted by Rate, which is the most important value if you're going to lend money.
* It's easier to follow one row, because of smart use of whitespace.
* The values are grouped together by points and terms, so you don't need to fill in the same values for points and terms in every row.
* The Rate and all numbers are aligned to the right -> you can compare it easier.
* "Mortgage" is not in every row but once in the header.
* We broke up the table in 2 parts: the "fixed" one and the "adjustable" one. This gives you a faster overview of your possibilites if you're going to lend money.
* The "lender" value is centered, because every lender is represented by exactly 3 characters - it's easier to follow.
* We used an unobtrusive grey rule to delineate the header from the body.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 2

2007-11-19T18:47:22Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_loan_rates.png]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

== Lösung der Aufgabe ==

=== Animadversion on the given table ===
# Absolutley no fill color
# No subdivisions i.e. loan type (there are only 2 types) or term (also 2 types). The information adjustable/fixed or 15/30 is used too often.
# The table is sorted by points. Maybe it would be better, if it´s sort by rate or term
# The word ‘mortgage’ is used to often in the column ‘lender’, it´s not necessary to repeat it so often
# In the column ‘points’ the numbers should have the same amount of digits before and after the decimal point
# The numbers in the column ‘rate’ should all have 3 digits after the decimal point
# The title “effective September 1, 2003” isn´t clear. Is this a date or something else? (because only 1,2003 is bold, why is september not bold?)
# Due to the use of white spaces the reader scans the table column by column but it would make more sense, if there is less white space between the columns but more white space between the rows. This would make it easier to read the table row by row.
=== The improved table ===
This table is the right one, if the value "points" is very important (for more details please go to "The improved table v2" below).
 
<table width="866" border="0">
<tr>
<td width="91" valign="top"> </td>
<td colspan="3" align="center">Loan Type: Adjustable <hr/></td>
<td colspan="3" align="center">Loan Type: Fixed <hr/></td>
</tr>
<tr>
<td>Points</td>
<td width="104">Rate</td>
<td width="149">Lender(Mortgage)</td>
<td width="110">Term</td>
<td width="135">Rate</td>
<td width="200">Lender(Mortage)</td>
<td width="47">Term</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.0</td>
<td>6.000%</td>
<td>ABC</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>15</td>
</tr>
<tr>
<td>6.000%</td>
<td>BCD</td>
<td>15</td>
<td>6.750%</td>
<td>BCD</td>
<td>15</td>
</tr>
<tr>
<td height="39" valign="top">6.000%</td>
<td valign="top">CDE</td>
<td valign="top">15</td>
<td valign="top">6.250%</td>
<td valign="top">ABC</td>
<td valign="top">15</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.5</td>
<td>6.500%</td>
<td>CDE</td>
<td>30</td>
<td>7.250%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>6.250%</td>
<td>BCD</td>
<td>30</td>
<td>7.000%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td height="38" valign="top">6.125%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
<td valign="top">6.500%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
</tr>
<tr>
<td rowspan="5" valign="top">1.0</td>
<td>5.750%</td>
<td>CDE</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td>6.500%</td>
<td>ABC</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td>6.500%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
</table>
'''Why is this table better than the original one?'''
* It's primary sorted by points.
* It's easier to follow one row, because of smart use of whitespace.
* All numbers are aligned to the left
* Now every Number of Rate has 3 digits on the right side of the decimal point
* "Mortgage" is not in every row but once in the header.
* We broke up the table in 2 parts: the "fixed" one and the "adjustable" one. This gives you a faster overview of your possibilites if you're going to lend money.

=== The improved table v2 ===
We were not sure, what the value "points" is. In the first version (above) we sorted the table by points, because it's also sorted by points in the original one. But afterwards we thought, that the value "points" is not so important, maybe it's just the commission. If it is so, it doesn't make sense to sort the table by commission. So we created a new version of the table (this version is better, if "points" is not important).
[[Image:Table v3.jpg]]
 
'''Why is this table better than the original one?'''
* It's sorted by Rate, which is the most important value if you're going to lend money.
* It's easier to follow one row, because of smart use of whitespace.
* The values are grouped together by points and terms, so you don't need to fill in the same values for points and terms in every row.
* The Rate and all numbers are aligned to the right -> you can compare it easier.
* "Mortgage" is not in every row but once in the header.
* We broke up the table in 2 parts: the "fixed" one and the "adjustable" one. This gives you a faster overview of your possibilites if you're going to lend money.
* The "lender" value is centered, because every lender is represented by exactly 3 characters - it's easier to follow.
* We used an unobtrusive grey rule to delineate the header from the body.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 2

2007-11-19T12:34:03Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_loan_rates.png]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

== Lösung der Aufgabe ==

=== Animadversion on the given table ===
# Absolutley no fill color
# No subdivisions i.e. loan type (there are only 2 types) or term (also 2 types). The information adjustable/fixed or 15/30 is used too often.
# The table is sorted by points. Maybe it would be better, if it´s sort by rate or term
# The word ‘mortgage’ is used to often in the column ‘lender’, it´s not necessary to repeat it so often
# In the column ‘points’ the numbers should have the same amount of digits before and after the decimal point
# The numbers in the column ‘rate’ should all have 3 digits after the decimal point
# The title “effective September 1, 2003” isn´t clear. Is this a date or something else? (because only 1,2003 is bold, why is september not bold?)
# Due to the use of white spaces the reader scans the table column by column but it would make more sense, if there is less white space between the columns but more white space between the rows. This would make it easier to read the table row by row.
=== The improved table ===
This table is the right one, if the value "points" is very important (for more details please go to "The improved table v2" below).
 
<table width="866" border="0">
<tr>
<td width="91" valign="top"> </td>
<td colspan="3" align="center">Loan Type: Adjustable <hr/></td>
<td colspan="3" align="center">Loan Type: Fixed <hr/></td>
</tr>
<tr>
<td>Points</td>
<td width="104">Rate</td>
<td width="149">Lender(Mortgage)</td>
<td width="110">Term</td>
<td width="135">Rate</td>
<td width="200">Lender(Mortage)</td>
<td width="47">Term</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.0</td>
<td>6.000%</td>
<td>ABC</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>15</td>
</tr>
<tr>
<td>6.000%</td>
<td>BCD</td>
<td>15</td>
<td>6.750%</td>
<td>BCD</td>
<td>15</td>
</tr>
<tr>
<td height="39" valign="top">6.000%</td>
<td valign="top">CDE</td>
<td valign="top">15</td>
<td valign="top">6.250%</td>
<td valign="top">ABC</td>
<td valign="top">15</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.5</td>
<td>6.500%</td>
<td>CDE</td>
<td>30</td>
<td>7.250%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>6.250%</td>
<td>BCD</td>
<td>30</td>
<td>7.000%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td height="38" valign="top">6.125%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
<td valign="top">6.500%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
</tr>
<tr>
<td rowspan="5" valign="top">1.0</td>
<td>5.750%</td>
<td>CDE</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td>6.500%</td>
<td>ABC</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td>6.500%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
</table>
=== The improved table v2 ===
We were not sure, what the value "points" is. In the first version (above) we sorted the table by points, because it's also sorted by points in the original one. But afterwards we thought, that the value "points" is not so important, maybe it's just the commission. If it is so, it doesn't make sense to sort the table by commission. So we created a new version of the table (this version is better, if "points" is not important).
[[Image:Table v3.jpg]]
 
'''Why is this table better than the original one?'''
* It's sorted by Rate, which is the most important value if you're going to lend money.
* It's easier to follow one row, because of smart use of whitespace.
* The values are grouped together by points and terms, so you don't need to fill in the same values for points and terms in every row.
* The Rate and all numbers are aligned to the right -> you can compare it easier.
* "Mortgage" is not in every row but once in the header.
* We broke up the table in 2 parts: the "fixed" one and the "adjustable" one. This gives you a faster overview of your possibilites if you're going to lend money.
* The "lender" value is centered, because every lender is represented by exactly 3 characters - it's easier to follow.
* We used an unobtrusive grey rule to delineate the header from the body.
 
'''ODER IST DIESE TABELLE BESSER????'''
 
[[Image:Table v2.jpg]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 2

2007-11-19T12:32:49Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_loan_rates.png]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

== Lösung der Aufgabe ==

=== Animadversion on the given table ===
# Absolutley no fill color
# No subdivisions i.e. loan type (there are only 2 types) or term (also 2 types). The information adjustable/fixed or 15/30 is used too often.
# The table is sorted by points. Maybe it would be better, if it´s sort by rate or term
# The word ‘mortgage’ is used to often in the column ‘lender’, it´s not necessary to repeat it so often
# In the column ‘points’ the numbers should have the same amount of digits before and after the decimal point
# The numbers in the column ‘rate’ should all have 3 digits after the decimal point
# The title “effective September 1, 2003” isn´t clear. Is this a date or something else? (because only 1,2003 is bold, why is september not bold?)
# Due to the use of white spaces the reader scans the table column by column but it would make more sense, if there is less white space between the columns but more white space between the rows. This would make it easier to read the table row by row.
=== The improved table ===
This table is the right one, if the value "points" is very important (for more details please go to "The improved table v2" below).
 
<table width="866" border="0">
<tr>
<td width="91" valign="top"> </td>
<td colspan="3" align="center">Loan Type: Adjustable <hr/></td>
<td colspan="3" align="center">Loan Type: Fixed <hr/></td>
</tr>
<tr>
<td>Points</td>
<td width="104">Rate</td>
<td width="149">Lender(Mortgage)</td>
<td width="110">Term</td>
<td width="135">Rate</td>
<td width="200">Lender(Mortage)</td>
<td width="47">Term</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.0</td>
<td>6.000%</td>
<td>ABC</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>15</td>
</tr>
<tr>
<td>6.000%</td>
<td>BCD</td>
<td>15</td>
<td>6.750%</td>
<td>BCD</td>
<td>15</td>
</tr>
<tr>
<td height="39" valign="top">6.000%</td>
<td valign="top">CDE</td>
<td valign="top">15</td>
<td valign="top">6.250%</td>
<td valign="top">ABC</td>
<td valign="top">15</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.5</td>
<td>6.500%</td>
<td>CDE</td>
<td>30</td>
<td>7.250%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>6.250%</td>
<td>BCD</td>
<td>30</td>
<td>7.000%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td height="38" valign="top">6.125%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
<td valign="top">6.500%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
</tr>
<tr>
<td rowspan="5" valign="top">1.0</td>
<td>5.750%</td>
<td>CDE</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td>6.500%</td>
<td>ABC</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td>6.500%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
</table>
=== The improved table v2 ===
We were not sure, what the value "points" is. In the first version (above) we sorted the table by points, because it's also sorted by points in the original one. But afterwards we thought, that the value "points" is not so important, maybe it's just the commission. If it is so, it doesn't make sense to sort the table by commission. So we created a new version of the table (this version is better, if "points" is not important).
[[Image:Table v3.jpg]]
 
'''Why is this table better than the original one?'''
* It's sorted by Rate, which is the most important value if you're going to lend money.
* It's easier to follow one row, because of smart use of whitespace.
* The values are grouped together by points and terms, so you don't need to fill in the same values for points and terms in every row.
* The Rate and all numbers are aligned to the right -> you can compare it easier.
* "Mortgage" is not in every row but once in the header.
* We broke up the table in 2 parts: the "fixed" one and the "adjustable" one. This gives you a faster overview of your possibilites if you're going to lend money.
* The "lender" value is centered, because every lender is represented by exactly 3 characters - it's easier to follow.
* We used an unobtrusive grey rule to delineate the header from the body.
 
ODER IST DIESE TABELLE BESSER????
[[Image:Table v2.jpg]]

File:Table v3.jpg

2007-11-19T12:31:28Z

UE-InfoVis0708 0425163: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 2

2007-11-19T12:25:23Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_loan_rates.png]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

== Lösung der Aufgabe ==

=== Animadversion on the given table ===
# Absolutley no fill color
# No subdivisions i.e. loan type (there are only 2 types) or term (also 2 types). The information adjustable/fixed or 15/30 is used too often.
# The table is sorted by points. Maybe it would be better, if it´s sort by rate or term
# The word ‘mortgage’ is used to often in the column ‘lender’, it´s not necessary to repeat it so often
# In the column ‘points’ the numbers should have the same amount of digits before and after the decimal point
# The numbers in the column ‘rate’ should all have 3 digits after the decimal point
# The title “effective September 1, 2003” isn´t clear. Is this a date or something else? (because only 1,2003 is bold, why is september not bold?)
# Due to the use of white spaces the reader scans the table column by column but it would make more sense, if there is less white space between the columns but more white space between the rows. This would make it easier to read the table row by row.
=== The improved table ===
This table is the right one, if the value "points" is very important (for more details please go to "The improved table v2" below).
 
<table width="866" border="0">
<tr>
<td width="91" valign="top"> </td>
<td colspan="3" align="center">Loan Type: Adjustable <hr/></td>
<td colspan="3" align="center">Loan Type: Fixed <hr/></td>
</tr>
<tr>
<td>Points</td>
<td width="104">Rate</td>
<td width="149">Lender(Mortgage)</td>
<td width="110">Term</td>
<td width="135">Rate</td>
<td width="200">Lender(Mortage)</td>
<td width="47">Term</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.0</td>
<td>6.000%</td>
<td>ABC</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>15</td>
</tr>
<tr>
<td>6.000%</td>
<td>BCD</td>
<td>15</td>
<td>6.750%</td>
<td>BCD</td>
<td>15</td>
</tr>
<tr>
<td height="39" valign="top">6.000%</td>
<td valign="top">CDE</td>
<td valign="top">15</td>
<td valign="top">6.250%</td>
<td valign="top">ABC</td>
<td valign="top">15</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.5</td>
<td>6.500%</td>
<td>CDE</td>
<td>30</td>
<td>7.250%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>6.250%</td>
<td>BCD</td>
<td>30</td>
<td>7.000%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td height="38" valign="top">6.125%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
<td valign="top">6.500%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
</tr>
<tr>
<td rowspan="5" valign="top">1.0</td>
<td>5.750%</td>
<td>CDE</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td>6.500%</td>
<td>ABC</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td>6.500%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
</table>
=== The improved table v2 ===
We were not sure, what the value "points" is. In the first version (above) we sorted the table by points, because it's also sorted by points in the original one. But afterwards we thought, that the value "points" is not so important, maybe it's just the commission. If it is so, it doesn't make sense to sort the table by commission. So we created a new version of the table (this version is better, if "points" is not important).
[[Image:Table v2.jpg]]
 
'''Why is this table better than the original one?'''
* It's sorted by Rate, which is the most important value if you're going to lend money.
* It's easier to follow one row, because of smart use of whitespace.
* The values are grouped together by points and terms, so you don't need to fill in the same values for points and terms in every row.
* The Rate and all numbers are aligned to the right -> you can compare it easier.
* "Mortgage" is not in every row but once in the header.
* We broke up the table in 2 parts: the "fixed" one and the "adjustable" one. This gives you a faster overview of your possibilites if you're going to lend money.
* The "lender" value is centered, because every lender is represented by exactly 3 characters - it's easier to follow.
* We used an unobtrusive grey rule to delineate the header from the body.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 2

2007-11-19T12:24:02Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_loan_rates.png]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

== Lösung der Aufgabe ==

=== Animadversion on the given table ===
# Absolutley no fill color
# No subdivisions i.e. loan type (there are only 2 types) or term (also 2 types). The information adjustable/fixed or 15/30 is used too often.
# The table is sorted by points. Maybe it would be better, if it´s sort by rate or term
# The word ‘mortgage’ is used to often in the column ‘lender’, it´s not necessary to repeat it so often
# In the column ‘points’ the numbers should have the same amount of digits before and after the decimal point
# The numbers in the column ‘rate’ should all have 3 digits after the decimal point
# The title “effective September 1, 2003” isn´t clear. Is this a date or something else? (because only 1,2003 is bold, why is september not bold?)
# Due to the use of white spaces the reader scans the table column by column but it would make more sense, if there is less white space between the columns but more white space between the rows. This would make it easier to read the table row by row.
=== The improved table ===
This table is the right one, if the value "points" is very important (for more details please go to "The improved table v2" below).
 
<table width="866" border="0">
<tr>
<td width="91" valign="top"> </td>
<td colspan="3" align="center">Loan Type: Adjustable <hr/></td>
<td colspan="3" align="center">Loan Type: Fixed <hr/></td>
</tr>
<tr>
<td>Points</td>
<td width="104">Rate</td>
<td width="149">Lender(Mortgage)</td>
<td width="110">Term</td>
<td width="135">Rate</td>
<td width="200">Lender(Mortage)</td>
<td width="47">Term</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.0</td>
<td>6.000%</td>
<td>ABC</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>15</td>
</tr>
<tr>
<td>6.000%</td>
<td>BCD</td>
<td>15</td>
<td>6.750%</td>
<td>BCD</td>
<td>15</td>
</tr>
<tr>
<td height="39" valign="top">6.000%</td>
<td valign="top">CDE</td>
<td valign="top">15</td>
<td valign="top">6.250%</td>
<td valign="top">ABC</td>
<td valign="top">15</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.5</td>
<td>6.500%</td>
<td>CDE</td>
<td>30</td>
<td>7.250%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>6.250%</td>
<td>BCD</td>
<td>30</td>
<td>7.000%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td height="38" valign="top">6.125%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
<td valign="top">6.500%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
</tr>
<tr>
<td rowspan="5" valign="top">1.0</td>
<td>5.750%</td>
<td>CDE</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td>6.500%</td>
<td>ABC</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td>6.500%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
</table>
=== The improved table v2 ===
We were not sure, what is meant by "points". In the first version (above) we sorted the table by points, because it's also sorted by points in the original one. But afterwards we thought, that the value "points" is not so important, maybe it's just the commission. If it is so, it doesn't make sense to sort the table by commission. So we created a new version of the table (this version is better, if "points" is not important).
[[Image:Table v2.jpg]]
 
'''Why is this table better than the original one?'''
* It's sorted by Rate, which is the most important value if you're going to lend money.
* It's easier to follow one row, because of smart use of whitespace.
* The values are grouped together by points and terms, so you don't need to fill in the same values for points and terms in every row.
* The Rate and all numbers are aligned to the right -> you can compare it easier.
* "Mortgage" is not in every row but once in the header.
* We broke up the table in 2 parts: the "fixed" one and the "adjustable" one. This gives you a faster overview of your possibilites if you're going to lend money.
* The "lender" value is centered, because every lender is represented by exactly 3 characters - it's easier to follow.
* We used an unobtrusive grey rule to delineate the header from the body.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 2

2007-11-19T12:20:24Z

UE-InfoVis0708 0425163:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_loan_rates.png]]

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05|Gruppe 05]]

== Lösung der Aufgabe ==

=== Animadversion on the given table ===
# Absolutley no fill color
# No subdivisions i.e. loan type (there are only 2 types) or term (also 2 types). The information adjustable/fixed or 15/30 is used too often.
# The table is sorted by points. Maybe it would be better, if it´s sort by rate or term
# The word ‘mortgage’ is used to often in the column ‘lender’, it´s not necessary to repeat it so often
# In the column ‘points’ the numbers should have the same amount of digits before and after the decimal point
# The numbers in the column ‘rate’ should all have 3 digits after the decimal point
# The title “effective September 1, 2003” isn´t clear. Is this a date or something else? ''--> Yes, that's a date - what else? ;-) --> but only 1,2003 is bold, why is september not bold? --> I think that's a mistake, that not everything is bold... BUT: Why do we discuss in english and not in German? ''
 
# Due to the use of white spaces the reader scans the table column by column but it would make more sense, if there is less white space between the columns but more white space between the rows. This would make it easier to read the table row by row.
=== The improved table ===
<table width="866" border="0">
<tr>
<td width="91" valign="top"> </td>
<td colspan="3" align="center">Loan Type: Adjustable <hr/></td>
<td colspan="3" align="center">Loan Type: Fixed <hr/></td>
</tr>
<tr>
<td>Points</td>
<td width="104">Rate</td>
<td width="149">Lender(Mortgage)</td>
<td width="110">Term</td>
<td width="135">Rate</td>
<td width="200">Lender(Mortage)</td>
<td width="47">Term</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.0</td>
<td>6.000%</td>
<td>ABC</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>15</td>
</tr>
<tr>
<td>6.000%</td>
<td>BCD</td>
<td>15</td>
<td>6.750%</td>
<td>BCD</td>
<td>15</td>
</tr>
<tr>
<td height="39" valign="top">6.000%</td>
<td valign="top">CDE</td>
<td valign="top">15</td>
<td valign="top">6.250%</td>
<td valign="top">ABC</td>
<td valign="top">15</td>
</tr>
<tr>
<td rowspan="3" valign="top">0.5</td>
<td>6.500%</td>
<td>CDE</td>
<td>30</td>
<td>7.250%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>6.250%</td>
<td>BCD</td>
<td>30</td>
<td>7.000%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td height="38" valign="top">6.125%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
<td valign="top">6.500%</td>
<td valign="top">ABC</td>
<td valign="top">30</td>
</tr>
<tr>
<td rowspan="5" valign="top">1.0</td>
<td>5.750%</td>
<td>CDE</td>
<td>15</td>
<td>7.000%</td>
<td>CDE</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td>6.500%</td>
<td>ABC</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td>6.500%</td>
<td>BCD</td>
<td>30</td>
</tr>
<tr>
<td>5.675%</td>
<td>ABC</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>5.675%</td>
<td>BCD</td>
<td>15</td>
<td> </td>
<td> </td>
<td> </td>
</tr>
</table>
=== The improved table v2 ===
We were not sure, what is meant by "points". In the first version (above) we sorted the table by points, because it's also sorted by points in the original one. But afterwards we thought, that the value "points" is not so important, maybe it's just the commission. If it is so, it doesn't make sense to sort the table by commission. So we created a new version of the table (this version is better, if "points" is not important).
[[Image:Table v2.jpg]]
'''Why is this table better than the original one?'''
* It's sorted by Rate, which is the most important value if you're going to lend money.
* It's easier to follow one row, because of smart use of whitespace.
* The values are grouped together by points and terms, so you don't need to fill in the same values for points and terms in every row.
* The Rate and all numbers are aligned to the right -> you can compare it easier.
* "Mortgage" is not in every row but once in the header.
* We broke up the table in 2 parts: the "fixed" one and the "adjustable" one. This gives you a faster overview of your possibilites if you're going to lend money.
* The "lender" value is centered, because every lender is represented by exactly 3 characters - it's easier to follow.
* We used an unobtrusive grey rule to delineate the header from the body.

File:Table v2.jpg

2007-11-19T12:07:00Z

UE-InfoVis0708 0425163: improved table

== Summary ==
improved table
== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 2

2007-11-19T12:04:41Z

UE-InfoVis0708 0425163:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 2

2007-11-17T11:02:19Z

UE-InfoVis0708 0425163:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 2

2007-11-17T09:19:32Z

UE-InfoVis0708 0425163:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-04T10:33:03Z

UE-InfoVis0708 0425163:

= Rendering =
==Definition==
Rendering is the process of creating an image out of an abstract model of this image (e.g. wire frame).
== Overview ==
Rendering is a term which is used in computer graphics very often. The shape of the abstract model is represented by many points and edges. After the rendering process, the picture is not represented by different edges anymore, but with a (realistic) surface. This process needs a lot of computing power, especially if you want to create a realistic environment and realistic objects with different light sources. Rendering also considers different textures and shadings of objects.
== Techniques ==
There are several different techniques:
# '''wire frame:''' This is the abstract representation of the object just with edges (with or without visible surface detection)
# '''scan fill:''' This rendering mode just fills the object with a solid color and doesn't consider any lighting, shading or reflections
# '''flat shading:''' -considers different lighting aspects (shading) and reflections. Every polygon mesh is filled with the same color, but it varies within the object. This method takes care of all lighting aspects, but it doesn't give you a smooth surface, because you still see all the edges from the wire frame.
# '''gouraud shading, phong shading:''' These are two similar techniques to create very smooth surfaces. The computation of the surface is complex, therefore it needs more computing power than the previous techniques, but today this kind of rendering is no problem at all, because nearly every computer has enough computation power to do this kind of rendering (of course, it depends on the scene, you're trying to render).

<gallery caption="" widths="100px" heights="100px" perrow="6">
Image:Wire frame.jpg|teapot represented by wire frames; no visible-surface detection
Image:Wire_frame_backface_culling.jpg|teapot represented by wire frames with visible-surface detection
Image:Scan_filled.jpg|teapot with scan-fill rendering
image:Flat_shaded.jpg|teapot with flat shaded rendering
image:Gouraud_shaded.jpg|teapot with gouraud shaded rendering
image:Phong_shaded.jpg|teapot with phong shaded rendering
</gallery>

==Visible surface detection==
This is not a special rendering technique, but it's the basics for the rendering. The object is represented through different edges (wire frame) which describes the object surface. There are mainly two different ways to represent the object in wire frames:
# you can see all edges, even if you shouldn't see them, because they are in the background of the object (hidden by the front surface)
# you do some kind of visible-surface detection; therefore you need algorithms to decide which edges should be visible and which shouldn't. You have to identify the visible parts of a scene.
==References==
[Purgathofer, 2005] Werner Purgathofer, Computer Graphics 1 (lecture). Date of lecture: 2005. http://www.cg.tuwien.ac.at/courses/CG/slides.html

[Unknown, ?] Unknown, Rendering: Definition. Created at: ?. Retrieved at: November 3, 2007. http://www.itwissen.info/definition/lexikon//__rendering_rendering.html

All pictures are created on my own with the CG1 LU Framework which was used in the lecture "CG1 LU" in 2005.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-03T13:09:22Z

UE-InfoVis0708 0425163:

= Rendering =
==Definition==
Rendering is the process of creating an image out of an abstract model of this image (e.g. wire frame).
== Overview ==
Rendering is a term which is used in computer graphics very often. The shape of the abstract model is represented by many points and edges. After the rendering process, the picture is not represented by different edges anymore, but with a (realistic) surface. This process needs a lot of computing power, especially if you want to create a realistic environment and realistic objects with different light sources. Rendering also considers different textures and shadings of objects.
== Techniques ==
There are several different techniques:
# '''wire frame:''' This is the abstract representation of the object just with edges (with or without visible surface detection)
# '''scan fill:''' This rendering mode just fills the object with a solid color and doesn't consider any lighting, shading or reflections
# '''flat shading:''' -considers different lighting aspects (shading) and reflections. Every polygon mesh is filled with the same color, but it varies within the object. This method takes care of all lighting aspects, but it doesn't give you a smooth surface, because you still see all the edges from the wire frame.
# '''gouraud shading, phong shading:''' These are two similar techniques to create very smooth surfaces. The computation of the surface is complex, therefore it needs more computing power than the previous techniques, but today this kind of rendering is no problem at all, because nearly every computer has enough computation power to do this kind of rendering (of course, it depends on the scene, you're trying to render).

<gallery caption="" widths="100px" heights="100px" perrow="6">
Image:Wire frame.jpg|teapot represented by wire frames; no visible-surface detection
Image:Wire_frame_backface_culling.jpg|teapot represented by wire frames with visible-surface detection
Image:Scan_filled.jpg|teapot with scan-fill rendering
image:Flat_shaded.jpg|teapot with flat shaded rendering
image:Gouraud_shaded.jpg|teapot with gouraud shaded rendering
image:Phong_shaded.jpg|teapot with phong shaded rendering
</gallery>

==Visible surface detection==
This is not a special rendering technique, but it's the basics for the rendering. The object is represented through different edges (wire frame) which describes the object surface. There are mainly two different ways to represent the object in wire frames:
# you can see all edges, even if you shouldn't see them, because they are in the background of the object (hidden by the front surface)
# you do some kind of visible-surface detection; therefore you need algorithms to decide which edges should be visible and which shouldn't. You have to identify visible parts of a scene.
==References==
[Purgathofer, 2005] Werner Purgathofer, Computer Graphics 1 (lecture). Date of lecture: 2005. http://www.cg.tuwien.ac.at/courses/CG/slides.html

[Unknown, ?] Unknown, Rendering: Definition. Created at: ?. Retrieved at: November 3, 2007. http://www.itwissen.info/definition/lexikon//__rendering_rendering.html

All pictures are created on my own with the CG1 LU Framework which was used in the lecture "CG1 LU" in 2005.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-03T13:01:47Z

UE-InfoVis0708 0425163:

= Rendering =
==Definition==
Rendering is the process of creating an image out of an abstract model of this image (e.g. wire frame).
== Overview ==
Rendering is a term which is used in computer graphics very often. The shape of the abstract model is represented by many points and edges. After the rendering process, the picture is not represented by different edges anymore, but with a (realistic) surface. This process needs a lot of computing power, especially if you want to create a realistic environment and realistic objects with different light sources. Rendering also considers different textures and shadings of objects.
== Techniques ==
There are several different techniques:
# '''wire frame:''' This is the abstract representation of the object just with edges (with or without visible surface detection)
# '''scan fill:''' This rendering mode just fills the object with a solid color and doesn't consider any lighting, shading or reflections
# '''flat shading:''' -considers different lighting aspects (shading) and reflections. Every polygon mesh is filled with the same color, but it varies within the object. This method takes care of all lighting aspects, but it doesn't give you a smooth surface, because you still see all the edges from the wire frame.
# '''gouraud shading, phong shading:''' These are two similar techniques to create very smooth surfaces. The computation of the surface is complex, therefore it needs more computing power than the previous techniques, but today this kind of rendering is no problem at all, because nearly every computer has enough computation power to do this kind of rendering (of course, it depends on the scene, you're trying to render).

<gallery caption="" widths="100px" heights="100px" perrow="6">
Image:Wire frame.jpg|teapot represented by wire frames; no visible-surface detection
Image:Wire_frame_backface_culling.jpg|teapot represented by wire frames with visible-surface detection
Image:Scan_filled.jpg|teapot with scan-fill rendering
image:Flat_shaded.jpg|teapot with flat shaded rendering
image:Gouraud_shaded.jpg|teapot with gouraud shaded rendering
image:Phong_shaded.jpg|teapot with phong shaded rendering
</gallery>

==Visible surface detection==
This is not a special rendering technique, but it's the basics for the rendering. The object is represented through different edges (wire frame) which describes the object surface. There are mainly two different ways to represent the object in wire frames:
# you can see all edges, even if you shouldn't see them, because they are in the background of the object (hidden by the front surface)
# you do some kind of visible-surface detection; therefore you need algorithms to decide which edges should be visible and which shouldn't. You have to identify visible parts of a scene.
==References==
[Purgathofer, 2005] Werner Purgathofer, Computer Graphics 1 (lecture). Date of lecture: 2005. http://www.cg.tuwien.ac.at/courses/CG/slides.html

[Unknown, ?] Unknown, Rendering: Definition. Created at: ?. Retrieved at: November 2, 2007. http://www.itwissen.info/definition/lexikon//__rendering_rendering.html

All pictures are created on my own with the CG1 LU Framework which was used in the lecture "CG1 LU" in 2005.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-03T12:57:23Z

UE-InfoVis0708 0425163:

= Rendering =
==Definition==
Rendering is the process of creating an image out of an abstract model of this image (e.g. wire frame).
== Overview ==
Rendering is a term which is used in computer graphics very often. The shape of the abstract model is represented by many points and edges. After the rendering process, the picture is not represented by different edges anymore, but with a (realistic) surface. This process needs a lot of computing power, especially if you want to create a realistic environment and realistic objects with different light sources. Rendering also considers different textures and shadings of objects.
== Techniques ==
There are several different techniques:
# '''wire frame:''' This is the abstract representation of the object just with edges (with or without visible surface detection)
# '''scan fill:''' This rendering mode just fills the object with a solid color and doesn't consider any lighting, shading or reflections
# '''flat shading:''' -considers different lighting aspects (shading) and reflections. Every polygon mesh is filled with the same color, but it varies within the object. This method takes care of all lighting aspects, but it doesn't give you a smooth surface, because you still see all the edges from the wire frame.
# '''gouraud shading, phong shading:''' These are two similar techniques to create very smooth surfaces. The computation of the surface is complex, therefore it needs more computing power than the previous techniques, but today this kind of rendering is no problem at all, because nearly every computer has enough computation power to do this kind of rendering (of course, it depends on the scene, you're trying to render).

<gallery caption="" widths="100px" heights="100px" perrow="6">
Image:Wire frame.jpg|teapot represented by wire frames; no visible-surface detection
Image:Wire_frame_backface_culling.jpg|teapot represented by wire frames with visible-surface detection
Image:Scan_filled.jpg|teapot with scan-fill rendering
image:Flat_shaded.jpg|teapot with flat shaded rendering
image:Gouraud_shaded.jpg|teapot with gouraud shaded rendering
image:Phong_shaded.jpg|teapot with phong shaded rendering
</gallery>

==Visible surface detection==
This is not a special rendering technique, but it's the basics for the rendering. The object is represented through different edges (wire frame) which describes the object surface. There are mainly two different ways to represent the object in wire frames:
# you can see all edges, even if you shouldn't see them, because they are in the background of the object (hidden by the front surface)
# you do some kind of visible-surface detection; therefore you need algorithms to decide which edges should be visible and which shouldn't. You have to identify visible parts of a scene.
==References==
[Purgathofer, 2005] Werner Purgathofer, Computer Graphics 1 (lecture). Date of lecture: 2005. http://www.cg.tuwien.ac.at/courses/CG/slides.html

[Unknown, ?] Unknown, Rendering: Definition. Created at: ?. Retrieved at: November 2, 2007. http://www.itwissen.info/definition/lexikon//__rendering_rendering.html

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-03T12:50:53Z

UE-InfoVis0708 0425163:

= Rendering =
==Definition==
Rendering is the process of creating an image out of an abstract model of this image (e.g. wire frame).
== Overview ==
Rendering is a term which is used in computer graphics very often. The shape of the abstract model is represented by many points and edges. After the rendering process, the picture is not represented by different edges anymore, but with a (realistic) surface. This process needs a lot of computing power, especially if you want to create a realistic environment and realistic objects with different light sources. It also takes care about different textures and shadings of objects.
== Techniques ==
There are several different techniques, how you can do the rendering:
# '''wire frame:''' This is the abstract representation of the object just with edges (with or without visible surface detection)
# '''scan fill:''' This rendering mode just fills the object with a solid color and doesn't take care of lighting, shading and reflection
# '''flat shading:''' -takes care of different lighting aspects (shading) and reflections. Every polygon mesh is filled with the same color, but it varies within the object. This method takes care of all lighting aspects, but it doesn't give you a smooth surface, because you still see all the edges from the wire frame.
# '''gouraud shading, phong shading:''' These are two similar techniques to create very smooth surfaces. The computation of the surface is complex, therefore it needs more computing power than the previous techniques, but today this kind of rendering is no problem at all, because nearly every has enough computation power to do that rendering (of course, it depends on the scene, you're trying to render).

<gallery caption="" widths="100px" heights="100px" perrow="6">
Image:Wire frame.jpg|teapot represented by wire frames; no visible-surface detection
Image:Wire_frame_backface_culling.jpg|teapot represented by wire frames with visible-surface detection
Image:Scan_filled.jpg|teapot with scan-fill rendering
image:Flat_shaded.jpg|teapot with flat shaded rendering
image:Gouraud_shaded.jpg|teapot with gouraud shaded rendering
image:Phong_shaded.jpg|teapot with phong shaded rendering
</gallery>

==Visible surface detection==
This is not a special rendering technique, but it's the basics for the rendering. The object is represented through different edges (wire frame) which describes the object surface. There are mainly two different ways to represent the object in wire frames:
# you can see all edges, even if you shouldn't see them, because they are in the background of the object an hidden by the front surface
# you do some kind of visible-surface detection; therefore you need algorithms to decide which edges should be visible and which shouldn't be visible because they are hidden, so that you identify visible parts of a scene
==References==
[Purgathofer, 2005] Werner Purgathofer, Computer Graphics 1 (lecture). Date of lecture: 2005. http://www.cg.tuwien.ac.at/courses/CG/slides.html

[Unknown, ?] Unknown, Rendering: Definition. Created at: ?. Retrieved at: November 2, 2007. http://www.itwissen.info/definition/lexikon//__rendering_rendering.html

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-03T12:30:50Z

UE-InfoVis0708 0425163:

= Rendering =
==Definition==
Rendering is the process of creating an image out of an abstract model of this image (e.g. wire frame).
== Overview ==
Rendering is a term which is used in computer graphics very often. The shape of the abstract model is represented by many points and edges. After the rendering process, the picture is not represented by different edges anymore, but with a (realistic) surface. This process needs a lot of computing power, especially if you want to create a realistic environment and realistic objects with different light sources. It also takes care about different textures and shadings of objects.
== Techniques ==
There are several different techniques, how you can do the rendering:
# '''wire frame:''' This is the abstract representation of the object just with edges (with or without visible surface detection)
# '''scan fill:''' This rendering mode just fills the object with a solid color and doesn't take care of lighting, shading and reflection
# '''flat shading:''' -takes care of different lighting aspects (shading) and reflections. Every polygon mesh is filled with the same color, but it varies within the object. This method takes care of all lighting aspects, but it doesn't give you a smooth surface, because you still see all the edges from the wire frame.
# '''gouraud shading, phong shading:''' These are two similar techniques to create very smooth surfaces. The computation of the surface is complex, therefore it needs more computing power than the previous techniques, but today this kind of rendering is no problem at all, because nearly every has enough computation power to do that rendering (of course, it depends on the scene, you're trying to render).

<gallery caption="" widths="100px" heights="100px" perrow="6">
Image:Wire frame.jpg|teapot represented by wire frames; no visible-surface detection
Image:Wire_frame_backface_culling.jpg|teapot represented by wire frames with visible-surface detection
Image:Scan_filled.jpg|teapot with scan-fill rendering
image:Flat_shaded.jpg|teapot with flat shaded rendering
image:Gouraud_shaded.jpg|teapot with gouraud shaded rendering
image:Phong_shaded.jpg|teapot with phong shaded rendering
</gallery>

==Visible surface detection==
This is not a special rendering technique, but it's the basics for the rendering. The object is represented through different edges which describes the object surface. There are mainly two different ways to represent the object in wire frames:
# you can see all edges, even if you shouldn't see them, because they are in the background of the object an hidden by the front surface
# you do some kind of visible-surface detection; therefore you need algorithms to decide which edges should be visible and which shouldn't be visible because they are hidden, so that you identify visible parts of a scene

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-03T12:16:30Z

UE-InfoVis0708 0425163:

= Rendering =
==Definition==
Rendering is the process of creating an image out of an abstract model of this image (e.g. wire frame).
== Overview ==
Rendering is a term which is used in computer graphics very often. The shape of the abstract model is represented by many points and edges. After the rendering process, the picture is not represented by different edges anymore, but with a (realistic) surface. This process needs a lot of computing power, especially if you want to create a realistic environment and realistic objects with different light sources. It also takes care about different textures and shadings of objects.
== Techniques ==
There are several different techniques, how you can do the rendering:
# '''wire frame:''' This is the abstract representation of the objectjust with edges (with or without visible surface detection)
# '''scan fill:''' This rendering mode just fills the object with a solid color and doesn't take care of lighting, shading and reflection
# '''flat shading:''' -takes care of different lighting aspects (shading) and reflections. Every polygon mesh is filled with the same color, but it varies within the object. This method takes care of all lighting aspects, but it doesn't give you a smooth surface, because you still see all the edges from the wire frame.
# '''gouraud shading, phong shading:''' These are two similar techniques to create very smooth surfaces. The computation of the surface is complex, therefore it needs more computing power than the previous techniques, but today this kind of rendering is no problem at all, because nearly every has enough computation power to do that rendering (of course, it depends on the scene, you're trying to render).
[[image:Wire frame.jpg|thumb|left|teapot represented by wire frames; no visible-surface detection]]
[[image:Wire_frame_backface_culling.jpg|thumb|left|teapot represented by wire frames with visible-surface detection]]
[[image:Scan_filled.jpg|thumb|left|teapot with scan-fill rendering]]
[[image:Flat_shaded.jpg|thumb|left|teapot with flat shaded rendering]]
[[image:Gouraud_shaded.jpg|thumb|left|teapot with gouraud shaded rendering]]
[[image:Phong_shaded.jpg|thumb|left|teapot with phong shaded rendering]]

===Visible surface detection===
This is not a special rendering technique, but it's the basics for the rendering. The object is represented through different edges which describes the object surface. There are mainly two different ways to represent the object in wire frames:
# you can see all edges, even if you shouldn't see them, because they are in the background of the object an hidden by the front surface
# you do some kind of visible-surface detection; therefore you need algorithms to decide which edges should be visible and which shouldn't be visible because they are hidden, so that you identify visible parts of a scene

File:Phong shaded.jpg

2007-11-03T12:15:46Z

UE-InfoVis0708 0425163: teapot with phong shaded rendering

== Summary ==
teapot with phong shaded rendering
== Copyright status ==

== Source ==
CG1 LU Mainframe

File:Gouraud shaded.jpg

2007-11-03T12:15:02Z

UE-InfoVis0708 0425163: teapot with gouraud shaded rendering

== Summary ==
teapot with gouraud shaded rendering
== Copyright status ==

== Source ==
CG1 LU Mainframe

File:Flat shaded.jpg

2007-11-03T12:13:28Z

UE-InfoVis0708 0425163: teapot with flat shaded rendering

== Summary ==
teapot with flat shaded rendering
== Copyright status ==

== Source ==
CG1 LU Mainframe

File:Scan filled.jpg

2007-11-03T12:11:37Z

UE-InfoVis0708 0425163: teapot with scan fill rendering

== Summary ==
teapot with scan fill rendering
== Copyright status ==

== Source ==
CG1 LU Mainframe

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-03T11:30:16Z

UE-InfoVis0708 0425163:

= Rendering =
== Introduction ==
Rendering is a term which is used in computer graphics very often. It's the process of creating an image out of an abstract model of this image (e.g. polygon mesh). The shape in this abstract model is represented by many points. After the rendering process, the picture is not represented by different points anymore, but with a (realistic) surface. This process needs a lot of computing power, especially if you want to create a realistic environment and realistic objects with different light sources.
== Techniques ==
There are several different techniques, how you can do the rendering. The following should give you a small overview of the most common techniques.
===Wire Frame===
This is not a special rendering technique, but it's the basics for the rendering. The object is represented through different points which are connected. The surface of the object is described with lines. There are mainly two different ways to represent the object:
# you can see all edges, even if you shouldn't see them, because they are in the background of the object an hidden by the front surface
# you do some kind of visible-surface detection; therefore you need algorithms to decide which edges should be visible and which shouldn't be visible because they are hidden, so that you identify visible parts of a scene
[[image:Wire frame.jpg|thumb|left|teapot represented by wire frames; no visible-surface detection]]
[[image:Wire_frame_backface_culling.jpg|thumb|left|teapot represented by wire frames with visible-surface detection]]
 
===Scan Fill===

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-03T11:26:20Z

UE-InfoVis0708 0425163:

= Rendering =
== Introduction ==
Rendering is a term which is used in computer graphics very often. It's the process of creating an image out of an abstract model of this image (e.g. polygon mesh). The shape in this abstract model is represented by many points. After the rendering process, the picture is not represented by different points anymore, but with a (realistic) surface. This process needs a lot of computing power, especially if you want to create a realistic environment and realistic objects with different light sources.
== Techniques ==
There are several different techniques, how you can do the rendering. The following should give you a small overview of the most common techniques.
===Wire Frame===
This is not a special rendering technique, but it's the basics for the rendering. The object is represented through different points which are connected. The surface of the object is described with lines. There are mainly two different ways to represent the object:
# you can see all edges, even if you shouldn't see them, because they are in the background of the object an hidden by the front surface
# you do some kind of visibility detection; therefore you need algorithms to decide which edges should be visible and which shouldn't be visible because they are hidden
[[image:Wire frame.jpg|thumb|left|teapot represented by wire frames; no visibility detection]]
[[image:Wire_frame_backface_culling.jpg|thumb|left|teapot represented by wire frames with visibility detection]]

File:Wire frame backface culling.jpg

2007-11-03T11:24:34Z

UE-InfoVis0708 0425163: teapot in wire frame mode with visibility detection (backface culling)

== Summary ==
teapot in wire frame mode with visibility detection (backface culling)
== Copyright status ==

== Source ==
CG1 LU Framework

File:Wire frame.jpg

2007-11-03T11:17:45Z

UE-InfoVis0708 0425163:

== Summary ==
teapot surface in wire frame mode
== Copyright status ==

== Source ==
CG1 LU Framework

File:Wire frame.jpg

2007-11-03T11:09:10Z

UE-InfoVis0708 0425163: teapot surface in wire frame mode

== Summary ==
teapot surface in wire frame mode
== Copyright status ==

== Source ==
CG1 LU Mainframe

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-03T10:59:40Z

UE-InfoVis0708 0425163:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 05 - Aufgabe 1 - Rendering

2007-11-03T10:44:21Z

UE-InfoVis0708 0425163: New page: = Rendering = == Introduction == Rendering is a term which is used in computer graphics very often. It's the process of creating a 3d image out of an abstract model of this image (e.g. pol...

= Rendering =
== Introduction ==
Rendering is a term which is used in computer graphics very often. It's the process of creating a 3d image out of an abstract model of this image (e.g. polygon mesh). The shape in this abstract model is represented by many points. After the rendering process, the picture is not represented by different points anymore, but with a (realistic) surface.

User:UE-InfoVis0708 0425163

2007-10-22T21:00:15Z

UE-InfoVis0708 0425163:

<table>
<tr>
<td>
[[Image:RainerPlaninc.jpg]]
</td>
<td>
==PLANINC Rainer==
 
*'''Matrikelnummer:''' 0425163 
*'''Studienkennzahl:''' 066 935 
*'''email-Adresse:''' rainer.planinc (ÄT) chello.at
</td>
</tr>
</table>
 
letzte Änderung: [[User:UE-InfoVis0708 0425163|UE-InfoVis0708 0425163]] 23:00, 22 October 2007 (CEST)

User:UE-InfoVis0708 0425163

2007-10-22T20:59:02Z

UE-InfoVis0708 0425163:

User:UE-InfoVis0708 0425163

2007-10-22T20:57:55Z

UE-InfoVis0708 0425163:

User:UE-InfoVis0708 0425163

2007-10-22T17:58:06Z

UE-InfoVis0708 0425163:

<table>
<tr>
<td>
[[Image:RainerPlaninc.jpg]]
</td>
<td>
'''''PLANINC Rainer''''' 
*'''Matrikelnummer:''' 0425163 
*'''Studienkennzahl:''' 066 935 
*'''email-Adresse:''' rainer.planinc (ÄT) chello.at
</td>
</tr>
</table>
 
letzte Änderung: [[User:UE-InfoVis0708 0425163|UE-InfoVis0708 0425163]] 19:58, 22 October 2007 (CEST)

User:UE-InfoVis0708 0425163

2007-10-22T17:56:54Z

UE-InfoVis0708 0425163:

<table>
<tr>
<td>
[[Image:RainerPlaninc.jpg]]
</td>
<td>
'''''PLANINC Rainer''''' 
*'''Matrikelnummer:''' 0425163 
*'''Studienkennzahl:''' 066 935 
*'''email-Adresse:''' rainer.planinc (ÄT) chello.at
</td>
</tr>
</table>
 
letzte Änderung: [[User:UE-InfoVis0607 0425163|UE-InfoVis0607 0425163]] 19:25, 22 October 2007 (CEST)

User:UE-InfoVis0708 0425163

2007-10-22T17:52:08Z

UE-InfoVis0708 0425163: New page: <table> <tr> <td> Image:RainerPlaninc.jpg </td> <td> '''PLANINC Rainer''' *'''Matrikelnummer:''' 0425163 *'''Studienkennzahl:''' 066 935 *'''email-Adresse:''' rainer.pl...

<table>
<tr>
<td>
[[Image:RainerPlaninc.jpg]]
</td>
<td>
'''PLANINC Rainer''' 
*'''Matrikelnummer:''' 0425163 
*'''Studienkennzahl:''' 066 935 
*'''email-Adresse:''' rainer.planinc (ÄT) chello.at
</td>
</tr>
</table>
 
letzte Änderung: [[User:UE-InfoVis0607 0425163|UE-InfoVis0607 0425163]] 19:25, 22 October 2007 (CEST)