ParaView 3 Telecon 08-28-2008
| Item | People | Description |
|---|---|---|
| 1 | Karelitz | MARS/V&V Milestone issues |
| 2 | Moreland | Easy Qt Version Change |
| 3 | Moreland | 64-bit Id Default |
| 3 | All | ParaView 3.4 Bugs |
MARS/V&V Milestone issues
Lisa is having trouble with loading resulting STL files into Cubit. The problem appears to be with non-manifold edges. Charles Law is at a conference. When he gets back, Berk will consult him.
The non-manifold edges appear in places where there is a pinch in the data. It happens where two fragments come together at the same volumetric cell. Basically, two fragments now share an edge, and when you "clean" the data, the points on this shared edge also get shared amongst fragments, which in turn causes problems.
Easy Qt Version Change
Lots of people are trying to currently compile ParaView with Qt 4.4, which we do not support. Right now, they either have to download and install an earlier version, or they have to hack the CMakeLists.txt code. What if instead there was a CMake option, defaulted to off, that overrode this check and allowed users to easily compiled with newer versions of Qt (with appropriate warnings about their version of ParaView now being unsupported, of course).
Utkarsh has already committed a change that just outputs a warning when trying to use a newer version of Qt.
On a tangential note, Utkarsh is seeing lots of artifacts with using Qt 4.4 on Linux. The GUI looks really terrible. The padding is bad and text is not respecting the bounds of the widgets it is in. Clint does not report the same problems. It might be an issue with Utkarsh's setup.
64-bit Id Default
By default, VTK_USE_64BIT_IDS is OFF. This means that global ids will be 32-bit, which could lead to problems with MPI servers even when compiling 32-bit executable. Should ParaView default VTK_USE_64BIT_IDS to ON?
The problem with turning it on all the time is that many things will take up more memory. The topology of any unstructured grid or poly data type would double. A greater issue is that the id size must be statically assigned at compile time. It would be much better if id sizes could be changed at compile time. This might be something that we can look at in the future.
