[Paraview] bug with slice filter object inspector panel when loading a state with multiple offsets

I've put a bug in mantis with a patch to resolve the issue - http://www.paraview.org/Bug/view.php?id=12252http://www.itk.org/Bug/view.php?id=12252 Regards, Paul ___ Powered by www.kitware.com Visit other Kitware open-source projects at

[Paraview] GetPolyData on a BoxWidget

Dear Users, I usually clip meshes using the clip filter and a box, or a plane. I would be interested in exporting the clipping box data, not the clippedData, but the box itself. I also would like to get the thickness of the box, eg. distance between two handles. I know that VTK allows to do

Re: [Paraview] Surface LIC memory usage

I doubt it's part of the design so to speak :). My suspicion is some OpenGL buffers are not being released or something of that nature. I'll try to track it down. Utkarsh On Mon, Jun 6, 2011 at 9:28 PM, Burlen Loring blor...@lbl.gov wrote: Hi, I am seeing some pretty astounding memory usage

Re: [Paraview] GetPolyData on a BoxWidget

What I'd do is subclass vtkPVClipDataset (the filter paraview uses for Clip). Make the subclass a two output-port filter (by calling vtkAlgorithm::SetNumberOfOutputPorts(2)) and producing the polydata matching the implicit function specified as the clipping function on the second output port. Now

Re: [Paraview] GetPolyData on a BoxWidget

Hi Utkarsh, Thanks for your reply! I'm used to subclass ITK and VTK classes, but I install Paraview using the binaries not yet from the sources. If I understand you, this could be very easily done subclassing the PVClipDataSet. What about displaying or saving the second output? How can I

Re: [Paraview] GetPolyData on a BoxWidget

Once you make the VTK filter have two output ports, paraview will automatically detect it and you will be able to see both output ports in the pipeline browser. On Tue, Jun 7, 2011 at 9:03 AM, Laurent Paul l.p...@uclouvain.be wrote: Hi Utkarsh, Thanks for your reply! I'm used to subclass ITK

Re: [Paraview] vtkPVPostFilter bug question

I suspect that something is wrong on your side. My reasoning: - vtkPVPostFilter already copies all of the meta-data (whole extent and extent translator) needed in the RequestInformation pass - There should be no need to copy this meta-data in RequestData pass, which is what CopyInformation()

Re: [Paraview] Change the font in the Line Chart/XY plot

I don't see the patch, I can take a look at the patch if you upload it. Now the vtkLegend object is exposed it should be relatively simple. Marcus On Tue, Jun 7, 2011 at 5:45 AM, Paul Edwards paul.m.edwa...@gmail.com wrote: BTW here is link to page on mantis - 

Re: [Paraview] GetPolyData on a BoxWidget

I'm currently building paraview from sources... I had errors caused by Qt. fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64' in QtGUI4.dll and in QtCore4.dll My computer runs Windows 7 64 bits. I have downloaded and installed (not built) Qt4.7.3 Vs2008. My

Re: [Paraview] GetPolyData on a BoxWidget

You are using 64-bit Qt while building a 32-bit binary. Make sure you re-configure ParaView (using cmake) and pick 64bit compiler. When clipping with box, you'd get a vtkPVBox as the implicit function. You can get the box dimensions from it and the construct your own polydata or use

Re: [Paraview] Iso volume

Nope (it indeed internally uses clip-by scalar for point scalars) except that it applies two clip-by-scalars and can also handle cell data (by internally using threshold filter) Utkarsh On Mon, Jun 6, 2011 at 10:48 PM, Mohammad Mirzadeh mirza...@gmail.com wrote: hi Guys, Just intalled paraview

Re: [Paraview] Shapefiles to Paraview (or VTK) format

Sure. I will attach the reader header and source in my next email (by the end of the day). Thanks, On Tue, Jun 7, 2011 at 4:27 AM, Takuya OSHIMA osh...@eng.niigata-u.ac.jp wrote: Hi Aashish, Would be great for me too if your reader may be shared (thus we have more options for importing

Re: [Paraview] Concept: A world without the Apply button

One thing that strikes me about this proposal, is that it relies a lot on VTK readers/filters providing the necessary meta data, particularly about fields. For example, the elevation filter would have to report in its meta data that it will be adding a scalar field named Elevation. That sounds

Re: [Paraview] Concept: A world without the Apply button

All-- Technical reasons aside, my own simulation efforts (software that relies on ParaView for post-processing) span a great variety of solid and structural mechanics applications. The software is not a single-formulation, single-solution, one-off problem solver. Put briefly, I find the

Re: [Paraview] Concept: A world without the Apply button

Sam, Please note that this proposal does not preclude the user from choosing which array to load from the reader's properties panel. That indeed will be supported. This proposal in fact allows you go back the reader change it's array selection, and then go the properties panel for a contour

Re: [Paraview] Concept: A world without the Apply button

Is there a way to mitigate the issues with the meta data mismatching what is actually generated?  Perhaps there could be a check to make sure that the data generated matches the meta data previously reported and issue a warning if there are any mismatches.  This would not solve the problem per