Abaqus mesh format

252 views
Skip to first unread message

jinlin.niu

unread,
Mar 20, 2017, 8:47:19 AM3/20/17
to moose-users
Hello all,
    Since MOOSE supports reading and writing a large number of formats, I try a Abaqus .inp format which is from a ICEM mesh. But MOOSE tells me "vtkExodusIIReaderPrivate (0x488d450): Unable to read database parameters
    My mesh file is "project3.inp" in attachment.
    So, I want to know the reason.
    Thank you!

project3.inp

Slaughter, Andrew E

unread,
Mar 20, 2017, 10:45:05 AM3/20/17
to moose...@googlegroups.com
Can you also send your input file?

--
You received this message because you are subscribed to the Google Groups "moose-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moose-users+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/e7f813f6-5414-4761-bae0-dcc6f279380e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Peterson, JW

unread,
Apr 3, 2017, 11:58:27 AM4/3/17
to moose-users
On Mon, Mar 20, 2017 at 6:47 AM, jinlin.niu <niu...@gmail.com> wrote:
Hello all,
    Since MOOSE supports reading and writing a large number of formats, I try a Abaqus .inp format which is from a ICEM mesh. But MOOSE tells me "vtkExodusIIReaderPrivate (0x488d450): Unable to read database parameters
    My mesh file is "project3.inp" in attachment.


The error message above doesn't make sense to me... I don't know why an ExodusII reader object would be getting invoked to read an Abaqus file.  This error is from Peacock I'm guessing?

That said, your Abaqus input file *should* work with MOOSE after some minor modifications:

Change:

"TYPE=S4" -> "TYPE=CPE4" 

and 

"TYPE=B31" -> "TYPE=T3D2"

everywhere they appear.

The S4 and B31 element types correspond to four-noded shell and two-noded beam elements, respectively, and are currently not supported by the Abaqus reader in libmesh. 

I don't see why we couldn't just treat them as the corresponding types when reading the file in, though, so I will probably patch the Abaqus reader to support this.

-- 
John
Reply all
Reply to author
Forward
0 new messages