<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 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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Consolas;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Consolas;color:#1F497D">Vijay, thanks a lot for the update. It’s not a problem<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Consolas;color:#1F497D">between now and early January 2015, but it would quickly<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Consolas;color:#1F497D">turn into an “existential crisis” after that.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Consolas;color:#1F497D">(And it wasn’t clear, if it was just my mistake or a deeper<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Consolas;color:#1F497D">issue.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Consolas;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Consolas;color:#1F497D">Thanks for all the hard work.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Consolas;color:#1F497D">G.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Consolas;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:Consolas;color:#1F497D"><o:p> </o:p></span></a></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Vijay S. Mahadevan [mailto:vijay.m@gmail.com]
<br>
<b>Sent:</b> Wednesday, December 17, 2014 10:17 AM<br>
<b>To:</b> Gerd Heber<br>
<b>Cc:</b> MOAB dev<br>
<b>Subject:</b> Re: [MOAB-dev] DMMoabOutput<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Gerd, sorry about the delay. We have an upcoming release and so I haven't had time to push a clean fix for this. I will be looking at this today and will let you know when the branch is ready.
<o:p></o:p></p>
<p>Thanks for your patience. <o:p></o:p></p>
<p>Vijay<o:p></o:p></p>
<div>
<p class="MsoNormal">On Dec 17, 2014 9:14 AM, "Gerd Heber" <<a href="mailto:gheber@hdfgroup.org">gheber@hdfgroup.org</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Any other thoughts? (This is a real showstopper for me...)<br>
<br>
G.<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:moab-dev-bounces@mcs.anl.gov">moab-dev-bounces@mcs.anl.gov</a> [mailto:<a href="mailto:moab-dev-bounces@mcs.anl.gov">moab-dev-bounces@mcs.anl.gov</a>] On Behalf Of Gerd Heber<br>
Sent: Monday, December 15, 2014 6:59 AM<br>
To: MOAB dev<br>
Subject: Re: [MOAB-dev] DMMoabOutput<br>
<br>
No iMesh here. The tags are created as dense tags via get_tag_handle/tag_set_data.<br>
<br>
G.<br>
<br>
-----Original Message-----<br>
From: Grindeanu, Iulian R. [mailto:<a href="mailto:iulian@mcs.anl.gov">iulian@mcs.anl.gov</a>]<br>
Sent: Saturday, December 13, 2014 9:14 AM<br>
To: Vijay S. Mahadevan; Gerd Heber<br>
Cc: MOAB dev<br>
Subject: RE: [MOAB-dev] DMMoabOutput<br>
<br>
The problem is the type of the tags<br>
Probably the new tags are created with iMesh_createTag() method from iMesh This method creates sparse tags (I don't remember why it is not sparse by default; maybe to be more general) In order to create a dense tag with iMesh, you need to use iMesh extensions
method<br>
<br>
iMesh_createTagWithOptions<br>
<br>
something like<br>
iBase_TagHandle tagh;<br>
iMesh_createTagWithOptions(mesh, "dum", "moab:TAG_STORAGE_TYPE=DENSE", 1, iBase_DOUBLE, &tagh, &err, 3, 27);<br>
<br>
<br>
With the right options, the tag will be dense, and saved in the entities portion of the h5m file<br>
<br>
<br>
Iulian<br>
<br>
<br>
________________________________________<br>
From: <a href="mailto:moab-dev-bounces@mcs.anl.gov">moab-dev-bounces@mcs.anl.gov</a> [<a href="mailto:moab-dev-bounces@mcs.anl.gov">moab-dev-bounces@mcs.anl.gov</a>] on behalf of Vijay S. Mahadevan [<a href="mailto:vijay.m@gmail.com">vijay.m@gmail.com</a>]<br>
Sent: Friday, December 12, 2014 10:31 PM<br>
To: Gerd Heber<br>
Cc: MOAB dev<br>
Subject: Re: [MOAB-dev] DMMoabOutput<br>
<br>
Gerd, this is possibly a bug in MOAB writer. I'll test your input file and see if I can replicate the issue on output. DMMoabOutput does not do anything else explicitly other than calling save on the Core object itself.<br>
<br>
Iulian, can you also take a look at this to see if you can replicate the issue. I want to make sure that the problem is not just due to mixed elements + element tag combinations.<br>
<br>
Vijay<br>
<br>
On Fri, Dec 12, 2014 at 7:24 AM, Gerd Heber <<a href="mailto:gheber@hdfgroup.org">gheber@hdfgroup.org</a>> wrote:<br>
> Maybe I'm doing something stupid, but I see some weird behavior from<br>
> DMMoabOutput. My input mesh is feawd.3.h5m. It has a mixture of Hex8<br>
> and Prism6 elements. I create a few nodal and element tags and call<br>
> DMMoabOutput to create feawd.out.h5m. The nodal tags look fine, but<br>
> the element tags get written correctly only for the prisms.<br>
> Something gets written for the hex elements, but it gets written in<br>
> the wrong place (under /tstt/tags/ instead of /tstt/elements/Hex8/tags).<br>
> Another indicator that something fishy is going on is that the<br>
> GLOBAL_ID tag has disappeared from Hex8 in the output file.<br>
> Maybe another "protocol error"?<br>
><br>
> Thanks for your help.<br>
> G.<o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>