5 |
**************************************************************************** |
**************************************************************************** |
6 |
|
|
7 |
|
|
8 |
- Two DataCollector instances needs to be created when two active scalars |
- Two DataCollector instances need to be created when two active scalars |
9 |
are read from the same file. |
are read from the same file. |
10 |
|
|
11 |
- setScalarRange() and generateCotours() must be supplied with the same range |
- setScalarRange() and generateContours() must be supplied with the same range |
12 |
in order for the colors to turn out correctly when contouring is performed. |
in order for the colors to turn out correctly when contouring is performed. |
13 |
|
|
14 |
- setPlaneToXY(), setPlaneToXZ() or setPlaneToYZ() needs to be executed |
- setPlaneToXY(), setPlaneToXZ() or setPlaneToYZ() needs to be executed |
28 |
|
|
29 |
- Movies cannot be generated from post script (.ps) files. |
- Movies cannot be generated from post script (.ps) files. |
30 |
|
|
31 |
- .iv (open inventor) and .wrl (VRML) files does not support multiple |
- .iv (open inventor) and .wrl (VRML) files do not support multiple |
32 |
viewports. |
viewports. |
33 |
|
|
34 |
- .iv files do suffer from some lighting problems when generated by VTK. |
- .iv files suffer from some lighting problems when generated by VTK. |
|
|
|
|
- On occasions, an inaccurate object may be rendered from cell data |
|
|
even after conversion. As such, it may be a good idea to use escript |
|
|
interpolation to get the node data. |
|
35 |
|
|
36 |
|
- On occasions, objects using cell data may be rendered incorrectly |
37 |
|
even after conversion. A workaround is to use escript interpolation to |
38 |
|
get the node data for visualizations. |
39 |
|
|