<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
span.hoenzb
{}
span.EmailStyle18
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.SpellE
{}
.MsoChpDefault
{font-family:"Calibri","sans-serif"}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
-->
</style><style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" style="" lang="EN-US" link="blue" vlink="purple">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Thanks! I did put my plugin inside
<span class="SpellE">ParaView</span>/Plugins in the same way as other Plugins, and enabled it when building
<span class="SpellE">ParaView</span> <span class="SpellE">superbuild</span> on Titan. I can see the static lib for the Plugin is built in
<span class="SpellE">paraview</span>-build/lib directory. And yes, I did use a plugin and load it via
<span class="SpellE">Tools|Manage</span> Plugins when creating python <span class="SpellE">
coprocessing</span> script. However, it looks like my plugin is not loaded automatically even though it is built by
<span class="SpellE">ParaView</span> <span class="SpellE">superbuild</span>. Perhaps I should still follow the link
</span><a href="http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications" target="_blank">http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications</a>
<span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">
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. <br>
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Thanks for any suggestions!
<br>
</span></p>
<p class="MsoNormal"><br>
<span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Hong<br>
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"><span style=""> </span></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><a name="_MailOriginal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b></a><span style=""><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> David E DeMarle [mailto:dave.demarle@kitware.com]
<br>
<b>Sent:</b> Thursday, September 26, 2013 1:28 PM<br>
<b>To:</b> Andy Bauer<br>
<b>Cc:</b> Hong Yi; paraview@paraview.org<br>
<b>Subject:</b> Re: [Paraview] My own filter as part of pipeline for coprocessing raises "name not defined" error</span></span></p>
<p class="MsoNormal"><span style=""> </span></p>
<div>
<p class="MsoNormal"><span style="">Utkarsh pointed out that you still need to follow </span><a href="http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications" target="_blank"><span style="">http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications</span><span style=""></span></a><span style=""></span></p>
<div>
<p class="MsoNormal"><span style="">when the plugin is external to ParaView. If you put your plugin inside ParaView/Plugins, then it is done automatically.</span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style=""><br style="" clear="all">
</span></p>
<div>
<p class="MsoNormal"><span style="">David E DeMarle<br>
Kitware, Inc.<br>
R&D Engineer<br>
21 Corporate Drive<br>
Clifton Park, NY 12065-8662<br>
Phone: 518-881-4909</span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style=""> </span></p>
<div>
<p class="MsoNormal"><span style="">On Thu, Sep 26, 2013 at 12:23 PM, David E DeMarle <</span><a href="mailto:dave.demarle@kitware.com" target="_blank"><span style="">dave.demarle@kitware.com</span><span style=""></span></a><span style="">> wrote:</span></p>
<div>
<p class="MsoNormal"><span style="">I think that information is out of date. I believe that is done automatically now.</span></p>
<div>
<p class="MsoNormal"><span style=""> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="">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.</span></p>
</div>
<div>
<p class="MsoNormal"><span style=""> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="">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.</span></p>
</div>
<div>
<p class="MsoNormal"><span style=""><span style="color:#888888"> </span></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style=""><span style="color:#888888"><br style="" clear="all">
</span><span class="hoenzb"></span></span></p>
<div>
<p class="MsoNormal"><span style=""><span style="color:#888888">David E DeMarle<br>
Kitware, Inc.<br>
R&D Engineer<br>
21 Corporate Drive<br>
Clifton Park, NY 12065-8662<br>
Phone: </span></span><a href="tel:518-881-4909" target="_blank"><span style="">518-881-4909</span><span style=""></span></a><span style=""></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style=""> </span></p>
<div>
<p class="MsoNormal"><span style="">On Wed, Sep 25, 2013 at 10:34 PM, Andy Bauer <</span><a href="mailto:andy.bauer@kitware.com" target="_blank"><span style="">andy.bauer@kitware.com</span><span style=""></span></a><span style="">> wrote:</span></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="">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
</span><a href="http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications" target="_blank"><span style="">http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Plugins_in_Static_Applications</span><span style=""></span></a><span style="">.
If that doesn't work, we'll have to figure out some other way to do it.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="">Andy</span></p>
</div>
<div>
<p class="MsoNormal"><span style=""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style=""> </span></p>
</div>
<p class="MsoNormal"><span style=""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style=""> </span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="">On Wed, Sep 25, 2013 at 9:16 PM, Hong Yi <</span><a href="mailto:hongyi@renci.org" target="_blank"><span style="">hongyi@renci.org</span><span style=""></span></a><span style="">> wrote:</span></p>
</div>
</div>
<blockquote style="border:none; border-left:solid #CCCCCC 1.0pt; padding:0in 0in 0in 6.0pt; margin-left:4.8pt; margin-right:0in">
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style=""><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">Hello,<br>
<br>
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.<br>
<br>
Thanks,<br>
<br>
Hong<br style="">
<br style="">
</span></span></p>
</div>
</div>
<p class="MsoNormal"><span style=""> </span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="">_______________________________________________<br>
Powered by </span><a href="http://www.kitware.com" target="_blank"><span style="">www.kitware.com</span><span style=""></span></a><span style=""><br>
<br>
Visit other Kitware open-source projects at </span><a href="http://www.kitware.com/opensource/opensource.html" target="_blank"><span style="">http://www.kitware.com/opensource/opensource.html</span><span style=""></span></a><span style=""><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: </span><a href="http://paraview.org/Wiki/ParaView" target="_blank"><span style="">http://paraview.org/Wiki/ParaView</span><span style=""></span></a><span style=""><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
</span><a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank"><span style="">http://www.paraview.org/mailman/listinfo/paraview</span><span style=""></span></a><span style=""></span></p>
</blockquote>
</div>
<p class="MsoNormal"><span style=""> </span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style=""><br>
_______________________________________________<br>
Powered by </span><a href="http://www.kitware.com" target="_blank"><span style="">www.kitware.com</span><span style=""></span></a><span style=""><br>
<br>
Visit other Kitware open-source projects at </span><a href="http://www.kitware.com/opensource/opensource.html" target="_blank"><span style="">http://www.kitware.com/opensource/opensource.html</span><span style=""></span></a><span style=""><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: </span><a href="http://paraview.org/Wiki/ParaView" target="_blank"><span style="">http://paraview.org/Wiki/ParaView</span><span style=""></span></a><span style=""><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
</span><a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank"><span style="">http://www.paraview.org/mailman/listinfo/paraview</span><span style=""></span></a><span style=""></span></p>
</div>
<p class="MsoNormal"><span style=""> </span></p>
</div>
</div>
</div>
</div>
<span style=""></span>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</body>
</html>