[Paraview-developers] IceT compositing in paraview

[Moreland, Kenneth]

John,

If I understand correctly, you are looking to either turn off the IceT compositing since you are doing it yourself or to use IceT to composite using your custom operator.

IceT supports a mode that will in effect turn off compositing. I think the ParaView representation/view classes support turning this on for the case when geometry is collected. Utkarsh would know better than me how to turn this on in ParaView.

The second mode of using IceT with your custom composite operation is not directly supported, yet. Currently IceT only supports the hard coded operations of Z compare and alpha blending. That said, adding a custom compositing mode should be pretty straightforward. I'd be willing to add that core capability to IceT if someone else was willing to add corresponding changes to the ParaView code.

-Ken

Sent from my iPad so blame autocorrect.

On Jul 30, 2014, at 9:33 AM, "Biddiscombe, John A." <biddisco at cscs.ch<mailto:biddisco at cscs.ch>> wrote:

Dear List, but hopefully/probably for the attention of Ken

Our custom splotch representation generates an image on each rank, but to get certain effects right, we pass all the images back from ranks>0 to rank=0 and perform a post render step on rank 0 (pixel normalization). Then  rank0 returns the final image to paraview and all ranks N>0 return an empty (black) image.

This means that the compositing step we do (inefficient because it is using MpiReduce and not binary swap or direct send - or any other nice stuff in IceT) is performed once, and then  paraview does its own compositing step as well.

I’d like to remove the duplicated compositing phase, but our image has no depth buffer information and so I need to tell paraview/IceT to do a composition of the images using a SUM operation rather than a z-buffer test.

is it possible to do this? (from a representation?)

If it is not possible to override the compositing step from paraview, could I implement a compositing step like allReduce(MPI::SUMP_OP), but using iceT instead of just raw MPI as it might improve performance.

We’d like to use>1024 GPUs to render some really big cosmological data and so the compositing will be expensive and doing it twice is naturally undesirable.

many thanks for any clues (I may have asked this question a couple of years ago, but have forgotten the answer).

yours

JB


--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch<http://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

_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org>
http://public.kitware.com/mailman/listinfo/paraview-developers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20140730/1654b876/attachment.html>