<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 14 (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;}
@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: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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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;}
--></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-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">When I compile paraview, I see that (for example) the vtkPistonSort.cu file gets the nvcc build rule setup with
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="font-family:"Courier New"">set(nvcc_flags -m64;-D_CRT_SECURE_NO_DEPRECATE;-D_CRT_NONSTDC_NO_DEPRECATE;-D_CRT_SECURE_NO_WARNINGS;-D_SCL_SECURE_NO_DEPRECATE;-D_SCL_SECURE_NO_WARNINGS;-DVTK_IN_VTK;-DMPICH_IGNORE_CXX_SEEK;-DMPICH_IGNORE_CXX_SEEK;-Dcuda_compile_EXPORTS)
# list<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">but when my plugin declares vtkBBPPistonSort.cu it gets the rules generated with<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="font-family:"Courier New"">set(nvcc_flags -m64;-DvtkFiltersFlowPaths_AUTOINIT=1(vtkFiltersParallelFlowPaths);-DvtkIOExodus_AUTOINIT=1(vtkIOParallelExodus);-DvtkIOImage_AUTOINIT=1(vtkIOMPIImage);-DvtkRenderingCore_INCLUDE="D:/build/plugins-vs10/CMakeFiles/vtkRenderingCore_AUTOINIT_vtkInteractionStyle_vtkRenderingFreeType_vtkRenderingFreeTypeOpenGL_vtkRenderingOpenGL.h";-DvtkRenderingVolume_AUTOINIT=1(vtkRenderingVolumeOpenGL);-DQT_DLL;-DQT_GUI_LIB;-DQT_CORE_LIB;-DZOLTAN_SUPPORT;-Dcuda_compile_EXPORTS)
# list<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Does anyone know how to make the <span style="font-family:"Courier New"">
AUTOINIT=1 (vtkBlahBlah)</span> stuff go away. Cmake seems to be inserting some info/messages here which mess up the nvcc compilation. Is there a flag in the vtk module support anywhere which disables the autoinit generation?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I’ve tried as hard as possible to mimic the cmake from the piston build, but something is being ‘added’ for the plugins. Any idea how to make it go away?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thanks<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">JB<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span lang="EN-US" style="mso-fareast-language:EN-GB">-----Original Message-----<br>
From: David E DeMarle [mailto:dave.demarle@kitware.com] <br>
Sent: 17 January 2013 17:38<br>
To: Biddiscombe, John A.<br>
Cc: paraview-developers@paraview.org; Sewell, Christopher Meyer; Li-Ta Lo; Kenneth Moreland; Utkarsh Ayachit<br>
Subject: Re: [Paraview-developers] piston in 3.98</span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I think b. Getting the lists into and out of the vtkPainter parts are the only thing I'm leary of, but that's because I haven't touched them often.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Ollie, Chris, Ken and Utkarsh know the relevant pieces of code better than I, so I've cc'd them specifically.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">David E DeMarle<o:p></o:p></p>
<p class="MsoPlainText">Kitware, Inc.<o:p></o:p></p>
<p class="MsoPlainText">R&D Engineer<o:p></o:p></p>
<p class="MsoPlainText">21 Corporate Drive<o:p></o:p></p>
<p class="MsoPlainText">Clifton Park, NY 12065-8662<o:p></o:p></p>
<p class="MsoPlainText">Phone: 518-881-4909<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On Thu, Jan 17, 2013 at 11:27 AM, Biddiscombe, John A. <<a href="mailto:biddisco@cscs.ch"><span style="color:windowtext;text-decoration:none">biddisco@cscs.ch</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText">> Dave<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Nice. It is working. Thanks.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> I'm very impressed. I wouldn't have thought of it being done like this, but the framework looks rather clever.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Here's a harder question if you have a moment.<o:p></o:p></p>
<p class="MsoPlainText">> My idea is to<o:p></o:p></p>
<p class="MsoPlainText">> 1) insert a painter in my chain which passes vertices (normal 3d) to cuda using the piston framework and also pass a IdType equivalent list of polygon vertex indices.<o:p></o:p></p>
<p class="MsoPlainText">> 2 )within the cuda code, generate a depth list of polygons based on one vertex from each, and sort that list. Then regenerate the vertex Idlist based on the sorted order.<o:p></o:p></p>
<p class="MsoPlainText">> 3) replace the painter that draws the actual primitives with a new one which uses the interop array of vertex Ids so we can do the depth sort witout retransferring stuff to and fro every frame.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> The painter chain is already setup to do depth sort on the CPU, so I'd only need to add a cuda version with the interop setup and then add a new primitive painter (or some kind of painter that does the final draw instead of the existing
one - might need to send the colours+opacities via interop too to avoid trouble retrieving them in the custom painter).<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Can you tell me based on your knowledge of how the piston stuff works
<o:p></o:p></p>
<p class="MsoPlainText">> if what I propose is essentially<o:p></o:p></p>
<p class="MsoPlainText">> a) ridiculous (I'll do something else productive)<o:p></o:p></p>
<p class="MsoPlainText">> b) doable<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> + any hints which will get me there quicker.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Many thanks again<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> JB<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> -----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">> From: David E DeMarle [<a href="mailto:dave.demarle@kitware.com"><span style="color:windowtext;text-decoration:none">mailto:dave.demarle@kitware.com</span></a>]<o:p></o:p></p>
<p class="MsoPlainText">> Sent: 17 January 2013 17:05<o:p></o:p></p>
<p class="MsoPlainText">> To: Biddiscombe, John A.<o:p></o:p></p>
<p class="MsoPlainText">> Cc: <a href="mailto:paraview-developers@paraview.org"><span style="color:windowtext;text-decoration:none">paraview-developers@paraview.org</span></a><o:p></o:p></p>
<p class="MsoPlainText">> Subject: Re: [Paraview-developers] piston in 3.98<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Start paraview with --use-cuda-interop<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> David E DeMarle<o:p></o:p></p>
<p class="MsoPlainText">> Kitware, Inc.<o:p></o:p></p>
<p class="MsoPlainText">> R&D Engineer<o:p></o:p></p>
<p class="MsoPlainText">> 21 Corporate Drive<o:p></o:p></p>
<p class="MsoPlainText">> Clifton Park, NY 12065-8662<o:p></o:p></p>
<p class="MsoPlainText">> Phone: 518-881-4909<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> On Thu, Jan 17, 2013 at 11:00 AM, Biddiscombe, John A. <<a href="mailto:biddisco@cscs.ch"><span style="color:windowtext;text-decoration:none">biddisco@cscs.ch</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText">>> The piston plugin appears to be working, and I'm able to select a dataset, "send to piston', and then "get from piston', however when I put a breakpoint in the piston mapper and check the rendering, it always stops in RenderOnCPU.<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>> I'd like to see the RenderOnGPU working. I poked around to see if there's an option in PistonRepresentation, (or even a PistonView) which might be activated which would trigger the GPU rendering activity, but couldn't find a way to
do it (without experimenting with code changes).<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>> Is there a combination of actions which displays using the GPU buffer objects.<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>> NB. PistonContour produces an output, slice and threshold produce empty results (so far).<o:p></o:p></p>
<p class="MsoPlainText">>> NB. Test machine has very old cuda support, will experiment on newer one if GPU render is possible.<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>> Thanks again<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>> JB<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>> -----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">>> From: David E DeMarle [<a href="mailto:dave.demarle@kitware.com"><span style="color:windowtext;text-decoration:none">mailto:dave.demarle@kitware.com</span></a>]<o:p></o:p></p>
<p class="MsoPlainText">>> Sent: 16 January 2013 19:49<o:p></o:p></p>
<p class="MsoPlainText">>> To: Biddiscombe, John A.<o:p></o:p></p>
<p class="MsoPlainText">>> Cc: <a href="mailto:paraview-developers@paraview.org">
<span style="color:windowtext;text-decoration:none">paraview-developers@paraview.org</span></a><o:p></o:p></p>
<p class="MsoPlainText">>> Subject: Re: [Paraview-developers] piston in 3.98<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>> Use piston sha 2913c77 for 3.98.<o:p></o:p></p>
<p class="MsoPlainText">>> Use piston sha b50cf296 for current master.<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>> David E DeMarle<o:p></o:p></p>
<p class="MsoPlainText">>> Kitware, Inc.<o:p></o:p></p>
<p class="MsoPlainText">>> R&D Engineer<o:p></o:p></p>
<p class="MsoPlainText">>> 21 Corporate Drive<o:p></o:p></p>
<p class="MsoPlainText">>> Clifton Park, NY 12065-8662<o:p></o:p></p>
<p class="MsoPlainText">>> Phone: 518-881-4909<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>> On Wed, Jan 16, 2013 at 1:06 PM, Biddiscombe, John A. <<a href="mailto:biddisco@cscs.ch"><span style="color:windowtext;text-decoration:none">biddisco@cscs.ch</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText">>>> I wanted to try a cuda based (depth) sort, then using interop, draw
<o:p></o:p></p>
<p class="MsoPlainText">>>> polygons using opengl in a custom painter - this would save a
<o:p></o:p></p>
<p class="MsoPlainText">>>> transfer from cpu-gpu on every frame.<o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>> Piston seems to have some interop facilities embedded, but I
<o:p></o:p></p>
<p class="MsoPlainText">>>> couldn't build the vtkAcceleratorsPiston using the (piston) version from github.<o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>> Is piston working in 3.98? and if so, should I use a different
<o:p></o:p></p>
<p class="MsoPlainText">>>> version than the github one.<o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>> Thanks for any info.<o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>> JB<o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>> --<o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>> John Biddiscombe, email:biddisco @.at.@ cscs.ch<o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>> <a href="http://www.cscs.ch/"><span style="color:windowtext;text-decoration:none">http://www.cscs.ch/</span></a><o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>> CSCS, Swiss National Supercomputing Centre | Tel: +41 (91)<o:p></o:p></p>
<p class="MsoPlainText">>>> 610.82.07<o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>> Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82<o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
<p class="MsoPlainText">>>> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">>>> Paraview-developers mailing list<o:p></o:p></p>
<p class="MsoPlainText">>>> <a href="mailto:Paraview-developers@paraview.org"><span style="color:windowtext;text-decoration:none">Paraview-developers@paraview.org</span></a><o:p></o:p></p>
<p class="MsoPlainText">>>> <a href="http://public.kitware.com/mailman/listinfo/paraview-developers">
<span style="color:windowtext;text-decoration:none">http://public.kitware.com/mailman/listinfo/paraview-developers</span></a><o:p></o:p></p>
<p class="MsoPlainText">>>><o:p> </o:p></p>
</div>
</body>
</html>