next up previous contents
Next: Load Definition Up: History Definition Previous: Procedure Definition

Subsections


Results Output Control

For each loadcase/step a large number of different result types can be calculated by ABAQUS. These results can be calculated at element gauss points, nodally averaged at nodes etc. and can be output either in printed form (the ABAQUS '.dat' file) or as a result file (the ABAQUS '.fil' file). Result output requests must appear in the ABAQUS input file unless only an ABAQUS restart file (.res) is requested.

The interface generates result output requests to the ABAQUS '.fil' file only. Where procedure definitions (load type 'PROC-DEF') are not used, the interface will make a sensible guess at the type of results that the user requires. It is then the responsibility of the user to edit the ABAQUS input file to modify this guess.

Where procedure definitions are used, the interface will produce a group of result output requests which are relevant to each procedure. The default result output requests for each procedure can be modified via the resource *.results.request (see section 1.4).

No result output requests are generated if only an ABAQUS restart file (.res) is requested.

Automatic Result Output Control

Where the interface detects structural load types, the following result output request cards will be placed in the ABAQUS input file for each step.

*NODE FILE
U
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
COORD

The following results output control options will be selected where heat loads have been defined in the model.

*NODE FILE
NT
*EL FILE, POSITION=INTEGRATION POINTS
TEMP
COORD

Selective Result Output Control

Where procedure definition load types are present (PROC-DEF) the result output requests are formed on the basis of the procedure type used. The interface uses a series of default result output requests for each procedure as illustrated in tables 6.4 to 6.16


*NODE FILE
U,RF,CF
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
ENER
COORD
Table 6.4: Default Result Output Requests for *BUCKLE


*NODE FILE
U,RF,CF,NT
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
ENER
TEMP
COORD
Table 6.5: Default Result Output Requests for *COUPLED TEMPERATURE-DISPLACEMENT



*NODE FILE
U,V,A,RF,CF,TU,TV,TA,PTU
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
PHS
PHE
COORD
Table 6.6: Default Result Output Requests for *DYNAMIC



*NODE FILE
U
Table 6.7: Default Result Output Requests for *FREQUENCY



*NODE FILE
U
*EL FILE, POSITION=AVERAGED AT NODES
S
*EL FILE, POSITION=NODES
S
*EL FILE, POSITION=INTEGRATION POINTS
S
COORD
Table 6.8: Default Result Output Requests for *GEOSTATIC



*NODE FILE
NT,RFL,CFL,RFLE
*EL FILE, POSITION=INTEGRATION POINTS
TEMP
HFL
COORD
Table 6.9: Default Result Output Requests for *HEAT TRANSFER



*NODE FILE
U,V,A,RF,CF
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
COORD
Table 6.10: Default Result Output Requests for *MODAL DYNAMIC



*NODE FILE
U,V,A,RF,CF,TU,TV,TA,RS,RE,RU,RV,RA,RTU,RTV,RTA,RRF
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
COORD
Table 6.11: Default Result Output Requests for *RANDOM RESPONSE



*NODE FILE
U,V,A,RF,CF
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
COORD
Table 6.12: Default Result Output Requests for *RESPONSE SPECTRUM



*NODE FILE
U,POR,RVF,RVT
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
VOIDR
POR
SAT
GELVR
FLUVR
E
COORD
Table 6.13: Default Result Output Requests for *SOIL



*NODE FILE
U,RF,CF
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
ENER
COORD
Table 6.14: Default Result Output Requests for *STATIC



*NODE FILE
U,V,A,RF,CF
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
ENER
COORD
Table 6.15: Default Result Output Requests for *STEADY STATE DYNAMICS



*NODE FILE
U,RF,CF
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S
E
ENER
CE
IE
COORD
Table 6.16: Default Result Output Requests for *VISCO

Manual Result Output Control

It is possible to replace the default result output requests detailed in the previous section with the users own preferences. This is achieved via a result output request file and the resource *.results.request (see section 1.4).

The resource *.results.request should be set to the full path name of an ascii file in which the desired result output requests are specified and the relevant procedure should be defined manually with the 'PROC-DEF' load type. The file should have the following simple free format:

**PRC1
Result output request
.
.
.
Result output request
**PRC2
Result output request
.
.
.
Result output request
**END

Example Result Output Request File

**FREQ
*NODE FILE
U
**STAT
*NODE FILE
U,RF,CF
*EL FILE, POSITION=AVERAGED AT NODES
S,E
*EL FILE, POSITION=NODES
S,E
*EL FILE, POSITION=INTEGRATION POINTS
S,COORD
E,COORD
**END

Note that the result output request file has a limit of 200 lines and that not all procedures need to be specified. It is thus possible to selectively replace the result output requests for only some of the procedures and use the interface defaults for any others. It is important to note that it is not possible to change result output requests from within FEMGEN.

Furthermore the values of the output variables at the beginning of each step, the zero increment, can be written to the '.fil' file by setting the resource *.results.zero_increment : YES (see Sections 1.3 and 1.4).


next up previous contents
Next: Load Definition Up: History Definition Previous: Procedure Definition

Femsys Limited
9/9/1999