What is Abaqus Explicit 1

Table of Contents

SURNAME

abaqus_info - abaqus_info

DESCRIPTION

ABAQUS program system (Version 5.7) Status: 04/21/98

(A) Overview
---------

1.
Brief description
1.1
ABAQUS modules
1.2
General
1.3
Areas of application
1.4
Element library
1.5
Material laws
1.6
special modeling options
1.7
Loads
1.8
miscellaneous
1.9
Restart incompatibility between version 5.6 and 5.7
1.10
Key features of version 5.7
1.11
New features of the ABAQUS products of version 5.7
2
Use of ABAQUS in the RRZN
2.1
General
2.2
Calling ABAQUS on the Sun cluster: SunAS and SunCS
2.3
ABAQUS script parameters
2.4
ABAQUS environment file
2.5
Runtime behavior of large FE models: memory and I / O
2.5.1
Main solver
2.5.2
Pre-processor (input processing)
2.6
ABAQUS post processing 2.6.1 ABAQUS / Post 2.6.1.1 Description of the script parameters 2.6.2 ABAQUS / Plot 2.6.2.1 Description of the script parameters
2.7
Initialization of ABAQUS
2.8
Examples for ABAQUS calls 2.8.1 ABAQUS / Standard 2.8.1.1 Description of the examples c1, c4 and c5 2.8.2 ABAQUS / Explicit
2.9
ABAQUS file name conventions
3
Utilities 3.1 ABAQUS Restart Translator (.res): abares
3.2
ASCII conversion of the result file (.fil): ascfil
3.3
Merging of two result files (.fil): append
3.4
Extraction of examples from archive files: fetch 3.5 ABAQUS online documentation: doc 3.6 Query of the example databases: findkeyword
4
Pre- and post-processing with MSC / PATRAN
4.1
Preprocessing
4.2
Post processing
5
documentation
6
Sample collection on the Sun cluster
7
ABAQUS status reports
8
ABAQUS release notes
9
care, support

1. Brief description

Program modules: ABAQUS / Standard, ABAQUS / Explicit ABAQUS / Post, ABAQUS / Plot
ABAQUS / Abares, ABAQUS / Ascfil, ABAQUS / Append, ABAQUS / Fetch

Distribution:
ABACOM, Aachen
Language:
FORTRAN 77

Further information on ABAQUS: http://www.hks.com/home.html http://www.hks.com/product-briefs.html

1.1 ABAQUS modules

ABAQUS / Standard: General finite element program with all analysis options except for non-linear dynamic analysis with the help of explicit time integration.

ABAQUS / Explicit: FE program system for non-linear, transient, dynamic analyzes of solids and structures with the help of explicit time integration, i.e. the dynamic equations are integrated time step by time step. Especially for problems with very large deformations, such as impact or short-term dynamic processes.

ABAQUS / Post: Interactive post-processor for ABAQUS with the following display options: undeformed and deformed configuration, contour and vector plots, display of contemporary history and XY plots of two variables as well as result animation (see Section 2.6.1)

ABAQUS / Plot: Conversion of the ABAQUS graphic files (.ppl and .mpl) into a PostScript file (.ps) for output on a laser printer or display on a graphic output device under Xwindow. (see chapter 2.6.2)

ABAQUS / Abares: Restart File (.res) Translator (see Section 3.1)

ABAQUS / Ascfil: Result File (.fil) Translator (see Section 3.2)

ABAQUS / Append: Combination of two result files (.fil) into a single file for further processing with ABAQUS / Post. (see chapter 3.3)

ABAQUS / Fetch: Extraction of examples from archive files according to the Example Problems Manuals (see Section 3.4)

1.2 General

ABAQUS is a finite element program system with which tasks from the areas of structural mechanics, heat conduction, acoustics, contact and coupling technology as well as soil mechanics can be dealt with. This FE package is particularly suitable for applications with large geometry and physical non-linearities, such as in forming processes. The widespread use of ABAQUS is mainly due to the versatility and independence of the element and material library, the great ability to handle non-linear forms of analysis and the variety in the modeling of contact problems as well as the possibility of integrating user routines. The following is a brief summary of the properties of ABAQUS.

1.3 Areas of application

a) structural mechanical calculations:

static and dynamic stress / strain analyzes geometrically linear and non-linear non-linear material (see material laws) fracture mechanics (J-integral calculation) bulges (lin. and non-linear), stability analyzes contact and impact problems elastomers with large expansions natural vibration problems, mode shapes response spectrum -Analysis
Time history analysis
Steady State Response Analysis acoustic calculations
Random Response Analysis
Soil mechanics (including pore pressure) Contact with viscous damping Creep and swell analysis Pore fluid flow
Mass diffusion
Composite shell application failure measurements
Underwater shock analysis
Crack propagation analysis

b) Heat calculation:

linear and non-linear
stationary and transient heat conduction, heat transfer, radiation application to analog potential problems (diffusion, seepage water, etc.)

c) Acoustics calculation:

Modeling dyn. Vibration problems including sound pressure coupled with structural mechanical model analysis

d) Interaction (coupling) problems for:

coupled temperature and displacement analysis coupled temperature and thermal stress analysis coupled structural mechanics and seepage water calculation coupled acoustic and structural vibration analysis coupled thermal-electrical analysis (joule heating)

1.4 Element library

There is an extensive modern element library with more than 200 elements; These include many special elements such as gap, mass, spring, damper and interface elements. The following summary gives a rough overview:

Spring elements
Bar elements
Beam elements (flat, spatial, curved) thick and thin shell elements 2D elements (plane stress / strain / axially symmetrical state)
3D elements (tetrahedron, cuboid, prism) tubular elements
rotationally symmetrical elements gap elements (for contact problems) interface elements (for contact and coupling problems) special elements (damping, drag chain, (point masses, rotational inertia) user-defined elements acoustic elements (one, two and three-dimensional) heat conduction elements ( one-, two- and three-dimensional) hydrostatic fluid elements Slide plane elements
Line spring elements (modeling of cracked shell structures
Finite Strain Shells with hyperelastic properties, axially symmetrical solid elements, manifolds

Element library for coupled analyzes

1.5 Material Laws

linear elastic materials non-linear elastic materials isotropic and anisotropic materials elasto-plastic materials (flow criteria from: Drucker-Prager, von Mises, Roscoe, Mohr-Coulomb, Ramberg-Osgood, ORNL theory, isotropic and kinematic hardening) creep
viscoelastic materials concrete model
temperature-dependent materials laws for: heat conduction, heat convection and radiation
porous medium (soil, rock, etc.) Clay plasticity model
Plasticity model with porous or linear elasticity user interface for own material definition permeability

1.6 special modeling options

linear and non-linear springs and dampers mass terms also in addition to the diagonals various coordinate systems combination of stiffening elements with any other elements
Simulation of the singularities of crack tips using isoparametic elements

1.7 loads

Each force can be applied over the time step or according to any given amplitude:

node-related loads:

Individual forces and moments Displacements, rotations, accelerations, temperatures and other field quantities

element-related loads:

even and uneven volume forces, pressure distributions
hydrostatic pressures
Centrifugal and Coriolis forces elastic bedding
Consequential charges

1.8 Other

Substructure technology (super elements) User interface (user subroutine) for the modeling of material laws, boundary and initial conditions, loads, user elements Pre- / Postprocessing with PATRAN or ABAQUS / Post Adding and removing elements INCLUDE option

1.9 Restart incompatibility between version 5.6 and 5.7

ABAQUS / Standard restart files are compatible between versions 5.6 and 5.7 for most analyzes.
ABAQUS / Explicit restart files are not compatible between version 5.6 and 5.7.

1.10 Key Features of Version 5.7

- Functional improvements in all ABAQUS products
- Performance improvement in the computing time requirement - Improvements in the contact analysis - Known program errors from version 5.6 have been corrected - Restart files between versions 5.6 and 5.7 are compatible with ABAQUS / Standard for most analyzes. Restart files for ABAQUS / Explicit are not compatible between versions 5.6 and 5.7 - Superelement Library files are compatible between versions 5.6 and 5.7. - Result files are compatible between versions 5.6 and 5.7 - Solver option (sparse or wavefront solver) possible at script level - New documentation is available with version 5.7 - Extended online documentation is also available

1.11 New features of the ABAQUS products of version 5.7

Detailed information can be found in the release notes; these are available as information files in both ASCII and PostScript format in the following directory:

Sun cluster:
/ opt / abaqus / abaqus57 / info

The following release notes files are available in this directory:

release_notes.ps: == Release Notes in PostScript format release_notes.txt: == Release Notes in ASCII format

The `ABAQUS Release Notes' manual is also available in the online documentation. (see chapter 3.5)

2 Use of ABAQUS in the RRZN
2.1 General

The RRZN has an academic license for the non-industrial use of ABAQUS. ABAQUS is installed on the SunCS (Sun Compute Server: Sun Sparc Ultra Enterprise 3000 with 1.5 GB of main memory) and on the SunAS (Sun Application Server: Sun Sparc Ultra 2). ABAQUS / Standard and ABAQUS / Explicit are available on the Sun cluster (SunAS and SunCS). The SunAS serves as a dialog computer for pre- and post-processing while the SunCS as a compute server carries out the FE analysis in batch mode.

Special memory requirements for very large FE models can be defined with the environment variables (file name «abaqus.env» in the $ HOME directory or in the current working directory of the user - e.g. the / work or / perm file system) the standard values ​​are overridden. (see chapters 2.4 and 2.5)

2.2 Calling ABAQUS on the SunAS

ABAQUS is called using the script command abaqus. With NQS a batch job is then automatically transferred to the compute server. For the initialization of the ABAQUS scripts see chap. 2.7.

Example: ABAQUS script call from SunAS

abaqus -jid job1 -bcl k

A batch job is placed in job class k. The job1.inp file contains the input data of the ABAQUS analysis; job1 is the job identifier. (see parameter description in section 2.3)

2.3 ABAQUS script parameters

ABAQUS is started when the user calls the execution procedure abaqus after calling init_abaqus once. This searches and evaluates up to 3 environment files in which the system parameters are set. The ABAQUS execution procedure generates one or two shell scripts id.com1 or id.com2, which initiate and execute the individual steps of the ABAQUS job. This section describes the parameters. Only the parameters relevant for the ABAQUS analysis have to be specified. A batch job is generated automatically. (see also ABAQUS / Standard User's Manual, Volume I, Chapter 3.2.1)

Parameter description:

Job Identifier
-jid required

Combination of any alphanumeric characters. Jobs that compute in the same directory at the same time must have different job identifications. All files that are generated by ABAQUS contain this identifier in their naming, followed by the extension .ext. (Explanation see chapter 2.9)

Input file
-inp optional (default: jid.inp)

File name with the input data for ABAQUS. Standard input file

is: jid.inp
The input file must be in the working directory.
ABAQUS modules
-p default = standard

Specification of the ABAQUS programs: standard for the FE system ABAQUS / Standard and explicit for the FE system ABAQUS / Explicit.

Oldjob Identifier -old optional

This option specifies the job identifier of a previous job (without file extension) with which a restart job can be started. This option is required if the * RESTART, * POST OUTPUT or * POST FILE option has been specified in the input file (.inp). These options read the restart (.res) and / or result file (.fil). The old job identifier must be different from the current job identifier.

Result file
-fil optional (default: append)

Option only for restart jobs. Specification affects whether an existing result file ("oldjob identifier.fil") should be extended or whether a new result file (-fil new) should be created. -Fil new is not allowed for ABAQUS / Explicit. Specification is only required for a * POST FILE analysis or a * RESTART, READ analysis to expand an old result file or to generate a new result file.

User subroutine
-us optional

Option to specify a FORTRAN source code file that contains all user subroutines for analysis. The file jid.f is compiled and integrated into the ABAQUS executable.

Fashion
-mod default = analysis

Program control option. The following options are currently available:

analysis
Carrying out a complete ABAQUS analysis (or a restart analysis).
datacheck
Only one data check run is carried out. All files for continuing an ABAQUS analysis (with mode continue) are saved.
continue
Continuation of the ABAQUS analysis after a data check run
doc
Online documentation
abares
Restart File Translator is activated. Translation of the binary restart file (.res or .rst) into a neutral binary format (.rnb) to continue the analysis on another computer system. Job is running in the background. (see also chapter 3.1)
ascfil
ASCII conversion of the result file (.fil). This possibility allows the postprocessing to be carried out on another computer system. (see chapter 3.2)

information Information text according to `Information Option 'is written to the .log file. There is no ABAQUS analysis. Job is running in the background.

findkeyword Query the ABAQUS sample database for keyword commands. The user can specify several ABAQUS keywords and receives a list of the input files that contain the specified keywords. Entering the keywords is expected via the keyboard. A blank line ends the input of the keywords. The job runs in the background. (See also the option parameter max - last parameter)

convert
This option is only available for ABAQUS / Explicit; The Convert option converts the ABAQUS / Explicit files (see Convert Option Parameters) into standard ABAQUS files after a previously performed ABAQUS / Explicit analysis with the options -mod analysis and -con no. Without file conversion, no results are available for postprocessing Disposition. The conversion can be carried out immediately after an analysis run (-mod analysis and -con yes) or as a separate job after an analysis run (-mod convert and -cop ...) in the background.
recover
This option is only available for ABAQUS / Explicit; the recover option causes a restart to be carried out at the last available step and increment in the state file. This option is intended for restarting after a system error in a previous analysis, e.g. after the following errors: CPU time limit or scratch or permfile disk space problems.
help
List of all ABAQUS scripts with their parameters. The information is written to the .log file. Job is running in the background.

Information option -inf optional

Option for the desired information text. This parameter is also effective with all options of the Mode parameter. The text is written to the .log file. The following options are currently available:

environment
All standard options of the environment file (abaqus.env in the ABAQUS installation directory) are listed.
local
Comments on the local installation are listed (recommendations, errors, etc.)
memory
Specification of the memory parameters. In the case of large FE models, it is necessary to adapt the user environment file (abaqus.env in the user's $ HOME or working directory). (see also chapter 2.5)
release
Release notes for the current ABAQUS version
status
Status report on the current ABAQUS version
Convert option
-con default = no

This option is only available for ABAQUS / Explicit; With the simultaneous option of -mod analysis and -con yes, it causes the analysis to be carried out with subsequent conversion of the results (required for postprocessing with ABAQUS / Post) in the same job.

Convert option parameter -cop default = all

This option is only available for ABAQUS / Explicit. Specification of the files to be converted.

restart
The ABAQUS / Explicit State file (.abq) and package file (.pac) are converted into a standard ABAQUS restart file (.res). This is only necessary if the restart file in ABAQUS / Post is to be used for contour plots, X-Y plots or deformed configurations.
select
The ABAQUS / Explicit selected results file (.sel) is converted into a standard ABAQUS results file (.fil).
Alles
The state, package and selected results files are converted.
Batch class
-bcl default = e
Specification of the batch classes:
e, k, l, nl, nm, wh
Double precision
-dp default = single

This option is only available for ABAQUS / Explicit; When using an explicit dynamic procedure, it enables the analysis to be carried out with double precision (64 bits): e.g. -dp double. Execution with double precision can also be activated with the help of the ABAQUS environment parameter explicit_precision = "double».

Globalmodel Results File Name -gm optional

This option is only available for ABAQUS / Standard. This specifies the results file of the global model data from which the results for the submodel analysis are interpolated. A file extension is not allowed. This option is required if the * SUBMODEL option or the * BOUNDARY, SUBMODEL option in the input file indicates that data should be read from the result file.

Maximum output for findkeyword
- max optional

Option to limit the number of sample files listed when searching for the keyword. The default value of max is 100.

ABAQUS / Standard Equation Solver - sol default = sparse

Option to select an equation solver for ABAQUS / Standard. Two options are available: `sparse 'or` wavefront'. The default is sol = sparse. (see also ABAQUS / Standard User's Manual, Volume I, Chapter 3.2.1)

2.4 ABAQUS environment file

The ABAQUS execution procedure reads environment files to define predefined system parameters that are used to execute an ABAQUS job. Three directories are searched for the environment file «abaqus.env» in the following order:

1. The RRZN-ABAQUS installation directory. The standard environment file is located here.

2. The user's $ HOME directory. This environment file is optional and overwrites any entries in the standard environment file.

3. The current working directory. This environment file is optional and overwrites any entries in the two previous files.

Entries in the environment file are always made in the form parameter = "value" (the value must be enclosed in double apostrophes). Comments are preceded by an exclamation mark, ie all characters that follow an exclamation mark are ignored. « value »must not contain an exclamation mark. Blank lines are also ignored. The integer values ​​in the following example are specified in 64-bit words.

Example of a user environment file:

!

!
USER ABAQUS ENVIRONMENT FILE! ! Memory request for a job class with 400 Mbytes! pre_memory = "12000000" pre_buffer = "4500000" standard_memory = "48000000" standard_buffer = "48000000" scratch = "/ tmp" explicit_precision = "single" split_dat = "yes" aux_scratch = "/ work / nhxxyyy" split_scratch = "40000000"! ! corresponds to 320 Mbytes in the / work / nhxxyyy directory for the split! Stiffness matrix jid.061

The parameters of the standard environment file are output using the following call of the ABAQUS script:

abaqus -jid xxx -mod information -inf environment

(see also ABAQUS / Standard User's Manual, Volume I, Chapter 3.4.1)

2.5 Runtime behavior of large FE models: memory and I / O problems

An ABAQUS job with a maximum of 165 Mbyte memory requirements (depending on the FE model size) is executed as standard. However, if a large FE model is running with only this memory requirement, ABAQUS will deal with this lack of memory in such a way that intensive I / O activities take place in the scratch directory. This is very ineffective and to improve this situation, as much data as possible must be kept in memory. A significant improvement in the runtime behavior can be achieved by newly specifying certain system parameters in the environment file and setting them with higher values. The following sections describe this change in detail.

2.5.1 Main Solver

The parameter «standard_memory» defines the maximum memory that can be used. The current memory required by a job is indicated by the text «ALLOCATED WORKSPACE» in the .dat file at the end of the input processing output. The "ALLOCATED WORKSPACE" can never exceed "standard_memory" and thus - if both values ​​are the same - one can conclude from this that this ABAQUS job has actually allocated too little memory and therefore intensive I / O is being processed in the scratch directory. In this case, the value of «standard_memory" in the environment file should be increased; this is particularly necessary if the active Wavefront block does not fit in the memory and the «Spilling Solver» is used (a warning message is displayed in this The use of the «Spilling Solver» is very inefficient, as the scratch directory is used to save the active Wavefront.

ABAQUS also generates several database files, some of which can be kept in the available memory. The maximum memory requirement that can be used for these database files is specified by the parameter «standard_buffer». The entire ABAQUS memory requirement ("ALLOCATED WORKSPACE" + "standard_buffer") can never exceed the value of "standard_memory". It is therefore advisable to preset the two parameters «standard_memory» and «standard_buffer» with the same value. It follows that the memory that is not used for the workspace is available for the database files and thus a more favorable I / O behavior of the job is achieved. An ABAQUS batch job therefore requires the following memory requirements in bytes:

standard_memory * 8 + approx. 5 * 10E6

That means for example with «standard_memory» = 20000000 a memory requirement of approx. 165 Mbyte is required. The default value for «standard_memory» and «standard_buffer» is preset as follows:

Sun cluster: 20,000,000 64 bit words
(Memory = approx. 165 MB)

See also the following information file, which is generated with the following command:

abaqus -jid mem -mod information -inf memory

2.5.2 Pre-processor (input processing)

The two relevant parameters for this processing step are «pre_memory» and «pre_buffer". The maximum memory required by the preprocessor process results from «pre_memory» * 8 + «pre_buffer» (this differs from the main phase) «Pre_memory» and «pre_buffer» are preset as follows:

pre_memory = 10 000 000 64 bit words

pre_buffer =
700,000 64 bit words

These values ​​are sufficient for most FE problems.

2.6 ABAQUS post processing

2.6.1 ABAQUS / Post

Interactive postprocessor for displaying FE results after an ABAQUS analysis. One of the restart files jid.res or jid.rst must be available or the file jid.fil.

Example: Call on the SunAS

abapost -jid c4 -res c4.res -inp c4.post

2.6.1.1 Description of the script parameters

Job Identifier
-jid required

Combination of any alphanumeric characters. Jobs that compute in the same directory at the same time must have different job identifiers. All files that are generated by ABAQUS contain this identifier in their naming, followed by the extension .ext. (Explanation see chapter 2.9)

Restart read file
-res optional

Name of the restart file; this file must have been created in a previous ABAQUS analysis (jid.res or jid.rst). ABAQUS / Post first looks for a file jid.rst and then for a file jid.res; the file found first is used.

ABAQUS / Post Input commands
-inp optional

Specification of a file from which input commands can be read. Only required for background or batch jobs.

Device type
-dev default = xwindow

Specification of the type of output device. Device names currently supported: xwindow, tek4207, terminal

Geometry
-geo default = 1000x700 + 12 + 34

This option specifies the Xwindow position and the size of the window. The format is width x height + xpos + ypos. Example: -geo 1000x700 + 12 + 34

Batch class
-bcl default = interactive

Specification of the batch classes: background, e, l

For interactive use with the DEVICE TYPE `xwindow 'see the comments in chap. 2.6.2.1 under the DEVICE TYPE parameter. If the hardcopy option is activated in an ABAQUS / Post session (* SET, HARDCOPY = ON), every image that appears on the screen is also written to a jid.mpl file. This file can then be converted into a PostScript file with ABAQUS / Plot or displayed picture by picture in an X11 window.

2.6.2 ABAQUS / Plot

Conversion of an ABAQUS `neutral plot file '(file jid.ppl or jid.mpl) into a PostScript file (.ps) or output in an X11 window.

Example: Call on the SunAS

abaplot -jid abap -inp abap.mpl -bcl background

The abap.mpl file contains the input data for ABAQUS / Plot and corresponds to the `neutral plot file ', which is generated by means of an ABAQUS / PRE analysis (jid.ppl), an ABAQUS-MAIN analysis (jid.mpl) or with ABAQUS / Post (hardcopy, jid.mpl) has been generated.

2.6.2.1 Description of the script parameters

Job Identifier
-jid required

Combination of any alphanumeric characters for job identification and for determining the PostScript file: jid.ps

ABAQUS Neutral Plot File
-inp required

File name with the input data for ABAQUS / Plot. This file corresponds to the `neutral plot file 'and must be generated in an ABAQUS analysis or in ABAQUS / Post. (File: jid.mpl or jid.ppl)

Device Type (xwin, ps)
-dev default = ps

Parameters for controlling the plotter interface programs or for identifying the graphic output device.
If xwin is specified, the graphical output takes place directly on the end device. Specifying ps (PostScript) creates a PostSricpt file that can be sent to the Canon color laser printer with the following command.

Sun cluster:
lpr -Pclc_rz_ps psfile

When calling ABAQUS / Plot via Xwindow (-dev = xwin), note the following:

1. The environment variable DISPLAY must be set to name: 0, where name is the host name of the Internet address of the server (computer on which the graphic is displayed). 2. The host name of the server must be entered in the / etc / hosts file on the client (computer on which ABAQUS / Plot is processed). Otherwise name must be replaced with the IP (Internet Protocol) address. 3. The X11 environment must be available on the client.

4. Issue the following command on the server: xhost + 'Client-Name'

In the Korn shell, the command sequence for setting the DISPLAY variable is, for example:

on the server: xhost + sunas on the client: export DISPLAY = sunxyz: 0

Frame
-fra default = all

Specification of the number of plot frames to be displayed by the `neutral plot file '. By default, all frames are shown (-fra all). It is also possible to enter an integer list [e.g .: -fra (1,4,8,10)]. The specification of a certain frame [e.g .: -fra 8 (i.e. the 8th frame is displayed)] is also permitted.

Options file
-opt default = cps.opt

This parameter specifies the name of the plot options file. This file defines standards for the various plot driver programs. (see ABAQUS / Post Manual chapter 5.1.6)

Run mode
-run default = interactive

Specification of the run mode: interactive or background

2.7 Initialization of the ABAQUS program system

2.7.1 Calling the init functions: SunAS or SunCS

The ABAQUS software package can only be started from the Sun cluster by issuing the following command for initialization:

init_abaqus57
(Version 5-7)
init_abaqus56
(Version 5-6)

Standard version: init_abaqus (currently verses 5-6)

2.7.2 Modification of the Unix variable PATH

If not the possibility under chap. 2.7.1 is used, the PATH parameter must be expanded directly in the $ LOGNAME / .myprofile file so that the ABAQUS scripts can be called:

PATH = / opt / abaqus / abaqus57: $ PATH
(Version 5-7)
PATH = / opt / abaqus / abaqus56: $ PATH
(Version 5-6)

2.8 Examples for ABAQUS calls

2.8.1 ABAQUS / Standard

The examples listed (c1, c4, c5) are available in the following directory:

Sun cluster: / opt / abaqus / abaqus57 / samples / corstd

a) ABAQUS call with generation of a Fil file (c1.fil):

abaqus -jid c1 -inp c1.inp

b) ABAQUS call of a nonlin. dynamic analysis with generation of a restart file (c4.res) and a fil file (c4.fil):

abaqus -jid c4 -inp c4.inp

c) Continuation of the analysis of example b) with generation of a new restart file (c5.res) and an extended Fil file (c5.fil):

abaqus -jid c5 -inp c5.inp -old c4 -fil append

2.8.1.1 Description of examples c1, c4 and c5

c1) c1 is a small displacement structural analysis. For this case ABAQUS will create an output listing (c1.dat), a file output file (c1.fil) and the status, message and log files.

c4) This is a nonlinear dynamic analysis of an extended version of the model c1. The job will create an output listing (c4.dat), a file output file (c4.fil) and a restart file (c4.res). The job ends because the * STEP option does not provide enough increments to complete the simulation time requested. c5 is a restart job to finish the required simulation time.

c5) This job continues the analysis of example c4. The job needs the file output file (c4.fil) and the restart file (c4.res) from c4. It will create an output listing (c5.dat), a new restart file (c5.res) and a file output file (c5.fil) which includes the results from both the c4 and c5 run.

2.8.2 ABAQUS / Explicit

Examples are in the following directory on the Sun cluster:

/ opt / abaqus / abaqus57 / samples / corxpl

a) ABAQUS / Explicit analysis with subsequent conversion of all relevant files:

abaqus -jid beam1 -mod analysis -p explicit -con yes -cop all -bcl e

b) ABAQUS / Explicit analysis without converting all relevant files but analysis with double precision:

abaqus -jid beam1 -mod analysis -p explicit -dp double -bcl e

c) Conversion of the ABAQUS / Explicit selected Results file after an analysis that has already been carried out according to example b):

abaqus -jid beam1 -mod convert -cop select

2.9 ABAQUS file name conventions

This chapter describes the names that are automatically used for the various ABAQUS files. Each of the following names is preceded by the name of the job identifier (1st parameter of the ABAQUS scripts) and a name extension (.ext) assigned by ABAQUS: jid.ext

ABAQUS script:

Surname
description
.com1
Batch job file
.com2
---"--

ABAQUS-PRE:

.inp
Input file
.dat
Output file
`old'.res
Restart read file of a previous job
.res
Restart Write File
.sup
Super element file
.ppl
Neutral plot file
.023
Communication file, database
.f
User subroutine

ABAQUS-MAIN:

.dat
Output file
.fil
File output (* FILE command)
.res
Restart Write File
.mpl
Neutral plot file
.sup
Super element file
.sta
Analysis status
.msg
Message file
.log
Job log
.023
Communication file, database
.061
split stiffness matrix

ABAQUS / Explicit:

.abq
Status file
.pac
Package file
.sel
Selected Results File

ABAQUS / Post script:

.jnl
Journal File
.rpt
Report file
.flc
Animation file
.mpl
Hard copy file

ABAQUS / plot script:

.ps
PostScript file

ABARES script:

.res
Restart native file
.rnb
Restart neutral file
.rst
Translated Native File
.log
Job log

ASCFIL script:

.fil
Result file (* FILE command)
.fin
Result File (ASCII)
.fin.log
Job log

There are also a number of other scratch files in ABAQUS / Pre and Main as well as in the various ABAQUS modules such as Post, Abares, Ascfil, Plot etc. (see also ABAQUS / Standard User's Manual, Volume I, Chapter 3.6.1 )

3 utilities

3.1 ABAQUS Restart Translator: abares

The -mod abares option translates the binary `native restart file '(.res) into a binary, neutral restart file with a neutral format (.rnb). This neutral restart file can be ported between different computers (e.g. with ftp); After a retranslation on the target computer (again calling abares with jid.rnb) into a `Native Restart File '(.rst), you can work with ABAQUS / Post, for example.

Example: Call on the SunAS

a)
abaqus -jid c4 -mod abares

or with selected time steps

b)
abaqus.exe abares job = job-name [restart = restart-name] [beginstep = step-number] [endstep = step-number] [increment = {all | endstep | final | none | integer-list}]

The content of the .res file differs considerably from the .rst file, since it no longer contains any restart information. So this procedure is irreversible. So if you plan to restart, you should keep the original restart file (.res), because a restart can only be carried out on the computer on which the .res file was created

3.2 ASCII conversion of the result file (.fil): ascfil

The -mode ascfil option converts the binary result file (.fil) into an ASCII format (.fin) for porting to another computer system and further processing there with another post-processing system (e.g. PATRAN). (see ABAQUS / Standard User's Manual Volume I, Chapter 3.2.6)

Example: Call on the SunAS

abaqus -jid c4 -mod ascfil

3.3 Summary of two result files (.fil): append

The ABAQUS / Append Utility enables two result files (.fil) to be combined into a single file for further processing with ABAQUS / Post. (see ABAQUS / Standard User's Manual Volume I, Chapter 3.2.7)

Example: Call on the SunAS

abaqus.exe append job = name oldjob = file1 input = file2 background

3.4 Extraction of examples from archive files (.tar): fetch

ABAQUS / Fetch enables the extraction of input files (input files [.inp] and journal files [.jnl]) from compressed archive files (.tar). The file names are specified in the following manuals:

ABAQUS / Standard Example Problems Manual, Vol. I + II ABAQUS / Explicit Example Problems Manual ABAQUS / Standard Verification Manual

Example: Call on the SunAS:

abaqus.exe fetch job = name [input = input-file]

(see ABAQUS / Standard User's Manual Volume I, Chapter 3.2.9)

3.5 ABAQUS online documentation: doc

The online documentation contains the following manuals:

- ABAQUS / Standard User's Manual
- ABAQUS / Standard Keywords - ABAQUS / Explicit User's Manual - ABAQUS / Explicit Keywords - Using ABAQUS Online Documentation - ABAQUS Release Notes - ABAQUS Site Guide

Example: Call on the SunAS

abaqus -mod doc

3.6 Query of the sample databases: findkeyword

ABAQUS / findkeyword enables the query of the sample databases for an ABAQUS keyword and lists all input files that contain all specified keywords. The keywords are specified using the keyboard. The max option limits the number of sample files to this value. The default value of max is equal to 100.

abaqus -jid bsp -mod findkeyword -max 50

* STEP
* STATIC
* RESTART
* return key ends the input (blank line !!!)

(see also ABAQUS / Standard User's Manual, Volume I, Chapter 3.2.8)

4 Pre- and post-processing with MSC / PATRAN

4.1 Preprocessing

An ABAQUS input file can be generated in the ANALYSIS menu in MSC / PATRAN. To do this, either ABAQUS must be selected when the PATRAN database is created for the first time or ABAQUS in the PREFERENCES menu. A file jid.inp is then created, where the job identification jid is the name of the PATRAN database. ABAQUS can then be started, e.g. with

abaqus -jid jid -inp jid.inp -bcl e

4.2 Post processing

The file output file (* FILE command) corresponds to the result file of an ABAQUS analysis (jid.fil) and must either be created in ASCII format and transferred to a suitable workstation using ftp or the ASCII conversion is carried out with the Option `ascfil 'of the mode parameter after a successful ABAQUS analysis. For the first case, the following options must be used in the ABAQUS input file (no longer absolutely necessary, as `ascfil 'is available):

* FILE FORMAT, ASCII * EL FILE, .....
* NODE FILE, ...

So that post-processing with MSC / PATRAN is possible, the FE results must be saved in the results file jid.fil. For postprocessing, jid.fil is read in via the ANALYSIS menu. Everything else is then a specific PATRAN application.

5 Documentation

The following ABAQUS manuals are available as documentation:

- ABAQUS / Standard User's Manual I,
Version 5.7 - ABAQUS / Standard User's Manual II, Version 5.7 - ABAQUS / Standard User's Manual III, Version 5.7
- ABAQUS / Explicit User's Manual I,
Version 5.7 - ABAQUS / Explicit User's Manual II, Version 5.7
- ABAQUS Theory Manual Version 5.7
- ABAQUS / Post Manual, Version 5.7
- ABAQUS / Standard Example Problems Manual I, II
Version 5.7
- ABAQUS / Explicit Example Problems Manual
Version 5.7
- ABAQUS / Standard Verification Manual Version 5.7
- ABAQUS Release Notes Version 5.7
- Newsletters: http://www.hks.com/newsletters/newsletters.html
- In the register
/ opt / abaqus / abaqus57 / info on the Sun cluster the following document is available in PostScript format:

ABAQUS UNIX SITE GUIDE -> file name: site_guide.ps

The ABAQUS manuals can be borrowed from the supervisors or purchased from the manufacturer.

6 Collection of examples on the Sun cluster:

In the register
/ opt / abaqus / abaqus57 / samples on the Sun cluster are archive files (tar files) corresponding to the problems from the Example Problems Manual.

The names of the archive files are:

exastd.tar:
ABAQUS / Standard Example Problems
exaxpl.tar:
ABAQUS / Explicit Example Problems
tax tariff:
ABAQUS / Standard Verification Problems
verxpl.tar:
ABAQUS / Explicit Verification Problems
postqa.tar:
ABAQUS / Post Example Problems
corstd.tar:
no manual available timerstd.tar: no manual available timerxpl.tar: no manual available

The required input files can then be extracted from the archive file using the ABAQUS Fetch utility (see Section 3.4), e.g .:

abaqus.exe fetch job = 1010101

The input file is then saved under 1010101.inp in the working directory.

Further information on applications:

http://www.hks.com/applications/applications.html

7 ABAQUS status reports

Status reports for all ABAQUS products are available as information files in ASCII format in the following directory:

Sun cluster: / opt / abaqus / abaqus57 / info Version 5.7

The following status report files are available in this directory:

status.info
: == all file names of the status reports

status_explicit.info: == ABAQUS / Explicit Status Report

status_post.info
: == ABAQUS / Post Status Report

status_standard.info: == ABAQUS / Standard Status Report

status_utility.info: == ABAQUS / Utility Status Report (eg., Abares, Ascfil, etc.)

Output of the current status report files is also possible with the following call:

abaqus -jid list -mod information -inf status

8 ABAQUS Release Notes

Release notes are available as information files in ASCII format and in PostScript format in the following directory:

Sun cluster:
/ opt / abaqus / abaqus57 / info Version 5.7

The following release notes files are available in this directory:

release_notes.ps: == Release notes in PostScript format

release_notes.txt: == Release notes in ASCII format

release.info
: == == all file names of the release notes

Output of the current release notes file (ASCII format) is also possible with the following call:

abaqus -jid rel -mod information -inf release

9 care

J. Fischer, Tel .: (0511) 762-5132 E-Mail: [email protected]

Dr. G. Brand, Tel .:
-5131 Email: [email protected] W. Sander, Tel .: -5132 Email: [email protected]

Header and Footer

abaqus_info (1) User Commands abaqus_info (1)
SunOS 5.5.1 Last change: 1

Table of Contents