Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ice-dev] ICE-ParaView integration
Scott,

For context, I've attached the Point Variables from the "ui" and "properties" JSON objects.

I suppose the problem is that although I can find what I want to display, I'm not sure what value(s) need to be updated in the proxy.

Thanks again,
Jordan
Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091
Email: deytonjh@xxxxxxxx
On 2/27/2015 5:48 PM, Jordan Deyton wrote:
Thanks for the quick reply, Scott!

So, say I decide I want to display variable called "temp". I find it in the "PointVariables" JSON object under the "properties" JSON object.

Which of the proxy's properties should be updated to force it to render "temp" rather than just the surface of the mesh?

Thanks,
Jordan
Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091
Email: deytonjh@xxxxxxxx
On 2/27/2015 5:21 PM, Scott Wittenburg wrote:


On Fri, Feb 27, 2015 at 3:07 PM, Jordan Deyton <deytonjh@xxxxxxxx> wrote:
Scott, Sebastien, et al,

I have been trying to open up an Exodus file using the http_pvw_server.py script that you wrote. I have successfully opened and rendered the test file by sending RPC calls to a remote server. In particular, I used "file.server.directory.list" and "pv.proxy.manager.create.reader" to get the files open. The end result is that the Exodus file is successfully opened and rendered over the connection (huzzah!).

However, I haven't been able to figure out how to customize what exactly is displayed for the file. For instance, I'd like to be able to switch between "surface", "wireframe", "surface with edges", and other representations. I would also like to switch between the different variables in the "Color By" widget seen in the Web Vizualizer's "Representation" section. See the attached pictures for a little more context.

It looks like I might be able to pull the different variables from the proxy's properties as returned by "pv.proxy.manager.get", but I'm not sure what RPC method (if any) can be used to change these settings.

You're right that you can get the properties by the rpc method you mentioned.  This will give you back a json object with a lot of information, including parallel, ordered lists of property values and information on what kind of ui component could be used for each one.  Then you will call the "pv.proxy.manager.update" rpc method to update them.  See my second link below. 
 
Also, would anyone happen to have a link to the most recent ParaViewWeb documentation?


The top-level of that documentation is here:


But based on your questions, you may be most interested to skip right to here:


Hope this helps,
Scott

 
Thanks,
Jordan

--
Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091
Email: deytonjh@xxxxxxxx




UI
    {
      "widget": "list-n",
      "size": -1,
      "advanced": 0,
      "values": [
        "burnup",
        "conc",
        "contact_pressure",
        "disp_",
        "fast_neutron_flux",
        "fission_rate",
        "fluence",
        "nodal_area_pellet_clad_mechanica",
        "paired_conc",
        "paired_k_temp",
        "paired_temp",
        "penetration",
        "temp"
      ],
      "name": "Point Variables",
      "doc": "Use this property to select which nodal (i.e.,\n        per-point) variables should be loaded.",
      "type": "str"
    }
    
PROPERTIES
    {
      "name": "PointVariables",
      "id": "352",
      "value": [
        "burnup",
        "conc",
        "contact_pressure",
        "disp_",
        "fast_neutron_flux",
        "fission_rate",
        "fluence",
        "nodal_area_pellet_clad_mechanica",
        "paired_conc",
        "paired_k_temp",
        "paired_temp",
        "penetration",
        "temp"
      ]
    }

Back to the top