Paluszek, Lukasz | 27 Jun 12:06 2016

Re: Opacity Issues

Switching to the old peeling implementation did the trick, no more issues and yes I am using remote rendering via pvserver.

 

Łukasz Paluszek

Airbus Helicopters

Aerodynamics Department (ETGA)

86607 Donauwörth

Germany

Tel.: +49 (90) 671 8231

Fax.: +49 (90) 671 9122

Lukasz.Paluszek <at> airbus.com

 

From: David Lonie [mailto:david.lonie <at> kitware.com]
Sent: 24 June 2016 21:22
To: Paluszek, Lukasz
Cc: paraview <at> paraview.org
Subject: Re: [Paraview] Opacity Issues

 

On Fri, Jun 24, 2016 at 2:15 PM, David Lonie <david.lonie <at> kitware.com> wrote:

On Fri, Jun 24, 2016 at 1:10 PM, Paluszek, Lukasz <lukasz.paluszek <at> airbus.com> wrote:

It doesn’t happen all the time, I suppose you need a fairly large surface dataset. I managed to reproduce the problem on a wavelet source (attached state file), try increasing the number of elements if you do not see any artifacts. I have bult Paraview from source on OpenSuse 13.1 but also cross-checked with the Linux binaries from Paraview.org and had same issues. There was no problem with the osmesa-llvm flavor though.

 

I couldn't reproduce this here on arch linux with a newer nVidia driver (367.27), so I'm suspicious that this is a driver bug that's affecting the new depth peeling implementation.

 

Since you're building from source, can you try editing VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, and change line 322

 

if (dualDepthPeelingSupported)

 

to

 

if (false)

 

in DeviceRenderTranslucentPolygonalGeometry, recompile using the OpenGL2 backend, and let me know if the issue goes away? I suspect it will since both the OpenGL1 backend and OpenGL2 mesa/llvm do not use the new code. 

 

I'll put together a patch to force the older peeling implementation via an environment variable to make the work-around easier to apply.

 

 

By the way, are you running paraview with remote rendering via pvserver? I was just made aware of a similar issue with remote rendering and depth peeling.

 

Dave

AIRBUS HELICOPTERS DEUTSCHLAND GmbH

Sitz der Gesellschaft / Registered Office: Donauwörth

Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508

Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury

Geschäftsführung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Schübel; Stefan Thomé

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
<div>
<div class="WordSection1">
<p class="MsoNormal"><span>Switching to the old peeling implementation did the trick, no more issues and yes I am using remote rendering via pvserver.<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span></span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span lang="FR">&#321;ukasz Paluszek</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span lang="FR">Airbus Helicopters</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span lang="FR">Aerodynamics Department (ETGA)</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span lang="FR">86607 Donauw&ouml;rth</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span lang="FR">Germany</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span>Tel.: +49 (90) 671 8231<p></p></span></p>
<p class="MsoNormal">
<span>Fax.: +49 (90)
</span><span>671 9122</span><span><p></p></span></p>
<p class="MsoNormal"><span><a href="mailto:Lukasz.Paluszek <at> airbus.com">Lukasz.Paluszek <at> airbus.com</a><p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>From:</span><span> David Lonie [mailto:david.lonie <at> kitware.com]
<br>Sent: 24 June 2016 21:22<br>To: Paluszek, Lukasz<br>Cc: paraview <at> paraview.org<br>Subject: Re: [Paraview] Opacity Issues<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<div>
<div>
<div>
<p class="MsoNormal">On Fri, Jun 24, 2016 at 2:15 PM, David Lonie &lt;<a href="mailto:david.lonie <at> kitware.com" target="_blank">david.lonie <at> kitware.com</a>&gt; wrote:<p></p></p>
<div>
<div>
<div>
<p class="MsoNormal">On Fri, Jun 24, 2016 at 1:10 PM, Paluszek, Lukasz &lt;<a href="mailto:lukasz.paluszek <at> airbus.com" target="_blank">lukasz.paluszek <at> airbus.com</a>&gt; wrote:<p></p></p>
<div>
<div>
<p class="MsoNormal"><span>It doesn&rsquo;t happen all the time, I suppose you need a fairly large surface dataset. I managed to reproduce
 the problem on a wavelet source (attached state file), try increasing the number of elements if you do not see any artifacts. I have bult Paraview from source on OpenSuse 13.1 but also cross-checked with the Linux binaries from Paraview.org and had same issues.
 There was no problem with the osmesa-llvm flavor though.</span><p></p></p>
</div>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">I couldn't reproduce this here on arch linux with a newer nVidia driver (367.27), so I'm suspicious that this is a driver bug that's affecting the new depth peeling implementation.<p></p></p>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">Since you're building from source, can you try editing VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, and change line 322<p></p></p>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">if (dualDepthPeelingSupported)<p></p></p>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">to<p></p></p>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">if (false)<p></p></p>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">in&nbsp;DeviceRenderTranslucentPolygonalGeometry, recompile using the OpenGL2 backend, and let me know if the issue goes away? I suspect it will since both the OpenGL1 backend and OpenGL2 mesa/llvm do not use the new code.&nbsp;<p></p></p>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">I'll put together a patch to force the older peeling implementation via an environment variable to make the work-around easier to apply.<p></p></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">Patch is here:&nbsp;<a href="https://gitlab.kitware.com/vtk/vtk/merge_requests/1589">https://gitlab.kitware.com/vtk/vtk/merge_requests/1589</a><p></p></p>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">By the way, are you running paraview with remote rendering via pvserver? I was just made aware of a similar issue with remote rendering and depth peeling.<p></p></p>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">Dave<p></p></p>
</div>
</div>
</div>
<p>AIRBUS HELICOPTERS DEUTSCHLAND GmbH</p>
<p>Sitz der Gesellschaft / Registered Office: Donauw&ouml;rth</p>
<p>Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508</p>
<p>Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury</p>
<p>Gesch&auml;ftsf&uuml;hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Sch&uuml;bel; Stefan Thom&eacute;</p>

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

</div>
Stephen Wornom | 27 Jun 10:14 2016
Picon
Picon

PV 4.1 how to extract a surface

The mesh is 3D unstructured about a 3D cylinder. I would like to extract the surface of the cylinder.

I have experience extracting surfaces with another code where the surfaces are defined by a variable (-3= cylinder surface).
I do it like this:
1-select extract surface
2-select conductivity
3-select threshold (choose -3 which corresponds to the cylinder surface).

but I am using a code where the cylinder surface is NOT a predefined variable.
How do I do I extract the surface?
Hope my question is clear,
Stephen


<div><div>
<div>The mesh is 3D unstructured about a 3D cylinder. I would like to extract the surface of the cylinder.<br>
</div>
<div><br></div>
<div>I have experience extracting surfaces with another code where the surfaces are defined by a variable (-3= cylinder surface).</div>
<div> I do it like this:<br>
</div>
<div>1-select extract surface<br>
</div>
<div>2-select conductivity<br>
</div>
<div>3-select threshold (choose -3 which corresponds to the cylinder surface).<br>
</div>
<div><br></div>
<div>but I am using a code where the cylinder surface is NOT a predefined variable.<br>
</div>
<div>How do I do I extract the surface?<br>
</div>
<div>Hope my question is clear,<br>
</div>
<div>Stephen<br>
</div>
<div><br></div>
<div><br></div>
</div></div>
Steve Lamont | 27 Jun 02:06 2016

A request

Is there any way that ParaView could be coded to give a better, more
helpful diagnostic than a core dump when a memory allocation fails?

In fact, could ParaView be coded to use an anonymous memory mapped file
allocation if the standard malloc() fails.  While this would result in
possibly degraded performance, at least one could get some sort of 
visualization done.

Thanks.

							spl
Joshua Murphy | 25 Jun 03:52 2016
Picon

error when trying to hide a sphere in a python script....

Hello,


I am writing a python script to do some analysis on magnetic field lines, and I am trying to generate some images for a sanity check.


The first image I have attached is the type of image I am trying to produce (verification_(5.25,0,0).png). 


The second image is generated in the same script.  The red and blue spheres that correspond to the ones in the first image should have been hidden, but when I try to hide them, I get the error:

(verification_(-5.25,0,0).png)


ERROR: In /Users/jjm390/src/Paraview/ParaView/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.cxx, line 409
vtkSMParaViewPipelineControllerWithRendering (0x7fca9e4cd180): Invalid producer (0x7fca9e4e12f0) or outputPort (0)


When the final render to screen is done, the spheres are all gone, but they do not get hidden when the image is generated.

The script I wrote is attached.  Note, if you need the entire project to help figure out why it isn't working, I can share it individually.  This is the script that generates the images.

​I would appreciate any help people might be able to offer!  I am running ParaView 5.0.1 on Mac OS X 10.11.5.

Thanks,
Josh Murphy



Attachment (noon_midnight_test.py): text/x-python-script, 6416 bytes
<div>
<p>Hello,<br></p>
<p><br></p>
<p>I am writing a python script to do some analysis on magnetic field lines, and I am trying to generate some images for a sanity check.<br></p>
<p><br></p>
<p>The first image I have attached is the type of image I am trying to produce (verification_(5.25,0,0).png).&nbsp;<br></p>
<p><br></p>
<p>The second image is generated in the same script. &nbsp;The red and blue spheres that correspond to the ones in the first image should have been hidden, but when I try to hide them, I get the error:<br></p>
<p><span>(</span><span>verification_(-5.25,0,0).png</span><span>)</span><br></p>
<div><br></div>
<div>ERROR: In /Users/jjm390/src/Paraview/ParaView/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.cxx, line 409</div>
<div>vtkSMParaViewPipelineControllerWithRendering (0x7fca9e4cd180): Invalid producer (0x7fca9e4e12f0) or outputPort (0)</div>
<div>
<br><br>
When the final render to screen is done, the spheres are all gone, but they do not get hidden when the image is generated.<br>
</div>
<div><br></div>
<div>The script I wrote is attached. &nbsp;Note, if you need the entire project to help figure out why it isn't working, I can share it individually. &nbsp;This is the script that generates the images.<br>
</div>
<div><br></div>
<div>&#8203;I would appreciate any help people might be able to offer! &nbsp;I am running ParaView 5.0.1 on Mac OS X 10.11.5.<br>
</div>
<div><br></div>
<div>Thanks,<br>
</div>
<div>Josh Murphy<br>
</div>
<div><br></div>
<p><br></p>
<p><br></p>
</div>
Paluszek, Lukasz | 24 Jun 19:10 2016

Re: Opacity Issues

It doesn’t happen all the time, I suppose you need a fairly large surface dataset. I managed to reproduce the problem on a wavelet source (attached state file), try increasing the number of elements if you do not see any artifacts. I have bult Paraview from source on OpenSuse 13.1 but also cross-checked with the Linux binaries from Paraview.org and had same issues. There was no problem with the osmesa-llvm flavor though.

 

 

Łukasz Paluszek

Airbus Helicopters

Aerodynamics Department (ETGA)

86607 Donauwörth

Germany

Tel.: +49 (90) 671 8231

Fax.: +49 (90) 671 9122

Lukasz.Paluszek <at> airbus.com

 

From: David Lonie [mailto:david.lonie <at> kitware.com]
Sent: 24 June 2016 18:24
To: Paluszek, Lukasz
Cc: paraview <at> paraview.org
Subject: Re: [Paraview] Opacity Issues

 

On Fri, Jun 24, 2016 at 11:15 AM, Paluszek, Lukasz <lukasz.paluszek <at> airbus.com> wrote:

Hello,

 

In Paraview 5.1.0 with OpenGL2, I have black slices throughout the model when opacity is on in parallel mode (see attached picture). When switching depth peeling off, the black slices disappear but the image gets blurred and some pixels glow with random colours. I can’t reproduce it with 5.0.0, my NVidia driver is 361.42. Does anyone else experience similar behaviour?

 

Interesting, I haven't seen this before. Does it happen for all depth peeled transparent rendering, or just certain scenes? If it's only certain scenes, can you provide a state file or details on the scene?

 

Also, which OS is this?

 

Thanks,

Dave

AIRBUS HELICOPTERS DEUTSCHLAND GmbH

Sitz der Gesellschaft / Registered Office: Donauwörth

Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508

Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury

Geschäftsführung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Schübel; Stefan Thomé

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
Attachment (opacity.pvsm): application/octet-stream, 184 KiB
<div>
<div class="WordSection1">
<p class="MsoNormal"><span>It doesn&rsquo;t happen all the time, I suppose you need a fairly large surface dataset. I managed to reproduce the problem on a wavelet source (attached state file),
 try increasing the number of elements if you do not see any artifacts. I have bult Paraview from source on OpenSuse 13.1 but also cross-checked with the Linux binaries from Paraview.org and had same issues. There was no problem with the osmesa-llvm flavor
 though.<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span></span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span lang="FR">&#321;ukasz Paluszek</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span lang="FR">Airbus Helicopters</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span lang="FR">Aerodynamics Department (ETGA)</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span lang="FR">86607 Donauw&ouml;rth</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span lang="FR">Germany</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">
<span>Tel.: +49 (90) 671 8231<p></p></span></p>
<p class="MsoNormal">
<span>Fax.: +49 (90)
</span><span>671 9122</span><span><p></p></span></p>
<p class="MsoNormal"><span><a href="mailto:Lukasz.Paluszek <at> airbus.com">Lukasz.Paluszek <at> airbus.com</a><p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>From:</span><span> David Lonie [mailto:david.lonie <at> kitware.com]
<br>Sent: 24 June 2016 18:24<br>To: Paluszek, Lukasz<br>Cc: paraview <at> paraview.org<br>Subject: Re: [Paraview] Opacity Issues<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<div>
<div>
<div>
<p class="MsoNormal">On Fri, Jun 24, 2016 at 11:15 AM, Paluszek, Lukasz &lt;<a href="mailto:lukasz.paluszek <at> airbus.com" target="_blank">lukasz.paluszek <at> airbus.com</a>&gt; wrote:<p></p></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Hello,</span><p></p></p>
<p class="MsoNormal"><span lang="EN-GB">&nbsp;</span><p></p></p>
<p class="MsoNormal"><span lang="EN-GB">In Paraview 5.1.0 with OpenGL2, I have black slices throughout the model when opacity is on in parallel mode (see attached picture). When switching depth peeling
 off, the black slices disappear but the image gets blurred and some pixels glow with random colours. I can&rsquo;t reproduce it with 5.0.0, my NVidia driver is 361.42. Does anyone else experience similar behaviour?</span><p></p></p>
</div>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">Interesting, I haven't seen this before. Does it happen for all depth peeled transparent rendering, or just certain scenes? If it's only certain scenes, can you provide a state file or details on the scene?<p></p></p>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">Also, which OS is this?<p></p></p>
</div>
<div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<p></p></p>
</div>
<div>
<p class="MsoNormal">Dave<p></p></p>
</div>
</div>
</div>
</div>
</div>
<p>AIRBUS HELICOPTERS DEUTSCHLAND GmbH</p>
<p>Sitz der Gesellschaft / Registered Office: Donauw&ouml;rth</p>
<p>Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508</p>
<p>Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury</p>
<p>Gesch&auml;ftsf&uuml;hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Sch&uuml;bel; Stefan Thom&eacute;</p>
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
</div>
Paluszek, Lukasz | 24 Jun 17:15 2016

Opacity Issues

Hello,

 

In Paraview 5.1.0 with OpenGL2, I have black slices throughout the model when opacity is on in parallel mode (see attached picture). When switching depth peeling off, the black slices disappear but the image gets blurred and some pixels glow with random colours. I can’t reproduce it with 5.0.0, my NVidia driver is 361.42. Does anyone else experience similar behaviour?

 

 

Reagrds,

Lukasz

Łukasz Paluszek

Airbus Helicopters

Aerodynamics Department (ETGA)

86607 Donauwörth

Germany

Tel.: +49 (90) 671 8231

Fax.: +49 (90) 671 9122

Lukasz.Paluszek <at> airbus.com

 

AIRBUS HELICOPTERS DEUTSCHLAND GmbH

Sitz der Gesellschaft / Registered Office: Donauwörth

Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508

Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury

Geschäftsführung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Schübel; Stefan Thomé

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
<div>
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB">Hello,<p></p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-GB">In Paraview 5.1.0 with OpenGL2, I have black slices throughout the model when opacity is on in parallel mode (see attached picture). When switching depth peeling off, the black slices disappear but the image gets blurred
 and some pixels glow with random colours. I can&rsquo;t reproduce it with 5.0.0, my NVidia driver is 361.42. Does anyone else experience similar behaviour?<p></p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Reagrds,<p></p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Lukasz<p></p></span></p>
<p class="MsoNormal"><span></span><span lang="EN-GB"><p></p></span></p>
<p class="MsoNormal">
<span lang="EN-GB">&#321;ukasz Paluszek</span><span lang="EN-GB"><p></p></span></p>
<p class="MsoNormal">
<span lang="EN-GB">Airbus Helicopters</span><span lang="EN-GB"><p></p></span></p>
<p class="MsoNormal">
<span lang="EN-GB">Aerodynamics Department (ETGA)</span><span lang="EN-GB"><p></p></span></p>
<p class="MsoNormal">
<span lang="EN-GB">86607 Donauw&ouml;rth</span><span lang="EN-GB"><p></p></span></p>
<p class="MsoNormal">
<span lang="EN-GB">Germany</span><span lang="EN-GB"><p></p></span></p>
<p class="MsoNormal">
<span lang="EN-GB">Tel.: +49 (90) 671 8231<p></p></span></p>
<p class="MsoNormal">
<span lang="EN-GB">Fax.: +49 (90)
</span><span lang="EN-GB">671 9122</span><span lang="EN-GB"><p></p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><a href="mailto:Lukasz.Paluszek <at> airbus.com"><span>Lukasz.Paluszek <at> airbus.com</span></a><p></p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><p>&nbsp;</p></span></p>
</div>
<p>AIRBUS HELICOPTERS DEUTSCHLAND GmbH</p>
<p>Sitz der Gesellschaft / Registered Office: Donauw&ouml;rth</p>
<p>Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508</p>
<p>Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury</p>
<p>Gesch&auml;ftsf&uuml;hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Sch&uuml;bel; Stefan Thom&eacute;</p>
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
</div>
kenichiro yoshimi | 24 Jun 12:37 2016
Picon

Question mark button launches a blank window with 5.1.0

Hi all,

I use ParaView 5.1.0 version installed from a binary file ParaView-5.1.0-Qt4-OpenGL2-Windows-64bit.exe. Unfortunately, this version's "ParaView Online Help" launched by clicking on Question mark button is not available because
the opened window is blank. This problem did not occur with 5.0.1 version.

Best Regards,
yoshimi kenichiro
<div><div dir="ltr">
<div>Hi all,</div>
<div><br></div>
<div>I use ParaView 5.1.0 version installed from a binary file ParaView-5.1.0-Qt4-OpenGL2-Windows-64bit.exe. Unfortunately, this version's "ParaView Online Help" launched by clicking on Question mark button is not available because</div>
<div>the opened window is blank. This problem did not occur with 5.0.1 version.</div>
<div><br></div>
<div>Best Regards,</div>
<div>yoshimi kenichiro</div>
</div></div>
Jim | 23 Jun 22:32 2016
Picon

Scalar scaling of glyphs causes unrecoverable error

I can import (raw binary) a 3D file (1178x1202x1000x1float), extract a 
subset and display it using sphere glyphs where the spheres are too 
large. However, when I set the scale mode to scalar and 1, the program 
displays nothing. The display area is just background color. I can't 
turn anything on or off. If I delete everything and then retry without 
the scaling, I still see nothing.

This looks like some sort of workspace corruption.  It looks like a bug 
to me.
Dean Neumann | 23 Jun 20:38 2016
Picon

SyntaxError reported parsing Python Calculator ?

on my paraview 5.0.1 64-bit on Windows-7
(from precompiled distribution at paraview.org)

What is the reason that I get the following errors when instantiating a Python Calculator filter on a single input of type UnstructuredGrid:

Traceback (most recent call last):

File "<string>", line 4, in <module>

File "C:\Program Files\ParaView\lib\paraview-5.0\site-packages\paraview\calculator.py", line 102, in execute

retVal = compute(inputs, expression, ns=variables)

File "C:\Program Files\ParaView\lib\paraview-5.0\site-packages\paraview\calculator.py", line 74, in compute

retVal = eval(expression, globals(), mylocals)

File "<string>", line 0

^

SyntaxError: unexpected EOF while parsing


What is being parsed?   The filter input is an internal paraview data set.  The input was active at the time the filter was instantiated.  The error occurs as soon as the filter is selected and added to the pipeline.
I can attach the input dataset if requested.
Thanks.

Dean Neumann

CEO,  Malaspina Labs Inc.

www.malaspina-labs.com


<div><div dir="ltr">on my paraview 5.0.1 64-bit on Windows-7<div>(from precompiled distribution at <a href="http://paraview.org">paraview.org</a>)</div>
<div><br></div>
<div>What is the reason that I get the following errors when instantiating a Python Calculator filter on a single input of type UnstructuredGrid:</div>
<div><br></div>
<div>
<p><span>Traceback (most recent call last):</span></p>
<p><span>  File "&lt;string&gt;", line 4, in &lt;module&gt;</span></p>
<p><span>  File "C:\Program Files\ParaView\lib\paraview-5.0\site-packages\paraview\calculator.py", line 102, in execute</span></p>
<p><span>    retVal = compute(inputs, expression, ns=variables)</span></p>
<p><span>  File "C:\Program Files\ParaView\lib\paraview-5.0\site-packages\paraview\calculator.py", line 74, in compute</span></p>
<p><span>    retVal = eval(expression, globals(), mylocals)</span></p>
<p><span>  File "&lt;string&gt;", line 0</span></p>
<p><span>    </span></p>
<p><span>    ^</span></p>
<p><span>SyntaxError: unexpected EOF while parsing</span></p>
<p><br></p>
</div>
<div>What is being parsed? &nbsp; The filter input is an internal paraview data set.&nbsp; The input was active at the time the filter was instantiated.&nbsp; The error occurs as soon as the filter is selected and added to the pipeline.</div>
<div>I can attach the input dataset if requested.</div>
<div>Thanks.</div>
<div>
<p>Dean Neumann</p>
<p>CEO, &nbsp;Malaspina Labs Inc.</p>
<p><a href="http://www.malaspina-labs.com">www.malaspina-labs.com</a></p>
<p><br></p>
</div>
</div></div>
Bertrand Gazanion | 23 Jun 16:10 2016

Find points within radius

On behalf of a colleague of mine working with ParaView 4.3.1

 

Hello,


I am using an algorithm doing calculation on points and their neighbours and I find the results of those points locators to be strange. To test it I made a simple algorithm counting how many neighbours each point has.
When I create a plane and set its x and y resolution to 100 each, all points should have the same number of neighbours except on the sides. However vtkPointLocator, vtkKdTreePointLocator and vtkOctreePointLocator do not find the same number of neighbours for each point.

Here is the algorithm that I use to get the number of neighbors each points has :
import vtk

pdi = self.GetInputDataObject(0,0)
nb_pts = pdi.GetNumberOfPoints()

# Point locator
loc = vtk.vtkPointLocator()
#loc = vtk.vtkOctreePointLocator()
#loc = vtk. vtkKdTreePointLocator()

loc.SetDataSet(pdi)
loc.BuildLocator()

pts = pdi.GetPoints()

neighbours = vtk.vtkTypeInt64Array()
neighbours.SetNumberOfComponents(1)
neighbours.SetNumberOfTuples(nb_pts)
neighbours.SetName('neighbours')

for k in range(nb_pts):

    xp = pdi.GetPoint(k)

    id_list = vtk.vtkIdList()

    loc.FindPointsWithinRadius(0.01,xp,id_list)
    loc.Update()

    N = id_list.GetNumberOfIds()
    neighbours.InsertTuple1(k,N)


self.GetOutput().GetPointData().AddArray(neighbours)

 

You will find attached sample picture describing the result I get with each point locator.

thank you very much

<div>

<div class="Section1">

<p class="MsoNormal"><span lang="EN-US">On behalf of a
colleague of mine working with ParaView 4.3.1<p></p></span></p>

<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoNormal"><span lang="EN-US">Hello,<p></p></span></p>

<p class="MsoNormal"><span lang="EN-US"><br>
I am using an algorithm doing calculation on points and their neighbours and I
find the results of those points locators to be strange. To test it I made a
simple algorithm counting how many neighbours each point has.<br>
When I create a plane and set its x and y resolution to 100 each, all points
should have the same number of neighbours except on the sides. However
vtkPointLocator, vtkKdTreePointLocator and vtkOctreePointLocator do not find the
same number of neighbours for each point.<br><br>
Here is the algorithm that I use to get the number of neighbors each points has
:<br></span><span lang="EN-US">import vtk<br><br>
pdi = self.GetInputDataObject(0,0)<br>
nb_pts = pdi.GetNumberOfPoints()<br><br>
# Point locator<br>
loc = vtk.vtkPointLocator()<br>
#loc = vtk.vtkOctreePointLocator()<br>
#loc = vtk. vtkKdTreePointLocator()<br><br>
loc.SetDataSet(pdi)<br>
loc.BuildLocator()<br><br>
pts = pdi.GetPoints()<br><br>
neighbours = vtk.vtkTypeInt64Array()<br>
neighbours.SetNumberOfComponents(1)<br>
neighbours.SetNumberOfTuples(nb_pts)<br>
neighbours.SetName('neighbours')<br><br>
for k in range(nb_pts):<br><br>
&nbsp;&nbsp;&nbsp; xp = pdi.GetPoint(k)<br><br>
&nbsp;&nbsp;&nbsp; id_list = vtk.vtkIdList()<br><br>
&nbsp;&nbsp;&nbsp; loc.FindPointsWithinRadius(0.01,xp,id_list)<br>
&nbsp;&nbsp;&nbsp; loc.Update()<br><br>
&nbsp;&nbsp;&nbsp; N = id_list.GetNumberOfIds()<br>
&nbsp;&nbsp;&nbsp; neighbours.InsertTuple1(k,N)<br><br><br>
self.GetOutput().GetPointData().AddArray(neighbours)</span><span lang="EN-US"><p></p></span></p>

<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoNormal"><span lang="EN-US">You will find attached sample picture
describing the result I get with each point locator.<br><br>
thank you very much<p></p></span></p>

</div>

</div>
Bertrand Gazanion | 23 Jun 16:13 2016

Re: Find points within radius

Forgot the pictures... Sorry for the spam.

Bertrand

 

De : Bertrand Gazanion [mailto:b.gazanion <at> gantha.com]
Envoyé : jeudi 23 juin 2016 16:11
À : 'paraview <at> paraview.org
'
Objet : Find points within radius

 

On behalf of a colleague of mine working with ParaView 4.3.1

 

Hello,


I am using an algorithm doing calculation on points and their neighbours and I find the results of those points locators to be strange. To test it I made a simple algorithm counting how many neighbours each point has.
When I create a plane and set its x and y resolution to 100 each, all points should have the same number of neighbours except on the sides. However vtkPointLocator, vtkKdTreePointLocator and vtkOctreePointLocator do not find the same number of neighbours for each point.

Here is the algorithm that I use to get the number of neighbors each points has :
import vtk

pdi = self.GetInputDataObject(0,0)
nb_pts = pdi.GetNumberOfPoints()

# Point locator
loc = vtk.vtkPointLocator()
#loc = vtk.vtkOctreePointLocator()
#loc = vtk. vtkKdTreePointLocator()

loc.SetDataSet(pdi)
loc.BuildLocator()

pts = pdi.GetPoints()

neighbours = vtk.vtkTypeInt64Array()
neighbours.SetNumberOfComponents(1)
neighbours.SetNumberOfTuples(nb_pts)
neighbours.SetName('neighbours')

for k in range(nb_pts):

    xp = pdi.GetPoint(k)

    id_list = vtk.vtkIdList()

    loc.FindPointsWithinRadius(0.01,xp,id_list)
    loc.Update()

    N = id_list.GetNumberOfIds()
    neighbours.InsertTuple1(k,N)


self.GetOutput().GetPointData().AddArray(neighbours)

 

You will find attached sample picture describing the result I get with each point locator.

thank you very much

<div>

<div class="Section1">

<p class="MsoNormal"><span lang="EN-US">Forgot the pictures...
Sorry for the spam.<p></p></span></p>

<p class="MsoNormal"><span lang="EN-US">Bertrand<p></p></span></p>

<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>

<div>

<div>

<p class="MsoNormal"><span lang="EN-US">De&nbsp;:</span><span lang="EN-US"> Bertrand Gazanion
[mailto:b.gazanion <at> gantha.com] <br>Envoy&eacute;&nbsp;: jeudi 23 juin 2016 16:11<br>&Agrave;&nbsp;: 'paraview <at> paraview.org</span><span>'<br>Objet&nbsp;: Find points within radius<p></p></span></p>

</div>

</div>

<p class="MsoNormal"><p>&nbsp;</p></p>

<p class="MsoNormal"><span lang="EN-US">On behalf of a
colleague of mine working with ParaView 4.3.1<p></p></span></p>

<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoNormal"><span lang="EN-US">Hello,<p></p></span></p>

<p class="MsoNormal"><span lang="EN-US"><br>
I am using an algorithm doing calculation on points and their neighbours and I
find the results of those points locators to be strange. To test it I made a
simple algorithm counting how many neighbours each point has.<br>
When I create a plane and set its x and y resolution to 100 each, all points
should have the same number of neighbours except on the sides. However
vtkPointLocator, vtkKdTreePointLocator and vtkOctreePointLocator do not find
the same number of neighbours for each point.<br><br>
Here is the algorithm that I use to get the number of neighbors each points has
:<br></span><span lang="EN-US">import vtk<br><br>
pdi = self.GetInputDataObject(0,0)<br>
nb_pts = pdi.GetNumberOfPoints()<br><br>
# Point locator<br>
loc = vtk.vtkPointLocator()<br>
#loc = vtk.vtkOctreePointLocator()<br>
#loc = vtk. vtkKdTreePointLocator()<br><br>
loc.SetDataSet(pdi)<br>
loc.BuildLocator()<br><br>
pts = pdi.GetPoints()<br><br>
neighbours = vtk.vtkTypeInt64Array()<br>
neighbours.SetNumberOfComponents(1)<br>
neighbours.SetNumberOfTuples(nb_pts)<br>
neighbours.SetName('neighbours')<br><br>
for k in range(nb_pts):<br><br>
&nbsp;&nbsp;&nbsp; xp = pdi.GetPoint(k)<br><br>
&nbsp;&nbsp;&nbsp; id_list = vtk.vtkIdList()<br><br>
&nbsp;&nbsp;&nbsp; loc.FindPointsWithinRadius(0.01,xp,id_list)<br>
&nbsp;&nbsp;&nbsp; loc.Update()<br><br>
&nbsp;&nbsp;&nbsp; N = id_list.GetNumberOfIds()<br>
&nbsp;&nbsp;&nbsp; neighbours.InsertTuple1(k,N)<br><br><br>
self.GetOutput().GetPointData().AddArray(neighbours)</span><span lang="EN-US"><p></p></span></p>

<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoNormal"><span lang="EN-US">You will find attached sample picture
describing the result I get with each point locator.<br><br>
thank you very much<p></p></span></p>

</div>

</div>

Gmane