Re: [Paraview] [vtk-developers] [vtk-users] OpenGL2 - GPU Volume Rendering performance

Dear Simon, Checking again. Wondering if you can provide some more detail on the binary you are using and whether or not without shading the rendering performance comparable to older version. Thanks, On Mon, Oct 26, 2015 at 3:12 PM, Aashish Chaudhary < aashish.chaudh...@kitware.com> wrote: >

Re: [Paraview] Saving a slice of data for later visualization

Hi Tim, I believe that the writer you want is the XML multiblock data writer -- XMLMultiBlockDataWriter(). The extension for that is .vtm. The reason for this is that a slice through a multiblock data set outputs a multiblock of polydata. You can use the Merge Blocks filter to reduce it to an

Re: [Paraview] Catalyst and adaptor: attaching new fields

Hi Michel, Yep, I saw your email that you figured out the issue. The Fortran API for Catalyst is probably a little bit clunky but it's difficult to tell who's using what for that so I didn't want to change anything there. Feel free to push some of that code back if you want to. The gitlab tools

Re: [Paraview] segmentation fault with netCDF when loading state file

David, Thanks for your investigation. I will be able to try this tomorrow. The original issue was with Paraview 4.3.1. We recently built the latest master, so I will be able to confirm whether it was fixed in between. Best, Ryan On Tue, Oct 27, 2015 at 10:23 AM, David Lonie

Re: [Paraview] Python array data into Paraview with simultaneous manipulation by Programmable Filter

> > Is there a way to conduct this procedure all in one fell swoop in the > Python Shell? Yes. You may want to write your Python script in a text file that you can run in ParaView's Python Shell via the "Run Script" button. > The main things I am curious about are 1) whether I can load a data

Re: [Paraview] Catalyst and adaptor: attaching new fields

Hi Andy, Thank you for your quick answer. You probably already read my previous answer about this issue. The problem was located in NeedToCreateGrid(...), which also clears any field data associated with an existing grid. The solution consists in calling simply this function only once for every

Re: [Paraview] Saving a slice of data for later visualization

I use this. Has worked for me fairly well. SaveData('fileName.vtm', proxy=Clip1, Writealltimestepsasfileseries=0, DataMode='Binary', HeaderType='UInt64', EncodeAppendedData=0, CompressorType='None') On Tue, Oct 27, 2015 at 7:55 AM Andy Bauer wrote: > Hi Tim, > > I

Re: [Paraview] Saving a slice of data for later visualization

Thanks guys, As always, it was a nice combination of user error and unexpected behavior. My slice origin was [1.0, 1.0, 0.0] and when I used the CSV writer, it happily wrote out data files for me so I assumed everything worked fine. But when I used any other writer, the slice didn't actually

Re: [Paraview] segmentation fault with netCDF when loading state file

Hi Ryan, I'm looking into this issue. I download the sample data you provided, and the state file loads and renders fine for me with the current (as of this morning) master branch of ParaView. What version of ParaView are you using? Can you test the latest master branch? It appears that whatever

Re: [Paraview] [vtk-developers] [vtk-users] OpenGL2 - GPU Volume Rendering performance

Hi Simon, This is helpful but just missing few more bits: 1) Did you try without the shading and see how the performance compares? 2) ParaView 4.4.0-193-gec96423 --> Where did you get this one from (ParaView download page or did you built yourself?) Also, so on your system the old mapper is

Re: [Paraview] [vtk-developers] [vtk-users] OpenGL2 - GPU Volume Rendering performance

Hello Aashish, Sorry for the late answer, I was busy this morning. Thanks for testing with the DataSet. I agree the performance is still quite good with the new backend, and I also get something like 15/20 fps on windows on an HD screen. But when compared to the old one, and in some condition