abaqus inp file

393 views
Skip to first unread message

Hao Wang

unread,
Apr 26, 2016, 5:41:31 PM4/26/16
to moose-users
Hello everyone,

I'm trying to use a .inp file for Mesh. When I try to run the simulation, it gives a error message "Unsupported order: 257". I'm using CPS3 element type, it changes to TRI3 when goes to libMesh. There's a case relates to TRI3 element type in fe_lagrange.C file, everything seems fine. I don't know how to solve this error.

Another question I notice is, when I create a node set in ABAQUS, its format is 
*Nset, nset=XXX
 2, 24, 1     (from element 2 to element 24, by increment 1)
but in MOOSE it will be just be element 1, 2 and 24. Maybe this is something in file reading. I just type all the element IDs, but it's a problem if I have a large a mount of elements.

Peterson, JW

unread,
Apr 27, 2016, 10:34:32 AM4/27/16
to moose-users
I don't think our Abaqus reader currently supports this format for generating node sets.

Could you send me your input file directly?  I will try and take a look...

Thanks, 
John

Hao Wang

unread,
Apr 27, 2016, 12:47:37 PM4/27/16
to moose-users
Hi John,

Thanks for reply. Here's the input file, I just try to modify an example input file and model it by myself.

Thanks,
Hao

在 2016年4月27日星期三 UTC-4上午10:34:32,John Peterson写道:
inptest.i
inptest.inp

Peterson, JW

unread,
Apr 27, 2016, 12:54:18 PM4/27/16
to moose-users
On Wed, Apr 27, 2016 at 10:47 AM, Hao Wang <ramhi...@gmail.com> wrote:
Hi John,

Thanks for reply. Here's the input file, I just try to modify an example input file and model it by myself.

Thanks.  None of the Nsets in this file seem to be the auto-generated kind:

*Nset, nset=claddingin, instance=CPI-1
  1,  2,  8,  9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21
 22, 23, 24, 25, 26, 27, 28
*Nset, nset=claddingout, instance=CPI-1
  3,  4, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42
 43, 44, 45, 46, 47, 48, 49
*Nset, nset=fuelout, instance=CPI-1
  5,  7, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87
 88, 89, 90, 91, 92
*Nset, nset=origin, instance=CPI-1
 6,

Unless I misunderstand the problem, MOOSE can already read this type of Nodeset.

--
John

Hao Wang

unread,
Apr 27, 2016, 1:06:20 PM4/27/16
to moose-users
Yes, I changed the format of this file, so MOOSE can read it correctly. But when I try to run simulation, it gives me error message "Unsupported order: 257". I don't know how to solve this. It comes from  'fe_lagrange.C' file, I saw a case relates to TRI3 element type there, so I don't know why it gives this error message.

Thanks,
Hao

在 2016年4月27日星期三 UTC-4下午12:54:18,John Peterson写道:

Peterson, JW

unread,
Apr 27, 2016, 1:15:30 PM4/27/16
to moose-users
On Wed, Apr 27, 2016 at 11:06 AM, Hao Wang <ramhi...@gmail.com> wrote:
Yes, I changed the format of this file, so MOOSE can read it correctly. But when I try to run simulation, it gives me error message "Unsupported order: 257". I don't know how to solve this. It comes from  'fe_lagrange.C' file, I saw a case relates to TRI3 element type there, so I don't know why it gives this error message.

You can't use SECOND, LAGRANGE with TRI3 elements:

[GlobalParams]
  order = SECOND
  family = LAGRANGE
[]


--
John

Peterson, JW

unread,
Apr 27, 2016, 1:17:49 PM4/27/16
to moose-users
BTW, please also send a version of your input file that uses the short-hand Nset notation, I'd like to test that as well.

--
John

Hao Wang

unread,
Apr 27, 2016, 5:02:19 PM4/27/16
to moose-users
Thanks for your help, John. I see the mistake, that's the point. Here's one inp file I used before, it's just one part of the model. I tried many times, and find something. It seems I can only creat node sets (sets based on element and geometry seems have some problems) in Abaqus to make it readable for MOOSE.

在 2016年4月27日星期三 UTC-4下午1:15:30,John Peterson写道:
inptest.inp
Reply all
Reply to author
Forward
0 new messages