Re: [Paraview] bug in v4.1
Hello. I do not reproduce this bug using PV 410 64 bits Linux or PV 410 32 bits Windows, both from binary installers. Changing opacity through the slider is always OK with no pop up message. Richard. Version: Paraview 4.1.0 64-bit on Windows Recipe to reproduce the bug: (1) Sources-Cone; (2) Change opacity by moving the slider. A window will pop up, and it keeps printing message: ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLRenderer.cxx, line 1068 vtkOpenGLRenderer (0B2CDC50): failed after RenderPeel 1 OpenGL errors detected 0 : (1282) Invalid operation whenever it refreshes the display, even though the opacity is effectively changed. -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:richard.gre...@onera.fr http://www.onera.fr ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] bug in v4.1
Weiguang, I suspect depth peeing (which is for the most part critical for translucent rendering) doesn't work well with your graphics card/drivers. Try upgrading your drivers. If that doesn't help, you may have to disable depth peeling by unchecking the Enable Depth Peeling checkbox on the Edit | Settings dialog's Render View page. Note with depth peeling disabled, translucent polygons will not look correct. Utkarsh On Thu, Jan 30, 2014 at 9:24 AM, Weiguang Guan gu...@rhpcs.mcmaster.ca wrote: Version: Paraview 4.1.0 64-bit on Windows Recipe to reproduce the bug: (1) Sources-Cone; (2) Change opacity by moving the slider. A window will pop up, and it keeps printing message: ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLRenderer.cxx, line 1068 vtkOpenGLRenderer (0B2CDC50): failed after RenderPeel 1 OpenGL errors detected 0 : (1282) Invalid operation whenever it refreshes the display, even though the opacity is effectively changed. Weiguang ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] bug in v4.1
and if the driver update doesn't fix it for you it would be good to capture the issue in a bug report. so we have a better sense of which cards/drivers have issues with the algorithm. Burlen On 01/31/2014 05:18 AM, Utkarsh Ayachit wrote: Weiguang, I suspect depth peeing (which is for the most part critical for translucent rendering) doesn't work well with your graphics card/drivers. Try upgrading your drivers. If that doesn't help, you may have to disable depth peeling by unchecking the Enable Depth Peeling checkbox on the Edit | Settings dialog's Render View page. Note with depth peeling disabled, translucent polygons will not look correct. Utkarsh On Thu, Jan 30, 2014 at 9:24 AM, Weiguang Guan gu...@rhpcs.mcmaster.ca wrote: Version: Paraview 4.1.0 64-bit on Windows Recipe to reproduce the bug: (1) Sources-Cone; (2) Change opacity by moving the slider. A window will pop up, and it keeps printing message: ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLRenderer.cxx, line 1068 vtkOpenGLRenderer (0B2CDC50): failed after RenderPeel 1 OpenGL errors detected 0 : (1282) Invalid operation whenever it refreshes the display, even though the opacity is effectively changed. Weiguang ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Comparing results computed with 2 different meshes
Thanks a lot for the help. I think Merge Blocks Resample With Dataset Python Calculator (or Append Attributes Calculator) allows me to do what I originally asked for, although now I'm realizing the Python Calculator may not be enough to do the calculations I want. I had some questions regarding the Python Calculator and the Programmable Filter: 1. The data I'm looking at is from a transient simulation. If I wanted to standardize a parameter for each time step by dividing it by the standard deviation of the population for that time point, am I understanding correctly that I would either have to calculate the standard deviation first and then manually type in the number into the Python Calculator or use the Python Programmable Filter? 2. Additionally, I've been looking around and it seems the only way to perform a summing operation is to use the Programmable Filter. Is that correct? 3. Regarding both the Python Calculator or Programmable Filter, is there an easy way to tell which index corresponds to which input? I thought perhaps it had to do with just order you click the inputs in, but I'm not so sure about that. Thanks for your time, Evan On Thu, Jan 30, 2014 at 12:25 PM, Cory Quammen cory.quam...@kitware.comwrote: On Thu, Jan 30, 2014 at 2:31 PM, Evan Kao tos...@gmail.com wrote: Hi Cory, Thanks for the suggestion. Resample With Dataset solves the problem of matching up the Point IDs, but only passes data from the Input (which I guess makes sense given its purpose), so I think regardless of what I rename the arrays, the data will always be from only one of the meshes meaning I can't use Calculator to compare the data. How about using Append Attributes to combine the arrays of Resample With Dataset and the Source? I think my main obstacle is the data type. Paraview reads in Ensight data as a Multi-Block data set, but neither Append Datasets nor the Python Calculator seem to work on that data type. Is there a simple way to convert them into a format that can be read by those filters? You can use Merge Blocks to combine all the blocks in a Multi-Block data set to an unstructured grid. Best, Cory Thanks, Evan On Thu, Jan 30, 2014 at 6:10 AM, Cory Quammen cory.quam...@kitware.com wrote: Evan, You might want to take a look at the Resample With Dataset filter. One of your meshes would be the Input and one would be the Source. What this filter will do is sample the data values in the Input mesh at the locations of points in the Source. If I understand the setup of your meshes, this should essentially take care of the problem where your point IDs are not the same. The result will be a single mesh with two data arrays that you can then compare point by point. You might run into a problem if both meshes use the same name for the point array from which you want to get values (one will clobber the other). You can take care of that by using the Calculator to rename one of the mesh's arrays, then using the result of the calculator as the Input or Source. Hope that helps, Cory On Mon, Jan 27, 2014 at 4:18 PM, Evan Kao tos...@gmail.com wrote: Hello all, I'm trying to compare the results of 2 CFD simulations (which are imported into Paraview as Ensight data) point-by-point but I'm having trouble figuring out how to even combine the data into a single Pipeline object so that I can do some simple calculations with the Calculator Filter. I'd appreciate it if anyone could let me know if what I'm trying to do is natively possible in Paraview, and if not, provide some suggestions on how to approach it. What might complicate the process is that the results were obtained using two different meshes (in fact, it's a mesh comparison test). The points I want to look at are the same for both meshes, but the point IDs are different. So what I'd like to do in summary is: 1) Is there a way to extract and sort the data in a way such that the point IDs are the same for both meshes? 2) Is there a way to convert/manipulate the data into a single Pipeline object for comparison? Or to compare the results of different Pipeline objects? I've tried various combinations of filters like AppendDatasets, GroupDatasets, and MergeBlocks with little success. Thanks, Evan ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
[Paraview] Get Values of CSV sources with Programmable Filter
Hi all, I'm using PV 4.1.0 and trying to get values of CSV sources with Programmable Filter. It's better to get them as numpy.array. How can I code it? Magician ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
