Re: [Paraview] unknown properties returned by ListProperties?

Grothausmann, Roman Dr. Wed, 28 Mar 2018 01:37:07 -0700

Dear Cory,

On 27/03/18 16:18, Cory Quammen wrote:

I'm sorry I haven't had a chance to look at this further. Have you made any moreprogress on this? I apologize for thinking it would be easy to hack ParaView tobetter support loading multiple state files - it appears to be more difficultthan expected after all.

Many thanks for your reply. No, problem at all. I am very thankful for Yoursupport. As you give it for free, I've no expectation on response time or anyhelp at all.Should I open a gitlab issue concerning the problem that the setting ofrepresentation properties does not seem to have any effect or is my code missingsomething obvious? I must admit that this is needing internals of PV that werenot covered by the PV course I attended some years ago.


Best
Roman

On Tue, Mar 20, 2018 at 12:13 PM, Grothausmann, Roman Dr.<grothausmann.ro...@mh-hannover.de <mailto:grothausmann.ro...@mh-hannover.de>>wrote:


    Many thanks Cory for your feedback. Not adding empty (None) properties did
    not help
    (http://github.com/romangrothausmann/ParaView_scripts/commit/d3af645dd1af2a
    
<http://github.com/romangrothausmann/ParaView_scripts/commit/d3af645dd1af2a>).
    Anyway, "ForceUseCache" has a vector of value 0 so it seems to me the actual
    problem still is that ListProperties() returns properties that are not part
    of the specific object that is calling ListProperties(). E.g. help(repr)
    does not list a property called "ForceUseCache" but e.g. "Visibility"

    So I decided to only restore the property "Visibility" for a start:
    http://github.com/romangrothausmann/ParaView_scripts/commit/d1c63f2682e834e
    
<http://github.com/romangrothausmann/ParaView_scripts/commit/d1c63f2682e834e>
    Even though there is no error on execution any more, the resulting PVSM has
    only the visibilities set for the last loaded PVSM, i.e. the setting of the
    "Visibility" of representations loaded from former PVSMs did not have any
    effect.
    Is there a need to call some kind of Update() to make the property setting
    have any effect? I tried some rendering
    (http://github.com/romangrothausmann/ParaView_scripts/commit/294ff85a0cc7a
    
<http://github.com/romangrothausmann/ParaView_scripts/commit/294ff85a0cc7a>), 
but
    that did not help either.


    On 20/03/18 06:12, Cory Quammen wrote:

        Roman,

        Looking at your original problem with the error:


             File
        
"/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py",
        line 375, in SetPropertyWithName
               prop.SetData(arg)
             File
        
"/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py",
        line 1296, in SetData
               self.SMProperty.AddProxy(value_proxy)
        TypeError: AddProxy argument 1: method requires a VTK object


        You are hitting this when attempting to set the DataAxesGrid, which is a
        ProxyProperty. In your dictionary, this entry has value 'None', but it
        looks like setting a property to value 'None' is not handled correctly
        in servermanager.py. As a workaround, I suggest filtering out properties
        from your dictionary that have 'None' as a value, i.e., do not add those
        property values to your dictionary.

        HTH,
        Cory

        On Mon, Mar 19, 2018 at 12:12 PM, Grothausmann, Roman Dr.
        <grothausmann.ro...@mh-hannover.de
        <mailto:grothausmann.ro...@mh-hannover.de>
        <mailto:grothausmann.ro...@mh-hannover.de
        <mailto:grothausmann.ro...@mh-hannover.de>>> wrote:

             Hi Cory,


             Trying to find out what causes the former problems, I inserted a
        line that
             just sets the property that got collected so far:
        
https://github.com/romangrothausmann/ParaView_scripts/commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420278bfff084788b82c715c452eR59
        
<https://github.com/romangrothausmann/ParaView_scripts/commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420278bfff084788b82c715c452eR59>

<https://github.com/romangrothausmann/ParaView_scripts/commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420278bfff084788b82c715c452eR59

        
<https://github.com/romangrothausmann/ParaView_scripts/commit/b8058f774535398da3767048219df12d6354e6c5#diff-2804420278bfff084788b82c715c452eR59>>
             It already aborts on the first property encountered 
(ForceUseCache):

             <paraview.servermanager.GeometryRepresentation object at
        0x7f7b591fc250>
             ForceUseCache 0
             Traceback (most recent call last):
                File "/net/home/paraview/scripts/pvsm-multi.py", line 91, in
        <module>
                  main()
                File "/net/home/paraview/scripts/pvsm-multi.py", line 59, in 
main
                  pvs.SetProperties(repr, **d)
                File

"/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py",

             line 567, in SetProperties
                  raise AttributeError("object has no property %s" % param)
             AttributeError: object has no property ForceUseCache

             Is ListProperties() returning properties that are not part of the
        specific
             object that is calling ListProperties()?

             Many thanks for any help or hints,
             Roman

             On 21/12/17 16:06, Grothausmann, Roman Dr. wrote:

                 Hi Cory,

                 On 06/12/17 23:06, Cory Quammen wrote:

                     Sorry I failed to follow up. Did you find a solution to
        this problem?


                 Many thanks for your reply. No, and I'm still stuck. I tried 
Your
                 suggestion to remove [0]

(https://github.com/romangrothausmann/ParaView_scripts/commit/e40d1016d698ee363500bb9bf04f29add89b99dd

        
<https://github.com/romangrothausmann/ParaView_scripts/commit/e40d1016d698ee363500bb9bf04f29add89b99dd>

<https://github.com/romangrothausmann/ParaView_scripts/commit/e40d1016d698ee363500bb9bf04f29add89b99dd

        
<https://github.com/romangrothausmann/ParaView_scripts/commit/e40d1016d698ee363500bb9bf04f29add89b99dd>>),

                 which changed the reported error from:

                     File