<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div></div>
<div>Hi. </div>
<div>I agree with both feature request but I can tell you right away that at least with respect to the material property you will not find much support. We had a method like that for a boundary id but that was now removed. The argument is that this data can
be stored by the user using the index set or the persistent container like your computational data. What you of course still need for the readers is to export the info from the file for the user. </div>
<div>Best </div>
<div>Andreas </div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-size:10px; color:#575757">Sent from Samsung Mobile</div>
</div>
</div>
<br>
<br>
-------- Original message --------<br>
From: Aleksejs Fomins <br>
Date:18/12/2014 12:55 (GMT+01:00) <br>
To: Dune <br>
Subject: [Dune] CurvilinearGridAPI: Implementation of EntityTags and BoundaryIterators
<br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Dear Dune,<br>
<br>
We are currently in the process of implementing the GridAPI for the<br>
curvilinear grid. While doing this, we realise that there is a certain<br>
functionality of the API which is currently not present, but would be<br>
very useful for the users. We wish to implement it, and ask for your<br>
suggestion on how best to do it<br>
<br>
1) We require a tag (integer) associated with each entity. This tag, for<br>
example, can contain the information about the material property of the<br>
entity. So far, this information was stored in DGF and accessed via the<br>
GridPtr.parameters() operation. However, we suggest that this<br>
information is a necessity for some users regardless of the mesh format<br>
and the reader used. Currently, we have a parallel GMSH reader, which<br>
reads the curvilinear grid in parallel and stores information associated<br>
with the elements (including the tag) within the CurvilinearGrid. The<br>
only question is, which way would<br>
the community prefer to access this information. We suggest to add a<br>
method EntityTag to the entity class of CurvilinearGrid, which would<br>
return the associated integer. We appreciate your suggestions<br>
<br>
2) There is a whole set of calculations that can be performed by<br>
iterating over the boundary of the grid, be it domain boundary or<br>
interprocessor boundary. In our electromagnetic code, to this point we<br>
have used the EntityIterator->IntersectionIterator->boundary() and<br>
->neighbor(), thus looping over all elements, then over all<br>
intersections of the element, and only performing certain operations if<br>
the faces of the element were not the internal faces. This operation<br>
could be significantly accelerated, if it was possible to directly<br>
iterate over DomainBoundaries and/or ProcessBoundaries. Is there<br>
currently a way to perform this operation. If not, then we would like to<br>
construct such iterators in CurvilinearGrid. We suggest classes<br>
DomainBoundaryIterator and ProcessBoundaryIterator. We appreciate your<br>
suggestions<br>
<br>
Regards,<br>
Aleksejs Fomins<br>
<br>
<br>
<br>
<br>
</div>
</span></font>
</body>
</html>