[Paraview] My own filter as part of pipeline for coprocessing raises "name not defined" error

[Andy Bauer]

Did you use a plugin to add in your custom filter when creating the Python
co-processing script? I'm not sure how plugins are "loaded" for static
builds but you may want to look at
http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications.
If that doesn't work, we'll have to figure out some other way to do it.

Andy






On Wed, Sep 25, 2013 at 9:16 PM, Hong Yi <hongyi at renci.org> wrote:

>  Hello,
>
> I set up a pipeline that used a custom filter I developed and exported it
> as a python script for coprocessing. I have made sure the static library
> for my custom filter is built and available in paraview-build/lib
> directory, and I have also linked this custom filter static library along
> with Catalyst libs to the simulation code for coprocessing. However, when I
> run the simulation linked with ParaView coprocessing for in-situ
> visualization, I got "NameError: name 'MyCustomizedFilterName' is not
> defined" error when the line of my customized filter in my python
> coprocessing script is read in for pipeline coprocessing. What should I do
> to get my custom filter wrapped in python so that it can be recognized and
> used as part of the python pipeline script for coprocessing? Any advice and
> suggestions are very much appreciated.
>
> Thanks,
>
> Hong
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130925/3553ef93/attachment.htm>