Hi,
I would like to define a custom programmable filter to work with
MultiBlockDatasets. In that filter, I need to access to the name of each
block being processed. By name, I mean the information given in the
InformationData Hierarchy tree.
Could you explain me how to access to that information
[Paraview] XML plugin syntax for FileChooser.
Hi,
I would like to create a custom programmable python filter to write some
calculation results in a file.
I’ve tried to use the following XML plugin syntax to define a FileChooser
button and help the user select the path of the output file :
PM, Utkarsh Ayachit <
> utkarsh.ayac...@kitware.com> wrote:
>
>> Doh! I forgot that the number of ports need to set in the constructor of
>> the vtkAlgorithm subclass. Grr...let me see if there's a workaround. I'll
>> get back to you on it.
>>
>> On F
.GetInputDataObject(1, 0)
>
> Here there's no confusion which data is on which input port.
>
> Hope that helps,
> Utkarsh
>
>
> On Fri, Jul 15, 2016 at 7:44 AM, Dennis Conklin
> <dennis_conk...@goodyear.com> wrote:
> > LB,
> >
> >
> >
> > Yes,
Hi Cory,
As I understand, the Python Programmable filter can accept only one input
port, but this port can accept multiple connections. The order of multiple
connections on the same port cannot be controlled by the user.
My filter need two input datasets, but they are not commutable.
The user
Hi,
I would like to make some custom python plugins for ParaView.
I've made one based on a PythonProgrammableFilter with the help of the
Python Filter Generator Script
(https://gitlab.kitware.com/paraview/paraview/snippets/5).
It's working pretty well, but it seems that the
Hi,
I've used the Find Data dialog to select a region of interest by filtering
point data with the "is one of" criterion.
I would like to extract the corresponding region, but clicking on "extract
selection" does not extract the corresponding cells.
Is there a way to select cells linked to
Hi,
When I try to open XDMF files, ParaView crashes when I use the XDMF3 Reader.
It seems to load fine with the classical "XDMF Reader".
I've had this issue with the following version of ParaView :
- Paraview 5.4.1 under Windows 7
- Paraview 5.0.1 under Linux 64
I've open a ticket in the bug
