[Paraview-developers] [EXTERNAL] Re: VTK data types representation

[Scott, W Alan]

I am thinking that at this point, for 3D structured datasets (rectilinear and AMR) that outline is significantly worse than just displaying with surface.  A user almost always will want to see if data read in correctly, thus will change to solid, then do whatever they need to do.  Another problem is that, if a dataset has a lot of blocks, the outline blends into a white blob that then cannot be colored, and at that point I get a bug report.  At the least, we should use the  threshold you put into the settings window, same as for interactive rendering.

See above.  Just change representations for different data types.

Alan

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Monday, July 23, 2012 8:40 PM
To: Scott, W Alan
Cc: paraview-developers at paraview.org
Subject: [EXTERNAL] Re: [Paraview-developers] VTK data types representation

> The reason this is coming up is that Wavelet always starts as Outline, 
> as does all CTH AMR data.  I had thought that it was due to the 
> dataset's size, but it is actually be design for these datatypes.  Thoughts?

This was done deliberate ages ago (even in ParaView 2 days). I can't remember exactly way (maybe it was before my time), but someone else may know. Possibly because the idea is that for 3D structured datasets more often than not users are interested in volume rendering or contouring or something like that rather than looking at the surface of the dataset -- and hence to save geometry extraction and rendering time, we pick outline by default.

>
> I would make the mods myself, but don't really understand all of the 
> VTK data objects.

What mods are you thinking of making and why?

Utkarsh