Cory,
Wow, that’s exactly what I need – now I just need to get some time to
re-implement my filters using this!
Thanks again
Dennis
From: Cory Quammen [mailto:cory.quam...@kitware.com]
Sent: Thursday, September 24, 2015 11:07 AM
To: Dennis Conklin
Cc: Paraview (paraview@paraview.org)
Subject
One more question – the original article says that
Alternatively, the Script properties can be hidden completely from the
properties panel.
How is this accomplished?
Thanks again
Dennis
From: Dennis Conklin
Sent: Thursday, September 24, 2015 12:20 PM
To: 'Cory Quammen'
Cc: Paraview (paraview
Dennis,
Great! I'm glad it's what you are looking for.
You can hide any property by editing the XML file. In the property element,
add an attribute called "panel_visibility" and set this to "never". This
will hide the property from view. You can also set it to "advanced" so that
it shows up only
Cory,
I’m pretending to be a real programmer, so my Programmable Filter script looks
something like this:
Def sub1:
Do some stuff
Return var
Def sub2(var):
Do some stuff
Return newVar
Def sub3(var):
Do some stuff
Return newVar
Def RequestData():
X=sub1()
Y=sub2
Hi Dennis,
The converter evaluates your Python script and then uses some Python
reflection features to extract the code in your RequestData function. But
it does this only for the RequestData function (as well as a
RequestInformation and RequestUpdateExtent functions, but these aren't
always neede
Cory,
I had just thought of this and tried it (successfully) about when your note
came in.
I hate to quibble, but I would suggest that in the typeMap in the
python_filter_generator.py vtkMultiBlockDataSet is listed as
vtkMultiblockDataSet and I had to figure this out and use a small ‘b’ before
All,
So, I can load the xml plugin but the filter is grayed out on the Filters menu.
I have tried removing the InputDataSetType so that it should accept any type
of input, but still gray. I am not sure how Paraview decides which filters
are inappropriate (greyed-out) so I don’t have many id
Hi Dennis,
What is your input to the Test Filter? I can apply it to a Sphere source
input.
For your custom filter, the XML file should contain the following:
This tells ParaView to enable your filt
Cory,
I applied to bake.e, which is a vtkMultiblockDataSet (I believe!).
I tried both “B” and “b” without success.
I just now changed the input_type to vtkDataSet, which I guessed was more
general and now it works. I have no idea why vtkMultiblockDataSet didn’t
work, but I have a workaround.
Oops, copying the list in to my last response.
On Thu, Sep 24, 2015 at 4:53 PM, Cory Quammen
wrote:
>
>
> On Thu, Sep 24, 2015 at 4:47 PM, Dennis Conklin <
> dennis_conk...@goodyear.com> wrote:
>
>> Cory,
>>
>>
>>
>> I applied to bake.e, which is a vtkMultiblockDataSet (I believe!).
>>
>
> Yes.
All,
It appears that the help or Documentation provided in the xml file is not
accessible from Paraview. I could not access it for the original files from
the blog, or from mine. Perhaps I just don’t understand the proper way to
access it, but all I got with clicking on ? or hitting F1 was t
Hi Dennis,
The documentation that is available in the online help is generated at
build time from the sources/filters/readers that ship with ParaView. The
same is true for binary pluginsthat are built into a shared library.
Unfortunately documentation from purely XML plugins is not added to the
o
All,
OK, I admit it – I’m greedy – I want it all.
As I have written these customized filters, one thing that I have realized is
that memory utilization is not optimum for my setup. I run on a single
machine, not a cluster, so I am concerned about memory usage.
I have possibly a radical idea
13 matches
Mail list logo
