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

[Andy Bauer]

Can you share your plugin or at least the CMakeLists.txt for your plugin?
Have you tried with any other plugins that get packaged with ParaView to
see if they work?

If you're using Catalyst, I would suggest adding in the
PV_PLUGIN_IMPORT_INIT macros to the adaptor.

Andy


On Thu, Sep 26, 2013 at 3:40 PM, Hong Yi <hongyi at renci.org> wrote:

>   Thanks! I did put my plugin inside ParaView/Plugins in the same way as
> other Plugins, and enabled it when building ParaView superbuild on Titan.
> I can see the static lib for the Plugin is built in paraview-build/lib
> directory. And yes, I did use a plugin and load it via Tools|ManagePlugins when creating python
> coprocessing script. However, it looks like my plugin is not loaded
> automatically even though it is built by ParaView superbuild. Perhaps I
> should still follow the link
> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications but
> I am having some difficulty in following the info in the link to do what is
> suggested. Specifically, to what file should I insert two macros? It does
> not sound right to insert them into my custom plugin cxx file. Where should
> I add two macros to get my custom filter plugin to be loaded and wrapper
> into python module? I see "LoadPlugin" function defined in simple.py to
> call servermanager.LoadPlugin(filename, remote) which I am thinking perhaps
> should be called to load my plugin before my python coprocessing script is
> executed, but not sure whether this is the case or not.
>
>
>
> Thanks for any suggestions!
>
>
>  Hong
>
>
>
>
>
> *From:* David E DeMarle [mailto:dave.demarle at kitware.com]
> *Sent:* Thursday, September 26, 2013 1:28 PM
> *To:* Andy Bauer
> *Cc:* Hong Yi; paraview at paraview.org
> *Subject:* Re: [Paraview] My own filter as part of pipeline for
> coprocessing raises "name not defined" error
>
>
>
> Utkarsh pointed out that you still need to follow
> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications
>
> when the plugin is external to ParaView. If you put your plugin inside
> ParaView/Plugins, then it is done automatically.
>
>
>  David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
>
> On Thu, Sep 26, 2013 at 12:23 PM, David E DeMarle <
> dave.demarle at kitware.com> wrote:
>
> I think that information is out of date. I believe that is done
> automatically now.
>
>
>
> Otherwise Andy is right. Putting the filter inside a plugin a good way to
> go. The plugin infrastructure will make it so that when you provide the XML
> that describes your vtk class, ParaView's build system will automatically
> wrap it into a proxy and python class so that ParaView will be able to use
> it.
>
>
>
> Also, I recommend trying it on a local static build first. That way the
> build time will be less and development will be quicker. Once you can load
> you plugin locally, then you should only have to compile on titan once.
>
>
>
>
>  David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
>
> On Wed, Sep 25, 2013 at 10:34 PM, Andy Bauer <andy.bauer at kitware.com>
> wrote:
>
> 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
>
>
>
>
> _______________________________________________
> 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/20130927/e1055a56/attachment.htm>