<div dir="ltr"><div>Hi Lars,<br><br></div>I was testing this out a bit more and am getting confused again. Can you send me a copy of your custom edition with everything in it as well as the command you used to create the Catalyst source? <br>
<br>Thanks,<br>Andy<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 19, 2014 at 11:29 AM, Andy Bauer <span dir="ltr"><<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi Lars,<br><br></div>Thanks for sticking with this. The Catalyst editions are a bit tricky and we haven't had enough people testing them out so there's a lot of space for mistakes so it takes me a bit of effort to try and figure out how to narrow down where the problem could be. I think I have enough information now to proceed. I should be able to spend a bit of time on this today.<br>
<br></div>Thanks,<br></div>Andy<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 19, 2014 at 11:23 AM, Lars Bilke <span dir="ltr"><<a href="mailto:lars.bilke@ufz.de" target="_blank">lars.bilke@ufz.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Andy,<br>
<br>
thanks for your efforts!<br>
<div><br>
> When you tried pvpython and creating an XMLPPolyDataWriter, did you do that with the pvpython that was built with your custom edition?<br>
<br>
</div>Yes.<br>
<div><br>
> Is there a reason you're using the next branch for this?<br>
<br>
</div>I also tried the master branch before.<br>
<div><br>
> Another question, are you linking your code to a developer installed location of Catalyst or the build location of Catalyst? If you're using the developer installed location you should try and see if you can use the build location to see if it works there.<br>
<br>
</div>I just used the build location.<br>
<div><br>
> For a full ParaView build and install with developer information I was able to successfully run a Catalyst example that was linked to the installed location but maybe there's something missing with the Catalyst editions that don't install everything as needed.<br>
<br>
</div>Yes I know. It is also ok for me do use the full ParaView build. But maybe in the future when I finished the Catalyst stuff it would be nice for other developers to just have to build a small subset of ParaView.<br>
<br>
But until then I do not want to waste your time!<br>
<br>
Thanks a lot,<br>
Lars<br>
<div><div><br>
><br>
> Regards,<br>
> Andy<br>
><br>
><br>
> On Tue, Aug 19, 2014 at 10:08 AM, Utkarsh Ayachit <<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>> wrote:<br>
> Yup, this indeed points to the issue I was alluding do. Andy, feel<br>
> free to stop by if you need more info.<br>
><br>
> Utkarsh<br>
><br>
> On Tue, Aug 19, 2014 at 3:02 AM, Lars Bilke <<a href="mailto:lars.bilke@ufz.de" target="_blank">lars.bilke@ufz.de</a>> wrote:<br>
> > Hi Andy,<br>
> ><br>
> > I can create XMLPPolyDataWriter in pvpython without errors. With a normal ParaView build as well as with the Rendering-Base-Python edition it works but I wanted to have a small custom edition.<br>
> ><br>
> > I am using the next branch from yesterday (79f7fdc).<br>
> ><br>
> > Best,<br>
> > Lars<br>
> ><br>
> > Am 18.08.2014 um 20:39 schrieb Andy Bauer <<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>>:<br>
> ><br>
> >> Hi Lars,<br>
> >><br>
> >> When you run pvpython can you create the XMLPPolyDataWriter ?<br>
> >><br>
> >> To test this just do:<br>
> >> from paraview.simple import *<br>
> >> w = XMLPPolyDataWriter()<br>
> >><br>
> >> The safest way to test this stuff is to try it with a "normal" ParaView build with MPI and Python enabled. If you can link and run against this then it has to do with your edition which you can then check on issues by using pvpython. We don't do a lot of testing on the generated Catalyst editions yet so it's possible that something snuck in to them.<br>
> >><br>
> >> Also, what version of ParaView are you using?<br>
> >><br>
> >> Andy<br>
> >><br>
> >><br>
> >><br>
> >><br>
> >> On Mon, Aug 18, 2014 at 2:22 PM, Lars Bilke <<a href="mailto:lars.bilke@ufz.de" target="_blank">lars.bilke@ufz.de</a>> wrote:<br>
> >> Hi Andy,<br>
> >><br>
> >> thanks for looking into it.<br>
> >><br>
> >> I further noticed that the same error occurs when I use the official Extras-edition (plus Enable-Python). When using the Rendering-Base-Python edition everything works.<br>
> >><br>
> >> Best,<br>
> >> Lars<br>
> >><br>
> >> Am 18.08.2014 um 16:26 schrieb Andy Bauer <<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>>:<br>
> >><br>
> >> > Hi,<br>
> >> ><br>
> >> > I will look at this a bit more but I'm wondering if you tried doing the same with just a full ParaView build and if you did, how did it work?<br>
> >> ><br>
> >> > Regards,<br>
> >> > Andy<br>
> >> ><br>
> >> ><br>
> >> > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke <<a href="mailto:lars.bilke@ufz.de" target="_blank">lars.bilke@ufz.de</a>> wrote:<br>
> >> > Dear ParaView users,<br>
> >> > I have created a custom catalyst edition (see attached manifest). It is basically the same as the Extras-edition with some parts removed. I have integrated a catalyst adaptor into my application. Everything builds and links fine. Now I want to use a python coprocessing pipeline (see attached script). When running I get the following output:<br>
> >> ><br>
> >> > Generic Warning: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h, line 254<br>
> >> > Non-app bundle in install directory not supported<br>
> >> ><br>
> >> > Error: Could not import vtkCommonComputationalGeometryPython<br>
> >> > Error: Could not import vtkRenderingCorePython<br>
> >> > Error: Cannot import vtkPVServerManagerDefaultPython<br>
> >> > Error: Cannot import vtkPVServerManagerRenderingPython<br>
> >> > Error: Cannot import vtkPVAnimationPython<br>
> >> > ERROR: In /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, line 565<br>
> >> > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that matches: group=filters and proxy=XMLPPolyDataWriter were found.<br>
> >> ><br>
> >> > Traceback (most recent call last):<br>
> >> > File "<string>", line 2, in <module><br>
> >> > File "Slice.py", line 73, in DoCoProcessing<br>
> >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 103, in UpdateProducers<br>
> >> > self.CreatePipeline(datadescription)<br>
> >> > File "Slice.py", line 29, in CreatePipeline<br>
> >> > File "Slice.py", line 17, in _CreatePipeline<br>
> >> > File "Slice.py", line 23, in Pipeline<br>
> >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 280, in CreateWriter<br>
> >> > return self.RegisterWriter(writer, filename, freq)<br>
> >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 234, in RegisterWriter<br>
> >> > writer, filename, freq)<br>
> >> > File "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py", line 252, in WriterParametersProxy<br>
> >> > proxy.GetProperty("Input").SetInputConnection(<br>
> >> > AttributeError: 'NoneType' object has no attribute ‚GetProperty'<br>
> >> ><br>
> >> ><br>
> >> > Why is the writer proxy searched in the filters group? It should be in the writers group right?<br>
> >> ><br>
> >> > Thanks for your help!<br>
> >> ><br>
> >> ><br>
> >> ><br>
> >> > _______________________________________________<br>
> >> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
> >> ><br>
> >> > Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
> >> ><br>
> >> > Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
> >> ><br>
> >> > Follow this link to subscribe/unsubscribe:<br>
> >> > <a href="http://public.kitware.com/mailman/listinfo/paraview" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><br>
> >> ><br>
> >> ><br>
> >><br>
> >><br>
> ><br>
> > _______________________________________________<br>
> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
> ><br>
> > Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
> ><br>
> > Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
> ><br>
> > Follow this link to subscribe/unsubscribe:<br>
> > <a href="http://public.kitware.com/mailman/listinfo/paraview" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><br>
><br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>