Skip to content

Reference

The authors acknowledge that naming conventions and input style formats for numgeo are based on those used by Abaqus1, a proprietary, general purpose finite element code.

The numgeo input file basically consists of two sections: a model definition Section describing the geometry and boundary conditions of the problem and one or more steps defining the loads:

input_file_name.inp

** Add a short description of the problem.
** This has no effect on the output
** and only serves for identification

Model definition

Step definition(s)

* End Input

All input is preceded by keywords, which all start with an asterisk (*), indicating the kind of data which follows. Detailed information on every keyword is given in the subsequent sections. In the following, a brief description of the structure model and step definition sections is given.

Upper vs lower case

The numgeo input file is case-insensitive - use upper and lower cases as you wish.

Blanks and tab stops

Blanks are ignored in the numgeo input file - use them to clarify your input file as you wish. Caution: tab stops are not automatically translated to blanks and should always be avoided.

Comments

Use comments and blank lines to clarify your input file - both will be ignored by numgeo. Comments start with ** and can be placed at the beginning of a line or somewhere within a line:

  • Example 1:

    ** This is a line comment. The entire line will be ignored.

  • Example 2:

    *Amplitude, name=name1, type=tabular ** This is an inline comment after a valid keyword

Model definition

The model definition Section starts at the beginning of the file and ends at the occurrence of the first *step statement.

The first statement of the model definition is the *node statement (see Node), followed by the node definitions.

Next, the elements are defined using the element keyword (see input_element) and listing for each element its type, which nodes belong to the element and in what order. Multiple node and *element statements are possible.

Nodes and elements can be grouped into sets using the keywords nset (see input_nset) and elset (see input_elset) respectively.

Next, a material and other properties are assigned to an element set by means of the keyword card solid section (input_solid_section). Subsequent, the assigned properties have to be defined, in this example, a material is defined using the material keyword. Other properties such as soil-water-retention curves etc. may follow. See the "Property:" sections (input_material ff) for more details.

The Amplitude and Initial conditions keywords are not mandatory. More details are given in input_amplitude and input_initial.

The definition of boundary conditions (*Boundary, see input_boundary) in the model definition Section may be skipped, but has then to be given during the first step definition.

*Node
n1, x1, y1, z1
n2, x2, y2, z2

*Element, type = ...
e1, n1, n2, n3, ...

*Nset, name = ...

*Elset, name = ...

*Solid Section, ...

*Material, name = ...

[Other property definitions]

*Amplitude, name = ...

*Initial conditions, ...

*Boundary

  1. For more information visit: https://www.3ds.com/de/produkte-und-services/simulia/produkte/abaqus/