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.<br><br><div><span class="gmail_quote">
On 8/7/06, <b class="gmail_sendername">Randall Hand</b> <<a href="mailto:randall.hand@gmail.com">randall.hand@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>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:<br><div style="margin-left: 40px;"><span style="font-family: courier new,monospace;">[rhand@plasma proc]$ pdsh -a top -b -n1 | grep pvserver | sort</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">plasma01ib: 18580 rhand 25 0 1969M 1.9G 21052 R 25.0 25.0 275:25 1 pvserver</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">
plasma01ib: 18581 rhand 25 0 1969M 1.9G 21052 S 0.0 25.0 0:00 3 pvserver</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">plasma01ib: 18582 rhand 25 0 1969M
1.9G 21052 S 0.0 25.0 0:00 3 pvserver</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">plasma02ib: 18367 rhand 25 0 1926M 1.9G 21052 R 25.0 24.5 275:22 1 pvserver
</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">plasma02ib: 18368 rhand 25 0 1926M 1.9G 21052 S 0.0 24.5 0:00 0 pvserver</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">plasma02ib: 18369 rhand 25 0 1926M 1.9G 21052 S 0.0 24.5 0:00 0 pvserver</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">
plasma03ib: 18407 rhand 25 0 3268M 3.2G 21052 R 25.2 41.7 275:20 1 pvserver</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">...(snip)...</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">plasma11ib: 20771 rhand 25 0 1997M 1.9G 21060 S 0.0 25.4 0:00 3 pvserver</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">
plasma12ib: 18301 rhand 18 0 4161M 4.0G 21164 S 0.0 53.1 6:38 1 pvserver</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">plasma12ib: 18302 rhand 25 0 4161M
4.0G 21164 S 0.0 53.1 0:00 1 pvserver</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">plasma12ib: 18303 rhand 25 0 4161M 4.0G 21164 S 0.0 53.1 0:00 1 pvserver
</span><br></div><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 <span style="font-weight: bold;">
production</span> 2.4.4 release, not my customized mullion-enabled one)<br></div><div><span class="sg">-- <br>----------------------------------------<br>Randall Hand<br>Visualization Scientist<br>ERDC MSRC-ITL
</span></div></blockquote></div><br><br clear="all"><br>-- <br>----------------------------------------<br>Randall Hand<br>Visualization Scientist<br>ERDC MSRC-ITL