[Paraview-developers] Visualization issues after switching from PV 5.1.2 to 5.3

[Schlottke-Lakemper, Michael]

Hi Utkarsh,

Thank you for your reply. I followed your advice and indeed: Once I store the data loaded in PV 5.3 as a .vtu file, I am able to open it in PV 5.1.2 and it displays correctly.

Furthermore, I think I have identified the culprit: It seems to be a problem with the OpenGL2 backend, which seems to be the default now and which I forgot about. Once I reinstalled ParaView with -DVTK_RENDERING_BACKEND=OpenGL, things resumed to work as usual. Now this raises other questions:

What could create the problem that everything compiles and runs just fine, except for the visualization part? Maybe our OpenGL2 version is too old?

Regards,

Michael

P.S.: Just in case it still might be helpful (although I doubt it, since it seems to be related to the rendering backend), I uploaded the two files generated once by ParaView 5.1.2 (OpenGL) and ParaView 5.3.0 (OpenGL2):




monopole.pv512.vtu <https://rwth-aachen.sciebo.de/index.php/s/2jClJdm5fCTST33>
(41 MB)
monopole.pv530.vtu <https://rwth-aachen.sciebo.de/index.php/s/yyZDm6pUrIuut1c>
(41 MB)

> On Jun 2, 2017, at 01:15, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
> 
> Odd. A good starting point is to save out the data opened in older and newer versions as one of the standard supported file formats and compare that they are indeed what's expected. At that point, if it possible to share the exported dataset (that way I won't need your plugin code), we could see if I can reproduce the issue and see what could be going on.
> 
> Utkarsh
> 
> 
> 
> On Thu, Jun 1, 2017 at 5:38 PM, Schlottke-Lakemper, Michael <m.schlottke-lakemper at aia.rwth-aachen.de <mailto:m.schlottke-lakemper at aia.rwth-aachen.de>> wrote:
> Hi folks,
> 
> We just updated our local ParaView installation from 5.1.2 to 5.3.0 and also re-compiled our custom plugins. Now we experience the issue that for some of our reader plugins, after loading a solution/grid file we can actually see the grid and its cells, but the data is not correctly visualized. That is, when looking at the data range in the inspector (or at the range of the legend), one can see the correct minimum/maximum values and if when applying the threshold filter, it cuts the correct cells. However, the cells itself remain uni-colored.
> 
> Is it possible that this is related to changes in the ParaView build process? Maybe some switch in some visualization-related CMake defaults? I’m really at a loss here.
> 
> Regards,
> 
> Michael
> 
> P.S.: Here is an example:
> 
> Original figure with PV 5.1.2 (this is what we expect):
> <pv_512.jpeg>
> 
> Same figure with PV 5.3.0
> <pv_530_raw.jpeg>
> 
> Same figure with PV 5.3.0 and threshold filter applied to show only positive values (to demonstrate that it is, in fact, related to the visualization and not just the data reading):
> <pv_530_threshold.jpeg>
> 
> _______________________________________________
> Powered by www.kitware.com <http://www.kitware.com/>
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
> 
> Search the list archives at: http://markmail.org/search/?q=Paraview-developers <http://markmail.org/search/?q=Paraview-developers>
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers <http://public.kitware.com/mailman/listinfo/paraview-developers>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170602/a78f4a26/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170602/a78f4a26/attachment.sig>