[Paraview] issue with savescreenshot in pvpython when having two renderviews

[Jens Dahl Kunoy]

Hi,
I want to compare two vtk files by having two render views and dump these
two renderviews into a single image file. The py script recorded by trace
works from GUI but not from the command line using pvpython. Using pvpython
the second renderview has no data and there is also other artefacts. You
can see the difference in the attached two files.

I put it up as an issue here:
https://gitlab.kitware.com/paraview/paraview/issues/17938

Any ideas?

BR
Jens
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] custom view plugin - minimal example needed

[Kolja Petersen]

Is it possible to write a plugin that derives from vtkPVView instead of
vtkPVRenderView?

I don't know how I can further shorten my question. The answer is quite
important to decide whether we can continue our ParaView developments.
Thank you
Kolja


Virenfrei.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Jan 15, 2018 at 7:32 PM, Kolja Petersen 
wrote:

> I have stripped down Plugin/MantaView until all compilation problems
> disappear. What is left, is basically a plugin for a vtkOpenGLRenderer.
> The code, consisting of only two minimal classes, is attached and can be
> built using:
> unzip snippet-viewplugin.zip && mkdir build && cd build && cmake && make
> (tested with ParaView 5.4.1)
>
> This brings me back to my initial question. I'd like to show a custom
> view, made of a number of Qt widgets (buttons and text) to show important
> statistics.
> In SnippetView.xml, the view is declared as:
>  base_proxyname="RenderView" ...
>
> How can I replace 'base_proxyname="RenderView"' by some generic view, to
> be filled with widgets? "View" or "ViewBase" are not recognized as base
> proxies.
> Thank you
> Kolja
>
>
> On Sun, Jan 14, 2018 at 5:05 PM, Kolja Petersen 
> wrote:
>
>> Dear plugin developers,
>> I need to implement a custom view to present datasets in a detailed
>> editable format.
>>
>> This link says that the plugin tutorial is obsolete for the view part:
>> https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_a
>> _custom_view_.2A_obsolete_.2A
>>
>> The Examples/Plugins/GUIView suggested in the link doesn't exist. The
>> Plugins/MantaView is rather complex and doesn't compile due to other bugs
>> as reported elsewhere, so that I can't get a clue how the MantaView plugin
>> is supposed to work.
>>
>> Could some kind developer upload a minimal working view plugin example,
>> which needs to display only a simple QButton or any other widget? This will
>> help to allow users build their custom views for ParaView 5.x.y.
>> Thank you
>> Kolja
>>
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

[Paraview] Material Interface Filter

[Scott, W Alan]

I have a user that wants to use the equivalent of the Material Interface Filter 
on VTK files.  Is there a way to do this?  I did find the Connectivity filter, 
that gets me half way.  I then want to find the mass of these individual 
fragments.

To test, I used Wavelet, the Clip by Sphere, then made the Radius 15, then ran 
the connectivity filter.

Thanks,

Alan


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

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

[Moreland, Kenneth]

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 
Date: Tuesday, January 16, 2018 at 7:58 AM
To: "Moreland, Kenneth" 
Cc: "paraview@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 
> 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.mahab...@geomechanica.com]
Sent: Wednesday, January 10, 2018 9:21 AM
To: Moreland, Kenneth >
Cc: paraview@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 
> 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-boun...@paraview.org] On 
Behalf Of Omid Mahabadi
Sent: Monday, January 8, 2018 2:30 PM
To: paraview@paraview.org
Subject: 

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

[Omid Mahabadi]

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 
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.mahab...@geomechanica.com]
> *Sent:* Wednesday, January 10, 2018 9:21 AM
> *To:* Moreland, Kenneth 
> *Cc:* paraview@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 
> 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-boun...@paraview.org] *On Behalf Of *Omid
> Mahabadi
> *Sent:* Monday, January 8, 2018 2:30 PM
> *To:* paraview@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: Inline image 1]
>
> However, in PV 5.x the lines are not fully visualized as if they're hidden
> below the other data object:
>
> [image: Inline 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