[Paraview] ParaView 5.x not showing all objects available in Pipeline Browser

Thu Jan 18 13:22:03 EST 2018

Thanks Ken. I will try this on other machines. BTW I have version 3.0 of
OpenGL:
$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 10.5.9

Best regards,
Omid
--
Omid Mahabadi, Ph.D., P.Eng.
President & Geomechanics Specialist
Geomechanica Inc

Suite 900 – 390 Bay Street,
Toronto, On, M5H 2Y2
Canada

http://www.geomechanica.com/
Tel: +1-647-478-9767
Cell: +1-416-824-2408
Skype: omid82

Standalone licenses and cloud subscriptions for Irazu 2D/3D geomechanics
simulation software are now available: http://irazu.geomechanica.com

This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify me immediately by
email if you have received this email by mistake and delete this email from
your system. Email transmission cannot be guaranteed to be secure or
error-free, as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The sender,
therefore, does not accept liability for any errors or omissions in the
contents of this message which arise as a result of email transmission. If
verification is required, please request a hard-copy version. Geomechanica
Inc.

On Tue, Jan 16, 2018 at 10:31 AM, Moreland, Kenneth <kmorel at sandia.gov>
wrote:

> Omid,
>
>
>
> The only other thing I can think of is that there is something odd about
> the OpenGL driver/hardware on your system that for some reason is not
> supporting the coincident topology resolution in ParaView. ParaView changed
> its rendering system from OpenGL 1.3 to OpenGL 3.1 in version 5, the
> version that you report seeing the issue.
>
>
>
> Once again, I recommend trying to run ParaView on a completely different
> computer if you can find access to one. You might also try updating the
> OpenGL drivers on your computer. Beyond that, I am out of ideas.
>
>
>
> -Ken
>
>
>
> *From: *Omid Mahabadi <omid.mahabadi at geomechanica.com>
> *Date: *Tuesday, January 16, 2018 at 7:58 AM
> *To: *"Moreland, Kenneth" <kmorel at sandia.gov>
> *Cc: *"paraview at paraview.org" <paraview at paraview.org>
>
> *Subject: *[EXTERNAL] Re: [Paraview] ParaView 5.x not showing all objects
> available in Pipeline Browser
>
>
>
> Hi Ken,
>
> Thanks for your feedback and sorry for my late reply. Somehow I didn't get
> this message and only found your reply after searching in my mailbox.
>
>
>
> I tried various values for the Z Shift, increasing it by one order of
> magnitude until reaching a value of 200, restarting in between changes.
> This didn't help.
>
>
>
> I haven't really made any other changes in ParaView settings. I even
> restored to defaults a couple of times. I've been using Linux Mint 17 and
> have also experienced the same issue on Ubuntu 14.04 both 64 bit.
>
>
>
> Thanks
>
>
> Best regards,
>
> Omid
>
>
>
>
>
>
>
> On Wed, Jan 10, 2018 at 12:45 PM, Moreland, Kenneth <kmorel at sandia.gov>
> wrote:
>
> Omid,
>
>
>
> Even after applying the Threshold filter, I cannot replicate your problem.
> I’ve tried on both ParaView 5.2 and 5.4. Both work fine for me.
>
>
>
> My settings are the default. “Resolve Coincident Topology” is set to
> “Shift z-buffer when rendering lines and points”. “Z Shift” is set to
> 0.002. (Polygon offset should not matter in this mode.) You could try
> increasing the Z Shift to fix the problem. Note that you have to restart
> ParaView in order for these options to take effect.
>
>
>
> It is possible that there is some quirk with the rendering system on your
> computer that does not implement the topology resolution. Do you happen to
> have another computer on which you can try to run this? I also noted that
> if I turn on OSPRay rendering, I do get the missing line issue you
> describe. There might be other display/rendering parameters that cause
> issues. But the defaults should be fine, so unless you have done some
> tinkering you should be OK.
>
>
>
> -Ken
>
>
>
> *From:* Omid Mahabadi [mailto:omid.mahabadi at geomechanica.com]
> *Sent:* Wednesday, January 10, 2018 9:21 AM
> *To:* Moreland, Kenneth <kmorel at sandia.gov>
> *Cc:* paraview at paraview.org
> *Subject:* [EXTERNAL] Re: [Paraview] ParaView 5.x not showing all objects
> available in Pipeline Browser
>
>
>
> Hi Ken,
>
> Thanks for the detailed reply. I could not get anything out of the
> settings dialog as per your suggestion. Did you have a combination of those
> settings that might work for my files?
>
> I can also see the image you sent; that's usually fine. However, I
> typically apply a Threshold filter to the _basic_ files (Scalar: alive;
> min: 0.1; max: 1). In this case, the _basic_ object is always drawn in
> front of the _broken_joint_ object.
>
> In addition, I visualize dozens of these files every day so Transforming
> every single object is a bit tedious.
>
> Thank you,
>
> Omid
>
>
>
>
>
> On Mon, Jan 8, 2018 at 5:56 PM, Moreland, Kenneth <kmorel at sandia.gov>
> wrote:
>
> Omid,
>
>
>
> I am unable to replicate your issue in ParaView 5.4.1. When I loaded your
> data and showed the broken_joint data in wireframe, I was clearly able to
> see the lines of broken_joint over the polygons of basic. (See the attached
> image.)
>
>
>
> The problem you are getting is likely caused by z-buffer fighting in the
> rendering. This happens when two objects are the exact same distance from
> the viewer, as I believe is the case in your data. Wanting to draw lines on
> top of polygons is common enough that there are some corrections to help
> the rendering determine what to draw in front. Perhaps by changing the
> settings on resolving coincident topology will resolve your issue. You can
> find them by opening the ParaView settings dialog (Edit → Settings),
> clicking on the Render View tab, and turning on the advanced options. The
> options you are looking for are “Resolve Coincident Topology,” “Polygon
> Offset Parameters”, and “Z Shift.”
>
>
>
> Another, possibly easier, solution it to simply move the lines of the
> broken_joint data closer to the camera. Click the broken_joint object and
> add the Transform filter. Change the Translate parameter to 0, 0, 1 and
> apply. That should shift the wireframe forward enough to see it properly.
>
>
>
> -Ken
>
>
>
> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Omid
> Mahabadi
> *Sent:* Monday, January 8, 2018 2:30 PM
> *To:* paraview at paraview.org
> *Subject:* [EXTERNAL] [Paraview] ParaView 5.x not showing all objects
> available in Pipeline Browser
>
>
>
> Hi,
>
> I use ParaView to visualize data of our simulations using the Unstructured
> Grid data format. Up until ParaView 4.x everything worked fine: we
> typically visualize one set of data files as Surfaces and another as
> Wireframe. The Wireframe dataset refers to "fracture lines" in our
> simulations.
>
> See below how the simulation looked like in PV version 4.x. You could
> clearly see the line around the boundaries of the model.
>
> [image: nline image 1]
>
> However, in PV 5.x the lines are not fully visualized as if they're hidden
> below the other data object:
>
> [image: nline image 2]
>
> I've tried a few versions of 5.x but they all behave similarly.
>
> Does anyone know what might be going on here? Is this a bug / removed
> featured from the new version or should I do something different with 5.x?
> I've noticed that this issue does not happen consistently. I've seen the
> issue on both Linux Mint 17.3 (64 bit) and Ubuntu
>
> I've attached two example VTU files. Please visualize the second file as
> Wireframe (_broken_joint). Below are two large VTU files.
>
> https://www.dropbox.com/s/kzt4jq1wbwfua4j/out.zip?dl=0
>
>
>
> Can someone else reproduce this issue?
>
>
>
> I'd really hope to start using ParaView 5 since it finally has the
> long-missing Reload Files options!
>
> Thank you,
>
> Omid
>
>
>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://paraview.org/pipermail/paraview/attachments/20180118/69424f8d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2965 bytes
Desc: not available
URL: <https://paraview.org/pipermail/paraview/attachments/20180118/69424f8d/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 2608 bytes
Desc: not available
URL: <https://paraview.org/pipermail/paraview/attachments/20180118/69424f8d/attachment-0001.jpg>