Re: [Paraview] [EXTERNAL] Re: Material Interface Filter

It sounds like it. I believe that the user would have to use the extract surface filter first though. On Tue, Jan 23, 2018 at 2:00 PM, Scott, W Alan wrote: > Andy, > Wouldn't the upcoming volume filter calculate the volume of fragments > coming from the Connectivity filter?

Re: [Paraview] [EXTERNAL] Re: Material Interface Filter

Andy, Wouldn't the upcoming volume filter calculate the volume of fragments coming from the Connectivity filter? Alan > -Original Message- > From: Cory Quammen [mailto:cory.quam...@kitware.com] > Sent: Monday, January 22, 2018 9:29 PM > To: Scott, W Alan > Cc:

Re: [Paraview] [EXTERNAL] Re: Material Interface Filter

As a happy coincidence, Will Schroeder just posted a merge request for a VTK filter that computes the volumes of connected regions in a poly data and stores the volumes in field data: https://gitlab.kitware.com/vtk/vtk/merge_requests/3825. We could expose this in ParaView once it lands in VTK.

Re: [Paraview] [EXTERNAL] Re: Material Interface Filter

On Wed, Jan 17, 2018 at 9:42 PM, Scott, W Alan wrote: > Thanks Andy! Although I will take a round about method, I would love a real > solution. > > > > Cory? Thoughts? > > > > Alan > > > > From: Andy Bauer [mailto:andy.ba...@kitware.com] > Sent: Wednesday, January 17, 2018

Re: [Paraview] [EXTERNAL] Re: Material Interface Filter

Thanks Andy! Although I will take a round about method, I would love a real solution. Cory? Thoughts? Alan From: Andy Bauer [mailto:andy.ba...@kitware.com] Sent: Wednesday, January 17, 2018 9:24 AM To: Scott, W Alan ; Quammen, Cory (External Contacts)

Re: [Paraview] [EXTERNAL] Re: Material Interface Filter

Bucky, I believe that the problem is that - as you suggest below - the material interface filter only accepts down converted unsigned chars. In my mind, this is a bug/feature hole. Either, 1) the Material Interface Filter should accept down converted unsigned chars or default variables, 2) a