[Paraview] How to select cells linked to selected points ?

[LB]

Hi,

I've used the Find Data dialog to select a region of interest by filtering
point data with the "is one of" criterion.
I would like to extract the corresponding region, but clicking on "extract
selection" does not extract the corresponding cells.

Is there a way to select cells linked to selected points ?


Regards,

-- 
Elby
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Unable to run any catalyst live visualization on Mac OS

[Jimmy .]

Dear community,


Please find the following issue: 
https://gitlab.kitware.com/paraview/paraview/issues/17752


Andrew redirected me to here. If someone with a Mac machine would be so kind to 
help me out on this, I would very much appreciate it.


Best,

Ahmad
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] LiveInsituLink proxy in pvpython client

[Kolja Petersen]

What is meant by support services? Step-by-step guidance to solve the
problem or a complete solution?

How much would it cost if you developed a python client script that
connects to a pvserver, waits for an insitu connection and writes rendered
images of all data available from catalyst to disk for all time steps?
200$, 2000$, 2$?
Thank you
Kolja

On Fri, Oct 27, 2017 at 8:38 PM, Andy Bauer  wrote:

> Unfortunately there's no comprehensive "developing paraview" guide. It can
> be used as a framework for other applications and has been designed to do
> that but we haven't had any funding to work on a comprehensive guide for
> that.
>
> I haven't looked at the Live parts in depth in a while so my memory is
> probably fuzzy on that and it would take a good bit of time for me to
> familiarize myself with that part of the code. By murky I mean that things
> get a bit confusing when you're looking at the classes for both the client,
> server and in situ side. Kitware does offer support services if this is
> important to get working for you.
>
> Best,
> Andy
>
> On Fri, Oct 27, 2017 at 12:51 PM, Kolja Petersen 
> wrote:
>
>> More questions below...
>>
>> On Thu, Oct 26, 2017 at 5:54 PM, Andy Bauer 
>> wrote:
>>
>>> I inlined some answers below...
>>>
>>> On Wed, Oct 25, 2017 at 1:42 PM, Kolja Petersen >> > wrote:
>>>
 Thank you, Andy,
 unfortunately your answer has shown me how little I understand about
 Catalyst. But maybe it leads in the right direction after some work from my
 side.

 Just to make sure that we are talking about the same thing: My pvpython
 client is supposed to automate some of the visualization functionality of
 the paraview GUI. The coprocessing.py is in charge of the other side of the
 link, namely to provide data to the visualization side, if I understand
 correctly? I rather followed what happens in the constructor
 pqLiveInsituVisualizationManager::pqLiveInsituVisualizationManager(int
 connection_port, pqServer* server), which creates a
 vtkSMLiveInsituLinkProxy, not a vtkLiveInsituLink as coprocessing.py.

>>>
>>> Yes, coprocessing.py should only be used on the simulation side.
>>>
>>
>> So, did you suggest, coprocessing.py could also help to develop the
>> visualization side? If yes, how? Or was my first email too unclear, so that
>> my intention was not obvious?
>>
>>
>>>

 Now I saw that the vtkLiveInsituLink class can have ProcessType LIVE
 (for the visualization side? as server side object of the proxy created by
 paraview?) or INSITU (for the simulation side?). So apparently the same
 class can take both roles? If yes, that'd clarify some of my confusion. But
 still I don't see how coprocessing.py helps me to implement a python
 visualization client?


>>> Yes, the same class does work in both roles with the LIVE ProcessType
>>> being the visualization side and the INSITU being the simulation side.
>>> Things get a little murkier when there is a separate pvserver from the
>>> client that connects to the simulation.
>>>
>>
>> What do you mean by "murkier"? Paraview also uses a proxy (to a
>> vtkLiveInsituLink instance either on a pvserver or on the builtin server),
>> not  the class itself. Do you have an easier solution (C++ or python) by
>> using vtkInsituLink directly?
>>
>> Are there any design documents from Kitware that show the timings and
>> message exchange between Catalyst, pvserver and Paraview (or other
>> clients)? I don't know Kitware's publishing policies. My impression was
>> always that you are not just developing the Paraview application but also
>> an open source visualization programming framework. Maybe I'm wrong, but I
>> am missing some kind of "Paraview Programming Guide" that goes beyond a
>> User's Guide, to enable others understand the concepts behind Paraview and
>> contribute at a deeper level than just adding filters and data processing
>> algorithms.
>> Anyway, thanks for your explanations, although I couldn't make much
>> progress.
>> Kolja
>>
>
>
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] LiveInsituLink proxy in pvpython client

[Andy Bauer]

Unfortunately there's no comprehensive "developing paraview" guide. It can
be used as a framework for other applications and has been designed to do
that but we haven't had any funding to work on a comprehensive guide for
that.

I haven't looked at the Live parts in depth in a while so my memory is
probably fuzzy on that and it would take a good bit of time for me to
familiarize myself with that part of the code. By murky I mean that things
get a bit confusing when you're looking at the classes for both the client,
server and in situ side. Kitware does offer support services if this is
important to get working for you.

Best,
Andy

On Fri, Oct 27, 2017 at 12:51 PM, Kolja Petersen 
wrote:

> More questions below...
>
> On Thu, Oct 26, 2017 at 5:54 PM, Andy Bauer 
> wrote:
>
>> I inlined some answers below...
>>
>> On Wed, Oct 25, 2017 at 1:42 PM, Kolja Petersen 
>> wrote:
>>
>>> Thank you, Andy,
>>> unfortunately your answer has shown me how little I understand about
>>> Catalyst. But maybe it leads in the right direction after some work from my
>>> side.
>>>
>>> Just to make sure that we are talking about the same thing: My pvpython
>>> client is supposed to automate some of the visualization functionality of
>>> the paraview GUI. The coprocessing.py is in charge of the other side of the
>>> link, namely to provide data to the visualization side, if I understand
>>> correctly? I rather followed what happens in the constructor
>>> pqLiveInsituVisualizationManager::pqLiveInsituVisualizationManager(int
>>> connection_port, pqServer* server), which creates a
>>> vtkSMLiveInsituLinkProxy, not a vtkLiveInsituLink as coprocessing.py.
>>>
>>
>> Yes, coprocessing.py should only be used on the simulation side.
>>
>
> So, did you suggest, coprocessing.py could also help to develop the
> visualization side? If yes, how? Or was my first email too unclear, so that
> my intention was not obvious?
>
>
>>
>>>
>>> Now I saw that the vtkLiveInsituLink class can have ProcessType LIVE
>>> (for the visualization side? as server side object of the proxy created by
>>> paraview?) or INSITU (for the simulation side?). So apparently the same
>>> class can take both roles? If yes, that'd clarify some of my confusion. But
>>> still I don't see how coprocessing.py helps me to implement a python
>>> visualization client?
>>>
>>>
>> Yes, the same class does work in both roles with the LIVE ProcessType
>> being the visualization side and the INSITU being the simulation side.
>> Things get a little murkier when there is a separate pvserver from the
>> client that connects to the simulation.
>>
>
> What do you mean by "murkier"? Paraview also uses a proxy (to a
> vtkLiveInsituLink instance either on a pvserver or on the builtin server),
> not  the class itself. Do you have an easier solution (C++ or python) by
> using vtkInsituLink directly?
>
> Are there any design documents from Kitware that show the timings and
> message exchange between Catalyst, pvserver and Paraview (or other
> clients)? I don't know Kitware's publishing policies. My impression was
> always that you are not just developing the Paraview application but also
> an open source visualization programming framework. Maybe I'm wrong, but I
> am missing some kind of "Paraview Programming Guide" that goes beyond a
> User's Guide, to enable others understand the concepts behind Paraview and
> contribute at a deeper level than just adding filters and data processing
> algorithms.
> Anyway, thanks for your explanations, although I couldn't make much
> progress.
> Kolja
>
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] vtkCutter

[Heiland, Randy]

The Properties for the vtkContourTriangulator filter don’t seem to allow 
coloring by a scalar field. Is that expected? 


> On Oct 26, 2017, at 11:18 AM, Cory Quammen  wrote:
> 
> On Thu, Oct 26, 2017 at 11:15 AM, Heiland, Randy  > wrote:
> Thanks! Before I start down that path, will this handle multiple, disjoint 
> polylines? E.g., a plane slicing through 2 spheres; I just want to cap the 
> sliced spheres.
> 
> I'm about 95% sure it will. It is fairly robust IIRC.
> 
> Cory
>> On Oct 26, 2017, at 11:10 AM, Cory Quammen > > wrote:
>> 
>> There isn't a filter exposed in ParaView to do this. You could expose 
>> vtkContourTriangulator in an XML plugin [1] and apply that to the polyline 
>> created by the planar Slice through your polygonal geometry.
>> 
>> Cory
>> 
>> [1] https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#XML_Only 
>> 
>> 
>> On Thu, Oct 26, 2017 at 10:35 AM, Heiland, Randy > > wrote:
>> Yes, sorry I wasn’t clear.
>> 
>>> On Oct 26, 2017, at 10:33 AM, Cory Quammen >> > wrote:
>>> 
>>> I'm not sure what you mean. Are you trying to clip some polygonal geometry 
>>> with a plane and want to fill in the hole created with a polygon?
>>> 
>>> On Thu, Oct 26, 2017 at 10:24 AM, Heiland, Randy >> > wrote:
>>> Is there a property that lets me cap the results?
>>> 
 On Oct 26, 2017, at 10:18 AM, Cory Quammen >>> > wrote:
 
 Sounds like you want the Slice filter.
 
 On Thu, Oct 26, 2017 at 10:14 AM, Heiland, Randy >>> > wrote:
 I’m not seeing the vtkCutter in the list of filters (well, perhaps the AMR 
 CutPlane). If not, any advice on how to accomplish it for some polydata? 
 https://www.paraview.org/Wiki/Python_Programmable_Filter 
  ?
 
 Thanks!
 
 ___
 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 
 
 Search the list archives at: http://markmail.org/search/?q=ParaView 
 
 
 Follow this link to subscribe/unsubscribe:
 http://public.kitware.com/mailman/listinfo/paraview 
 
 
 
 
 
 -- 
 Cory Quammen
 Staff R&D Engineer
 Kitware, Inc.
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Cory Quammen
>>> Staff R&D Engineer
>>> Kitware, Inc.
>> 
>> 
>> 
>> 
>> -- 
>> Cory Quammen
>> Staff R&D Engineer
>> Kitware, Inc.
> 
> 
> 
> 
> -- 
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.



smime.p7s
Description: S/MIME cryptographic signature
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Disable auto show

[Quentin d'Avout]

Hi All,



I would like to disable the auto show setting, but couldn’t find such a
setting in the settings…

When you create and apply a new filter, paraview automatically shows that
new filter in a view.

I would like to disable that.



Thanks

Quentin
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] LiveInsituLink proxy in pvpython client

[Kolja Petersen]

More questions below...

On Thu, Oct 26, 2017 at 5:54 PM, Andy Bauer  wrote:

> I inlined some answers below...
>
> On Wed, Oct 25, 2017 at 1:42 PM, Kolja Petersen 
> wrote:
>
>> Thank you, Andy,
>> unfortunately your answer has shown me how little I understand about
>> Catalyst. But maybe it leads in the right direction after some work from my
>> side.
>>
>> Just to make sure that we are talking about the same thing: My pvpython
>> client is supposed to automate some of the visualization functionality of
>> the paraview GUI. The coprocessing.py is in charge of the other side of the
>> link, namely to provide data to the visualization side, if I understand
>> correctly? I rather followed what happens in the constructor
>> pqLiveInsituVisualizationManager::pqLiveInsituVisualizationManager(int
>> connection_port, pqServer* server), which creates a
>> vtkSMLiveInsituLinkProxy, not a vtkLiveInsituLink as coprocessing.py.
>>
>
> Yes, coprocessing.py should only be used on the simulation side.
>

So, did you suggest, coprocessing.py could also help to develop the
visualization side? If yes, how? Or was my first email too unclear, so that
my intention was not obvious?


>
>>
>> Now I saw that the vtkLiveInsituLink class can have ProcessType LIVE (for
>> the visualization side? as server side object of the proxy created by
>> paraview?) or INSITU (for the simulation side?). So apparently the same
>> class can take both roles? If yes, that'd clarify some of my confusion. But
>> still I don't see how coprocessing.py helps me to implement a python
>> visualization client?
>>
>>
> Yes, the same class does work in both roles with the LIVE ProcessType
> being the visualization side and the INSITU being the simulation side.
> Things get a little murkier when there is a separate pvserver from the
> client that connects to the simulation.
>

What do you mean by "murkier"? Paraview also uses a proxy (to a
vtkLiveInsituLink instance either on a pvserver or on the builtin server),
not  the class itself. Do you have an easier solution (C++ or python) by
using vtkInsituLink directly?

Are there any design documents from Kitware that show the timings and
message exchange between Catalyst, pvserver and Paraview (or other
clients)? I don't know Kitware's publishing policies. My impression was
always that you are not just developing the Paraview application but also
an open source visualization programming framework. Maybe I'm wrong, but I
am missing some kind of "Paraview Programming Guide" that goes beyond a
User's Guide, to enable others understand the concepts behind Paraview and
contribute at a deeper level than just adding filters and data processing
algorithms.
Anyway, thanks for your explanations, although I couldn't make much
progress.
Kolja
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] TemporalInterpolator error

[John Haase]

Hello all,

I am trying to compare two data set, so I use the Temporal Interpolator to
make certain the time steps match. It works; however, I get the error

ERROR: In
> /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/VTK/Common/ExecutionModel/vtkMultiTimeStepAlgorithm.cxx,
> line 125
> vtkTemporalInterpolator (0x3c900f0): No temporal data has been requested.
> ERROR: In
> /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx,
> line 784
> vtkPVCompositeDataPipeline (0x3c94820): Algorithm
> vtkTemporalInterpolator(0x3c900f0) returned failure for request:
> vtkInformation (0x3cfdf80)
>   Debug: Off
>   Modified Time: 239712
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_DATA
>   FORWARD_DIRECTION: 0
>   ALGORITHM_AFTER_FORWARD: 1
>   FROM_OUTPUT_PORT: 0
>
>
> ERROR: In
> /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/VTK/Common/ExecutionModel/vtkMultiTimeStepAlgorithm.cxx,
> line 125
> vtkTemporalInterpolator (0x3ca5720): No temporal data has been requested.
> ERROR: In
> /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx,
> line 784
> vtkPVCompositeDataPipeline (0x3cac7c0): Algorithm
> vtkTemporalInterpolator(0x3ca5720) returned failure for request:
> vtkInformation (0x3cfdf80)
>   Debug: Off
>   Modified Time: 241098
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_DATA
>   FORWARD_DIRECTION: 0
>   ALGORITHM_AFTER_FORWARD: 1
>   FROM_OUTPUT_PORT: 0


Any idea if I can change something in my process to fix this?

Regards,

John R. Haase
jhaa...@nd.edu
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Extract Cells by Region, glyphs

[Heiland, Randy]

Crap. Yes. I need to expand my mental checklist :)  Thanks!

> On Oct 27, 2017, at 7:37 AM, David E DeMarle  wrote:
> 
> They glyph filter's default is to sub sample. You can choose the total number 
> of samples and among different subsample strategies, via the gui. Click the 
> gear too see all controls if necessary.
> 
> On Oct 27, 2017 6:16 AM, "Heiland, Randy"  > wrote:
> I’m using this filter on my polydata  (points) and it extracts them as 
> expected (using Intersect with Plane). I display the resulting points with 
> OSPRay. Then I use a Glyph filter on those results, but only some of the 
> points are glyphed. See attachment. Suggestions?
> 
> thanks, Randy
> 
> 
> 
> ___
> 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 
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView 
> 
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview 
> 
> 



smime.p7s
Description: S/MIME cryptographic signature
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Extract Cells by Region, glyphs

[Dennis Conklin]

Randy,

Is it possible you have not switched Masking Glyph Mode to All Points?I've 
forgotten that a few time myself!

Dennis
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

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

[louise.davies]

Hi Sebastien,

I’ve made it so that the plugin autoloads (and I’ve checked that the plugins 
are autoloading by selecting a reader plugin as autoload as well, and it does 
indeed allow me to open the associated filetype without me loading the plugin 
via the command line) and I still have the same result in Visualizer – the 
filter does not apply or appear in the pipeline.

Due to this, it must be how I am specifying the filter in the proxies file 
rather than the plugins not loading (I would think). What property in the 
plugin xml should I be using in my proxies json file?

Kind Regards,

Louise

From: Sebastien Jourdain [mailto:sebastien.jourd...@kitware.com]
Sent: 26 October 2017 17:11
To: Davies, Louise (STFC,RAL,SC) 
Cc: Scott Wittenburg ; paraview@paraview.org
Subject: Re: [Paraview] Specifying filters from plugins in ParaViewWeb 
Visualizer proxy file

Another easy approach (not great but easy), is to check that plugin in ParaView 
Qt ui as auto load and then make sure Visualizer is not started with the "-dr" 
argument.
That way, the plugin will load at start time.

On Thu, Oct 26, 2017 at 10:06 AM, 
mailto:louise.dav...@stfc.ac.uk>> wrote:
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.wittenb...@kitware.com]
Sent: 26 October 2017 16:53

To: Davies, Louise (STFC,RAL,SC) 
mailto:louise.dav...@stfc.ac.uk>>
Cc: paraview@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, 
mailto:louise.dav...@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.wittenb...@kitware.com]
Sent: 26 October 2017 16:30
To: Davies, Louise (STFC,RAL,SC) 
mailto:louise.dav...@stfc.ac.uk>>
Cc: paraview@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, 
mailto:louise.dav...@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
 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
 (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

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