![]() Every proxy state get automatically synchronized across clients.Īs Collaboration implies more networking usage for synchronization purpose, this feature is not enable by default.Other clients such as pvpython or ParaViewWeb could benefit from it and be part of the collaboration. The collaboration is not limited to the ParaView Qt client.The master can either give its right to someone else or either force everyone to follow him in its navigation in 2D and 3D views or any other slave user. A master/slave paradigm is used for controlling the pipeline parameters.It allow several clients to connect to a same server and share the same visualization pipeline and views.And now on top of that we provide collaboration as a built-in feature.īut what does collaboration brings to ParaView ? The reason for such move reside in the benefit of the ParaView framework where scalability, distributed architecture became transparent. Nowadays, more projects are considering using ParaView as a library instead of VTK. Those major changes open new doors to the usage of ParaView and not only application wise but also framework wise. Such configuration even works with collaborative server even if in such configuration it can be thought to understand what is going on and who is controlling the application. -) Moreover, a ParaView client can now handle several connected servers at the same time. Those clients can be either the regular ParaView Qt client or simply a pvpython batch or even a ParaViewWeb application. For more details about the API changes and logic underneath, please read the Developer corner section.īut now, it is possible to connect several clients to a single pvserver and share the pipeline and visualization across different clients. We are doing our best to keep the documentation updated as well as the main ParaView code. Those changes were not trivial to make and even if we tried to keep the API unchanged for backward compatibility we definitely break some stuff. Finally, drop the client limitation by allowing a client to connect to several servers at the same time.The second step was to allow a pvserver to accept several clients and make sure the client get synchronized in someway so simulation analysis could be achieved across different sites at the same time.This work has been released with ParaView 3.12. ![]() To achieved that all the Proxy layer has been cleaned up and now we rely on Protobuf messages to store and encode proxy state across processes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |