[Paraview] Specifying filters from plugins in ParaViewWeb Visualizer proxy file

[louise.davies at stfc.ac.uk]

Hi Scott,

Yes, the ui item is there but all that happens is that the logo flickers for like a second then nothing.


1.       I have no log output other than the regular output I get via starting the server

2.       Running 5.4.1, compiled from source

3.       It’s an .mha file, looking at the file info gives “Image (Uniform Rectilinear Grid)”. Note that I’m using the flying edges filter as an example since it’s a standard plugin and I can get it to apply to this dataset in ParaView desktop, so I don’t think it is the datatype. It also doesn’t work if I use a Wavelet like specified in this blog post: https://blog.kitware.com/accelerated-filters-in-paraview-5/

Louise

From: Scott Wittenburg [mailto:scott.wittenburg at kitware.com]
Sent: 26 October 2017 16:53
To: Davies, Louise (STFC,RAL,SC) <louise.davies at stfc.ac.uk>
Cc: paraview at paraview.org
Subject: Re: [Paraview] Specifying filters from plugins in ParaViewWeb Visualizer proxy file

I see, I read your first email a bit too quickly.  So you do see the filter appear in the web ui, but it just doesn't have any effect you can see.  A few more questions then: 1) Is there any log output you can share? 2) what version of paraview are you running?  3) what filter or dataset type are you giving as input to the flying edges filter?

Scott

On Thu, Oct 26, 2017 at 9:37 AM, <louise.davies at stfc.ac.uk<mailto:louise.davies at stfc.ac.uk>> wrote:
Hi Scott,

I am using the default pvw-visualizer.py server file, which does register ParaViewWebStartupPluginLoader before ParaViewWebProxyManager.

For clarification, this is what I’m adding to my json file (using the Flying Edges 3D example):

In the “filters” section:
{ "name": "FlyingEdges3D", "label": "Flying Edges 3D"}

Louise

From: Scott Wittenburg [mailto:scott.wittenburg at kitware.com<mailto:scott.wittenburg at kitware.com>]
Sent: 26 October 2017 16:30
To: Davies, Louise (STFC,RAL,SC) <louise.davies at stfc.ac.uk<mailto:louise.davies at stfc.ac.uk>>
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Specifying filters from plugins in ParaViewWeb Visualizer proxy file

Hi Louise,

   Off the top of my head, I would think that what you are doing should work, but maybe Seb can chime in otherwise.  In your application server code, do you register the "ParaViewWebStartupPluginLoader" before the "ParaViewWebProxyManager"?

Scott

On Thu, Oct 26, 2017 at 9:24 AM, <louise.davies at stfc.ac.uk<mailto:louise.davies at stfc.ac.uk>> wrote:
Hello all,

I’m specifying some plugins to load with Visualizer, and I want to be able to apply filters from these plugins in Visualizer. I’ve copied the defaultProxies.json<https://github.com/Kitware/ParaView/blob/master/Web/Python/defaultProxies.json> file from the ParaView source code and I don’t know how to get ParaView to recognise my plugin filter name.

For example, I specify on the command line I want to load the default AcceleratedAlgorithms plugin. I want to expose the Flying Edges 3D filter in Visualizer. However, all of the names I can find related to the Flying Edges 3D filter in its .xml file<https://github.com/Kitware/ParaView/blob/master/Plugins/AcceleratedAlgorithms/AcceleratedAlgorithms.xml> (e.g. FlyingEdges3D, vtkFlyingEdges3D) do not allow me to use the filter. When I click on the item in the filters pane it does nothing.

Am I understanding this incorrectly? Does it work differently for filters loaded from plugins than from default ParaView filters?

Kind Regards,

Louise

_______________________________________________
Powered by www.kitware.com<http://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

Search the list archives at: http://markmail.org/search/?q=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/20171026/ceb3e3b9/attachment.html>