[MOAB-dev] mbconvert from abaqus to h5m

[Grindeanu, Iulian R.]

Hi Jake,
It is still not clear what do you plan to do with the h5m file. Will you use moab to read it back? 
 
Right now, as I said before, it is trying to read part or assemblies, and it is creating a hierarchy, using sets in moab,
that encapsulates also information from "*NSET"s and "*ELSET"s.
We can probably change it to read directly nodes and elements, without searching first for parts and assemblies, and
then creating the sets.

We are also saving some attributes/tags to the sets, like type and name.

prism 15 and hexa 20 are currently skipped

I started a branch, we will need to work more on it.

https://bitbucket.org/fathomteam/moab/pull-request/105/abaqus-reader-fixes

Iulian

________________________________________
From: Jacob Hochhalter [Jacob.D.Hochhalter at nasa.gov]
Sent: Wednesday, April 22, 2015 8:48 AM
To: Grindeanu, Iulian R.; moab-dev at mcs.anl.gov
Subject: Re: [MOAB-dev] mbconvert from abaqus to h5m

Hi Iulian,

I would like to use the converter to translate an abaqus mesh
representation to h5m.  I only am concerned with the mesh:  nodal
coordinates, element connectivity, and the associated sets.  I am
attaching a zip file which contains 6 small inp files that you could use
for testing, which represent commonly used element topologies.
Translation of the information under the following blocks would be
sufficient (for me):  *Node, *Element,*Nset, *Elset.

I wrote out the inp files from the ABAQUS CAE. There is one option that
I chose within ABAQUS that is useful. Inside the 'Model->Attributes'
menu in ABAQUS, one can select a check box that says "Do not use parts
and assemblies in input files" (as shown in the attached image).  Having
"PART" and "ASSEMBLY" info in the .inp file complicates mesh translation
since one would need to aggregate & assimilate the node and element
numbering of all the possible parts & assemblies.  By making the
selection shown in the attached image, ABAQUS will take care of all that
before writing the .inp file, combining the various parts and assemblies
into a single coherent mesh description.  I do not think there would be
any loss of generality for MOAB in enforcing that this option be
selected for .inp files that mbconvert uses, and it would certainly make
the translation of abaqus meshes much simpler and robust.

Hope this helps!  Let me know if you have any other questions/thoughts.

- Jake

On 04/22/2015 09:18 AM, Grindeanu, Iulian R. wrote:
> Hello Jake,
> What do you plan to do with this converter?
> How did you generate the abaqus input file?
> It is clear this reader needs more work, but we need to understand the context, and maybe you can send us some input files you would be interested in converting.
>
> Thanks,
> Iulian
>
> ________________________________________
> From: moab-dev-bounces at mcs.anl.gov [moab-dev-bounces at mcs.anl.gov] on behalf of Jacob Hochhalter [Jacob.D.Hochhalter at nasa.gov]
> Sent: Tuesday, April 21, 2015 12:56 PM
> To: moab-dev at mcs.anl.gov
> Subject: [MOAB-dev] mbconvert from abaqus to h5m
>
> Hello,
>
> I would like to use the mbconvert tool to translate abaqus '.inp' files
> to '.h5m' files.  I have tried the following command:
>
> mbconvert -g tet4.inp tet4.h5m
>
> on moab 4.6 and 4.8 (tet4.inp is attached), but both return '.h5m' files
> without any mesh data.
>
> 'mbconvert -l' returns:
>
> Format  Description                    Read  Write  File Name Suffixes
> ------  -----------------------------  ----  ----- ------------------
> ...
> Abaqus mesh  ABAQUS INP mesh format    yes     no  abq
> ...
>
> which makes me think I should be able to run the conversion.
>
> Am I missing something, or is this not yet functional?
>
> Thanks,
> - Jake