<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Paul,</p>
<p>My own simulation software allows non-sequential, but unique
assignment of user-specified ID's for Points and Cells. (It is
user friendly, and requires and provides a wealth of datum
checking to see if the input datum set is logically connected.) <br>
</p>
<p>For what it is worth, the EnSight format supports user-assigned
Point and Cell ID's. <br>
</p>
<p>HOWEVER, the ParaView EnSight Reader which in all other respects
appears to be bullet proof and supports arbitrary n-vertex
polyhedral finite elements that my software uses, simply skips the
reading and storing of the user-assigned Point and Cell ID's.</p>
<p> (I rely heavily on ParaView for post processing and will
continue to write out the Point and Cell ID's to the
EnSight-formatted simulation datum set in the hope that some day
ParaView will accept and make use of the Point and Cell ID's. )<br>
</p>
<p>A possible solution may be the following for identifying Cells --
my software writes out Material Model user-assigned ID's "MatID"
as Cell data. The software's EnSight Writer uses the EnSight
Part-construct to create a "graphically displayable object" for
each domain based on a common value for MatID. The user, planning
ahead, can artificially give one or more Cells a unique MatID.
Then ParaView's Extract Block filter allows any combination of
material domains to be selected for further
processing/examination.</p>
<p>The attached image is a two-cell example. (Two independent finite
elements with different Mat ID's and the same material properties
but with different large-strain formulations each subjected to the
same strain loop).</p>
<p>Sam Key<br>
</p>
<br>
<div class="moz-cite-prefix">On 5/5/2018 3:10 AM,
<a class="moz-txt-link-abbreviated" href="mailto:paul.carrico@free.fr">paul.carrico@free.fr</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8c03825224d04612d323bd65d4d9781d@free.fr">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>Dear All,</p>
<p>This email is an echo of a previous one where I noticed that
for XDMF format, Node Id and Element one are not explicitely
provided (for performance issue I guess); writing an interface
for renumbering topology (connectivity), datasets and so on is
not a problem by itself (jus more work), but rather the fact
that information's are lost (information's from the solver based
on the original mesh for example).</p>
<p>Thus I'm having a look to Exodus ii format and how I can use y
h5 file (through netCDF I guess and not directly) ... if I'm
right it allows nodes/elements Id's.</p>
<p>Compared to Xdmf, does somebody want to share his
feedback? (limitations, implementation, performance,
parallelisation, and so on)</p>
<p>Thanks for any help</p>
<p>Regards</p>
<p>Paul</p>
<p><br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>
Visit other Kitware open-source projects at <a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
Please keep messages on-topic and check the ParaView Wiki at: <a class="moz-txt-link-freetext" href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a>
Search the list archives at: <a class="moz-txt-link-freetext" href="http://markmail.org/search/?q=ParaView">http://markmail.org/search/?q=ParaView</a>
Follow this link to subscribe/unsubscribe:
<a class="moz-txt-link-freetext" href="https://public.kitware.com/mailman/listinfo/paraview">https://public.kitware.com/mailman/listinfo/paraview</a>
</pre>
</blockquote>
<br>
</body>
</html>