<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>John,</div>
</div>
</div>
<div><br>
</div>
<div>I have no experience with DisplayCluster and haven't messed with tiled displays in a long time, so I don't have a complete answer for you. But perhaps I can fill in some holes.</div>
<div><br>
</div>
<div>If you give the arguments —tdx=1 —tdy=1, ParaView should happily create a "tiled" display of a single image that you can then break up and transfer with another software service. The only real problem I can see is that there is no way to directly specify
the number of pixels in the display. The original implementation assumed that node GPUs are connected directly to displays, so just gets the size of the displays from the Xhost screen. So specifying the size of the framebuffers will require some code modification,
but they should be pretty minor ones.</div>
<div><br>
</div>
<div>I don't know if anyone has directly interfaced ParaView with the DisplayCluster software. I have not been following it that closely. I do remember a presentation on SAGE in the 2008 Ultrascale Visualization Workshop that described using SAGE to stream
pixels from ParaView on one cluster to another cluster driving a tiled display very similarly to what you are doing (<a href="http://vis.cs.ucdavis.edu/Ultravis08/slides/Leigh-UltraViz.pdf">http://vis.cs.ucdavis.edu/Ultravis08/slides/Leigh-UltraViz.pdf</a>).
If you have no other luck, you might consider contacting those authors.</div>
<div><br>
</div>
<div>As far as data replication is concerned, ParaView should handle that for you. The standard mode of operation is to leave the data distributed and use image composition for parallel rendering. I believe that if the size of the data being rendering is
below the remote rendering threshold, then the data will be distributed among all tiled display renders just as it would be sent to the client, but unless you screwed up your settings that only happens when the data is small enough to be collected.</div>
<div><br>
</div>
<div>As far as ParaView is concerned, handling 12 vs 6 vs 1 tiles is about the same because IceT takes care of all that internally. As far as performance is concerned, I would expect the single huge display to be at least marginally better than the small displays
because of better load balancing and fewer possible rendering passes. However, I do worry about the memory overhead of compositing a single 7920x3060 image. I expect IceT to create at least 3 framebuffers to simultaneously send, receive, and compress/composite
images. By my count that is over 1/2 GB per MPI process.</div>
<div><br>
</div>
<div>-Ken</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><Biddiscombe>, "John A." <<a href="mailto:biddisco@cscs.ch">biddisco@cscs.ch</a>><br>
<span style="font-weight:bold">Date: </span>Monday, June 3, 2013 2:19 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a>" <<a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a>><br>
<span style="font-weight:bold">Subject: </span>[EXTERNAL] [Paraview-developers] DisplayCluster + ParaView<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:9793540;
mso-list-type:hybrid;
mso-list-template-ids:214100582 134807569 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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]-->
<div lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Colleagues have installed a large tiled display and are running displaycluster from TACC on it.<o:p></o:p></p>
<p class="MsoNormal">I’ve never used a tiled display, with paraview or any other software so I’m not sure what to do.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The out of the box solution is to use –tdx=4 –tdy=3 and set the display env var to point to the correct gpu, but I don’t have access to the nodes hosting the wall itself (can’t run 6 pvservers on the wall nodes or send X to them) and would
like to use the viz cluster to run N pvservers (where N>number of tiles) and send the pixels using the displaycluster API ( see
<a href="https://github.com/TACC/DisplayCluster">https://github.com/TACC/DisplayCluster</a> ). It essentially allows you to send rectangular blocks of pixels into the final image, so I’d simply want 4x3 regions to send.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ll therefore need to setup a custom view in paraview and capture pixels to send them. Since the display could conceivably be 1980x1020 X4 X3 pixels, this will mean some very large framebuffers on all nodes –
<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span><!--[endif]-->Has anyone already integrated DisplayCluster into paraview and is there a paraview branch anywhere with developments in?<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span><!--[endif]-->I do not want to replicate data on each render node, which seems to be considered usual for tiled displays, but is out of the question as far as I’m concerned. Is there a better strategy for handling the display. Is 12 small windows
better than 1 very large one for example – I can imagine setting 12 views with a different frustum and pasting them into the final large image, but then perhaps the overhead of managing 12 windows is worse than 1 huge one?) (NB. It’s actually 6 windows instead
of 12 because 2 displays are driven off each GPU on the wall driver nodes and the x server considers them as one)<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:18.0pt"><o:p> </o:p></p>
<p class="MsoNormal">Any advice gratefully received. Thanks<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">JB<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size: 10.5pt; color: rgb(31, 73, 125); font-family: 'Courier New'; ">--
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size: 10.5pt; color: rgb(31, 73, 125); font-family: 'Courier New'; ">John Biddiscombe, email:biddisco @.at.@ cscs.ch<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size: 10.5pt; color: rgb(31, 73, 125); font-family: 'Courier New'; "><a href="http://www.cscs.ch/"><span style="color:blue">http://www.cscs.ch/</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size: 10.5pt; color: rgb(31, 73, 125); font-family: 'Courier New'; ">CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="IT-CH" style="font-size: 10.5pt; color: rgb(31, 73, 125); font-family: 'Courier New'; ">Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="IT-CH"><o:p> </o:p></span></p>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>