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

[David E DeMarle]

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/20130926/409d2707/attachment-0001.htm>