[Paraview] Catalyst edition: no proxy for XMLPPolyDataWriter found

Thu Aug 21 11:47:18 EDT 2014

Hi Lars,

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?

Thanks,
Andy

On Tue, Aug 19, 2014 at 11:29 AM, Andy Bauer <andy.bauer at kitware.com> wrote:

> Hi Lars,
>
> 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.
>
> Thanks,
> Andy
>
>
> On Tue, Aug 19, 2014 at 11:23 AM, Lars Bilke <lars.bilke at ufz.de> wrote:
>
>> Hi Andy,
>>
>> thanks for your efforts!
>>
>> > When you tried pvpython and creating an XMLPPolyDataWriter, did you do
>> that with the pvpython that was built with your custom edition?
>>
>> Yes.
>>
>> > Is there a reason you're using the next branch for this?
>>
>> I also tried the master branch before.
>>
>> > 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.
>>
>> I just used the build location.
>>
>> > 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.
>>
>> 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.
>>
>> But until then I do not want to waste your time!
>>
>> Thanks a lot,
>> Lars
>>
>> >
>> > Regards,
>> > Andy
>> >
>> >
>> > On Tue, Aug 19, 2014 at 10:08 AM, Utkarsh Ayachit <
>> utkarsh.ayachit at kitware.com> wrote:
>> > Yup, this indeed points to the issue I was alluding do. Andy, feel
>> > free to stop by if you need more info.
>> >
>> > Utkarsh
>> >
>> > On Tue, Aug 19, 2014 at 3:02 AM, Lars Bilke <lars.bilke at ufz.de> wrote:
>> > > Hi Andy,
>> > >
>> > > 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.
>> > >
>> > > I am using the next branch from yesterday (79f7fdc).
>> > >
>> > > Best,
>> > > Lars
>> > >
>> > > Am 18.08.2014 um 20:39 schrieb Andy Bauer <andy.bauer at kitware.com>:
>> > >
>> > >> Hi Lars,
>> > >>
>> > >> When you run pvpython can you create the XMLPPolyDataWriter ?
>> > >>
>> > >> To test this just do:
>> > >> from paraview.simple import *
>> > >> w = XMLPPolyDataWriter()
>> > >>
>> > >> 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.
>> > >>
>> > >> Also, what version of ParaView are you using?
>> > >>
>> > >> Andy
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> On Mon, Aug 18, 2014 at 2:22 PM, Lars Bilke <lars.bilke at ufz.de>
>> wrote:
>> > >> Hi Andy,
>> > >>
>> > >> thanks for looking into it.
>> > >>
>> > >> 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.
>> > >>
>> > >> Best,
>> > >> Lars
>> > >>
>> > >> Am 18.08.2014 um 16:26 schrieb Andy Bauer <andy.bauer at kitware.com>:
>> > >>
>> > >> > Hi,
>> > >> >
>> > >> > 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?
>> > >> >
>> > >> > Regards,
>> > >> > Andy
>> > >> >
>> > >> >
>> > >> > On Mon, Aug 18, 2014 at 9:42 AM, Lars Bilke <lars.bilke at ufz.de>
>> wrote:
>> > >> > Dear ParaView users,
>> > >> > 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:
>> > >> >
>> > >> > Generic Warning: In
>> /Users/bilke/code/catalyst/fem-python/ParaViewCore/ClientServerCore/Core/vtkProcessModuleInitializePython.h,
>> line 254
>> > >> > Non-app bundle in install directory not supported
>> > >> >
>> > >> > Error: Could not import vtkCommonComputationalGeometryPython
>> > >> > Error: Could not import vtkRenderingCorePython
>> > >> > Error: Cannot import vtkPVServerManagerDefaultPython
>> > >> > Error: Cannot import vtkPVServerManagerRenderingPython
>> > >> > Error: Cannot import vtkPVAnimationPython
>> > >> > ERROR: In
>> /Users/bilke/code/catalyst/fem-python/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx,
>> line 565
>> > >> > vtkSIProxyDefinitionManager (0x7ff1c9527d70): No proxy that
>> matches: group=filters and proxy=XMLPPolyDataWriter were found.
>> > >> >
>> > >> > Traceback (most recent call last):
>> > >> >   File "<string>", line 2, in <module>
>> > >> >   File "Slice.py", line 73, in DoCoProcessing
>> > >> >   File
>> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py",
>> line 103, in UpdateProducers
>> > >> >     self.CreatePipeline(datadescription)
>> > >> >   File "Slice.py", line 29, in CreatePipeline
>> > >> >   File "Slice.py", line 17, in _CreatePipeline
>> > >> >   File "Slice.py", line 23, in Pipeline
>> > >> >   File
>> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py",
>> line 280, in CreateWriter
>> > >> >     return self.RegisterWriter(writer, filename, freq)
>> > >> >   File
>> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py",
>> line 234, in RegisterWriter
>> > >> >     writer, filename, freq)
>> > >> >   File
>> "/Users/bilke/code/catalyst/build-fem-python/lib/site-packages/paraview/coprocessing.py",
>> line 252, in WriterParametersProxy
>> > >> >     proxy.GetProperty("Input").SetInputConnection(
>> > >> > AttributeError: 'NoneType' object has no attribute ‚GetProperty'
>> > >> >
>> > >> >
>> > >> > Why is the writer proxy searched in the filters group? It should
>> be in the writers group right?
>> > >> >
>> > >> > Thanks for your help!
>> > >> >
>> > >> >
>> > >> >
>> > >> > _______________________________________________
>> > >> > 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://public.kitware.com/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://public.kitware.com/mailman/listinfo/paraview
>> >
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140821/df3dd428/attachment.html>