[Paraview] [ParaView] data from multiple servers rendered in the same view

[Claude]

Hi Mathieu,

Too bad, and at the same time understandable it is not possible in a parallel remote rendering architecture.
Thank you for the workaround!!
Cheers
Claude 

Thank you for the trick Mathieu.

> On Jan 9, 2017, at 3:02 AM, Mathieu Westphal <mathieu.westphal at kitware.com> wrote:
> 
> Hi Claude
> 
> Sadly, no, you can't.
> However, one find you can do is use the interactive view link.
> Right click on one view. add a CameraLink with the other view and check "Interactive View Link"
> 
> You now have a "window" of a view into another view. Checkout the options in the "adjust camera" dialog, you can set opacity and hide the background.
> 
> Regards,
> 
> Mathieu Westphal
> 
>> On Sun, Jan 8, 2017 at 6:22 PM, claude <claude at theweak.link> wrote:
>> Hello Sam,
>> 
>> thank you for the quick reply, I may not be doing it properly then. Each time I toggle on the object to view, it ignores the current active viewer and opens it in a new viewer/layout tab (or the viewer already "linked" to the server if I didn't close that view yet). 
>> 
>> I attached 2 snapshots trying to show the behavior: each time I toggle on one or the other data, it switches automatically the layout (here "layout #2" and "layout #3"). Even if I close one of the layout and keep only one, it will recreate a brand new one.
>> The servers are started with "$PARAVIEW/bin/pvserver --multi-clients" and Paraview is started with "$PARAVIEW/bin/paraview --multi-servers". Is this because the servers are both data+rendering and I should instead have 2 data servers but one rendering server maybe?
>> 
>> Thanks again.
>> 
>> cheers
>> 
>> claude
>> 
>> 
>>> On 01/08/2017 10:44 AM, Samuel Key wrote:
>>> Claude,
>>> 
>>> I am quite certain that I am the least qualified individual to answer your question, but I have been an avid PV user for several years.
>>> 
>>> As you click on each view to make it the active view (blue line around the view's perimeter), look at the pipeline browser. You should see the on/off "eyeballs" change.
>>> 
>>> The appearance of the eyeball is either black for the datum set in the current active view and the others are "grayed out," that is, inactive as in "not visible." You should be able to click on a grayed out eyeball and make it active/visible in your current selected view. 
>>> 
>>> Hope this helps.
>>> 
>>> Sam Key
>>> 
>>>> On 1/7/2017 10:19 PM, Claude wrote:
>>>> Dear community of ParaView experts,
>>>> 
>>>> I am a new ParaView user and hopefully plugin developer, and first time
>>>> poster to the list. I hope the following will not sound too silly and I
>>>> thank you in advance for your replies.
>>>> 
>>>> There are several paraview servers setup and I am able to connect to all
>>>> of them from the Paraview application. I can properly visualize the data
>>>> on each server. However each data appear in a separate view and I would
>>>> like to render them all in the same view (because they happen to be
>>>> different type of data in the same volume of interest). These data are
>>>> not on the same server for proprietary reasons (e.g. server A and server
>>>> B are not held by the same people and do not share their data among
>>>> themselves).
>>>> Is there any way to "merge" the views together although they come from
>>>> different sources? I couldn't find it in the UI but I wonder if this
>>>> even possible/permitted by a software architecture standpoint. I would
>>>> be ready to develop a plugin for it but as I am still exploring the
>>>> devkit, I haven't found the answer yet (and I figured someone would know
>>>> if it's even possible at all).
>>>> 
>>>> I have searched the email archives (http://paraview.markmail.org) but
>>>> didn't find anything similar. I found a lot about comparing data in
>>>> multiple views or parallelizing the rendering of data but from the same
>>>> server.
>>>> 
>>>> Thank you in advance.
>>>> all the best
>>>> claude
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> 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
>> 
>> 
>> _______________________________________________
>> 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
>> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170109/63cff40b/attachment.html>