<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Courier New";
color:maroon;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>The default
composite mode of IceT is to composite using z-buffer comparisons.
Because nothing is written to the z-buffer when rendering transparent geometry
or volumes, the z-buffer comparisons are invalid.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>New with
ParaView 2.4, there is a view option to perform “ordered compositing.”
When you do that, ParaView will, under the covers, redistribute your data (yet
again) very carefully so that IceT can perform a front-to-back color blending
compositing. Note, however, that there is a pretty high overhead for
redistributing your data if you are planning to make a lot of changes to your
pipeline. Also note that there is a bug in the way OpenGL blends the
alpha channel that makes the blending incorrect (Bug #2347), but at least it is
visible.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>-Ken<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
paraview-bounces+kmorel=sandia.gov@paraview.org
[mailto:paraview-bounces+kmorel=sandia.gov@paraview.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Randall Hand<br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, August 07, 2006 2:31
PM<br>
<b><span style='font-weight:bold'>To:</span></b> Paraview List<br>
<b><span style='font-weight:bold'>Subject:</span></b> [Paraview] Re: Even more
Questions about ParaView on a Tiled Display</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>Oh, I almost forgot this
one..<br>
<br>
#5: Is there a known problem with Opacity & IceT? I tried setting one
of the isosurfaces at 50% transparent, but it simply vanished. Where it
overlapped with the other (fully opaque) surface it could be seen, but the rest
of the area was blank. <br>
<br>
I saw a similar effect with attempting to Volume Render a different
dataset. I could see the volume effects where they intersected solid
polygonal geometry (bounding box, etc) but nowhere else.<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><span class=gmailquote><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>On 8/7/06, <b><span style='font-weight:bold'>Randall Hand</span></b>
<<a href="mailto:randall.hand@gmail.com">randall.hand@gmail.com</a>>
wrote:</span></font></span><o:p></o:p></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Ok, so I've got my Mullions code (still looking for any comments about
that) working on our RenderWall and I'm noticing some interesting behaviour
that i've got some questions about.<br>
<br>
In this cluster, we have 12 nodes + 1 head node, each one connected via a
GeForce 7800GTX to a 1600x1200 LCD Display. Each node has 2 single-core
Xeon processors Hyperthreaded, for an "effective" 4 cores, and 8G of
ram. All connected via Infiniband. I've loaded up 2 PVTP
datasets: <br>
a) Dataset A is a 52Million Triangle 24-part surface, RGB per
point<br>
b) Dataset B is a 67Million Triangle 12-part surface, no data per
point (Geometry only)<br>
<br>
(Both datasets were load-balanced with Paraview's D3 filter.) <br>
<br>
Now when I load them in Paraview, with a Tiled Display, they both load and I'm
able to interact with them beautifully. 119Million Triangles rendered in
1s (for a still frame). I applied a cutting plane to one of them, and
then another D3 (to balance the newly cut surface, right?), and the results are
still fabulously interactive. But a few things i've noticed: <br>
1) Even tho the results are now "load balanced" again (via the D3),
my memory usage is still fairly varying. I'm seeing numbers ranging from
1.8G to 3.8G on various nodes. Is this because the memory isn't really
freed-up from the Cut operation? <br>
2) One of my 12 nodes is basically "idle". While the other 11
nodes show runtimes of over 250minutes on the pvserver process, one node shows
less than 5. Images are visible on all 12 displays.<br>
3) On every node I have 3 processes. 4 I would understand, and 1 I had
expected. But 3? It seems one is for the Rendering & MPI work,
while the other 2 are for computations (one has the usual spinlock runtime of
250+minutes, while the others have 0.00).<br>
<br>
An example:<o:p></o:p></span></font></p>
<div style='margin-left:30.0pt'>
<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>[rhand@plasma proc]$ pdsh -a top -b -n1 | grep
pvserver | sort<br>
plasma01ib: 18580 rhand 25 0 1969M 1.9G
21052 R 25.0 25.0 275:25 1 pvserver<br>
plasma01ib: 18581 rhand 25 0 1969M 1.9G
21052 S 0.0 25.0 0:00 3
pvserver<br>
plasma01ib: 18582 rhand 25 0 1969M 1.9G
21052 S 0.0 25.0 0:00 3
pvserver<br>
plasma02ib: 18367 rhand 25 0 1926M 1.9G
21052 R 25.0 24.5 275:22 1 pvserver <br>
plasma02ib: 18368 rhand 25 0 1926M 1.9G
21052 S 0.0 24.5 0:00 0
pvserver<br>
plasma02ib: 18369 rhand 25 0 1926M 1.9G
21052 S 0.0 24.5 0:00 0
pvserver<br>
plasma03ib: 18407 rhand 25 0 3268M 3.2G
21052 R 25.2 41.7 275:20 1 pvserver<br>
...(snip)...<br>
plasma11ib: 20771 rhand 25 0 1997M 1.9G
21060 S 0.0 25.4 0:00 3
pvserver<br>
plasma12ib: 18301 rhand 18 0 4161M 4.0G
21164 S 0.0 53.1 6:38 1
pvserver<br>
plasma12ib: 18302 rhand 25 0 4161M 4.0G
21164 S 0.0 53.1 0:00 1
pvserver<br>
plasma12ib: 18303 rhand 25 0 4161M 4.0G
21164 S 0.0 53.1 0:00 1
pvserver </span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br clear=all>
<br>
4) While interacting, the 2D Scalar Bar seems to resize/move down to the
display closest the origin (lower-left corner), and then return to it's desired
location when the full-res image is rendered again. Is this a glitch, or
by design? <br>
<br>
So can someone explain to me a bit of what's going on "behind the
curtain"? I've also had no luck chasing down what's going on with
the Slow Renderings &mangled options on tiled Displays (On the <b><span
style='font-weight:bold'>production</span></b> 2.4.4 release, not my customized
mullion-enabled one)<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><span class=sg><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>-- </span></font></span><br>
<span class=sg>----------------------------------------</span><br>
<span class=sg>Randall Hand</span><br>
<span class=sg>Visualization Scientist</span><br>
<span class=sg>ERDC MSRC-ITL </span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<br clear=all>
<br>
-- <br>
----------------------------------------<br>
Randall Hand<br>
Visualization Scientist<br>
ERDC MSRC-ITL <o:p></o:p></span></font></p>
</div>
</div>
</body>
</html>