Abaqus import (*.inp file)

GiD Import/Export
1

I would like to know how to use correctly the option “Files > Import > Abaqus…” available since version 14.1.8d (developer version).

In version 14.1.8d when I choose this option, a window opens and I can choose files with *.inp extension. A kind of code runs, and in the end I can’t see the mesh anywhere.

In version 14.1.9d when I choose this option, I can do the same as the previous step, but in the end, I receive an error message.

What I am doing wrong?

PS: Next, I present the contents of the “test.inp” file, in case someone wanted to reproduce my steps.

*Heading
** Job name: Job-1 Model name: Model-1
** Generated by: Abaqus/CAE 2017
*Preprint, echo=NO, model=NO, history=NO, contact=NO
**
** PARTS
**
*Part, name=Part-1
*Node
      1,           0.,           0.
      2,  0.200000003,           0.
      3,  0.400000006,           0.
      4,  0.600000024,           0.
      5,  0.800000012,           0.
      6,           1.,           0.
      7,           0.,  0.200000003
      8,  0.200000003,  0.200000003
      9,  0.400000006,  0.200000003
     10,  0.600000024,  0.200000003
     11,  0.800000012,  0.200000003
     12,           1.,  0.200000003
     13,           0.,  0.400000006
     14,  0.200000003,  0.400000006
     15,  0.400000006,  0.400000006
     16,  0.600000024,  0.400000006
     17,  0.800000012,  0.400000006
     18,           1.,  0.400000006
     19,           0.,  0.600000024
     20,  0.200000003,  0.600000024
     21,  0.400000006,  0.600000024
     22,  0.600000024,  0.600000024
     23,  0.800000012,  0.600000024
     24,           1.,  0.600000024
     25,           0.,  0.800000012
     26,  0.200000003,  0.800000012
     27,  0.400000006,  0.800000012
     28,  0.600000024,  0.800000012
     29,  0.800000012,  0.800000012
     30,           1.,  0.800000012
     31,           0.,           1.
     32,  0.200000003,           1.
     33,  0.400000006,           1.
     34,  0.600000024,           1.
     35,  0.800000012,           1.
     36,           1.,           1.
     37,           0.,   1.20000005
     38,  0.200000003,   1.20000005
     39,  0.400000006,   1.20000005
     40,  0.600000024,   1.20000005
     41,  0.800000012,   1.20000005
     42,           1.,   1.20000005
     43,           0.,   1.39999998
     44,  0.200000003,   1.39999998
     45,  0.400000006,   1.39999998
     46,  0.600000024,   1.39999998
     47,  0.800000012,   1.39999998
     48,           1.,   1.39999998
     49,           0.,   1.60000002
     50,  0.200000003,   1.60000002
     51,  0.400000006,   1.60000002
     52,  0.600000024,   1.60000002
     53,  0.800000012,   1.60000002
     54,           1.,   1.60000002
     55,           0.,   1.79999995
     56,  0.200000003,   1.79999995
     57,  0.400000006,   1.79999995
     58,  0.600000024,   1.79999995
     59,  0.800000012,   1.79999995
     60,           1.,   1.79999995
     61,           0.,           2.
     62,  0.200000003,           2.
     63,  0.400000006,           2.
     64,  0.600000024,           2.
     65,  0.800000012,           2.
     66,           1.,           2.
*Element, type=CPS4
 1,  1,  2,  8,  7
 2,  2,  3,  9,  8
 3,  3,  4, 10,  9
 4,  4,  5, 11, 10
 5,  5,  6, 12, 11
 6,  7,  8, 14, 13
 7,  8,  9, 15, 14
 8,  9, 10, 16, 15
 9, 10, 11, 17, 16
10, 11, 12, 18, 17
11, 13, 14, 20, 19
12, 14, 15, 21, 20
13, 15, 16, 22, 21
14, 16, 17, 23, 22
15, 17, 18, 24, 23
16, 19, 20, 26, 25
17, 20, 21, 27, 26
18, 21, 22, 28, 27
19, 22, 23, 29, 28
20, 23, 24, 30, 29
21, 25, 26, 32, 31
22, 26, 27, 33, 32
23, 27, 28, 34, 33
24, 28, 29, 35, 34
25, 29, 30, 36, 35
26, 31, 32, 38, 37
27, 32, 33, 39, 38
28, 33, 34, 40, 39
29, 34, 35, 41, 40
30, 35, 36, 42, 41
31, 37, 38, 44, 43
32, 38, 39, 45, 44
33, 39, 40, 46, 45
34, 40, 41, 47, 46
35, 41, 42, 48, 47
36, 43, 44, 50, 49
37, 44, 45, 51, 50
38, 45, 46, 52, 51
39, 46, 47, 53, 52
40, 47, 48, 54, 53
41, 49, 50, 56, 55
42, 50, 51, 57, 56
43, 51, 52, 58, 57
44, 52, 53, 59, 58
45, 53, 54, 60, 59
46, 55, 56, 62, 61
47, 56, 57, 63, 62
48, 57, 58, 64, 63
49, 58, 59, 65, 64
50, 59, 60, 66, 65
*Nset, nset="Rock 1", generate
  1,  66,   1
*Elset, elset="Rock 1", generate
  1,  50,   1
** Section: Section-1
*Solid Section, elset="Rock 1", material="Rock 1"
1.,
*End Part
**  
**
** ASSEMBLY
**
*Assembly, name=Assembly
**  
*Instance, name=Part-1-1, part=Part-1
*End Instance
**  
*Nset, nset=Loads, instance=Part-1-1
 61, 66
*Nset, nset=Set-3, instance=Part-1-1
 1,
*Nset, nset=line, instance=Part-1-1, generate
 1,  6,  1
*Elset, elset=line, instance=Part-1-1, generate
 1,  5,  1
*End Assembly
** 
** MATERIALS
** 
*Material, name="Rock 1"
*Elastic
 3e+07, 0.2
** 
** BOUNDARY CONDITIONS
** 
** Name: BC-1 Type: Displacement/Rotation
*Boundary
line, 2, 2
** Name: BC-2 Type: Displacement/Rotation
*Boundary
Set-3, 1, 1
** ----------------------------------------------------------------
** 
** STEP: Load
** 
*Step, name=Load, nlgeom=NO
Load
*Static
1., 1., 1e-05, 1.
** 
** LOADS
** 
** Name: Loads   Type: Concentrated force
*Cload
Loads, 2, -100.
** 
** OUTPUT REQUESTS
** 
*Restart, write, frequency=0
** 
** FIELD OUTPUT: F-Output-1
** 
*Output, field, variable=PRESELECT
** 
** HISTORY OUTPUT: H-Output-1
** 
*Output, history, variable=PRESELECT
*End Step
2

There is an small bug in the Abaqus mesh import plugin v 0.1
I attach an
Abaqus.zip (4.59 KB)
with a fixed 0.2 version

To use it must simply unzip at “\plugins\Import\pre”, replacing the current one.

You can see the content of the zip, there are two text files, the .xml with declarations of the plugin, and the .tcl with the scripting code to read the .inp files and create the mesh.

Your example could be read without problems with this plugin version.
If do you have problems with other examples send us a copy (can be sent privatelly if necessary)

Next GiD versions will include the updated plugin,

3

[quoteThere is an small bug in the Abaqus mesh import plugin v 0.1
I attach an Abaqus.zip with a fixed 0.2 version

To use it must simply unzip at “\plugins\Import\pre”, replacing the current one.

You can see the content of the zip, there are two text files, the .xml with declarations of the plugin, and the .tcl with the scripting code to read the .inp files and create the mesh.

Your example could be read without problems with this plugin version.
If do you have problems with other examples send us a copy (can be sent privatelly if necessary)

Next GiD versions will include the updated plugin,[/quote]

wow
really handy addon
I was looking for some workaround and found a gold plugging
thanks a lot

4

Hello! I want to import an ABAQUS .inp file, the type of element is C3D10. GiD verson is 14.0.1.
When I try to import, there is an error:

GiD_Mesh – node ‘1’ already exists
GiD_Mesh – node ‘1’ already exists
while executing
“GiD_Mesh create node $node_id [list $x $y $z]”
(procedure “Abaqus::ReadPreMesh” line 75)
invoked from within
“Abaqus::ReadPreMesh $filename”
(procedure “Abaqus::ReadPre0” line 15)
invoked from within
“Abaqus::ReadPre0 $filenames”
(procedure “Abaqus::ReadPre” line 5)
invoked from within
“Abaqus::ReadPre E:/ABAQUS2018/temp/practice/Job-1.inp”
(“eval” body line 1)
invoked from within
“eval $args”
(procedure “GidUtils::EvalAndEnterInBatch” line 3)
invoked from within
“GidUtils::EvalAndEnterInBatch Abaqus::ReadPre $filenames”
(procedure “Abaqus::ReadPreW” line 9)
invoked from within
“Abaqus::ReadPreW”
(menu invoke)

This is my inp file


Could you please help me? Thank you!
Job-1.zip (244 KB)

5

Does this mean that only one part can be imported at a time?

6

You are right, the plugin Abaqus 0.2 was not prepared for multiple parts that use for each part the same local ids for nodes and elements, and then become repeated ids.

Now we have implemented it:
Simply unzip this file
Abaqus.zip (5.03 KB)
with the version 0.3 or the abaqus plugin in the folder /plugins/Import/pre
replacing the previous copy.

7

Thank you very much! This version is OK. Excellent!

8

Hello! I used the plugin Abaqus to import the mesh. I created two sets (for the same part) in Abaqus by defining the keywords *Nset and *ELset. I want to store the information of the elements and nodes of these two sets in two layers, so as to define different properties. Can it be achieved by modifying Abaqus.tcl?

I also thought of another way. Through layer->send to->element, then by command. This can be achieved by entering the element number. But if there are many elements in the set, it is very troublesome. Can it be achieved by a command? For example, “1, 10, 1”, to select elements 1~10.

Thank you！

9

In fact I have already implemented a new version 0.4 of our Abaqus plugin that use the Nset and Elset Abaqus information and assign them to GiD groups
The group concept similar to layer, but an entity can belong to more than one group but is limited to belong to one layer (and the groups window contextual menu has an option to create+assign layers from groups and vice-versa)

If you install GiD 16.1.0d (the current last developer version it has this Abaqus plugin 0.4 version)
I attach also a copy here:
Abaqus-0.4.zip (5.71 KB)
And about the selection of GiD, in a command that is requiring a selection you can specify it with this syntax
1:10 25 27
to mean from 1 to 10 and the 25 and 27
there are more other selection syntax with filters, e.g. to select the entities of a layer can write
layer:
Read this page of the ‘reference manual’: https://gidsimulation.atlassian.net/wiki/spaces/GRM/pages/2385546385/Entity+selection

10

Thank you! I will try.

11

There is another problem, I did assembly of part-1 and part-2 in abaqus and translation of part-1. But when imported into GiD, part-1 is the position before the translation.
Does that mean that translation operations in abaqus are not valid in GiD?

12

I used the ‘set’ in ABAQUS to define some elements, which were placed in a ‘group’ after the inp file was imported into the GID. When I convert a group to a layer, it doesn’t include low entities. Right? Can I include them?

I also want to ask a question about pre-GID processing. Is there a tool for partition similar to abaqus in pre-GID processing?

Thank you very much!

13

As you pointed the tool ‘Groups to layers’ will create the layers from the selected groups (or all if any is selected)
with the strict entities of the group, won’t add to the layer other lower-entities

if do you also want that a layer has its dependencies can select these layers and in the contextual menu select
Send to->Self-dependencies
but take into account that an entity can belong to one, and only one, layer (but can belong to multiple groups)
e.g. a line shared by two surfaces in different layers cannot be in both layers simultaneously

I don’t know what is doing the ‘tool partition of Abaqus’.
In GiD for example you can use the macro button to send each ‘top-level’ entity to a new layer
top geometry to layers.png
or can send to a layer some entities and its dependent lower-entities

and while selecting surfaces or curves in the contextual menu the ‘Connected tangent’ command will add to the selection the entities connected with the current ones that are tangent with a tolerance angle (that could be set to 180 degrees for example to select all connected without take into account its normal)

14

Thank you! I will try.