[Paraview] Catalyst question

Thu Oct 16 10:48:35 EDT 2014

Hi John,

I'll be at SC14 and I'd be interested in seeing your demo. Are the details
of when and where ready yet?

Regards,
Andy

On Thu, Oct 16, 2014 at 10:43 AM, Biddiscombe, John A. <biddisco at cscs.ch>
wrote:

>  Andy, Dan
>
>
>
> Thank you both for clarifying this. I might give the
> catalyst->server->client version a go, but it seems like it might be too
> much trouble ...
>
> I expect I’ll just use the solution we developed here at CSCS a couple of
> years ago where we just connect  the simulation to the pvservers and then
> connect the client to them. That way I won’t need to copy the data between
> processes again (there is already a copy because the simulation is writing
> to a shared memory buffer and the pvservers would read from that - not the
> same as the H5FDdsm stuff we developed, but very similar, and I can simply
> piggy back our live viz on top of that).
>
>
>
> We wanted to do a live demo of GPU rendering on 1024 or so nodes at SC14
> so it may be that using something I’m already familiar with will save me
> time as were getting close to Nov ...
>
>
>
> On that note : It ought to be trivial to whip up a catalyst “view” which
> captures the images from the internal renderwindow created by catalyst and
> have them displayed in the GUI so that the user can see the ‘live’ viz. Not
> sure how you’d pass the interactions back to handle mouse etc, but if the
> client can write to the camera objects via proxies then it should be
> possible ....  might try this myself if I have a moment spare.
>
>
>
> thanks again
>
>
>
> JB
>
>
>
> *From:* Dan Lipsa [mailto:dan.lipsa at kitware.com]
> *Sent:* 16 October 2014 16:32
> *To:* Biddiscombe, John A.
> *Cc:* Andy Bauer; paraview at paraview.org
>
> *Subject:* Re: [Paraview] Catalyst question
>
>
>
> Hi John,
>
>
>
>  I had imagined that I’d run a simulation on N ranks, have catalyst bound
> to them and be able to do vis on those N ranks. But in fact, when I connect
> to a live simulation, I have to “extract” results from them and then render
> them back on the client.
>
>
>
> Is this the case or did I miss something?
>
>
>
> Just to confirm Andy's answer, you can do the rendering on a separate
> ParaView server (pvserver), which can be the same as the server you run the
> simulation on. Catalyst will send extracts to this server which will render
> them.
>
> Only images will be send back to the client.
>
>
>
> We show that use case at the end of our article.
>
>
>
> http://www.kitware.com/blog/home/post/722
>
>
>
> Dan
>
>
>
>
>
>
>
>
>
> The parallel image generation appears to work as advertised, but the
> images go off to disk and not to the renderwindow. Is there a way on
> configuring it so that I can see the actual rendering taking place in the
> renderview? I wanted to display the contents of a custom render plugin
> using cuda based rendering on many GPUs and be able to interact with it,
> but I am obviously missing something in my setup.
>
>
>
> thanks
>
>
>
> JB
>
>
>
> *From:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Sent:* 26 August 2014 15:34
> *To:* Biddiscombe, John A.
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Catalyst question
>
>
>
> Hi John,
>
>
>
> This live capability is now available and recently has been cleaned up
> quite a bit. There are still a couple more small changes that are waiting a
> code review process before they go into the master branch. The user's guide
> needs an update for a bunch of new information (live, catalyst editions,
> zero-copy arrays) that's important for Catalyst. We're also doing some
> preliminary testing with a newly developed ADIOS writer for better IO
> performance as well.
>
> Getting back to the live viz stuff, when you create a Catalyst Python
> script and export it using the wizard you'll have the option to enable live
> viz (it's the same wizard page as the screenshot output specification).
> Then, while your simulation is running use the Catalyst->Connect option to
> connect. There are two tests (pv.CatalystLiveSetBreakpoint and
> pvcs.CatalystLiveSetBreakpoint) that demonstrate the newly implemented live
> functionality which now includes the option to set a breakpoint in the
> simulation.
>
> If you get a chance to try it out, let me know what you think.
>
> Andy
>
>
>
> On Tue, Aug 26, 2014 at 3:40 AM, Biddiscombe, John A. <biddisco at cscs.ch>
> wrote:
>
> Dear Catalyst people
>
>
>
> I dragged out an old simulation demo I created some time ago and got it
> working with paraview/catalyst from git master branch - my plan was to test
> a live visualization of the simulation with the paraview GUI connected to
> the simulation. I had thought this capability was now possible, but I have
> not been following development closely and it looks like I was mistaken.
>
>
>
> Is it possible to visualize the simulation live - rather than just
> generate images (which works fine). (I had a quick skim through the user
> manual, but didn’t see this feature mentioned).
>
>
>
> Thanks
>
>
>
> JB
>
>
>
> --
>
> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>
> http://www.cscs.ch/
>
> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>
> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>
>
>
>
> _______________________________________________
> 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
>
> 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
>
> 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/20141016/931255c2/attachment-0001.html>