[Paraview] [Issue] Connecting multiple pvpython scripts simultaneously

[Mariam]

Hi,

I am using the collaboration module in pvpython to connect 30 clients to 
pvserver. 

However, when a certain number of clients are connected (13 or 14), the system 
crashes and it is not able to accept more clients. I receive the following 
error in the server side:

vtkPVAlgorithmPortsInformation: Could not downcast vtkAlgorithm.

 

The setup that I would like to achieve is:

-  PVServer - running in parallel (with MPI)

-  ParaView GUI - establishes a connection and load the model/ create a 
source

-  30 pvpython clients connected to the server in the collaboration 
mode (sharing the same session of ParaView GUI) but each with different camera 
configuration.

 

I tried to control the time of establishing the connection of each client, then 
I was able to increase the number of connected clients to 20 (max). 

 

Could anyone provide any tips or guidance? Or is this technically not doable? 

 

Today, I came across this article: 
https://blog.kitware.com/beat-the-heat-by-freezing-python-in-paraview/ 

Could that be a possible contribution to the issue of launching multiple 
pvpython scripts?

 

Let me know if you require any further details.

 

Regards,

 

___
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] Running a simple example using ParaviewWeb

[Sebastien Jourdain]

With ParaViewWeb, we force the user to pick the version of the dependencies
they wants to install instead of forcing them.

Regarding your import path they are still wrong.

from paraviewweb/src/Component/Native/Composite/example/index.js

when you import '..' that resolve to
paraviewweb/src/Component/Native/Composite

which means your imports should be:

import CompositeComponent   from 'paraviewweb/src/Component/Native/Composite
';
import BGColorComponent from 'paraviewweb/src/Component/
Native/BackgroundColor';

On Wed, Aug 9, 2017 at 7:37 PM, Léo Pessanha 
wrote:

> So, I was able to build using 'paraviewweb/src/' and installing forcibly
> mout, axios and hammerjs packages.
>
> Now there's other js errors that I am going after like /plotly.js\ and
> global reference ones !
>
> It's definitely not a simple task to build an example of paraviewweb as a
> standalone app.
>
> Definitely will come back with updates.
>
> Best regards,
>
>
> Leonardo Pessanha
> Laboratory of Computational Methods in Engineering
> Federal University of Rio de Janeiro - COPPE
> Rio de Janeiro, RJ, Brasil
>
>
> 2017-08-09 19:58 GMT-03:00 Léo Pessanha :
>
>> So I am not sure of the first path yet. Is it 'paraviewweb/src/' or
>> 'paraviewweb/src/Component'?
>>
>> I have the exactly same result using full path or starting with
>> 'paraviewweb'
>>
>> Using:
>>
>> import CompositeComponent   from 'paraviewweb/src/';
>>> import BGColorComponent from 'paraviewweb/src/Component/Nat
>>> ive/BackgroundColor';
>>>
>>
>> Outputs a lot of:
>>
>> Module not found: Error: Can't resolve
>>>
>>
>> So I did a 'npm list x' with x being the modules it couldn't
>> resolve(axios, hammerjs and etc) and none of then was installed.
>>
>> root@PC:~/MyWebProject# npm list hammerjs
>>> projeto1@0.0.1 /home/gabriel/MyWebProject
>>> └── (empty)
>>>
>>> root@PC:~/MyWebProject# npm list axios
>>> projeto1@0.0.1 /home/gabriel/MyWebProject
>>> └── (empty)
>>>
>>
>>
>> Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite
>> --save-dev* failed installing the dependencies correctly?
>>
>> Best regards,
>>
>> Leonardo Pessanha
>> Laboratory of Computational Methods in Engineering
>> Federal University of Rio de Janeiro - COPPE
>> Rio de Janeiro, RJ, Brasil
>>
>>
>> 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain <
>> sebastien.jourd...@kitware.com>:
>>
>>> The import should start with 'paraviewweb' then you provide the full
>>> path from there like:
>>>
>>> import BGColorComponent from 'paraviewweb/src/Component/Native/
>>> BackgroundColor';
>>>
>>> On Wed, Aug 9, 2017 at 6:24 PM, Léo Pessanha <
>>> leonardopessanh...@gmail.com> wrote:
>>>
 Hi! I did the changes. The only thing I am not sure it's the right
 paths in the imports of ${ROOT}/src/index.js

 import CompositeComponent   from '..';
> import BGColorComponent from '../../BackgroundColor';
>
>
 Should I change this paths?

 I did try

 import CompositeComponent   from '/home/user/MyWebProject/node_
 modules/paraviewweb/src';
 import BGColorComponent from '/home/user/MyWebProject/node_
 modules/paraviewweb/src/Component/Native/BackgroundColor';

 and

 import CompositeComponent   from '/home/user/MyWebProject/node_
 modules/paraviewweb/src/Component';
 import BGColorComponent from '/home/user/MyWebProject/node_
 modules/paraviewweb/src/Component/Native/BackgroundColor';

 and

 import CompositeComponent   from '/home/user/MyWebProject/node_
 modules/paraviewweb/src/Component/Native';
 import BGColorComponent from '/home/user/MyWebProject/node_
 modules/paraviewweb/src/Component/Native/BackgroundColor';

 With the last 2 sucessfully building but with JS errors in Firefox

 TypeError: _Component2.default is not a constructor[Learn More]
>

 and

 TypeError: _Native2.default is not a constructor
>

 and the first one not building and giving me a lot of

 Module not found: Error: Can't resolve
>


 Thanks in advance!


 Leonardo Pessanha
 Laboratory of Computational Methods in Engineering
 Federal University of Rio de Janeiro - COPPE
 Rio de Janeiro, RJ, Brasil


 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain <
 sebastien.jourd...@kitware.com>:

> If I get to it, I'll do what I've done with vtk.js to support both.
>
> See: https://github.com/Kitware/vtk-js/blob/master/Utilities
> /config/dependency.js
>
> On Thu, Aug 3, 2017 at 1:49 PM, Léo Pessanha <
> leonardopessanh...@gmail.com> wrote:
>
>> Thank you, Sebastien. I will give a try!
>>
>> Do you believe it's best to rollback webpack to 1.x or to change the
>> webpack.config.js in order to fit webpack 2.x API?
>>
>> Leonardo Pessanha
>> Laboratory of Computational