<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=koi8-r">
<meta name="Generator" content="Microsoft Word 14 (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: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;}
@font-face
        {font-family:"MS PGothic";
        panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
        {font-family:"\@MS PGothic";
        panose-1:2 11 6 0 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        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
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"MS PGothic","sans-serif";
        mso-fareast-language:JA;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";
        mso-fareast-language:EN-US;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";
        mso-fareast-language:EN-US;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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 bgcolor="white" lang="NL" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">The example you give describes very well the purpose of our interface elements. We insert such an element to model the discontinuity, and hence the element consists of two ‘sides’ each connected
 to one of the regular elements between which the discontinuity exists. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:JA">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:JA"> John Platt [mailto:jcplatt@dsl.pipex.com]
<br>
<b>Sent:</b> Tuesday, April 05, 2011 10:04 AM<br>
<b>To:</b> Andreas Buykx; vtk-developers@vtk.org<br>
<b>Subject:</b> Re: [vtk-developers] interface elements<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">Andreas,</span><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">You might like to consider creating separate unstructured grids for your elements depending on their visual display characteristics. For example, a
 mass element could be shown as a sphere with diameter proportional to the mass. Actors for each sub grid can then be added to a prop collection or assembly. You can also make each grid share the same points and point data even though they will be "oversize"
 for the sub grids. However, this does lead to greater programming complexity.</span><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">If any of your point data is discontinuous, for example, stress components between dissimilar materials, you should ponder this problem at an early
 stage.</span><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">John.</span><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">----- Original Message -----
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:#E4E4E4"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">From:</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">
<a href="mailto:A.Buykx@tnodiana.com" title="A.Buykx@tnodiana.com">Andreas Buykx</a>
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">To:</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">
<a href="mailto:vtk-developers@vtk.org" title="vtk-developers@vtk.org">vtk-developers@vtk.org</a>
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">Sent:</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA"> Monday, April 04, 2011 1:38 PM<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA">Subject:</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-language:JA"> [vtk-developers] interface elements<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">Our finite-element application has ‘interface elements’ which are used to model discontinuities between ‘conventional’ elements. We would like to be able to visualize these as transparent elements with one or more lines
 connecting the sides of the interface element. For this we need to filter such elements and process them in a proper way. What would the preferred way of discriminating between interface and conventional elements be? Should we add a boolean attribute to each
 cell specifying whether it is an interface element?</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Thanks,</span><o:p></o:p></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:NL">Andreas Buykx</span></b><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:NL">Senior Software Engineer</span><o:p></o:p></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.5pt;font-family:"Arial","sans-serif";color:#CB2027;mso-fareast-language:NL">TNO DIANA BV
</span></b><o:p></o:p></p>
<p class="MsoNormal"><i><span lang="EN-US" style="font-size:8.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:NL">Software Developers and Analysis Consultants for Civil and Geotechnical Engineering
</span></i><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:NL">Delftechpark 19a, 2628 XJ, Delft, The Netherlands
</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:NL">Tel: +31 88 34262 15 (Direct)
</span><span lang="EN-US" style="color:black;mso-fareast-language:NL"> Tel: +31 88 34262 00 (Switchboard)  +31 88 34262 99 (Fax)
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:NL"><a href="http://tnodiana.com/"><span lang="EN-US">http://tnodiana.com</span></a></span><b><i><span style="font-size:9.0pt;mso-fareast-language:NL">
</span></i></b><o:p></o:p></p>
<p class="MsoNormal"><b><i><span lang="EN-US" style="font-size:9.0pt;mso-fareast-language:NL">…be green keep it on screen</span></i></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Courier New";mso-fareast-language:JA">____________________________________________________________<br>
TNO DIANA BV is a limited liability company registered in the trade register of the Chamber of Commerce as TNO DIANA BV with registered number 27252655.<br>
</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Courier New";mso-fareast-language:JA">____________________________________________________________<br>
This e-mail and its contents are subject to the DISCLAIMER at </span><span style="font-size:12.0pt;font-family:"Courier New";mso-fareast-language:JA"><a href="http://tnodiana.com/content/Disclaimer"><span lang="EN-US">http://tnodiana.com/content/Disclaimer</span></a></span><span lang="EN-US" style="font-size:12.0pt;font-family:"Courier New";mso-fareast-language:JA"><br>
____________________________________________________________</span><span lang="EN-US" style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA">
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US" style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA">_______________________________________________<br>
Powered by </span><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><a href="http://www.kitware.com"><span lang="EN-US">www.kitware.com</span></a></span><span lang="EN-US" style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><br>
<br>
Visit other Kitware open-source projects at </span><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><a href="http://www.kitware.com/opensource/opensource.html"><span lang="EN-US">http://www.kitware.com/opensource/opensource.html</span></a></span><span lang="EN-US" style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
</span><span style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><a href="http://www.vtk.org/mailman/listinfo/vtk-developers"><span lang="EN-US">http://www.vtk.org/mailman/listinfo/vtk-developers</span></a></span><span lang="EN-US" style="font-size:12.0pt;font-family:"MS PGothic","sans-serif";mso-fareast-language:JA"><o:p></o:p></span></p>
</blockquote>
</div>
<font face="monospace">____________________________________________________________<br>
TNO DIANA BV is a limited liability company registered in the trade register of the Chamber of Commerce as TNO DIANA BV with registered number 27252655.<br>
____________________________________________________________<br>
This e-mail and its contents are subject to the DISCLAIMER at http://tnodiana.com/content/Disclaimer<br>
____________________________________________________________</font></body>
</html>