Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Reference Manual
Corporate
MSC.Software Corporation
2 MacArthur Place
Santa Ana, CA 92707
Telephone: (800) 345-2078
FAX: (714) 784-4056
Europe
MSC.Software GmbH
Am Moosfeld 13
81829 Munich
GERMANY
Telephone: (49) (89) 43 19 87 0
Fax: (49) (89) 43 61 71 6
Asia Pacific
MSC.Software Japan Ltd.
Shinjuku First West 8F
23-7 Nishi Shinjuku
1-Chome, Shinjuku-Ku
Tokyo 160-0023, JAPAN
Telephone: (81) (3)-6911-1200
Fax: (81) (3)-6911-1201
Worldwide Web
www.mscsoftware.com
User Documentation: Copyright 2010 MSC.Software Corporation. Printed in U.S.A. All Rights Reserved.
This document, and the software described in it, are furnished under license and may be used or copied only in accordance with the
terms of such license. Any reproduction or distribution of this document, in whole or in part, without the prior written authorization of
MSC.Software Corporation is strictly prohibited.
MSC.Software Corporation reserves the right to make changes in specifications and other information contained in this document
without prior notice. The concepts, methods, and examples presented in this document are for illustrative and educational purposes
only and are not intended to be exhaustive or to apply to any particular engineering problem or design. THIS DOCUMENT IS
PROVIDED ON AN “AS-IS” BASIS AND ALL EXPRESS AND IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, ARE
DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
MSC.Software logo, MSC, MSC., MD, Adams, Dytran, Marc, Mentat, and Patran are trademarks or registered trademarks of
MSC.Software Corporation or its subsidiaries in the United States and/or other countries.
NASTRAN is a registered trademark of NASA. LS-DYNA is a trademark of Livermore Software Technology Corporation. All other
trademarks are the property of their respective owners.
Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 12.212 (Commercial Computer
Software) and DFARS 227.7202 (Commercial Computer Software and Commercial Computer Software Documentation),
as applicable.
DT*V2010*Z*Z*Z*DC-REF
Contents
Dytran Reference Manual
Contents
1 Introduction
Overview 18
Summary 25
Prestress Analysis 25
New Analyses 25
Restart Control 25
User Code 25
File Selection 25
FMS Descriptions 26
BULKOUT — Prestress Grid Point Output, 27
EULINIT — Imports an Euler archive from a previous run, 28
IMMFILE — Initial Metric Method File Section, 30
NASTDISP — Prestress MD Nastran Displacement File, 31
NASTINP — Prestress MD Nastran Solution File, 32
NASTOUT — MD Nastran Input File for Prestress Analysis, 33
PRESTRESS — Prestress Analysis, 34
RESTART — Restarts a Previous Run, 35
RSTBEGIN — Restart Time Step, 36
RSTFILE — Restart File Section, 37
SAVE — Interval Between Saving an Output File, 38
SOLINIT — Specify an Initial Solution File from Prestress Analysis, 39
SOLUOUT — Specifies the Output Solution File from a Prestress Analysis, 40
START — Primary Analysis, 41
TYPE — Type of Output File, 42
USERCODE — User Subroutine Selection, 43
4 Dytran Reference Manual
6 Parameters
Overview 611
7 User Subroutines
Overview 735
Loading the User Subroutines with Dytran 736
User Access to Element and Grid Point Data from User Subroutines 736
User-written Subroutine Notes 738
EEXOUT — User-defined Element Output, 739
EXALE — User-defined ALE Grid Point Motion, 743
EXBRK — User-defined Failure of Breakable Joins, 746
EXCOMP — User-defined Orthotropic Failure Model, 748
EXCOMP1 — User-defined Orthotropic Failure Model that allows to model
Property Degradation, 755
EXELAS — User-defined CELAS1 Spring Element, 767
EXEOS — User-defined Equation of State, 770
EXEOS1 — User-specified Equation of State, 775
EXFAIL — User-defined Failure Model, 779
EXFAIL1 — User-defined Orthotropic Failure Model, 781
16 Dytran Reference Manual
8 Diagnostic Messages
A References
Chapter 1: Introduction
Dytran Reference Manual
1 Introduction
Overview 18
Similarity with MD Nastran 19
18 Dytran Reference Manual
Overview
Overview
Input to Dytran™ takes the form of a data file where each line can contain up to 80 characters. The file
contains all the information to define the analysis model and control the analysis.
The input to Dytran is similar, but not identical, to that for MD Nastran® and Dyna. If you are familiar
with MD Nastran, learning to use Dytran will be very easy although you should note the areas in which
the two programs differ. These differences are summarized in Similarity with MD Nastran.
The input data is split into four main sections, which must be in the following order:
1. File Management Section (FMS)
2. Executive Control Section
3. Case Control Section
4. Bulk Data Section (Note that parameter options may appear at any location within the Bulk
Data Section.)
The File Management Section contains information about the files used during the analysis and to control
restarting. The Executive Control Section is not used often in Dytran, since the program does not have
an Executive System like MD Nastran.
The Case Control Section controls the analysis, specifies the type of input and output required, selects
the constraints and loading from the Bulk Data, and allows you to control the way the analysis progresses.
A discussion of the functions available in the Case Control Section and a detailed description of the
commands that can be used is given in the Case Control section of this manual.
The Bulk Data Section contains all data necessary to define the model, the constraints, loading
conditions, and initial conditions. Only one model can be defined in the input data, but several types of
constraints and loading can be specified. The constraints and loading actually used in the analysis are
selected in the Case Control Section. The Bulk Data Section is discussed in the this manual together with
a detailed description of the entries.
The File Management, Executive Control, and Case Control Sections use a free-format input, which
means that the data can appear anywhere on the line with individual items separated by commas or
spaces. The Bulk Data Section can also be in free format and can optionally be in fixed format. In cases
where additional precision is required, large format can be used, where each entry occupies two lines in
the input file. Free, fixed, and large format can be mixed as needed in the input file on a line-by-line basis.
Comments can appear anywhere in the input file by placing a $ at the start of the comment. A full
description of the various input formats is given in Format of Bulk Data Entries.
The input data can be present in several separate files. In this case, you can use the INCLUDE command
or entry, available in both the Case Control and Bulk Data Sections, to direct Dytran to read the
appropriate file. The mechanism can be used to store the infrequently changed Bulk Data in one file,
while the File Management, Executive Control, and Case Control Sections, which are usually modified
more often, can be stored in another file.
Chapter 1: Introduction 19
Similarity with MD Nastran
It is important to remember that MD Nastran and Dytran are completely different programs even though
they offer similar input. A CQUAD4 shell element in Dytran has nothing in common with the CQUAD4
shell element in MD Nastran, since it differs in formulation, type of integration, and capabilities.
Similarly, other features defined using the same entries do not necessarily behave in the same way. The
solution method is different, so an identical analysis in MD Nastran and Dytran can give slightly different
results, although they will be within engineering accuracy.
Input
MD Nastran has a wide range of facilities of which a number are not available in Dytran. Therefore, there
are MD Nastran entries that are not valid in Dytran.
The following entries are compatible with both codes:
Elements
CBAR CHEXA
CBEAM CQUAD4
CDAMP1 CROD
CDAMP2 CTETRA
CELAS1 CTRIA3
CELAS2 CVISC
20 Dytran Reference Manual
Similarity with MD Nastran
Properties
PBAR PROD
PBEAM PSHELL
PCOMP PSOLID
PDAMP PVISC
PELAS
Materials
MAT1 MAT8
Coordinate Systems
CORD1C CORD2C
CORD1R CORD2R
CORD1S CORD2S
Other Entries
CONM2 TITLE
GRID TLOAD1
TABLED1 TLOAD5
TIME
The FMS has the same purpose in both Dytran and MD Nastran, but it is less important in Dytran since
all the filenames are automatically defined. The FMS controls restarting and user-written subroutines as
well as specification of the type of the output files.
The Executive Control Section exists but is rarely used since Dytran does not have an Executive System
or DMAP.
Chapter 1: Introduction 21
Similarity with MD Nastran
The Case Control Section has the same function in both Dytran and MD Nastran but uses
different commands.
PARAM entries are used by Dytran but offer different options to those in MD Nastran.
Dytran offers slightly greater flexibility in the way the input file can be defined, as listed below:
• Free format data can have more than eight characters.
• Continuation mnemonics do not have to be unique.
• Fixed and free format input can be freely mixed on a line-by-line basis.
• Real numbers can be entered as integers.
However, continuation lines must follow the entry that references them. If you intend on using both
Dytran and MD Nastran on a regular basis, use only those options that are available in both programs to
avoid confusion and incompatibility.
Loading
Several of the entries used for static loading in MD Nastran (such as FORCE, MOMENT, and PLOAD) are
used for dynamic transient loading in Dytran. Instead of being referenced directly from Case Control,
they are referenced from a TLOAD1 entry that gives the variation of the load with time.
The DAREA entry, used for transient loading in MD Nastran, is also valid in Dytran.
22 Dytran Reference Manual
Similarity with MD Nastran
Chapter 2: File Management Statements (FMS)
Dytran Reference Manual
Overview 24
Summary 25
FMS Descriptions 26
BULKOUT 27
EULINIT 28
IMMFILE 30
NASTDISP 31
NASTINP 32
NASTOUT 33
PRESTRESS 34
RESTART 35
RSTBEGIN 36
RSTFILE 37
SAVE 38
SOLINIT 39
SOLUOUT 40
START 41
TYPE 42
USERCODE 43
24 Dytran Reference Manual
Overview
Overview
The File Management Section (FMS) controls any file assignments that are required by Dytran. It also
controls restarting. The FMS must be placed at the beginning of the input file, but the individual
statements can be in any order within the FMS.
Most of the file assignments are made automatically by Dytran and cannot be changed by the user. The
filenames used are machine dependent and are listed in the Dytran Installation and Execution Guide.
A summary of the statements available in the FMS is given below. Each statement is described in
this chapter.
Chapter 2: File Management Statements (FMS) 25
Summary
Summary
The following statements are valid in the FMS:
Prestress Analysis
PRESTRESS Indicates a prestress analysis.
BULKOUT Selects the file to which grid-point data is to be written.
NASTDISP Selects the MD Nastran displacement file to be used.
SOLUOUT Selects a file to which solution data is to be written.
New Analyses
START Indicates a new analysis.
NASTINP Selects an MD Nastran solution file from which Dytran is to be initialized.
SOLINIT Selects a Dytran prestress solution file from which Dytran is to be initialized.
NASTOUT Selects a file to which Dytran writes geometric and material data in MD
Nastran format.
Restart Control
RESTART Indicates a restart of a previous analysis.
RSTFILE Selects the restart file to be used.
RSTBEGIN Selects the time step at which the calculation is to be restarted.
User Code
USERCODE Indicates that user-written subroutines are required for the analysis and defines
the filename containing the Fortran user-written subroutines.
File Selection
TYPE Defines the format of a file
SAVE Defines the interval of saving an output file
26 Dytran Reference Manual
FMS Descriptions
FMS Descriptions
The format of the FMS statements is free field. In presenting the general formats for each statement, the
following conventions are used:
• Uppercase letters should be typed as shown.
• Lowercase letters indicate that a value or option can be substituted.
• Brackets [ ] give a choice of different options.
The default value indicates the value that is used if no FMS command is present. The type column
indicates the type of data you must supply. This can be I (Integer), R (Real), or C (Character). In addition,
a range of permissible values may also be indicated. For example, I > 0 means that you must supply an
integer that is greater than zero.
BULKOUT 27
Prestress Grid Point Output
Defines a file to which grid point data is written at the end of the prestress analysis.
Remarks
1. The Bulk Data file filename contains only grid point data of the deformed geometry at the end
of the prestress analysis. It can be used to construct an ALE mesh for the final transient
dynamic analysis.
2. See NASTDISP, Prestress Analysis, and SOLUOUT in this chapter, and NASINIT, Chapter 5: Bulk
Data Entry Descriptions in this manual.
28 EULINIT
Imports an Euler archive from a previous run
Specifies an Euler archive used as input for a transient analysis. The Euler archive is mapped onto a set
of Euler elements that can equal in size or either finer or coarser.
0.
Remarks
1. The target elements are the elements defined in the follow-up run and are the elements that will
be initialized using the import archive.
2. Both defined and imported Euler elements need to be orthogonal in the global system
3. MESH-ID enables support for multiple Euler domains. If MESH-ID is not set the import archive
will be mapped onto all Euler elements.
4. For multi-material Euler analyses with multiple Eulerian materials all material variables in the
import archive require the material number. These material variables are MASS, DENSITY, SIE,
FMAT. The required list of variables for a MMHYDRO run are: MASSXX, SIEXX, FMATXX,
XVEL, YVEL, ZVEL. Here XX denotes the material number. FOR MMSTREN the variables TXX,
TYY, TZZ, TXY, TYZ, TZX, EFFPLS have to be added. If the multi-material run uses only one
Eulerian material then the material numbers can be left out.
5. For multi-material Euler analyses with EOSIG, the following has to be added for the IG materials:
MASS-EXX, MASS-PXX, RHO-EXX, RHO-PXX, IGBURNXX, FMAT-PXX, FMAT-PXX,
SIE-EXX, and SIE-PXX. Here XX denotes the material number.
6. For the single-material Hydro Euler solver the required list is MASS, DENSITY, SIE, FMAT,
and FVUNC.
7. IF FVUNC is not included in the Import archive it is assumed that all elements in this archive are
fully uncovered. It is allowed to import such an archive in a simulation with a coupling surface.
In this follow up simulation the target elements can have uncover fractions different from one. In
this case conservative quantities of imported elements are reduced by the uncover fraction of the
target element. This is to avoid unwanted pressure increases. It simply means that any mass of the
import archive that is located in the covered part of the target elements is thrown away. As a result
not all mass in the import archive is mapped to the target elements. How much of the mass of the
import archive is mapped is shown in the out file.
EULINIT 29
Imports an Euler archive from a previous run
8. In the OUT file, a summary is shown of all variables that are mapped.
9. In the follow-up run, the cycle and time are taken from the import archive. The results of the first
cycle of the follow-up run are determined from remapping only and has not gone trough an
equation of state yet. This will happen in the next cycle.
10. If needed the remapping can be checked by doing only one additional cycle in the follow-up run
with a quite small time step. Then, the follow-up OUT file shows two cycles and the results should
be almost identical to the results of the import archive. Also, material summaries in the OUT file
between first run and follow-up run should be identical. The only exceptions are the summaries
of momentum, kinetic energy, and total energy per material. For these three quantities, only the
total amounts will remain constant between first and follow-up run.
30 IMMFILE
Initial Metric Method File Section
Defines the reference file to be used for the Initial Metric Method
.
Remark
The Initial Metric Method is described in the Dytran User’s Guide in Initial Metric Method for Air Bags.
NASTDISP 31
Prestress MD Nastran Displacement File
Specifies an MD Nastran displacement file to be used as input for the prestress analysis.
.
Remarks
1. The displacement file must be either in MD Patran format, formed by using NASPAT on the
MD Nastran OUTPUT2 results file.
2. The default file type is MSC.XL format. This can be changed using PARAM,INITNAS.
3. See also the BULKOUT, Prestress Analysis, and SOLUOUT in this chapter, and NASINIT, Chapter
5: Bulk Data Entry Descriptions in this manual.
32 NASTINP
Prestress MD Nastran Solution File
Specifies an MD Nastran solution file from which Dytran is to be initialized via element stresses and
grid-point displacements.
Remarks
1. The stresses and displacement files are obtained by using NASPAT on the OUTPUT2 results file
from MD Nastran.
2. Element stresses are defined in the material coordinate system.
3. It is recommended that the MD Nastran geometrical problem setup be performed by Dytran for
consistency (see NASTOUT).
4. This option causes Dytran to read a MASS.DAT file that is automatically generated by the
NASTOUT File Management Section statement.
NASTOUT 33
MD Nastran Input File for Prestress Analysis
Specifies that Dytran write out MD Nastran input containing geometry and material definitions including
material coordinate systems, if applicable.
Remark
The option causes a MASS.DAT file to be written containing the element initial masses. This file is read
when the NASTINP File Management Section statement is used.
34 PRESTRESS
Prestress Analysis
Remarks
1. The following entries should be present elsewhere in the File Management Section or Bulk Data
Section for a prestress analysis:
2. The SOLUOUT file is then used to initialize Dytran for the primary analysis (via a SOLINIT
FMS statement).
3. Prestressing is described in the Dytran User’s Guide, Chapter 9: Running the Analysis,
PRESTRESS
RESTART 35
Restarts a Previous Run
Remarks
1. The RSTBEGIN File Management Section statement must be present to specify the time step from
which the calculation is to be restarted.
2. The RSTFILEFile Management Section statement must be present to specify the name of the
restart file to be used.
3. Restarting is described in Dytran User’s Guide, Chapter 9: Running the Analysis, Restarting a
Previous Analysis.
36 RSTBEGIN
Restart Time Step
Remarks
1. A RESTART File Management Section statement must be present to indicate a restart analysis.
2. A RSTFILE File Management Section statement must be present to specify the name of the restart
file to be used.
3. Restarting is described in Dytran User’s Guide, Chapter 9: Running the Analysis, Restarting a
Previous Analysis.
RSTFILE 37
Restart File Section
Remarks
1. A RESTART File Management Section statement must be present to indicate a Restart analysis.
2. A RSTBEGIN File Management Section statement must be present to specify the time step at
which the calculations are to be restarted.
3. Restarting is described in Dytran User’s Guide, Chapter 9: Running the Analysis, Restarting a
Previous Analysis.
38 SAVE
Interval Between Saving an Output File
Defines how often the file is written before it is closed and saved.
Remarks
1. When the file is written the specified number of times, it is closed, saved, and subsequent results
are stored in a new file.
2. Results are available for postprocessing when the file has been closed and saved. If the SAVE
statement is set to 1, results are stored in individual files and can be postprocessed immediately.
3. If value of n is negative for a RESTART request, the file is overwritten for every restart save. If
the n value is positive, a new file is created for every restart save request.
SOLINIT 39
Specify an Initial Solution File from Prestress Analysis
Specifies a solution file used as input for a transient analysis of a prestressed structure.
Remarks
1. The SOLINIT File Management Section statement causes Dytran to initialize the structural part
of the transient problem from a previous prestress analysis.
2. See also the BULKOUT, NASTDISP, PRESTRESS and SOLUOUT FMS statements, and the
NASINIT Bulk Data entry, for performing the prestress analysis.
3. The solution file should correspond to the filename used to write out the solution data at the end
of the prestress analysis (see the SOLUOUT File Management Section statement).
4. See PARAM,INITFILE for an overview of the different initialization methods and information
on the element types for which prestressing is available.
40 SOLUOUT
Specifies the Output Solution File from a Prestress Analysis
Specifies an output file to which the solution data is written at the end of a prestress analysis.
Remarks
1. The solution file is a binary file. It contains all necessary data of the solution at the end of an
Dytran prestress analysis.
2. See also the BULKOUT and PRESTRESS File Management Section statements, and the NASINIT
Bulk Data entry.
3. The solution output file should be the same file as used for initializing the primary analysis (see
the SOLINIT File Management Section statement).
4. See PARAM,INITFILE for an overview of the different initialization methods and information
on the element types for which prestressing is available.
START 41
Primary Analysis
Remarks
1. Since the default is a start analysis, this statement can be omitted.
2. See also the PRESTRESS and RESTART File Management Section statements.
3. This entry can be accompanied by using either of the following File Management
Section statements:
Remarks
1. Archive files are normally used to store results at one or more time steps during the analysis.
Archive files are used in postprocessing to produce deformed shapes, contour plots, and vector
plots. Archive files contain the model geometry and results.
2. Time-history files are normally used to store results for particular grid points and elements and
are used to produce time-history plots. Only the results are stored.
3. Restart files are used to restart the calculation.
4. The summaries STEPSUM, MATSUM, MRSUM, and EBDSUM are always printed on standard
output, irrespective of the value of logical_file.
5. The default output frequency is every 50 cycles for MATSUM, MRSUM, and EBDSUM. The default
for STEPSUM is every cycle.
USERCODE 43
User Subroutine Selection
Defines the file containing user-written subroutines to be used with the analysis.
Remarks
1. The USERCODE command causes the user-written subroutines to be compiled and linked into a
new, temporary version of Dytran. On most computers, this is automatic. See the Dytran
Installation and Execution Guide for details on how it is performed on your computer.
2. If the USERCODE statement is not present, the standard version of Dytran is used.
3. See Chapter 7: User Subroutines in this manual for details on how to write and use
user-written subroutines.
44 USERCODE
User Subroutine Selection
Chapter 3: Executive Control Statements
Dytran Reference Manual
Overview 46
Executive Control Summary 47
Executive Control Descriptions 48
CEND 49
MEMORY-SIZE 50
TIME 51
46 Dytran Reference Manual
Overview
Overview
Executive Control is not used extensively by Dytran since, unlike MD Nastran, it does not contain an
Executive System, and DMAP is not available. It is retained for compatibility with MD Nastran.
The Executive Control Section immediately follows the FMS and is terminated by a CEND statement.
The Executive Control statements can appear in any order within the Executive Control Section.
Chapter 3: Executive Control Statements 47
Executive Control Summary
The default value is used if the statement is not present. Where you can supply an option, the type heading
indicates the type of data you must supply. This can be I (Integer), R (Real), or C (Character). A
restriction on the range of the option may also be included. For example, I > 0 indicates that you must
supply an integer that is greater than zero, while 0 < R < 1. indicates that you must supply a real number
greater than zero and less than one.
CEND 49
Terminates the Executive Control Section
Marks the end of the Executive Control Section and the beginning of the Case Control Section.
Remark
If there are no FMS or Executive Control statements, the input file can start directly with the Case
Control Section.
50 MEMORY-SIZE
Definition of Memory Usage
The MEMORY-SIZE statement defines the size of the integer and float core memory Dytran uses. The
memory requested is dynamically allocated.
Remarks
1. Both values are required data. If you wish to use the default memory size for any of the values,
you can use the word DEFAULT for that specific value entry. The entry is case insensitive.
2. Dytran defines the memory size according to the following rules.
a. The user-specified definition by the MEMORY-SIZE entry always prevails.
b. If the MEMORY-SIZE entry is not used, the default memory size depends on the setting when
the analysis was submitted. On UNIX platforms, the run script takes the “size” entry that
defines the memory size. The choices are small (default), medium, and large. On Windows
platforms, you can define the memory size from Dytran Explorer.
c. If you do not specify anything, the predefined default (small) applies.
3. Due to the implementation, it may still be possible that your analysis data does not fit in the
requested memory. You can then alter the definition in the input file, or increase the size using
Dytran Explorer. If you need an estimate of the size the analysis approximately needs, you can
look at the memory summary at the end of the output file. Please note the memory sizes mentioned
are only an indication, as the summary is written when the analysis stopped. If the analysis
completed successfully, the core memory size is accurate.
4. There is no entry to define the character memory size. Dytran does not use any core memory
character data.
TIME 51
Selects the Maximum CPU Time
The TIME statement is used to set the CPU time of an Dytran analysis.
Remarks
1. When the CPU time specified on the TIME statement is used, the analysis terminates. The
analysis may be continued by performing a restart, if a restart file is requested at the end of
the analysis.
2. It is not possible to specify a maximum I/O time. I/O time is normally insignificant compared to
the CPU time for a Dytran analysis.
3. The time is specified in minutes. Thus, 1.5 is equivalent to 90 seconds, and 480 gives 8 hours.
4. It is advised to use the TIME statement to control CPU time, rather than specifying a time limit
for the batch queue or the job. If you do give a job or batch queue limit, make sure it is
significantly longer than specified on the TIME statement to ensure that Dytran terminates
normally and does not corrupt the files.
52 TIME
Selects the Maximum CPU Time
Chapter 4: Case Control Commands
Dytran Reference Manual
Overview 56
Case Control Summary 57
Case Control Descriptions 60
ACC 61
CHECK 62
CMARKOUT 63
CMARKS 64
COG 65
CONTOUT 66
CONTS 67
CORDDEF 68
CPLSOUT 69
CPLSURFS 70
CSECS 71
CSOUT 72
EBDOUT 73
EBDS 74
ELEMENTS 75
54 Dytran Reference Manual
ELEXOUT 76
ELOUT 77
ENDSTEP 78
ENDTIME 79
GBAGOUT 80
GBAGS 81
GPEXOUT 82
GPOUT 83
GRIDS 84
HIC 85
INCLUDE 87
MATOUT 90
MATS 91
PARAM 92
PLANES 93
RBOUT 95
RELOUT 96
RELS 97
RIGIDS 98
SET 99
SETC 101
SPC 103
STEPS 104
SUBSOUT 105
SUBSURFS 106
Chapter 4: Case Control Commands 55
SURFACES 107
SURFOUT 108
TIC 109
TIMES 110
TITLE 111
TLOAD 112
56 Dytran Reference Manual
Overview
Overview
The Case Control Section of the input file controls the analysis, makes selections from the Bulk Data
Section, and determines what results are output and how often. Case Control immediately follows the
CEND statement, marking the end of the Executive Control Section, and is terminated by a BEGIN
BULK entry or, in the case of a restart, by an ENDDATA entry. The Case Control commands can be in any
order within the section. A summary of the commands available is given below.
Chapter 4: Case Control Commands 57
Case Control Summary
Analysis Control
ENDSTEP Termination step for the analysis
ENDTIME Termination time for the analysis
CHECK Data check
Data Selection
TLOAD Selects transient loading
TIC Selects transient initial conditions
SPC Selects single-point constraints
Output Control
CORDDEF Defines the moving rectangular coordinate system for deformation output
SET Defines lists of entity numbers for use in output requests
SETC Defines lists of names for use in output requests
TITLE Defines the title of the analysis
SURFACES Defines the surfaces for which results are to be written to a file
EBDS Defines the Eulerian boundary conditions for which results are written to a file
Output Frequency
TIMES Lists the times at which output is required
STEPS Lists the time steps at which output is required
User-Defined Output
GPEXOUT Indicates that user subroutines are used for grid point output
ELEXOUT Indicates that user subroutines are used for element output
Chapter 4: Case Control Commands 59
Case Control Summary
Miscellaneous
PARAM Specifies parameters
ACC Creates time history output of an accelerometer in local coordinate system
COG Calculates the center of gravity for a group of elements
HIC Calculates Head Injury Criteria (HIC) value
60 Dytran Reference Manual
Case Control Descriptions
The default value is used if the command is not present. Where you need to supply an option, the type
heading indicates the type of data you must supply. This can be I (Integer), R (Real), or C (Character).
A restriction on the range of the option may also be included. For example, I > 0 indicates that you must
supply an integer greater than zero; 0. < R < 1. indicates that you must supply a real number greater than
zero and less than one.
ACC 61
Accelerometer Output
Remarks:
1. For each ACC output request, a file will be generated according to:
{JOBNAME}_{NAME}_XX.THS.
2. The set SID referenced must contain 1 grid point ID, which must be the same node that defines
the origin of the (moving) coordinate system referenced with CID.
3. The ACC output request automatically stores the following variables in the timehistory file:
a. XPOS, YPOS, and ZPOS: Position of accelerometer in global coordinate system.
b. XVEL, YVEL, and ZVEL: The velocity of the accelerometer in coordinates of the local
coordinate system.
c. XACC, YACC, and ZACC: The acceleration of the accelerometer in coordinates of the local
coordinate system.
d. RVEL and RACC: The absolute velocity and absolute acceleration of the accelerometer.
4. If any BODYFOR boundary condition is defined for the grid point defined in the SET, it is
subtracted from the global acceleration of the gird point. Any other acceleration fields like GRAV,
RFORCE, or ATBACC are not subtracted from the measured grid point acceleration.
62 CHECK
Data Check
Remarks
1. The data check option performs the following:
a. Reads the input data.
b. Checks for errors.
c. Produces printed output.
d. Runs two time steps.
e. Writes the model data to the output files.
2. The default is YES for a new analysis and NO for a restart analysis.
CMARKOUT 63
Marker Data to be Output
Remarks
1. The elements for which data is written are specified using the CMARKERS command. The element
results that can be requested for output are listed in Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The frequency of output is controlled using the TIMES and STEPS commands.
3. For a description of how to output the results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. Continuation lines are not allowed when using the CMARKOUT command. If the CMARKOUT
command exceeds 80 characters, a second CMARKOUT command (with the same
logical_file name) can be used as follows:
CMARKOUT (logical_file) = var 1, var 2
CMARKOUT (logical_file) = var 3
64 CMARKS
CMARKS to be Output
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The element results written are specified using the CMARKOUT command. The element results
that can be output are listed in Dytran User’s Guide, Chapter 9: Running the Analysis, Outputting
Results. The frequency of output is controlled by using the TIMES and STEPS commands.
COG 65
Center of Gravity Calculation
Calculate the center of gravity for a group of elements and print the results in a time history file.
ELEM: Element
SID Unique SET number I>0
SAMPLE Dytran sampling rate. This value determines the time step when center of R>0
gravity will be calculated and stored in the timehistory file.
Remarks
1. For each COG output request, a file is generated according to: {JOB-NAME}_{NAME}_XX.THS
2. The elements referenced in the SET entry can be a combination of elastic, plastic and rigid
elements. However, CONM2 definitions are not included in this calculation of the center
of gravity.
66 CONTOUT
Contact Surface Data to be Output
Indicates the contact surface results that are to be written to an output file.
Remarks
1. The contact surfaces for which data is written are specified using the CONTS command. The
contact-surface results that can be requested for output are listed in Dytran User’s Guide, Chapter
9: Running the Analysis, Outputting Results.
2. The frequency of the output is controlled using theTIMES or STEPS command.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. Continuation lines are not allowed when using the CONTOUT command. If the CONTOUT
command exceeds 80 characters, a second CONTOUT command (with the same logical_file name)
can be used as follows:
CONTOUT (logical_file) = var1, var2
CONTOUT (logical_file) = var3
5. For a time-history file, the following entities are written to the file together with the
corresponding results:
Master-Slave Contact:
C < Contact Surface ID > M:Forces/accelerations on/of the master surface.
C < Contact Surface ID > S:Forces/accelerations on/of the slave surface.
C < Contact Surface ID > T:Difference between the forces/accelerations on/of the master and
slave surfaces of the contact set.
Single-Surface Contact:
C < Contact Surface ID > T:Forces/accelerations on/of the single surface.
For an archive file, the combined entity C < Contact Surface ID > T is not written.
CONTS 67
Contact Surfaces to be Stored
Defines the contact surfaces for which results are to be output to a file
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The results are specified using the CONTOUT command. The contact surface results that can be
requested for output are listed in Dytran User’s Guide, Chapter 9: Running the Analysis,
Outputting Results. The frequency of the output is controlled using the TIMES or
STEPS command.
3. An archive file can contain only one contact surface definition. You can, of course, define
multiple contact output definitions.
4. Contact-surface data can only be written to time-history files. (See the TYPE FMS statement.)
5. For a time-history file, the following entities are written to the file together with the
corresponding results:
Master-Slave Contact:
C < Contact Surface ID > M:Forces/accelerations on/of the master surface.
C < Contact Surface ID > S:Forces/accelerations on/of the slave surface.
C < Contact Surface ID > T:Difference between the forces/accelerations on/of the master and
slave surfaces of the contact set.
Single-Surface Contact:
C < Contact Surface ID > T:Forces/accelerations on/of the single surface.
For an archive file, the combined entity C < Contact Surface ID > T is not written.
68 CORDDEF
Coordinate System for Deformation Output
Defines the moving rectangular coordinate system in which the deformations are written to the
archive files.
The CORDDEF entry can be added to any output request of TYPE = ARCHIVE. The grid point locations
written to the archive file are the locations in the coordinate system referenced by the CORDDEF entry.
The option is particularly useful when studying the motion of a structure in a moving coordinate system
.
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. Note that this entry is applicable only to output requests with TYPE=ARCHIVE.
CPLSOUT 69
Coupling Surface Data to be Output
Remarks
1. The coupling surfaces for which output is written must be specified using the
CPLSURFS command. The coupling-surface results available for output are defined in Dytran
User’s Guide, Chapter 9: Running the Analysis, Outputting Results.
2. The frequency of the output is controlled by the TIMESor the STEPS command.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. Continuation lines are not allowed when using the CPLSOUT command. When the command line
exceeds 80 characters, a second CPLSOUT command (with the same logical file name) can be
used as follows:
CPLSOUT(SRF_1) = vanr, var2
CPLSOUT (SRF_1) = var3
70 CPLSURFS
Coupling Surfaces to be Output
Defines the coupling surfaces for which results are to be output to a file.
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results
2. The results written are specified using the CPLSOUT command. The coupling surface results
available for output are described in Dytran User’s Guide, Chapter 9: Running the Analysis,
Outputting Results
3. The frequency of output is controlled by the TIMES or STEPS command.
CSECS 71
Cross Sections to be Output
Defines the cross sections for which results are to be output to a file
.
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The results written are specified using theCSOUT command. The cross section results that can be
requested for output are listed in Dytran User’s Guide, Chapter 9: Running the Analysis,
Outputting Results. The frequency of output is controlled using the TIMES or STEPS command.
3. Cross-section data can only be written to time-history files. (See theTYPE FMS statement.)
72 CSOUT
Cross-section Data to be Output
Remarks
1. The cross sections for which output is written are specified using the CSECS command. The cross
section results that can be requested for output are listed in Dytran User’s Guide, Chapter 9:
Running the Analysis, Outputting Results
2. The frequency of the output is controlled using the TIMES or the STEPS command.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis,Outputting Results
4. Continuation lines are not allowed when using the CSOUT command. If the command exceeds 80
characters, a second CSOUT command (with the same logical filename) can be used as follows:
CSOUT(SEC001) = var1, var2
CSOUT (SEC001) = var3
5. Cross-section data can only be written to time-history files. (See the TYPE FMS statement.)
EBDOUT 73
Eulerian Boundary Data to be Output
Remarks
1. The Eulerian boundaries for which data is written are specified using the EBDS command. The
Eulerian boundary results that can be requested for output are listed in Dytran User’s Guide,
Chapter 9: Running the Analysis, Outputting Results
2. The frequency of the output is controlled using the TIMES and STEPS commands.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. Eulerian boundary data can only be written to time-history files.
5. Continuation lines are not allowed when using the EBDOUT command. If the EBDOUT exceeds
80 characters, a second EBDOUT (with the same logical_file name) can be used as follows:
EBDOUT (logical_file) = var 1, var 2
EBDOUT (logical_file) = var 3
74 EBDS
Eulerian Boundaries to be Output
Defines the Eulerian boundaries for which results are to be output to a file.
Remarks
1. The Eulerian boundary results to be written are specified using the EBDOUT command. The
Eulerian boundary results that can be requested for output are listed in Dytran User’s Guide,
Chapter 9: Running the Analysis, Outputting Results.
2. The SET command n has to refer to a series of flow boundary names. For example, a flow
definition starts with FLOW,12.. and to get a time history for this particular flow definition, the
name FLOW12 has to be added to the SET entry.
3. The frequency of the output is controlled using the TIMES and STEPS commands.
4. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
5. Eulerian boundary results can only be written to time-history files.
ELEMENTS 75
Elements to be Output
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results. The element results written are specified using the ELOUT
command. The element results that can be output are listed in Dytran User’s Guide, Chapter 9:
Running the Analysis, Outputting Results.
2. The frequency of output is controlled using theTIMES and STEPS commands.
76 ELEXOUT
User-defined Element Output
Remarks
1. At every time or time step specified by the TIMES or STEPS command, a subroutine named
ELEXOUT is called for each of the elements listed using the ELEMENTS command allowing the
user to calculate specific quantities for output.
2. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
3. For a description of how to use user-written subroutines, see Chapter 7: User Subroutines in
this manual.
4. The following commands:
ELEXOUT (USEROUT)
ELEMENTS (USEROUT) = 10
SET 10 = 101, THRU, 110
TIMES (USEROUT) = 1.0E-3, 2.0E-3
cause the EEXOUT subroutine to be called at times 1.0E–3 and 2.0E–3 for elements 101 through
110 with the user-supplied name USEROUT.
ELOUT 77
Element Data to be Output
Remarks
1. The elements for which data is written are specified using the ELEMENTS command. The element
results that can be requested for output are listed in Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results. The frequency of output is controlled using the TIMES and STEPS
commands.
2. For a description of how to output the results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
3. Continuation lines are not allowed when using the ELOUT command. If the ELOUT command
exceeds 80 characters, a second ELOUT command (with the same logical_file name) can
be used as follows:
ELOUT (logical_file) = var 1, var 2
ELOUT (logical_file) = var 3
78 ENDSTEP
Final Time Step
Remarks
1. The RESTART statement can be used to continue a previous analysis. Therefore, you do not need
to set ENDSTEP to the final point you want to reach, but instead, to the point at which you want
the analysis to stop.
2. Unless you are very sure of what the analysis will do, you should always run the analysis in stages.
Then use the RESTART statement to continue the analysis after you have checked how the
mesh deforms.
3. The ENDTIME command can be used to terminate the analysis based on time.
4. If ENDTIME is specified, ENDSTEP is set to a large value (9999999).
5. At least one of the two termination criteria must be specified, either ENDSTEP or ENDTIME
ENDTIME 79
Analysis Termination Time
Remarks
1. The RESTART statement can be used to continue a previous analysis. Therefore, you do not need
to set ENDTIME to the final point you want to reach, but instead, to the point at which you want
the analysis to stop.
2. Unless you are very sure of what the analysis will do, you should always run the analysis in stages.
Then use the RESTART statement to continue the analysis after you have checked how the
mesh deforms.
3. The ENDSTEP command can be used to terminate the analysis based on the number of time steps.
4. If ENDSTEP is specified, endtime is set to large value (99999).
5. At least one of the two termination criteria must be specified, either ENDTIME or ENDSTEP.
80 GBAGOUT
Gas Bag Data to be Output
Remarks
1. The gas bags, for which data is written, are specified using the GBAGS command. The gas-bag
results that can be requested for output are listed in Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results, GBAGOUT — Gas Bag Results.
2. The frequency of the output is controlled using the TIMES and STEPS commands.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results, GBAGOUT — Gas Bag Results.
4. Gas-bag data can only be written to time-history files. (See the TYPE FMS statement.)
5. Continuation lines are not allowed when using the GBAGOUT command. If the GBAGOUT
command exceeds 80 characters, a second GBAGOUT command (with the same logical_file
name) can be used as follows:
GBAGOUT (logical_file) = var 1, var 2
GBAGOUT (logical_file) = var 3
GBAGS 81
Gas Bags to be Output
Defines the gas bags for which results are to be output to a file.
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The results written are specified using the GBAGOUT command. The gas bag results that can be
requested for output are listed in Dytran User’s Guide, Chapter 9: Running the Analysis,
Outputting Results, GBAGOUT — Gas Bag Results.
3. The frequency of output is controlled using theTIMES and STEPS commands.
4. Gas bag data can only be written to time-history files. (See theTYPE FMS statement.)
82 Dytran Reference Manual
User-defined Grid Point Output
Remarks
1. At every time or time step specified by the TIMES or STEPS commands, a subroutine called
GEXOUT is called for each of the grid points specified using a GRIDS command that allows you
to calculate specific quantities for output.
2. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results
3. For a description of how to use user-written subroutines, see Chapter 7: User Subroutines in
this manual.
4. The following commands:
GPEXOUT (DYTRAN_EXT_GP)
GRIDS (DYTRAN_EXT_GP) = 3
SET, 3, 1 THRU 35.
STEPS (DYTRAN_EXT_GP) = 5, 10, 15
cause the GPEXOUT user subroutine to be called at time steps 5, 10, and 15 for grid points 1
through 35 with the user-supplied name DYTRAN_EXT_GP.
GPOUT 83
Grid Point Data to be Output
Remarks
1. The grid points for which data is written are specified using theGRIDS command. The grid-point
results that can be requested for output are listed in Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The frequency of the output is controlled using the TIMES and STEPS commands.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. Continuation lines are not allowed when using the GPOUT command. If the GPOUT command
exceeds 80 characters, a second GPOUT command (with the same logical_file name) can
be used as follows:
GPOUT (logical_file) = var 1, var 2
GPOUT (logical_file) = var 3
84 GRIDS
Grid Points to be Output
Defines the grid points for which results are to be output to a file.
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The grid point results to be written are specified using the GPOUT command. The grid point
results that can be requested for output are listed in Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
3. The frequency of output is controlled using theTIMES and STEPS commands.
HIC 85
Head Injury Criteria Calculation
Calculate Head Injury Criteria (HIC) value, its time duration and resultants from head acceleration time
history curve, by means of the maximum of an integral with variable limits. Two different definitions are
used in HIC calculation: unlimited time envelope and a limited time envelope.
Remarks
1. The summary of HIC calculation will be written to *.OUT file
2. If the sampling rate (SAMPLE) is close to the delta time step of Dytran, then a warning message
is written to the *.OUT file of suspicious HIC values.
3. The value of the gravity used by the HIC calculations has to be set by the parameter HICGRAV.
When this value is not set, a warning message is issued and the default value of 9.80665 is used.
INCLUDE 87
Starts Reading of a New File
Switches reading of the input data to another file. Once that file has been read, processing returns to the
original file immediately after the INCLUDE file.
Remarks
1. The file must be present in the working area where Dytran is executing.
2. BEGIN BULK and ENDDATA may be included in an INCLUDE file.
88 MATBOUT
MATBX Data to be Output
Remarks
1. The boxes for which data is written are specified using the MATBX command. The MATBX results
that can be requested for output are listed in the Dytran User’s Guide, Chapter 9: Running the
Analysis, Time Histories for Boxes. All Eulerian element variables can be requested. In most
cases, results are the mass weighted average of all element values that are inside a box. Exceptions
are MASS, ENER, XMOM, YMOM, ZMOM. These are not averaged but simply accumulated. Material
Fractions are weighted with the uncovered volume of the elements inside the box. The uncovered
volume fraction FVUNC is weighted with total element volume.
2. The frequency of the output is controlled using the TIMES and STEPS commands.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Time Histories for Boxes.
4. MATBX data can only be written to time-history files.
5. Continuation lines are not allowed when using the MATBOUT command. If the MATBOUT
command exceeds 80 characters, a second MATBOUT command (with the same logical_file
name) can be used as follows:
MATBOUT (logical_file) = var 1, var 2
MATBOUT (logical_file) = var 3
MATBX 89
Boxes to be Output
Remarks
1. For a description of how to output results, see the Dytran User’s Guide, Chapter 9: Running the
Analysis, Time Histories for Boxes.
2. The box results written are specified using the MATBOUT command. The element results that can
be output are listed in the Dytran User’s Guide, Chapter 9: Running the Analysis, Time Histories
for Boxes.
3. For each box, it is determined which elements are inside the box. Elements that are only partially
inside a box will also be partially be taken into account.
4. MATBX is only available for Eulerian elements and fully supports multiple coupling surfaces.
5. MATBX can be seen as a CHEXA marker. For non-orthogonal meshes, markers are not supported
and MATBX is then a good alternative. There are no limits on the volume of the box, so the box
can be chosen small such that matbx resembles a marker. Defining many MATBX entries will not
significantly increase simulation times.
6. The frequency of output is controlled using the TIMES and STEPS commands.
7. An example is given below
TYPE (ARCMATBX) = TIMEHIS
MATBOUT (ARCMATBX) = DENSITY4,DENSITY4,MASS100,MASS100,
XVEL,YVEL,ZVEL,FMAT4,FMAT100,PRESSURE
MATBX (ARCMATBX) = 70
SET 70 = 50,60
STEPS (ARCMATBX) = 0,THRU,END,BY,1
SAVE (ARCMATBX) = 99999
BOX,50,,0.5625,-1,9.68,3.75,2,0.93
BOX,60,,0.5625,-1,4.35,3.75,2,0.93
90 MATOUT
Material Data to be Output
Remarks
1. The materials for which data is written are specified using the MATS command. The material
results that can be requested for output are listed in Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results,MATOUT — Material Results.
2. The frequency of the output is controlled using the TIMES and STEPS commands.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results, MATOUT — Material Results .
4. Material data can only be written to time-history files.
5. Continuation lines are not allowed when using the MATOUT command. If the MATOUT command
exceeds 80 characters, a second MATOUT command (with the same logical_file name) can
be used as follows:
MATOUT (logical_file) = var 1, var 2
MATOUT (logical_file) = var 3
MATS 91
Materials to be Output
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The material results to be written are specified using the MATOUT command. The material results
that can be requested for output are listed in Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
3. The frequency of output is controlled using the TIMES and STEPS commands.
4. Material results can only be written to time-history files.
92 PARAM
Parameter Specification
Defines the values for the parameters that are used during the analysis
Remark
This command is normally used in the Bulk Data Section. A list of parameters that can be set, along with
the parameter names and values, is given in Chapter 6: Parameters of this manual.
PLANES 93
Rigid Planes to be Output
Remarks
1. The rigid planes results to be written are specified using the PLNOUT — Rigid Plane Results
command. The rigid planes results that can be requested for output are listed in Dytran User’s
Guide, Chapter 9: Running the Analysis, Outputting Results.
2. The frequency of the output is controlled using the TIMES and STEPS commands.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. A SETC is used to enable output for rigid planes obtained from MADYMO.
5. Rigid plane data can only be written to archive files. See also the TYPE FMS statement.
94 PLNOUT
Rigid Plane Data to be Output
Remarks
1. The rigid planes for which data is written are specified using the PLANES command. The rigid
plane results that can be requested for output are listed in Dytran User’s Guide, Chapter 9:
Running the Analysis, Outputting Results.
2. The frequency of the output is controlled using the TIMES and STEPS commands.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. The keyword GEOMETRY causes a mesh to be placed on the rigid planes for visualization
purposes in the postprocessor.
5. Plane output can only be used for ARCHIVE output requests.
6. Continuation lines are not allowed when using the PLNOUT command. If the PLNOUT
command exceeds 80 characters, a second PLNOUT (with the same logical_file name) can
be used as follows:
PLNOUT (logical_file) = var 1, var 2
PLNOUT (logical_file) = var 3
RBOUT 95
Rigid Body Data to be Output
Remarks
1. The rigid bodies for which data is written are specified using the RIGIDS command. The rigid
body results that can be requested for output are listed in Dytran User’s Guide, Chapter 9:
Running the Analysis, Outputting Results.
2. The frequency of the output is controlled using the TIMES and STEPS commands.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. Continuation lines are not allowed when using the RBOUT command. If the RBOUT command
exceeds 80 characters, a second RBOUT (with the same logical_file name) can be used
as follows:
RBOUT (logical_file) = var 1, var 2
RBOUT (logical_file) = var 3
96 RELOUT
Rigid Ellipsoid Data to be Output
Remarks
1. The rigid ellipsoids for which data is written are specified using the RELS command. The rigid
ellipsoid results that can be requested for output are listed in Dytran User’s Guide, Chapter 9:
Running the Analysis, Outputting Results, RELOUT — Rigid Ellipsoid Results.
2. The frequency of the output is controlled using the TIMES and STEPS commands.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results, RELOUT — Rigid Ellipsoid Results.
4. The keyword GEOMETRY causes a mesh to be placed on the rigid ellipsoids for visualization
purposes in the postprocessor. This keyword can be used only with archive files.
5. Continuation lines are not allowed when using the RELOUT command. If the RELOUT command
exceeds 80 characters, a second RELOUT command (with the same logical_file name) can
be used as follows:
RELOUT (logical_file) = var 1, var 2
RELOUT (logical_file) = var 3
RELS 97
Rigid Ellipsoids to be Output
Defines the rigid ellipsoids for which results are to be output to a file.
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The rigid ellipsoid results to be written are specified using the RELOUT command. The rigid-
ellipsoid results that can be requested for output are listed in Dytran User’s Guide, Chapter 9:
Running the Analysis, Outputting Results.
3. The frequency of output is controlled using the TIMES and STEPS commands.
4. A SETC is used to enable output for rigid ellipsoids obtained from MADYMO or ATB.
98 RIGIDS
Rigid Bodies to be Output
Defines the rigid bodies for which results are to be output to a file.
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The rigid-body results to be written are specified using the RBOUT command. The rigid-body
results that can be requested for output are listed in Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
3. The SET can refer to a RIGID surface (id), a MATRIG (MR<id>), or an RBE2-FULLRIG
(FR<id>).
4. The frequency of output is controlled using the TIMES and STEPS commands.
SET 99
Set Definition
Defines a list of grid points, elements, etc., for which output is required.
Remarks
1. A SET command may occupy more than one line in the input file. A comma (,) at the end of a line
signifies that the next line is a continuation. Commas cannot end a set.
2. The keyword BY does not have to be used when specifying an i1 THRU i2 range since the
assumed default is 1.
SETC 101
List of Names
Defines a list of names (character strings) that are used to specify what output is required.
Remarks
1. A SETC command may occupy more than one line of the input file. A comma (,) at the end of a
line signifies that the next line is a continuation. Commas cannot end a set.
2. This SETC may be referred to from outside the Case Control Section.
3. The length of the character string must be 16 characters or less.
4. The RELS command uses the SETC instead of the normal SET1, enabling the user to specify
character strings rather than integers.
102 SGAUGES
Surface Gauges to be Stored
Defines the surface gauges for which results are to be output to a file.
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The frequency of the output is controlled using the TIMES or STEPS command.
3. Surface gauge data can only be written to time-history files. (See the TYPE FMS statement).
SPC 103
Single Point Constraint Set Selection
Remark
Single point constraints are not used by Dytran unless they are selected in the Case Control Section.
104 STEPS
Time Steps at which Data is Written
Remarks
1. The keyword END can be used to indicate the end of the calculation.
2. The TIMES command can be used instead to control the output using the values of time.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. A list of steps should be in ascending order.
SUBSOUT 105
Subsurface Data to be Output
Option Meaning
logical_file The logical name of the file to which the subsurface output is written.
vari Variable name to be output.
Remarks
1. The subsurfaces for which data is written are specified using the SUBOUT command. The
subsurface data that can be requested for output are listed in Dytran User’s Guide, Chapter 9:
Running the Analysis, Outputting Results.
2. The frequency of the output is controlled using the TIMES or STEPS command.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. Subsurface output data can only be written to a time history files. (See theTYPE FMS statement.)
106 SUBSURFS
Subsurfaces to be Stored
Option Meaning
logical_file The logical name of the file to which the subsurface output is written.
n Number of a SET command. Only data for GBAG or COUPLING
subsurfaces that appear in the set are output.
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The results are specified using the SUBSOUT command. The subsurf data that can be requested
for output are listed in Dytran User’s Guide, Chapter 9: Running the Analysis, Outputting Results.
3. The frequency of the output is controlled using theTIMES or STEPS command.
4. Subsurface output data can only be written to a time history files. (See the TYPE FMS statement).
5. The SUBSURFACEs specified in the SET command need to be part of a SURFACE referenced by
a COUPLE or GBAG entry.
SURFACES 107
Surfaces to be Stored
Option Meaning
logical_file The logical name of the file to which the surface output is written.
n Number of a SET command. Only data for GBAG or COUPLING
surfaces that appear in the set are output.
Remarks
1. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The results are specified using the SURFOUT command. The subsurf data that can be requested
for output is listed in Dytran User’s Guide, Chapter 9: Running the Analysis, Outputting Results.
3. The frequency of the output is controlled using the TIMES or STEPS command.
4. Surface output data can only be written to a time history files. (See the TYPE FMS statement).
5. The SURFACEs specified in the SET command need to be referenced by a COUPLE or
GBAG entry.
108 SURFOUT
Surface Data to be Output
Option Meaning
logical_file The logical name of the file to which the subsurface output is written.
vari Variable name to be output.
Remarks
1. The surfaces for which data is written are specified using the SURFACES command. The surface
data that can be requested for output are listed in Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
2. The frequency of the output is controlled using theTIMES or STEPS command.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. Surface output data can only be written to a time history files. (See the TYPE FMS statement.)
TIC 109
Transient Initial Condition Selection
Remark
Initial conditions are not used by Dytran unless they are selected in the Case Control Section.
110 TIMES
Times at which Data is Written
Remarks
1. The keyword END can be used to indicate the end of the calculation.
2. The STEPS command can be used instead to control the output using the time-step numbers.
3. For a description of how to output results, see Dytran User’s Guide, Chapter 9: Running the
Analysis, Outputting Results.
4. A list of times should be in ascending order.
TITLE 111
Output Title
Remark
The title is written to the output files for use in postprocessing.
112 TLOAD
Transient Load Selection
Remark
Loads, pressures, flow boundaries, and enforced motion are not used by Dytran unless they are selected
in the Case Control Section.
Chapter 5: Bulk Data Entry Descriptions
Dytran Reference Manual
Overview 123
Format of Bulk Data Entries 124
Bulk Data Summary 127
Bulk Data Descriptions 137
$ 138
ACTIVE 139
ALE 141
ALEGRID 142
ALEGRID1 145
ATBACC 147
ATBJNT 148
ATBSEG 151
BEGIN BULK 153
BIAS 154
BJOIN 156
BODYFOR 160
BOFYFR1 162
BOX 164
BOX1 165
114 Dytran Reference Manual
CBAR 166
CBEAM 168
CDAMP1 170
CDAMP2 172
CELAS1 174
CELAS2 176
CFACE 178
CFACE1 180
CHEXA 181
CMARKB2 183
CMARKN1 184
CONM2 185
CONTACT 186
CONTFORC 205
CONTINI 207
CONTREL 209
CORD1C 210
CORD1R 212
CORD1S 214
CORD2C 216
CORD2R 218
CORD2S 220
CORD3R 222
CORD4R 224
CORDROT 226
COUHTR 227
COUINFL 229
COUOPT 231
COUP1FL 233
Chapter 5: Bulk Data Entry Descriptions 115
COUP1INT 234
COUPLE 235
COUPLE1 239
COUPOR 241
CPENTA 246
CQUAD4 247
CROD 249
CSEG 250
CSPR 251
CTETRA 252
CTRIA3 253
CVISC 255
CYLINDER 256
DAREA 257
DETSPH 258
DMAT 259
DMATEL 261
DMATEP 263
DMATOR 264
DYMAT14 267
DYMAT24 270
DYMAT25 272
DYMAT26 274
ENDDATA 278
EOSEX 279
EOSEX1 280
EOSGAM 281
EOSIG 283
EOSJWL 289
116 Dytran Reference Manual
EOSMG 291
EOSPOL 293
EOSTAIT 296
FABRIC 298
FAILEST 302
FAILEX 303
FAILEX1 304
FAILEX2 305
FAILJC 306
FAILMES 308
FAILMPS 309
FAILPRS 310
FAILSDT 311
FFCONTR 312
FLOW 314
FLOWC 316
FLOWCDR 318
FLOWCSQ 321
FLOWDEF 324
FLOWDIR 326
FLOWEX 328
FLOWSQ 330
FLOWT 332
FLOWTSQ 335
FOAM1 338
FOAM2 340
FORCE 343
FORCE1 344
FORCE2 345
Chapter 5: Bulk Data Entry Descriptions 117
FORCE3 346
FORCEEX 348
GBAG 349
GBAGC 357
GBAGCOU 360
GBAGHTR 361
GBAGINFL 363
GBAGPOR 365
GRAV 368
GRDSET 369
GRID 370
GROFFS 371
HGSUPPR 372
HTRCONV 375
HTRRAD 376
HYDSTAT 377
IGNORE 379
INCLUDE 380
INFLATR 381
INFLATR1 383
INFLCG 385
INFLFRAC 387
INFLGAS 388
INFLHYB 390
INFLHYB1 391
INFLTANK 392
INITGAS 394
JOIN 395
KJOIN 396
118 Dytran Reference Manual
MADGRP 397
MAT1 398
MAT2 399
MAT8 400
MAT8A 401
MATINI 405
MATRIG 407
MESH 410
MOMENT 418
MOMENT1 419
MOMENT2 420
NASINIT 421
PARAM 422
PBAR 423
PBCOMP 424
PBEAM 426
PBEAM1 428
PBEAM1 432
PBEAM1 434
PBEAML 439
PBELT 442
PCOMP 444
PCOMPA 446
PDAMP 448
PELAS 449
PELAS1 450
PELASEX 451
PERMEAB 453
PERMGBG 455
Chapter 5: Bulk Data Entry Descriptions 119
PEULER 456
PEULER1 458
PLOAD 459
PLOAD4 460
PLOADEX 462
PMARKER 463
PMINC 464
POREX 466
PORFCPL 467
PORFGBG 468
PORFLCPL 469
PORFLGBG 470
PORFLOW 472
PORFLOWT 474
PORHOLE 477
PORHYDST 478
PORLHOLE 479
PROD 481
PSHELL 482
PSHELL1 484
PSOLID 487
PSPR 489
PSPR1 490
PSPREX 491
PVISC 492
PVISC1 493
PVISCEX 494
PWELD 495
PWELD1 498
120 Dytran Reference Manual
PWELD2 502
RBC3 505
RBE2 507
RBHINGE 509
RCONN 510
RCONREL 513
RELEX 514
RELLIPS 516
RFORCE 517
RIGID 518
RJCYL 519
RJPLA 521
RJREV 523
RJSPH 525
RJTRA 527
RJUNI 529
RPLEX 531
RUBBER1 533
SECTION 535
SET1 536
SETC 537
SETTING 538
SHEETMAT 540
SHREL 544
SHREX 545
SHRLVE 546
SHRPOL 548
SPC 549
SPC1 550
Chapter 5: Bulk Data Entry Descriptions 121
SPC2 551
SPC3 553
SPHERE 555
SUBSURF 556
SURFACE 558
TABFILE 560
TABLED1 561
TABLEEX 563
TIC 564
TIC1 565
TIC2 566
TIC3 567
TICEEX 569
TICEL 570
TICEUL 571
TICGEX 573
TICGP 574
TICVAL 575
TLOAD1 577
TLOAD2 579
VISCDMP 581
WALL 583
WALLDIR 585
WALLET 586
YLDEX 587
YLDEX1 588
YLDHY 589
YLDJC 590
YLDMC 592
122 Dytran Reference Manual
YLDMSS 593
YLDPOL 595
YLDRPL 596
YLDSG 597
YLDTM 599
YLDVM 601
YLDZA 604
Chapter 5: Bulk Data Entry Descriptions 123
Overview
Overview
The Bulk Data Section of the input file contains all the data to fully describe the analysis model, including
the geometry, topology, constraints, and loading. This section must begin with a BEGIN BULK entry.
Thereafter, entries can appear in any order except that continuation lines must follow the entry from
which they are referenced. Entries can be numbered in any manner that is convenient. Gaps in the
numbering are allowed. The input file must finish with an ENDDATA entry.
Many of the entries are the same as those used for MD Nastran. However, sometimes not all the fields
are used for Dytran. If data occurs in the unused fields, a User Warning Message is issued and the excess
data is ignored, see Chapter 1: Introduction, Similarity with MD Nastran in this manual. Similarly, any MD
Nastran entry that is not used by Dytran is ignored.
124 Dytran Reference Manual
Format of Bulk Data Entries
1a 2 3 4 5 6a
8 16 16 16 16 8
1b 2 3 4 5 6b
8 16 16 16 16 8
The large field format is denoted by placing the symbol * after the mnemonic in Field 1a and a + as the
first character of Field 10a. The second line contains the symbol * in column one. The second line may,
in turn, be used to point to a large or small field continuation line, depending on whether the continuation
line contains the symbol * (for a large field) or the symbol + (for a small field) in column one. The use
of multiple and large field lines is illustrated in the following examples:
Geometry
Grid Points
GRID Grid-point location, coordinate system selection.
GRDSET Default options for GRID entries.
GROFFS Grid-point offset in the local coordinate system.
CONM2 Concentrated grid-point mass and/or inertia.
Coordinate Systems
CORD1R,CORD2R Rectangular coordinate system definition
CORD1C, CORD2C Cylindrical coordinate system definition
CORD1S, CORD2S Spherical coordinate system definition
CORD3R Moving rectangular coordinate system definition, form 1
CORD4R Moving rectangular coordinate system definition, form 2
CORDROT Corotational frame definition
Mesh Generation
MESH Mesh generator
128 Dytran Reference Manual
Bulk Data Summary
Lagrangian Elements
Solid Elements
CHEXA Connection definition for brick element with eight grid points
CPENTA Connection definition for wedge element with six grid points
CTETRA Connection definition for tetrahedron element with four grid points
PSOLID Property definition for CHEXA, CPENTA, CPENTA
Surface Elements
CQUAD4 Connection definition for a quadrilateral shell element with four grid points
CTRIA3 Connection definition for a triangular shell or membrane element with three grid points
PSHELL Property definition for CQUAD4 and CTRIA3
PSHELL1 Extended property definition for CQUAD4and CTRIA3
PCOMP Layered composite element property
PCOMPA Additional data for layered composite element property
1-D Elements
CBAR Connection definition for a line element with two grid points
CBEAM Connection definition for a line element with two grid points
CROD Connection definition for a line element with two grid points
CDAMP1 Connection definition for a scalar damper element with two grid points
CDAMP2 Connection definition for a linear damper element with two grid points
CELAS1 Connection definition for a scalar spring element with two grid points
CELAS2 Connection and property definition for a scalar spring element with two grid points
CSPR Connection definition for spring element with two grid points
CVISC Connection definition for a viscous damper element with two grid points
PBAR Property definition for a CBAR element
PBEAM Property definition for CBAR and CBEAM
PBEAM1 Extended property definition for CBARand CBEAM
PBEAML Complex property definition forCBAR and CBEAM by cross-sectional dimensions
PBELT Property definition for a seat belt element defined by CROD
PDAMP Property definition forCDAMP1 and CDAMP2
PELAS Property definition for CELASn
PELAS1 Property definition on nonlinear elastic springs for CELASn
PELASEX Property definition for CELASn with user subroutines
Chapter 5: Bulk Data Entry Descriptions 129
Bulk Data Summary
Eulerian Elements
Solid Elements
CHEXA Connection definition for a brick element with eight grid points
CPENTA Connection definition for a wedge element with six grid points
CTETRA Connection definition for a tetrahedral element with four grid points
PEULER Property definition for CHEXA, CPENTA CTETRA
PEULER1 Property definition for CHEXA, CPENTA, CTETRA using geometrical regions
Constitutive Models
DMAT General constitutive model
DMATEL Isotropic elastic material properties
DMATEP Elastic or elastoplastic material properties
DMATOR Orthotropic material properties
DYMAT14 Soil and crushable foam material properties
DYMAT24 Piecewise linear plasticity material properties, with strain rate dependent plasticity
DYMAT25 Kinematic hardening Cap material properties
DYMAT26 Orthotropic crushable material properties used to model composites
FABRIC Bi-directional woven fabric material properties
FOAM1 Crushable foam material properties
FOAM2 Crushable foam material properties
MAT1 Linear-isotropic material properties
MAT2 Anisotropic material properties
130 Dytran Reference Manual
Bulk Data Summary
Yield Models
YLDHY Hydrodynamic yield properties
YLDVM von Mises yield properties
YLDJC Johnson-Cook yield properties
YLDMC Mohr-Coulomb yield properties
YLDTM Tanimura-Mimura yield properties
YLDZA Zerilli-Armstrong yield properties
YLDRPL Rate power law yield properties
YLDMSS Snow material yield properties
YLDPOL Polynomial yield properties
YLDEX User-defined yield properties
Shear Models
SHREL Elastic shear properties
SHRLVE Isotropic linear viscoelastic shear properties
SHRPOL Polynomial shear properties
SHREX User-defined shear properties
Equations of State
EOSPOL Polynomial equation of state
EOSJWL JWL explosive equation of state
EOSGAM Gamma law equation of state
EOSTAIT Equation of state based on Tait model
EOSEX Equation of state defined by user subroutines
EOSIG Ignition and growth equation of state
Detonation Models
DETSPH Spherical detonation wave
Chapter 5: Bulk Data Entry Descriptions 131
Bulk Data Summary
Failure Models
FAILEST Maximum equivalent stress and minimum time-step failure model
FAILEX Failure model defined by user subroutines
FAILEX1 Extended failure model defined by user subroutines
FAILMES Maximum equivalent stress failure model
FAILMPS Maximum plastic strain failure model
FAILPRS Maximum pressure failure model
FAILSDT Maximum plastic strain and minimum time-step failure model
Spallation Models
PMINC Constant spallation pressure properties
Rigid Bodies
MATRIG Rigid-body properties
RBE2 Rigid-body element
RELEX MADYMO or ATB ellipsoid to be used with Dytran
RPLEX MADYMO planes to be used in Dytran
RELLIPS Analytical rigid ellipsoid
RIGID Rigid-body properties
SURFACE Geometry of a rigid body
ATB Interface
ATBACC Acceleration field applied to ATB segments
ATBJNT Interface to ATB joints
ATBSEG Interface to ATB segments
Lagrangian Constraints
Single-Point Constraints
GRDSET Includes the default for single-point constraints on the GRID entry
GRID Includes the single-point constraint definition (permanentSPCs)
SPC Single-point constraint to put velocity components to zero
SPC1 Single-point constraint to put velocity components to zero
132 Dytran Reference Manual
Bulk Data Summary
Contact Surfaces
CONTACT Defines contact between Lagrangian objects
CONTINI Defines initialization of contact state between two subsurfaces
CONTREL Defines rigid-ellipsoid contact with Lagrangian grid points or rigid bodies
SURFACE Defines a multifaceted surface
SUBSURF Defines a multifaceted subsurface
CSEG Defines segments of a surface
CFACE Defines segments of a surface
CFACE1 Defines segments of a surface
Connections
JOIN Defines a rigid connection between grid points of 1-D, shell, and solids
BJOIN Defines a breakable rigid connection between grid points of 1-D and
shell elements
KJOIN Defines the kinematic join of shell and solid grid points
RCONN Defines a rigid connection between two surfaces
RCONREL Defines a connection with rigid ellipsoids for grids and surfaces
RJCYL Cylindrical-joint constraint between rigid bodies
RJPLA Planar-joint constraint between rigid bodies
RJREV Revolute-joint constraint between rigid bodies
RJSPH Spherical-joint constraint between rigid bodies
RJTRA Translational-joint constraint between rigid bodies
RJUNII Universal-joint constraint between rigid bodies
Rigid Walls
WALL Defines a rigid wall for grid points
Chapter 5: Bulk Data Entry Descriptions 133
Bulk Data Summary
Lagrangian Loading
Transient Loading
TLOAD1 Defines the transient load
TLOAD2 Defines the transient time-varying load
DAREA Defines the position and scale factor of a concentrated load
FORCE Defines the position and scale factor of a concentrated force
FORCE1 Defines a follower force, form 1
FORCE2 Defines a follower force, form 2
MOMENT Defines the position and scale factor of a concentrated moment
MOMENT1 Defines a follower moment, form 1
MOMENT2 Defines a follower moment, form 2
PLOAD Defines the position and scale factor of a pressure load
PLOAD4 Defines the position and scale factor of a pressure load
PLOADEX Defines a pressure load of which the magnitude is specified by a user subroutine
RFORCE Defines the centrifugal load
GRAV Defines the gravitational load
Enforced Motion
TLOAD1 Defines the transient enforced motion
TLOAD2 Defines the transient time-varying enforced motion
DAREA Defines the direction and scale factor of motion
FORCE Defines the direction and scale factor of motion
FORCE3 Defines the direction and scale factor of motion in local coordinate systems
FORCEEX Enforced translational velocity defined by user subroutines
MOMENT Defines the direction and scale factor of motion
134 Dytran Reference Manual
Bulk Data Summary
Initial Conditions
TIC Defines transient initial velocities of grid points
TIC1 Defines transient initial velocities of grid points
TIC2 Defines an initial rotational velocity field for grid points
TICEL Defines the transient initial conditions of element variables
TICGP Defines the transient initial conditions of grid point variables
TICEEX Transient initial conditions of element variables defined by user subroutines
TICGEX Transient initial conditions of grid-point variables by a user-written subroutine
Flow Boundary
TLOAD1 Defines the transient load
FLOW Defines the flow boundary
FLOWEX Flow boundary defined by user subroutines
FLOWDEF Defines the free Eulerian faces to be a flow boundary by default
POREX Defines a porosity model through a user-written subroutine
PORFLOW Defines a porous flow boundary
PORHOLE Defines a hole in a couple and/or GBAG(sub)surface
PORLHOLE Defines a large hole in a couple and/or GBAG (sub)surface
CSEG Defines the face to which the flow boundary is applied
CFACE Defines the face to which the flow boundary is applied
CFACE1 Defines the face to which the flow boundary is applied
Wall
WALLET Defines a wall for Eulerian material flow
Chapter 5: Bulk Data Entry Descriptions 135
Bulk Data Summary
Gravity
GRAV Defines the gravitational load
Initial Conditions
TIC Defines the initial rotational grid-point velocities for ALEGRIDpoints
TICGP Defines the transient initial grid-point variables
TICEL Defines the transient initial condition for element variables
TICEUL Defines the transient initial conditions for element variables using
geometric regions
TICVAL Defines the transient initial conditions
CYLINDER, Defines the geometrical shapes
SPHERE, BOX
Euler/Lagrange Coupling
COUP1FL Defines the surrounding variables when a segment of a coupling surface fails
COUP1INT Defines the interaction between two coupling surfaces
COUPLE Defines the general coupling between the Eulerian and Lagrangian meshes
COUPLE1 Defines the general coupling between the Roe solver for single hydro materials
and Lagrangian structures
COUOPT Defines the coupling options
COUPOR Defines the coupling surface or subsurface porosity
ALE Defines the arbitrary Lagrange-Euler (ALE) coupling
GBAG Gas bag pressure definition
GBAGC Defines flow between two gas bags
GBAGCOU General coupling to gas bag switch to save CPU time
SURFACE Defines the coupling surface
SUBSURF Defines the subsurface
Miscellaneous
Comments
$ For inserting comments in Bulk Data Section
Parameters
PARAM Specifies values for the parameters used in the solution
136 Dytran Reference Manual
Bulk Data Summary
Tabular Input
TABLED1 Tabular functions for loads, properties, materials, etc.
TABLEEX Analytical function for loads, properties, materials, etc. defined
by user subroutines
Sets
SET1 Sets of numbers for use by other entries
SETC Sets of names for use by other entries
Solution Control
ACTIVE Activates or deactivates elements and interaction
VISCDMP Defines dynamic relaxation factors for damping
Output
SECTION Cross section
Prestress Analysis
NASINIT Defines the prestress analysis logistics
$ Comment
Anything that appears after a $ on a line is treated as a comment and is ignored. If a $ appears as the first
character, the entire line is a comment.
Remark
If a comment is placed in fields which would otherwise contain data, the data in those fields is given the
fields’ default values.
ACTIVE 139
Activate Elements and Interaction
Allows you to activate parts of the program for a part of the problem time only.
+ TIME TIMEV
+ TABLE 1
Remarks
1. The default is all parts of the program are active at all times.
2. For CONTACT, an activity switch can also be set on the entry itself. These settings overrule
settings on the ACTIVE entry.
3. The active option for multimaterial with shear strength is activated by using
TYPEV = MULTIEULHYDRO.
4. For COUPLE and C in combination with PARAM, LIMITER, ROE, an activity switch can also be
set on the COUPLE1 entry. These settings overrule the settings on the ACTIVE entry.
ALE 141
Arbitrary Lagrange Eulerian (ALE) Interface
Remarks
1. SIDLG and SIDEU must reference the SID of a SURFACE entry.
2. The Eulerian and Lagrangian SURFACEs must have a one-to-one correspondence. This means
that the Eulerian and Lagrangian grid points in the SURFACEs must coincide in physical but not
in logical space (same position, different number).
3. The tolerance used in finding coinciding SURFACE nodes is defined by the ALETOL parameter.
4. ALE is not applicable in combination with the single material Euler solver with a
full-stress tensor. (EULSTRENGTH), please use the multimaterial solver instead
of (MULTIEULSTRENGTH).
142 ALEGRID
Eulerian Grid Point Motion Definition
+ G1 G2 THRU G3 BY G4 -etc.-
+ 1 2 THRU 15 BY 3
Remarks
1. The MINCUT and MAXCUT parameters define the minimum and maximum allowable grid-point
velocity of ALE grid points. Usually the defaults are sufficient.
q
u g = max MINCUT ------- u g sign u g
t
q
u g = min MINCUT ------- u g sign u g
t
where n is the normal to the free surface. u fs is the free surface velocity defined
as:
vi
i =1 -
-------------
u fs =
N
with v i the material velocity of the elements connected to the grid point.
ug
tentative
is the tentative grid point velocity.
FIXED: Grid points that are defined as FIXED move as on a fixed wall.
ug = ug – ug n n
tentative tentative
ug = ug + ug – ug t t
int tentative int
where g int is the grid point velocity of the closest internal grid point.
3. More than one ALEGRID entry can occur in input, with each one having a different type
definition. All ALEGRID entries that have the same AID are merged into one definition. This
requires a consistent definition with respect to the options of all of the ALEGRID entries that have
the same AID.
4. The number of relaxation iterations for the grid point displacement is one by default but can be
changed using PARAM,ALEITR.
5. There can be as many continuation lines as necessary.
6. The weight factors determine the grid point motion. If the option is set to COMPUTED (default),
Dytran computes the weight factors based on geometrical considerations. If the option is set to
EQUAL, all weight factors are set to a constant. The latter is automatically done when a local
distortion of the Eulerian mesh is encountered that does not allow for the computation of the
weight factors.
7. If the TYPE field is set to USER, all other fields are ignored except the NAME field which
is mandatory.
8. For a description of user-written subroutines, see Chapter 7: User Subroutines in this manual.
ALEGRID1 145
Eulerian Grid Point Motion Definition
FDIAG YES/NO C NO
Specifies if the neighboring grid points along the face diagonals need
to be taken into account for the mesh motion.
Remarks
1. The ALEGRID1 mesh motion algorithm has the following features:
No limit on the number of neighboring grid points exists. This is in contrast to the ALEGRID
algorithm where a limit of eight neighboring nodes exists.
The velocity of the grid points is based on a changing weight factor, which is calculated
accordingly
l gi u gi
u g = -----------------------------------
l g i
l g = the distance between the Eulerian grid point and the neighbor grid points i
i
2. When the Lagrangian mesh is moving very fast it can happen that the Eulerian mesh is not
properly following the structure, and Eulerian elements get distorted.
The mesh motion can be improved by increasing the value of PARAM,ALEITR. Multiple
iterations per time step will be performed to determine the grid point velocities.
3. Multiple SET1 entries with the same SID are automatically concatenated.
4. A combination of ALEGRID and ALEGRID1 entries in one analysis model is not allowed.
ATBACC 147
Acceleration Field Applied to ATB Segments
Remarks
1. The acceleration a t is defined as:
a t = T t * SCALE * N
where SCALE is the acceleration scale factor; N is the vector defined by NX, NY, and NZ; T t is
the value interpolated at time t from the table referenced by the TLOADn entry.
2. LID must be referenced by a TLOADn entry.
3. The type field on the TLOADn entry must be set to zero.
4. More than one ATBACC acceleration field can be defined per problem.
5. This acceleration field is intended to apply a crash pulse to ATB segments that define a crash
dummy. The acceleration is multiplied by the mass of the segment and the resulting force is added
as an external force.
6. To compare the accelerations of the ATB segments to experiments, the crash pulse needs to be
subtracted from the total acceleration. The acceleration of the segments as defined on the H1
entries in the ATB input file are automatically corrected.
148 ATBJNT
Interface to ATB Joints
This entry can only be used together with the ATBSEG entries that this joint connects. The ATBSEG
entries overwrite the position and orientation of the ATB segments as specified in the ATB input file. The
ATBJNT entry can be used to create a Bulk Data file containing elements and grid points to visualize the
ATB segment together with its joints. This visualization of the joints makes it possible to position the
ATB model in any available preprocessor. See also PARAM,ATBSEGCREATE.
Remark
All elements related to an ATB segment refer to the same material number. This material number is
defined on the ATBSEG entry. If the material is defined to be rigid by means of a MATRIG entry, all
elements can be easily connected to the contact ellipsoid of the ATB segment by means of an RCONREL
entry referencing the MATRIG entry. In this way, all elements related to an ATB segment move together
with the ATB segment during the analyses and can be postprocessed.
ATBSEG 151
Interface to ATB Segments
Defines the position and orientation of the ATB segments. The position and orientation as specified on
the G.2 and G.3 entries in the ATB input file will be overruled by the definitions given here.
This entry can be used to create a Bulk Data file containing elements and grid points to visualize the ATB
segment, together with the contact ellipsoid and the joints it is connected by. See also ATBJNT and
PARAM,ATBSEGCREATE.
Remarks
1. All elements related to an ATB segment reference the same material number. This material
number is defined on the ATBSEG entry. If the material is defined as rigid by means of a
MATRIGentry, all elements can be easily connected to the contact ellipsoid of the ATB segment
by means of an RCONREL entry referencing the MATRIGentry. In this way, all elements related
to an ATB segment move together with the ATB segment during the analysis and can be
postprocessed. The elements can also be used in a CONTACT ALE, and/or COUPLING surface to
define interaction between the ATB segment and other parts of the finite element model. The
forces and moments acting on the elements are transferred to the ATB segment to which they
are connected.
2. The MATRIG entry written to the file has the inertia properties of the segment, as defined in the
ATB input file.
BEGIN BULK 153
The Beginning of the Bulk Data
Marks the end of the Case Control Section and the beginning of the Bulk Data Section in the input file.
Remark
A BEGIN BULK entry must always be present.
154 BIAS
Bias Definition
Specifies a variation of the mesh-size in one direction for use in the MESH entry. The MESH entry can
create a biased or non-uniform mesh. A uniform mesh consists of a number of planes separated by a fixed
distance, but for a biased mesh the distance between subsequent planes can differ. The BIAS definition
allows specifying the locations of planes in one direction. For a number of intervals the density of planes
can be specified.
Remarks
1. The begin point of the first interval has to be equal the X0 field of the MESH entry and may be left
unspecified. The end point of the last interval is given by X0+DX as specified by the MESH entry.
In the example above the first interval is given by [-4.5, -1], The second one by [-1,1] and the last
one by [1,4.5], assuming that X0+DX =4.5 on the MESH entry that uses the bias definition as a
IBIDX.
2. The locations of the planes are written out in the OUT file as part of MESH output. Also the total
number of elements is written out.
3. Here it is assumed that the BIAS ID-number was used on the IBIDX field of the MESH entry.
4. GRWTHi is not equal 1.0 the smallest mesh-size in an interval is given by:
Xi + 1 – Xi
-----------------------------------------------------------------
GROWSM * GRSTP – 1
-----------------------------------------------------------------
GRSTP – 1
where
1
---------------
Ni – 1
GRSTP = GROWSM
Here GROWSM is the maximum of GROWTHi and 1.0/GROWTHi, which is the ratio between the
largest mesh size and smallest mesh-size. Furthermore X(i) denotes Xi and X(i+1) denotes the
next Xi value. The locations of the planes are written to the OUT file. In addition, the growth of
the element sizes is written out in the next column. This is given as the ratio in element size
between the layer of elements to the right of the plane and to the left of the plane. Let x0, x1 and
x2 denote three subsequent planes, then the element size to the left of the x1-plane is given x1-x0
and to the right it is given by x2-x1. The ratio by which the element size grows if one goes across
the x1-plane is:
X2 – X1
---------------------
X1 – X0
To get physically meaningful results, this value should not exceed 1.3 or be smaller than 0.7
156 BJOIN
Breakable Join
Defines (multiple) pairs of grid points of one-dimensional and/or shell elements to be joined during
the analysis. When the failure criterion for a grid point pair is satisfied, the grid point pair is removed
from the join and the grid point motion is computed for the separate grid points. The join ceases to exist
when all pairs of the join have failed, after which all of the grid points of the join are treated as separate
grid points
1
x bjoin = --- x gr id + x gr id
2 1 2
Remarks
1. If the TYPE field is set to USER, the user subroutine must be present in the file referenced by the
USERCODE FMS statement.
2. The breakable joins can only be used for grid points of Lagrangian one-dimensional and shell
elements. Note that any grid point can be made into a one-dimensional grid-point type by
connecting a dummy spring to the grid point.
BJOIN 159
Breakable Join
3. The constant force or constant moment failure criterion (TYPE=FOMO) is met once the following
inequality is true:
2 2 2 2
F x1 – F x2 + F y1 – F y2 + F z1 – F z2 F
In the above formula, F is either a force or a moment. F max is the value defined in the
VALUEn fields.
4. If component failure is requested (TYPE=COMPO), the comparison is performed for each
component of the force and moment vector. Depending on the criterion-type definition, the forces,
the moments, or both are taken into account to determine whether the join fails.
5. In component failure, note that if one of the determining failure component values is left blank,
this component can never cause the join to fail.
6. The first entity that satisfies the criterion for failure will cause the join to fail.
7. The undefined components in component failure are automatically set to infinity. This means that
when failure on force components is requested, the moment criteria are set to infinity. The same
is true for the forces when moment component failure is requested.
8. The user-defined criterion name can be a maximum of eight characters long.
9. At the moment of failure, an informational message is written to the output file.
10. The breakable joins for skin-stringer delamination (TYPE=RUPTURE) can only be used for beam-
shell element connections. This type of connection can also be defined by the PWELD entry. The
PWELD1 definition has an additional advantage in that it gives you access to the load on the
connection. SeePWELD1 for more details.
11. A solid-shell connection, like for example the connection of the facing and core of a sandwich
structure can be modeled using the PWELD2 entry. See PWELD2for more details.
160 BODYFOR
Body Force Loading
Remarks
1. The default for entity TYPEV is all entities of TYPE.
2. By default the components are zero, but at least one of them should be nonzero.
3. Only one BODYFOR entry per type of entity TYPEV is allowed.
162 BOFYFR1
Body Force for Eulerian Regions
Defines body force for Eulerian regions. The Eulerian regions are defined by geometric shapes. For each
coordinate direction a time-depended acceleration can be defined.
Remarks
1. BODYFR1 is only available for the multi-material Euler solver.
2. The combination of Eulerian region and material ID determines where the body force load
is applied.
3. It is allowed to cover only part of the Euler domain with BODYFR1 definitions.
4. All level indicators LEVELi must have different values. The level indicator can be negative.
5. To increase the accuracy of the region definition, the MICRO parameter can be used.
6. The total acceleration per element can be visualized by requesting the Eulerian scratch variable
FLUXVOL.
164 BOX
Defines the Shape of a Box
Box shape used in the initial condition definition on the TICEUL entry.
Remarks
1. The box is aligned with the coordinates axis.
2. Initial conditions are defined for the elements that are fully or partially inside the box. See Dytran
User’s Guide, Chapter 3: Constraints and Loading, Eulerian Loading and Constraints
3. See also TICEUL Bulk Data entry.
BOX1 165
Defines the Shape of a General BOX
Box1 shape used in the initial condition definition on the TICEUL entry.
+ X1 Y1 Z1 X2 Y2 Z2 +
+ 0 0 0 0 0 1 +
+ X3 Y3 Z3 X4 Y4 Z4 +
+ 0 0 1 1 0 0 +
+ X5 Y5 Z5 X6 Y6 Z6 +
+ 0 1 0 0 0 1 +
+ X7 Y7 Z7 X8 Y8 Z8
+ 0 0 1 1 1 0
Remarks
1. The Box1 allows a general box and edges do not need to be aligned with the coordinates axis. The
eight grid points define the box identical to the CHEXA grid point numbering. Points may
coincide as illustrated in the example values. These values give a pyramid shape.
2. Initial conditions are defined for the elements that are fully or partially inside the box. See
Eulerian Loading and Constraints.
3. See also TICEUL Bulk Data entry.
166 CBAR
Bar Element Connection
Remarks
1. The element number must be unique with respect to all other element numbers.
2. The third grid point is used to specify a vector from G1 to G3. The local x-axis of the beam is in
the direction of the beam from point G1 to G2. The local y-axis is perpendicular to the beam in
the plane containing the vector from G1 to G3. The local z-axis is perpendicular to the local x and
y-axes (see Dytran User’s Guide, Chapter 2: Elements, Beam Elements).
3. If field 6 (X1, G3) is an integer, G3 is used to define the x-y plane. If field 6 (X1, G3) is real, X1,
X2, and X3 are used.
4. The following figures define the elemental force and moment sign convention (a and b are
equivalent with G1 and G2, respectively).
168 CBEAM
Beam-Element Connectivity
+ COORD
+
Remarks
1. The element number must be unique with respect to all other element numbers.
2. The third grid point is used to specify a vector from G1 to G3. The local x-axis of the beam is in
the direction of the beam from point G1 to G2. The local y-axis is perpendicular to the beam in
the plane containing the vector from G1 to G3. The local z-axis is perpendicular to the local x-
and y-axes (See Dytran User’s Guide, Chapter 2: Elements, Beam Elements).
3. If field 6 (X1, G3) is an integer, G3 is used to define the x-y plane. If field 6 (X1, G3) is real, X1,
X2, and X3 are used.
4. Offset vectors are treated like rigid elements.
170 CDAMP1
Damper Connectivity
+ CORD FOLLOW
+ 3 G1
Remarks
1. The element number must be unique with respect to all other element numbers.
2. The damper always acts in the direction given by C1 and C2 regardless of the relative positions
of the grid points. CVISC defines a damper with an orientation that changes during the analysis.
3. Setting G1 or G2 to zero gives a grounded damper.
4. The damper can connect translational or rotational degrees of freedom.
5. The property entry PDAMP defines the damper characteristic.
CDAMP1 171
Damper Connectivity
6. If the degree of freedom is defined in a nonbasic coordinate system, the degrees of freedom G1
and G2 must be equal or one must be grounded.
7. The coordinate system CORD must be rectangular.
8. For fast rotating structures, it is advised to use a CORD3R or CORD4R to define the follow
motion. A moving coordinate system CORD4R is updated according to the full-rotation
equations, while a direction vector that rotates with G1 or G2 is updated using the Hughes-Winget
relation. The Hughes-Winget relation becomes less accurate when the rotation angle per time step
is very high.
172 CDAMP2
Linear Damper
Defines a linear scalar damper element where the damping coefficient is defined directly.
+ CORD FOLLOW
+ 3 G1
Remarks
1. The element number must be unique with respect to all other element numbers.
2. The damper always acts in the direction given by C1 and C2, regardless of the relative positions of
the grid points. CVISC defines a damper with an orientation that can change during the analysis.
3. Setting G1 or G2 to zero gives a grounded damper.
4. The damper can connect translational or rotational degrees of freedom.
5. CDAMP1 can also be used to define linear scalar dampers. When there are many dampers with the
same damping coefficient, it is more efficient to use CDAMP1.
CDAMP2 173
Linear Damper
6. When the degree of freedom is defined in a nonbasic coordinate system, the degrees of freedom
G1 and G2 must be equal or one must be grounded.
7. The coordinate system CORD must be rectangular.
8. For fast rotating structures, it is advised to use a CORD3R or CORD4R to define the follow
motion. A moving coordinate system CORD4R is updated according to the full-rotation
equations, while a direction vector that rotates with G1 or G2 is updated using the Hughes-Winget
relation. The Hughes-Winget relation becomes less accurate when the rotation angle per time step
is very high.
174 CELAS1
Scalar-Spring Connection
+ CORD FOLLOW
+ 3 G1
Remarks
1. A grounded spring is defined by setting G1 or G2 to zero in which case the corresponding C1 or
C2 is zero or blank. (A grounded grid point is a grid point where the displacement is constrained
to zero.)
2. Element numbers must be unique with respect to all other element numbers.
3. The connection grid points G1 and G2 must be distinct.
4. If the degree of freedom is defined in a nonbasic coordinate system, the degrees of freedom G1
and G2 must be equal or one must be grounded.
CELAS1 175
Scalar-Spring Connection
+ CORD FOLLOW
+ 3 G1
Remarks
1. A grounded spring is defined by:
a. Setting G1 or G2 to zero in which case the corresponding C1 or C2 is zero or blank.
b. Using a scalar point for G1 and/or G2 in which case the corresponding C1 and/or C2 is zero
or blank. (A grounded grid point is a grid point where the displacement is constrained to zero.)
2. Element numbers must be unique with respect to all other element numbers.
3. This entry completely defines the element since no material or geometric properties are required.
4. The two connection points G1 and G2 must be distinct.
5. If the degree of freedom is defined in a nonbasic coordinate system, the degrees of freedom G1
and G2 must be equal or one must be grounded.
CELAS2 177
Scalar-Spring Property and Connection
Remarks
1. The face number FID must be unique with respect to all other face numbers.
2. The CSEG entry is also used to define faces in terms of the grid-point numbers. The CFACE1
entry is also used to define faces.
3. A negative face number indicates that the face normal direction is reversed.
4. The element-face numbers are as follows:
CFACE 179
Face of an Element
180 CFACE1
Face of an Element
Defines a face on an element in terms of the element number and two grid points on the required face.
This is particularly suitable for defining the faces on solid elements.
Remark
A PLOAD4 entry with an absolute pressure of 9999. is automatically converted to a CFACE1 entry. This
makes defining CFACE1 entries in preprocessors very easy. See also Dytran User’s Guide, Chapter 9:
Running the Analysis, Using a Modeling Program with Dytran.
CHEXA 181
Element with Eight Grid Points
+ G7 G8
+ 9 10
Remarks
1. The element number must be unique with respect to all other element numbers.
2. Grid points G1 through G4 must be given in consecutive order about one quadrilateral face. G5
through G8 must be on the opposite face with G5 opposite G1, G6 opposite G2, etc.
3. Number according to the figure shown in this CHEXA entry description.
4. The property number references a PSOLID or a PEULER entry. This determines whether the
element is Lagrangian or Eulerian.
5. Only the first eight grid points on a CHEXA are used in Dytran. The excess is ignored.
CMARKB2 183
Two-noded Marker Connectivity Definition
Defines a two-noded marker beam element by means of connecting two grid points.
Remarks
1. A CMARKB2 element may refer to two types of grid points:
a. Structural grid points, thus grid points that are part of the connectivity of an element.
b. Free grid points in space. These grid points do not have mass associated with them. The
motion of these grid points is specified by the PMARKER property.
2. The ID must be unique in the model and may not be used as structural element ID.
184 CMARKN1
One-noded Marker Connectivity Definition
Defines a concentrated grid point mass and/or inertia for Lagrangian elements.
Remarks
1. All grid points in the model must have mass associated with them, either by the properties of the
elements attached to the grid point or by using a CONM2 entry.
2. When PARAM,CONM2OUT is set to NO, there is no summary on the CONM2 entries defined. This
means that the mass, momentum, and energy of the CONM2s are not added to the material and
cycle summaries. Setting PARAM,CONM2OUT,NO saves memory and CPU time.
3. The CONM2 results cannot be output on time-history or archive files.
186 CONTACT
Contact Surface
Defines contact between Lagrangian grid points and elements. The algorithm is based on the contact of
slave nodes with master faces.
+ TENDNEW
+
Remarks
1. See also the information on the contact algorithm in the Getting Started Manual.
2. The SETC ID referred to by ELLIPS may contain more than one ellipsoid. The ELLIPS option
may only use the V4 contact algorithm and the default thickness factor for the ELLIPS option
is 0.0.
196 CONTACT
Contact Surface
4. When a nonzero value has been specified for THICK and/or GAP, a contact thickness is assigned
to both the slave nodes and the master faces
CASE 1: Shell-to-shell Contact
where
t_contact = GAP
For all other options, the shell thickness of each slave node is calculated as the average thickness
of those elements in the slave surface that are connected to the slave node.
Contact occurs when the contact thickness of a slave node overlaps the contact thickness of a
master face. This is the best physical contact representation of shell structures. There are also
several other advantages to using a contact thickness:
a. Use of a contact thickness prevents “hooking” in case of T-joints:
b. Use of a contact thickness prevents losing contacts in the “dead region” on the “penetrated
side” of neighboring master faces. When a slave node enters the “dead region” between
neighboring master faces, it is not projected on either face, and the contact is lost:
CONTACT 199
Contact Surface
Using a contact thickness has the disadvantage that an unwanted initial penetration
might occurs where the edge of shell elements meets a master surface. The following is a
good example:
5. The search for the closest master face for a slave node is performed by a normal projection of the
slave node on the faces of the master surface. For the search option FULL, all faces of the master
surface are taken into account. This is the most reliable option, but takes the most
computational time.
The SLIDE search option searches for the closest master face under the assumption that a slave
node will only slide from the current master face to its neighbors during one time step. This search
algorithm is much faster than the FULL option. However, this search option can cause problems
for slave nodes that have entered the “dead-region” on the “penetrated side” between neighboring
master faces, where it can not be projected on either face, and the contact is lost because of that.
The BPLANE search option alleviates the problems for slave nodes that have entered the “dead-
region” by creating automatically a plane perpendicular to the folding line between two master
faces. Contact for slave nodes that reside in the back-up plane area is preserved and the nodes
remain in the contact search algorithm. A force perpendicular to the BPLANE is applied to those
nodes, since they are on the penetrated side of the master surface.
Because the BPLANE search algorithm is very fast, it is the recommended contact search
algorithm for air bag analysis.
200 CONTACT
Contact Surface
The BPFULL algorithm combines features of the FULL search contact algorithm and the BPLANE
search contact algorithm. The same back-up planes are generated as the BPLANE contact;
however, new contacts can be initialized during the simulation. This new initiation is especially
important for air bags that have large internal open regions and where contacts between layers
occur later during the simulation time. Special care is taken into account to initialize the correct
side of the master face so that hooking behind layers is reduced to a minimum. Consequently, this
type of contact is very CPU intensive. To this end, the new search algorithm can be skipped after
a certain time has been reached. This time can be defined by the user with the TENDNEW entry on
the CONTACT option. After this time has been reached, no new contact is searched for.
Effectively, after the new TENDNEW is reached, the BPFULL contact algorithm behaves the same
as the regular BPLANE contact algorithm.
6. An edge-to-edge contact is defined by specifying the surfaces of which you want the free edges
to be included in the contact definition. The “free” edges are derived only from the supplied
elements within those surfaces. This means that they are not necessarily the real free edges of
the model.
Limitation: when you want to use the edge-to-edge contact, you need to define a contact entry
that has both the master and the slave surface in contact be of the type SURFEDGE. Of course,
you can combine “normal” contact definitions with the edge-to-edge definition. Please note that
each contact must be separately defined as a contact specification.
You can influence the behavior of the searching algorithm that defines the edges that are in
contact. By default, the edge contact is recognized when the direction of the velocity of the point
that has potential contact is in the direction of the normal to the edge. This criterion may be too
strict for some occasions. Therefore, with the EVIEW definition on the contact specification you
may define an angle that defines a 3-D cone with the edge normal as the center line. When the
velocity vector of a point searching for contact with an edge falls within this 3-D cone, the point
is considered for contact with the edge. If the velocity vector of the point falls outside the 3-D
cone, the point is ignored in the contact search. You can use this parameter when you encounter
spurious edge-to-edge contact situations.
7. In case of V4 contact, REVERSE=ON takes effect only for edge-to-edge and master-slave
contacts. For master-slave contact, it is only necessary to align the face normal when the SIDE
entry is TOP or BOTTOM. For other situations, in principle, it is not necessary without violating
the contact constraints.
8. TENDNEW is used only when the BPFULL contact search algorithm is used. After the TENDNEW
time is reached, no new contacts are searched for.
9. A detailed description of the slave node (de)activation methods is given here. These methods are
only available for VERSION = V4:
When a master surface might fold onto itself, is more suited for eroding master-slave contact
behaves as a single surface.
CONTACT 201
Contact Surface
METHOD1 Nodes become active as slave once they reside on the outside of the mesh. In
case of master slave contact, nodes on the master surface will not act as a slave.
Nodes will be deactivated as slave once all connected elements have failed.
METHOD2 Nodes become active as slave once they reside on the outside of the mesh. In
case of master-slave contact, nodes on the master surface will not act as a slave.
Nodes will remain active as slave once all connected elements have failed.
METHOD3 Nodes are active as slave from the start of the calculation, independent of
whether they reside on the inside or the outside of the mesh. In case of master-
slave contact, nodes on the master surface will not act as a slave.
Nodes will be deactivated as slave once all connected elements have failed.
METHOD4 Nodes are active as slave from the start of the calculation, independent of
whether they reside on the inside or the outside of the mesh. In case of master-
slave contact, nodes on the master surface will not act as a slave.
Nodes will remain active as slave once all connected elements have failed.
METHOD1A For master-slave contact only. Nodes become active as slave once they reside
on the outside of the mesh. Nodes on the master surface will also act as slave,
once they reside on the outside of the mesh. This method is more suited for
eroding master-slave contact than METHOD1.
Nodes will be deactivated as slave once all connected elements have failed.
METHOD2A For master-slave contact only. Nodes become active as slave once they reside
on the outside of the mesh. Nodes on the master surface will also act as slave,
once they reside on the outside of the mesh. This method is more suited for
eroding master-slave contact than METHOD2.
Nodes will remain active as slave once all connected elements have failed.
METHOD3A For master-slave contact only. Nodes are active as slave from the start of the
calculation, independent of whether they reside on the inside or the outside of
the mesh. Nodes on the master surface will also act as slave, once they reside on
the outside of the mesh. This method is more suited for eroding master-slave
contact than METHOD3.
Nodes will be deactivated as slave once all connected elements have failed.
METHOD4A For master-slave contact only. Nodes are active as slave from the start of the
calculation, independent of whether they reside on the inside or the outside of
the mesh. Nodes on the master surface will also act as slave, once they reside on
the outside of the mesh. This method is more suited for eroding master-slave
contact than METHOD4.
Nodes will remain active as slave once all connected elements have failed.
202 CONTACT
Contact Surface
To choose the correct slave activity switch, you can use the following flow schemes. The selection
of a method depends on the desired results, and can be captured by three questions:
a. Only nodes on the outside of the mesh are active?
In most cases only the slave nodes on the outside need to be active.
In cases of high-velocity impact, it might be necessary to activate the internal slave nodes also.
This will prevent missing contacts for slave nodes that move across the monitoring region of
the master face during the time-step it is activated.
b. Deactivate slave nodes when all connected elements have failed?
This determines whether slave nodes will remain active after all its connected elements have
failed. This option only applies to an adaptive contact.
c. Nodes on the master surface will also act as slave?
When a master surface might fold onto itself this will prevent the master surface from
penetrating itself. Therefore the master surface will behave as a single surface.
Flow scheme for a single surface contact:
CONTACT 203
Contact Surface
The contact force is determined by force-deflection curves for loading and unloading. Damping can be
specified either as a constant value or as a tabular function.
Remarks
1. Either K or LOAD must be specified.
2. None or just one of the options B-CONST, or B-TABLE must be specified.
CONTINI 207
Contact Initialization for In-Plane Folded Air Bags
Defines the initial contact state between two SUBSURF entries. Used for contact initialization of in-plane
folded air bags.
Remarks
1. By default the SIDE is equal to the SIDE as specified on the CONTACT entry.
2. It is allowed to have multiple CONTINIs defined for a slave subsurface. If a grid point of a slave
subsurface (SUBID1) finds a contact in more than one master subsurface, only the ones with the
highest level are accepted.
For example, suppose a subsurf is used as slave in three CONTINI definitions:
CONTINI,1,101,SUBID1,SUBID2,,LEVEL1
CONTINI,2,101,SUBID1,SUBID3,,LEVEL2
CONTINI,3,101,SUBID1,SUBID4,,LEVEL3
When a slave node of SUBSURF,SUBID1 finds a contact in all three master SUBSURFs. The
following logic applies:
LEVEL1=LEVEL2=LEVEL3 all contacts are accepted
LEVEL1>LEVEL2,LEVEL3 only contact 1 is accepted
LEVEL1=LEVEL2>LEVEL3 only contact 1 and 2 are accepted
LEVEL1,LEVEL2<LEVEL3 only contact 3 and 2 are accepted
LEVEL1<LEVEL2>LEVEL3 only contact 2 is accepted
3. The options LEVEL, SIDE, and REVERSE are only valid for contact version V4.
CONTREL 209
Contact with Rigid Ellipsoids
Defines contact between rigid ellipsoids and Lagrangian grid points or rigid bodies.
Remarks
1. For grid points attached to Lagrangian elements, the default for ARF is 1.0. For rigid surfaces, the
default is 0.1.
2. Only rigid surfaces can be defined in the SET1 entry and are referenced by their number. MATRIG
and RBE2-FULLRIGs cannot be referenced by this entry. Use the CONTACT entry instead.
210 CORD1C
Cylindrical Coordinate System Definition, Form 1
Defines up to two cylindrical coordinate systems per entry by referencing three grid points that define a
coordinate system. The grid points must be defined in a coordinate system other than the coordinate
system that is being defined. The first grid point is the origin, the second lies on the z-axis, and the third
lies in the plane of the azimuthal origin.
Remarks
1. All coordinate system numbers must be unique.
2. The three grid points G1, G2, and G3 must not be colinear.
3. The location of a grid point in the coordinate system is given by ( R , , Z ) where is measured
in radians.
4. The velocity component directions at P depend on the location of P as shown above by U r , U ,
and U z , when the coordinate system is used in a motion prescription.
5. One or two coordinate systems may be defined on a single line.
212 CORD1R
Rectangular Coordinate System Definition, Form 1
Defines up to two rectangular coordinate systems per entry by referencing three grid points that define a
coordinate system. The grid points must be defined in a coordinate system other than the coordinate
system that is being defined. The first grid point is the origin, the second lies on the z-axis, and the third
lies in the x-z plane.
Remarks
1. All coordinate system numbers must be unique.
2. The three grid points G1, G2, and G3 must not be collinear.
3. The location of a grid point in this coordinate system is given by ( X , Y , Z ).
4. The velocity component directions at P depend on the location of P as shown above by U x , U y ,
and U z , when the coordinate system is used in a motion prescription.
5. One or two coordinate systems may be defined on a single line.
214 CORD1S
Spherical Coordinate System Definition, Form 1
Defines up to two spherical coordinate systems per entry by referencing three grid points that define a
coordinate system. The grid points must be defined in an independent coordinate system. The first grid
point is the origin. The second lies on the z-axis. The third lies in the plane of the azimuthal origin.
Remarks
1. All coordinate system numbers must be unique.
2. The three grid points G1, G2, and G3 must not be collinear.
3. The location of a grid point in this coordinate system is given by ( R , , ) where and are
measured in degrees.
4. The velocity component directions at P depend on the location of P as shown above by U r , U ,
and U , when the coordinate system is used in a motion prescription.
5. Grid points on the polar axis may not have their displacement directions defined in this coordinate
system, since an ambiguity results.
6. One or two coordinate systems may be defined on a single line.
216 CORD2C
Cylindrical Coordinate System Definition, Form 2
Defines a cylindrical coordinate system by referencing the coordinates of three grid points. The first point
defines the origin, the second defines the direction of the z-axis, and the third lies in the plane of the
azimuthal origin. The reference coordinate system must be independently defined.
+ C1 C2 C3
+ 5.2 1.0 -2.9
Remarks
1. The continuation line must be present.
2. The three points (A1, A2, A3), (B1, B2, B3), and (C1, C2, C3) must be unique and must not
be collinear.
3. All coordinate system numbers must be unique.
4. The location of a grid point in the coordinate system is given by ( R , , Z ) where is measured
in degrees.
5. The velocity component directions at P depend on the location of P as shown above by U r , U ,
and U z when the coordinate system is used in a motion prescription.
6. A RID of zero references the basic coordinate system.
218 CORD2R
Rectangular Coordinate System Definition, Form 2
Defines a rectangular coordinate system by referencing the coordinates of three points. The first point
defines the origin, the second defines the direction of the z-axis, and the third defines a vector that, with
the z-axis, defines the x-z plane. The reference coordinate system must be independently defined.
+ C1 C2 C3
+ 3.14 .1592 .653
Remarks
1. The continuation line must be present.
2. The three points (A1, A2, A3), (B1, B2, B3), and (C1, C2, C3) must be unique and must not
be collinear.
3. All coordinate system numbers must be unique.
4. The location of a grid point in this coordinate system is given by ( X , Y , Z ).
5. The velocity-component directions at P depend on the location of P as shown above by U x , U y ,
and U z , when the coordinate system is used in a motion prescription.
6. An RID of zero references the basic coordinate system.
220 CORD2S
Spherical Coordinate System Definition, Form 2
Defines a spherical coordinate system by referencing the coordinates of three points. The first point
defines the origin, the second defines the direction of the z-axis, and the third lies in the plane of the
azimuthal origin. The reference coordinate system must be independently defined.
+ C1 C2 C3
+ 5.2 1.0 -2.9
Remarks
1. The continuation line must be present.
2. The three points (A1, A2, A3), (B1, B2, B3) and (C1, C2, C3) must be unique and must not be
collinear.
3. All coordinate system numbers must be unique.
4. The location of a grid point in this coordinate system is given by ( R , , ) where and are
measured in degrees.
5. The velocity components directions at P depend on the location of P as shown above by U r , U ,
and U , when the coordinate system is used in a motion prescription.
6. Grid points on the polar axis may not have their displacement directions defined in this coordinate
system, since an ambiguity results.
7. A RID of zero references the basic coordinate system.
222 CORD3R
Moving Rectangular Coordinate System Definition, Form 1
Defines a rectangular coordinate system by referencing three grid points. The grid points must be defined
in an independent coordinate system. The first grid point is the origin, the second lies on the z-axis, and
the third lies in the x-z plane. The position and orientation of the coordinate system is updated as the grid
points move.
Remarks
1. All coordinate system numbers must be unique.
2. The three points G1, G2, G3 must not be collinear.
3. The location of a grid point P in this coordinate system is given by ( X , Y , Z ).
4. The displacement coordinate directions at P are shown above by ux , uy , and uz .
5. One or two coordinate systems may be defined on a single line.
6. The orientation of the coordinate system is updated each time step based on the motion of the
grid points.
224 CORD4R
Moving Rectangular Coordinate System Definition, Form 2
Defines a rectangular coordinate system by referencing the coordinates of three points. The first point
defines the origin, the second defines the direction of the z-axis, and the third defines a vector that, with
the z-axis, defines the x-z plane. The position and orientation of the coordinate system moves during the
analysis by prescribed translation and rotation.
+ C1 C2 C3 +
+ 5.2 1.0 -2.9 +
Remarks
1. The continuation line must be present.
2. The three points (A1, A2, A3), (B1, B2, B3), and (C1, C2, C3) must be unique and must not
be collinear.
3. All coordinate-system numbers must be unique.
4. The location of a grid point P in this coordinate system is given by ( X , Y , Z ).
5. The displacement coordinate directions at V are shown by ux , uy , and uz .
226 CORDROT
Corotational-frame Definition
Remarks
1. The DMAT and DMATEL entries can refer to this type of coordinate system.
2. G1 defines the origin, G2 lies on the corotational z-axis, and G3 lies in the corotational
(X-Z) plane.
Figure 5-11 Element Corotational Frame According to the Example Given Above
3. The orientation of the element corotational frame is updated according to the spin of the element.
4. If the fields G1, G2, G3 are left blank, the default applies.
5. If it is referred by linear tetrahedron elements, the default of G1, G2, G3 is 1, 2, 4, respectively
COUHTR 227
Heat Transfer Model to be Used with COUPLE Entry
Defines an heat transfer model suited for Euler Coupled analyses. The heat transfer model is defined as
part of the coupling surface.
Remarks
1. The same HTRTYPE entry referenced from this COUHTR entry can be referenced by a GBAGHTR
entry. This allows for setting up the exact same model for either a uniform pressure model or an
Euler Coupled model:
This makes it possible to set up the model using the switch from full gas dynamics to uniform
pressure (GBAGCOU).
2. A mixture of multiple COUHTR with different HTRTYPEs is allowed.
3. For the same SUBSURF, multiple different types of heat transfer may be defined.
4. A more detailed description can be found in Dytran User’s Guide, Chapter 6: Air Bags and
Occupant Safety, Porosity in Air Bags.
COUINFL 229
Inflator Model to be Used with COUPLE Entry
Defines an inflator model suited for Euler Coupled analyses. The inflator model is defined as part of the
coupling surface.
Remarks
1. The INFLATR, INFLATR1, INFLHYB, or INFLHYB1 inflator geometry and location is defined
by a subsurface (SUBID). The area of the hole through which the gas enters is equal to the area
of the subsurface multiplied by COEFFV. A value of COEFFV = 1.0 opens up the complete
subsurface area, while a value of COEFFV = 0.0 results in a closed inflator area with no inflow.
2. The same INFTYPE entry referenced from this COUINFL entry can be referenced by a
GBAGINFL entry. This allows for setting up the exact same model for either a uniform pressure
model or an Euler Coupled model:
This makes it possible to set up the model using the switch from full gas dynamics to uniform
pressure (GBAGCOU).
3. One couple entry can reference more than one COUINFL entry. This allows for modeling multiple
inflators in an airbag module.
COUOPT 231
Coupling Options
Defines the interaction factor and a pressure load from the covered side acting on a SURFACE
or SUBSURF.
+ PLCOVER PLCOVERV
+ CONSTANT 1.E5
Remarks
1. The effect of specifying an interaction FACTOR is similar to specifying a porosity coefficient on
a COUPOR entry. The difference is that in this case the SURFACE or SUBSURF still acts as a
wall boundary for the Eulerian material.
2. Applying a PLCOVER instead of applying a pressure load on the faces through either a PLOAD,
PLOAD4, or DAREA entry gives the following differences:
a. PLCOVER is applied only when there is a balancing Eulerian pressure greater than zero.
b. Possible porosity as defined on a COUPOR entry is taken into account when applying
the PLCOVER.
c. With PARAM,PLCOVCUT you can define a cut-off time that is applied to PLCOVER.
3. The covered side of a SURFACE lies on the side where there is no Eulerian material. See Dytran
User’s Guide, Chapter 4: Fluid Structure Interaction, General Coupling.
COUP1FL 233
Coupling Surface Failure
Defines the surrounding variables when a segment of a coupling surface will fail.
Remarks
1. This entry can only be used in combination with PARAM,FASTCOUP,FAIL and with either the
HYDRO, MMHYDRO, or MMSTREN Euler Solver. For restrictions on the use of COUP1FL
refer to param,flow-method. The coupling surface failure is associated with the element failure of
the structure to which the surface is connected. Therefore, you have to define a failure model for
the structure for the entry to take effect in the analysis.
2. For the Roe solver at least one of the surrounding variables should be defined. The default value
of the density (RHO) will be set equal to the reference density as defined on the DMAT entry and
the other variables (SIE, XVEL, YVEL, and ZVEL) are, by default, equal to zero.
3. The coupling surface must only consist of CQUADs and/or CTRIAs elements.
4. The PRESSURE field has to be left blank in combination with the Roe solver.
5. In combination with multi-material Euler, only outflow of material is allowed. Each material in
an outflow Euler element is transported. The materials are transported in proportion to their
relative volume fractions.
234 COUP1INT
Coupling Surface Interaction
Remarks
1. This entry can only be used in combination with PARAM,FASTCOUP, ,FAIL and with either
the HYDRO, MMHYDRO or MMSTREN Euler Solver. For restrictions on the use of
COUP1INT refer to PARAM, FLOW-METHOD. The interaction will be activated when failure of
a Lagrangian structure on which the coupling surface lies is defined. Therefore, you have to define
a failure model for the material of the structure.
2. The coupling surface should consist of CQUADs and/or CTRIAs.
3. For more detail on modeling flow between Eulerian domains, see PARAM, FLOW-METHOD.
COUPLE 235
General Euler-Lagrange Coupling Surface
Defines a coupling surface that acts as the interface between an Eulerian (finite volume) and a Lagrangian
(finite element) domain.
Remarks
1. All coupling surfaces must from a multi-faceted closed volume. If necessary, additional segments
must be defined to achieve the closed volume. The closed volume must intersect at least one Euler
element initially.
2. All segments must de attached to the face of an element. Dummy elements can be used to define
any additional segments that are required to create the closed volume.
3. The normals of all segments that from the coupling surface must point in the same general
direction and result in a positive closed volume. Setting the REVERSE option to ON ensures that
this condition is satisfied, regardless of the initial definition of the segments.
4. The COVER field determines how Eulerian elements that are inside and outside of the coupling
surface are processed. The default setting of INSIDE is appropriate for most of the problems. In
the majority of analyses, the Eulerian material flows around the outside of the coupling surface.
Therefore, the Eulerian elements that fall within the coupling surface do not contain material.
For some specific applications, such as air bag inflation, the Eulerian material (gas) is completed
contained within the coupling surface. In these cases, the COVER definition should be set
to OUTSIDE.
238 COUPLE
General Euler-Lagrange Coupling Surface
5. When you want to use the fast coupling algorithm, you can define the parameter
PARAM,FASTCOUP in the input file. The algorithm then used is substantially faster than the
general coupling. The restriction is that you cannot use an arbitrarily shaped Euler mesh with the
fast coupling algorithm. All element faces of the Euler mesh must have their normal pointing in
any of the three basic coordinate directions. Thus, the mesh must be aligned with the three basic
coordinate directions.
6. The friction model implemented for the coupling algorithm is a simple Coulomb friction
definition. The friction coefficient is defined as:
– v
= k + s – k e
where s is the static friction coefficient, k is the kinetic friction coefficient, the exponential
decay coefficient and v the relative sliding at the point of contact.
7. An initial gas composition is for use with the single-material hydrodynamic Euler solver and an
ideal-gas equation of state (EOSGAM) only.
8. Multiple coupling surfaces are available when you associate one Eulerian domain with a single
coupling surface by either using the SET1ID or the MESHID option. Note that only one of the
two options may be set and work only in combination with the fast coupling algorithm defined by
PARAM,FASTCOUP.
9. The COUP1FL option is available and valid only in combination with the fast coupling algorithm
with the failure option (PARAM,PARAM, ,FAIL). If no number is given the default values of the
surrounding variables are used; the density (RHO) is set equal to the reference density as defined
on the DMAT entry. By default, the other variables (SIE, XVEL, YVEL, and ZVEL are set equal
to zero.
10. If an ACTIVE entry is present, its definition is ignored in case the TDEAC value is defined in
combination with the fast coupling algorithm (PARAM,FASTCOUP).
11. The skin friction is defined as:
w
C f = --------2-
u
Here, w denotes the shear friction in an Euler element adjacent to a couple surface segment where
is the density and u is the tangential relative velocity in the Euler element that is adjacent to a
couple surface segment.
COUPLE1 239
Euler-Lagrange Coupling Surface
Use COUPLEas this entry will be obsolete in the next release of Dytran.
Defines a coupling surface that acts as the interface between an Eulerian and a Lagrangian mesh for the
Roe solver for single hydrodynamic materials.
Remarks
1. All coupling surfaces must form a multifaceted closed volume. If necessary, additional segments
must be specified to achieve this.
2. All segments must be attached to the face of an element. Dummy elements must be used to define
any additional segments that are required to create a closed volume.
3. The normals of all the segments that form the coupling surface must point in the same general
direction and result in a positive closed volume. Setting the REVERSE field to ON ensures that
this condition is satisfied, regardless of how the segments are defined initially.
4. The COVER field determines how Eulerian elements that are inside and outside of the coupling
surface are processed. The default setting of INSIDE is appropriate for most problems, since in
the majority of analyses, the Eulerian material flows around the outside of the coupling surface.
Therefore, the Eulerian elements within the coupling surface are empty. However, for some
specialized applications (such as air bag inflation), the Eulerian material is completely contained
within the coupling surface, and in these cases COVER should be set to OUTSIDE.
5. For the fast coupling algorithm use PARAM,FASTCOUP.
6. The COUPLE1 entry can only be used in combination with PARAM,LIMITER,ROE.
7. Multiple coupling surfaces can be used defining one Eulerian region belonging to each coupling
surface by setting the SET1ID or the MESHID option. Only one of the two options can be set and
works only in combination with PARAM,FASTCOUP.
8. The COUP1FL option is only working in combination with PARAM,FASTCOUP, ,FAIL. If
no number is given, the default values of the surrounding variables are given; the RHO is equal to
the reference RHO on the DMAT entry and the other variables (SIE, XVEL, YVEL and ZVEL) are,
by default, equal to zero.
9. The ACTIVE entry is ignored in case TDEAC is used in combination with PARAM,FASTCOUP.
COUPOR 241
Coupling Porosity
Remarks
1. A mixture of multiple COUPORs with different PORTYPEs is allowed.
2. All options of PORTYPE except PORFLOW, POREX, PORFCPL, and PORFLCPL can also be
referenced by a GBAGPOR. This makes it possible to setup the exact same model for either a
uniform pressure model (GBAG GBAGPOR) or an Eulerian model (COUPLE COUPOR). It
allows for setting up the model using a switch from full gas dynamics to uniform
pressure (GBAGCOU).
3. The options PORFGBG and PERMGBG can be used to model air bags with
different compartments.
4. The pressure, as defined by a PORFLOW or PORHOLE entry, is exerted on the Eulerian material.
Similarly, the pressure in the connected GBAG, in case of a PORFGBG entry, is exerted on the
Eulerian material. This pressure is applied over the open area only. The open area is equal to the
area of the (sub)surface multiplied by COEFFV. The remaining closed area behaves as a wall
boundary condition for the gas.
5. Any model that is not supported by the default types can be user-programmed in a subroutine
called EXPOR.
6. To determine to use small hole definition (PORHOLE/PORFGBG/PORFCPL) or large hole
definition PORLHOLE/PORFLGBG/PORFCPL) depends on the size of the hole relative to the
size of the Euler elements. In general, when the size of the hole is 2-3 times larger than the Euler
elements, use the velocity (or large hole) definition. When it is smaller use the pressure (or small
hole) definition.
246 CPENTA
Solid Element with Six Grid Points
Remarks
1. The element number must be unique with respect to all other elements.
2. G1, G2, and G3 must define a triangular face. G4, G5, and G6 define the opposite face with G1
opposite G4; G2 opposite G5, etc.
3. The faces may be numbered either clockwise or counterclockwise.
4. The Lagrangian CPENTA element performs poorly compared with the CHEXA element. This
element should only be used where the geometry demands it, and it should be located well away
from any critical areas. Always use the CHEXA element if you can.
5. The property number references a PSOLID or a PEULER entry. This determines whether the
element is Lagrangian or Eulerian.
CQUAD4 247
Quadrilateral Element Connection
+ T1 T2 T3 T4
+
T1-T4 Thickness at the grid points G1 through G4. R > 0.0 See Remark 4.
248 CQUAD4
Quadrilateral Element Connection
Remarks
1. The element number must be unique with respect to all other elements.
2. Grid points G1 to G4 must be ordered consecutively around the perimeter of the element.
3. If a CQUAD4 element has a thickness of 9999. (set on the PSHELL entry), it is not a shell element
but it is converted to a CSEG entry. This conversion allows CSEGs to be easily defined using
standard preprocessors. See Dytran User’s Guide, Chapter 9: Running the Analysis, Using a
Modeling Program with Dytran for details.
4. If the four grid-point thicknesses are defined, the element thickness is the average of the defined
thickness at the four grid points. If the thicknesses are not defined, the default thickness as
specified on the PSHELLentry is used.
5. The THETA entry is only used with orthotropic materials.
CROD 249
Rod Element Connection
Remarks
1. Element numbers must be unique with respect to all other element numbers.
2. Only one rod element may be defined on a single line.
250 CSEG
Segment of a Contact Surface or Coupling Surface
Remarks
1. The segment number must be unique with respect to all other segments.
2. Grid points G1 to G4 must be ordered consecutively around the perimeter of the element.
3. Segments can be automatically generated for shell and membrane elements, thereby saving the
effort of creating several CSEG entries for contact surfaces and coupling with CQUAD4 and
CTRIA3 elements. The elements for which segments are automatically generated are selected on
SET1 entries referenced by the SURFACE entry.
4. To simplify the generation and checking of CSEG entries, CSEG entries can alternatively be
defined using the CQUAD4 and CTRIA3 entries with a thickness of 9999. For details, see Dytran
User’s Guide, Chapter 9: Running the Analysis, Using a Modeling Program with Dytran.
5. Segments also can be defined using the CFACE and CFACE1 entries.
CSPR 251
Spring Connection
Remarks
1. The element number must be unique with respect to all other elements.
2. This entry defines a spring acting between two grid points. The force always acts in the direction
of the line connecting the two grid points. The direction changes during the analysis as the grid
points move.
3. The spring can have a linear or nonlinear force/deflection characteristic depending on the PSPR
entry it references.
Linear elastic with failure (PSPR)
Nonlinear elastic (PSPR1)
User-defined (PSPREX)
4. CELAS1 and CELAS2define springs with a fixed orientation.
252 CTETRA
Solid Element with Four Grid Points
Remarks
1. The element number must be unique with respect to all other element numbers.
2. The element can be numbered in any convenient order.
3. There are two types of Lagrangian CTETRA elements. The first one is based on linear tetrahedron
FE formulation. The second one is based on collapsed CHEXA formulation that is the default due
to upward compatibility reason. It performs poorly compared with the CHEXA element and should
not be used unless absolutely necessary. It should be located well away from any area of interest.
4. The property number references a PSOLIDor PEULER entry. This determines whether the
element is Lagrangian or Eulerian. To activate the linear tetrahedron FE formulation, IN and ISOP
entry of the PSOLID must be set to 1.
CTRIA3 253
Triangular Element Connection
+ T1 T2 T3
+
T1-T3 Thickness at the grid points G1 through G3. R > 0.0 See Remark 3.
254 CTRIA3
Triangular Element Connection
Remarks
1. The element number must be unique with respect to all other elements.
2. Grid points G1 to G3 must be ordered consecutively around the perimeter of the element.
3. If a CTRIA3 element has a thickness of 9999 (set on the PSHELLn entry), it is not a shell element
but is converted to a CSEG entry. This conversion allows CSEGs to be easily defined using
standard preprocessors. See Dytran User’s Guide, Chapter 9: Running the Analysis, Using a
Modeling Program with Dytran for details.
If the three grid point thicknesses are defined, the element thickness is the average of the defined
thickness at the three grid points.
If the thicknesses are not defined, the default thickness as specified on the PSHELL entry is used.
CVISC 255
Damper Connection
Remarks
1. The element number must be unique with respect to all other element numbers.
2. This entry defines a damper acting between two grid points. The force always acts in the direction
of the line connecting the two grid points. The direction changes during the analysis as the grid
points move.
3. The damper can have a linear or nonlinear force/velocity characteristic depending on the PVISC
entry it references.
Linear (PVISC)
Nonlinear (PVISC1)
User-defined (PVISCEX)
4. CDAMP1 and CDAMP2 define dampers with a fixed orientation.
256 CYLINDER
Defines the Shape of a Cylinder
Cylindrical shape used in the initial condition definition on the TICEUL entry.
+ RAD
+ .5
Remarks
1. A cylinder is defined by the two end points of the cylinder axis and a radius.
2. Initial conditions are defined for the elements that are fully or partially inside the cylinder. See
Dytran User’s Guide, Chapter 3: Constraints and Loading, Eulerian Loading and Constraints.
3. Also see theTICEUL Bulk Data entry.
DAREA 257
Concentrated Load or Enforced Motion
This entry is used in conjunction with a TLOAD entry and defines the location and direction of a
concentrated load or enforced motion with a scale factor.
Remarks
1. One or two loads can be defined on a line.
2. At time t , the load F t is given by
F t = SCALE * T t
where SCALE is the scale factor and T t is given by a table referenced from the TLOAD entry.
3. The load direction is defined in the basic coordinate system.
4. The direction of the load does not change during the analysis.
5. If G references a MATRIG, an RBE2 FULLRIG, or a RIGID surface, the load is applied to the
center of the rigid body. If G references a MATRIG, G must be MR<id>, where id is the MATRIG
number. If G references an RBE2 FULLRIG, G must be FR<id>, where id is the RBE2 number.
If G references a RIGID surface, G is the RIGID surface number.
6. If the TYPE field on the TLOAD entry is 0, it defines a force or moment applied to a grid point. If
the TYPE field is 2, it defines an enforced motion of the grid point. If the TYPE field is set to 12,
it defines an enforced motion applied to the center of a rigid body. If the TYPE field is 13, it
defines a force or moment applied to the center of a rigid body.
258 DETSPH
Spherical Detonation Wave
Defines the ignition point from which a spherical detonation wave travels, causing the reaction of high
explosive materials.
Remark
An element detonates when a spherical detonation wave originating from the detonation point at the
specified time reaches the element.
DMAT 259
General Constitutive Model
Defines a complete constitutive model as a combination of an equation of state, a shear model, a yield
model, a failure model, a spall model (PMIN), and corotational frame.
Remarks
1. This material model can be used with Lagrangian and Eulerian solid elements and membrane
elements.
2. If YID is blank or zero, a hydrodynamic yield model is used.
3. For Eulerian elements, if the TYPE field on the PEULER entry is set to HYDRO, then YID is either
blank or references a YLDHY entry, and SID is blank. Conversely, if the TYPE field is set to
STRENGTH, a non hydrodynamic yield model is specified.
4. This material is discussed in Materials.
5. Materials of shell elements need to be specified using the MAT1, MAT8, DMATEP, DYMAT24 or
SHEETMAT entries.
6. If no PMINCentry is referenced, a minimum pressure of zero is assumed for the Eulerian elements,
while spallation is prevented for the Lagrangian solid elements by assuming a minimum pressure
of -1.E20. The PMINC entry will be ignored when a cavitation model through the EOSTAIT entry
has been given.
7. The definition of a corotational coordinate system can only be used for Lagrangian solid elements.
If no corotational coordinate system is specified, all stresses are in the basic coordinate system.
8. The failure model for Eulerian materials can be FAILEXor FAILMPS. For Lagrangian materials
FAILMPS, FAILEX, FAILMES, and FAILSDTcan be addressed.
9. When PARAM,PMINFAIL is also set and a failure model is defined, Lagrangian solid elements
also fail on the defined spallation pressure.
DMATEL 261
Isotropic Elastic Material Properties
Defines the properties of an isotropic elastic material for Lagrangian solid and membrane elements.
Remarks
1. Only two of the elastic constants E, Nu, G, and K should be defined.
2. The behavior of this material is discussed in Materials.
3. This material model can be used only with Lagrangian solid and membrane shell elements.
4. The definition of the corotational coordinate system can be used only for Lagrangian
solid elements. If no corotational coordinate system is specified, all stresses are in the basic
coordinate system.
5. For air bag modeling the following values of CSCALE and DMPFAC are suggested:
CSCALE = 0.1
DMPFAC= 0.05 to 0.20
6. The entry PMAXCUT, which was supported by Dytran V4.5 has become obsolete. A better
methodology is now offered by scaling the compressive stresses in the principal directions, and
using damping to suppress high-frequency oscillations (CSCALE and DMPFAC).
7. The Initial Metric Method relaxation factor is used to slow down the expansion of the membrane
elements during the calculation. The default is sufficient in most simulations. The value of
IMMREL is not used when the type of IMM is zero (see PARAM, IMM). The Initial Metric Method
is described in the Dytran User’s Guide in Initial Metric Method for Air Bags.
DMATEP 263
Elastoplastic Material Properties
Defines the properties of an isotropic-elastoplastic material for shell and beam elements.
Remarks
1. Only two of the elastic constants E , v , G , or K should be defined.
2. The behavior of this material is discussed in Materials.
3. This material model can be used only with shell and beam elements.
4. If YID is 0 or blank, the material is elastic.
5. YID can refer to a YLDVM entry, in which case the material is elastoplastic with isotropic
hardening, or for CQUADy and CTRIAz elements only, to a YLDJC entry to define a Johnson-
Cook yield model.
6. If an elastoplastic material is specified for Belytschko-Schwer beams, a resultant plasticity model
is used. The entire cross section yields at once.
7. The failure models that can be addressed by the DMATEP material definition are FAILMPS
and FAILEX
264 DMATOR
Orthotropic Elastic Material Properties
+ X1 Y1 Z1 X2 Y2 Z2 +
+ +
v ab , v ac , v bc , v ba , v ca , v cb
Remarks
1. The continuation line with bulk-viscosity data can be omitted.
2. The behavior of this material is discussed in Materials.
3. This material model can be used only with Lagrangian solid elements.
4. The failure models addressed by an orthotropic (DMATOR) material definition are FAILEX
FAILEX1, FAILMES, FAILPRS, and FAILEST.
5. If FAILEX1, the extended user-defined failure, is used, set the OPTION to either ELMAT or
ELPROP. The user-defined failure, FAILEX1, gives access to the material properties on an
element basis.
6. The sum of any two ratios is less or equal to 1.
DYMAT14 267
Soil and Crushable Foam Material Properties
Defines a nonlinear material for Lagrangian solid elements that crushes under hydrostatic loading and is
elastic-plastic under deviatoric loading. Material failure can be included.
+ A0 A1 A2 YIELD YSTYP +
+ 1. 0. 0. YSURF DYNA +
Remarks:
1. If BULKTYP, BULKQ, or BULKL are blank or zero the default values are used.
2. The continuation line with the bulk-viscosity data can be omitted.
3. The pressure-volume characteristic can either be defined in terms of the amount of crush, which
is minus the engineering strain and is defined as (1 – V/V0), with V/V0 as the relative volume; or
in terms of the volumetric (true) strain which is defined as:
t
dV
-----
V
- or, ln V V 0 .
t0
If the YSURF option is used, the yield surface in three-dimensional space is defined by s = 0
here
1 2 2
s = --- s ij s ij – B 0 + B 1 p + B 2 p = J 2 – B 0 + B 1 p + B 2 p
2
where s ij are the deviatoric stresses and J 2 is the second invariant of the stress deviation. The
coefficients B 0 , B 1 , and B 2 can be related to the coefficients A 0 , A 1 , and A 2 , which are defined
on the DYMAT14 entry. The relation between the coefficients depends on the YSTYP field as
shown below. If the YSTYP field is DYTRAN, then
B0 = A0
B1 = A1
B2 = A2
Thus, the yield stress (see Dytran User Guide, Chapter 3: Constraints and Loading) is defined as
2
y = 3 A0 + A1 p + A2 p
2
B 1 = --- A 0 A 1
3
1 2
B 2 = --- A 1
3
and A 2 is ignored.
Thus, the yield stress is defined as
y = A0 + A1 p
8. The behavior of this material is described in Dytran Theory Manual, Chapter 3: Materials.
270 DYMAT24
Piecewise Linear Plasticity Material
Defines the properties of a nonlinear, plastic material with isotropic hardening where the stress-strain
curve is piecewise linear for shell, beam and Lagrangian solid elements.
Remarks:
1. If BULKTYP, BULKQ, or BULKL are blank or zero, the default values apply.
2. The continuation line with the bulk-viscosity data can be omitted.
3. If TABLE is blank or zero, a bilinear stress-strain curve is assumed. If TABLE has a value, it refers
to a TABLED1 entry giving the stress-strain curve for the material.
4. If TABLE is defined, the value of YIELD should be left blank, since it is determined from the
stress-strain curve.
5. If TABY is blank or zero, and D and P are blank or zero, the yield stress does not vary with strain
rate. If TABY has a value, then it references a TABLED1 entry, which gives the variation with
strain rate of the scale factor applied to the yield stress (D and P must be blank or zero).
If TABY is blank or zero and D and P are defined, the enhancement of the yield stress with strain
rate is calculated as
d 1P
·
------ = 1 + ----
y D
where d is the dynamic stress and y is the static yield stress (YIELD), and · is the equivalent
plastic strain rate.
6. If TYPE is set to ENG or TRUE, Young’s modulus is calculated from the stress-strain curve. When
Young’s modulus is specified together with TYPE set to ENG or TRUE, the calculated Young’s
modulus is substituted by the value specified.
7. The behavior of this material is described in Section Materials.
8. This material can only be used with Lagrangian solid, shell and beam elements.
272 DYMAT25
Cap Material Model
Defines a kinematic hardening Cap material model. The material can be used to model soil with
compaction to capture a soft soil response. It can also be used to model materials like concrete or rock.
+ TOFF +
+ -1.0E+11 +
Remarks
1. If BULKTYP, BULKQ, or BULKL are blank or zero, the default values apply.
2. The continuation lines with the bulk viscosity data may be omitted.
3. For a physically meaningful model, the value of the failure envelope exponential coefficient
should be less than the failure envelope parameter .
4. This material can only be used with Lagrangian solid elements.
5. The tension cut off value ( T off ) can be defined on the entry and must be less than zero. If the
tension cut off is left blank, Dytran calculates the tension cut off as the intersection point of the
failure envelope surface with the J1-axis as described in the Theory Manual.
6. The behavior of this material is discussed in detail in the Theory Manual.
274 DYMAT26
Orthotropic Crushable Material Model
Defines the properties of an orthotropic, crushable material model for Lagrangian solid elements.
+ X1 Y1 Z1 X2 Y2 Z2
+ 0. 1. 1. 1. 1. 0.
Remarks
1. If BULKTYP, BULKQ, or BULKL are blank or zero, the default values are used.
2. If the initial Poisson’s ratios are not supplied, the default is set to zero. Therefore, the behavior of
the material during compaction is uncoupled. This means that straining in the (local) x-direction
produces stresses only in the (local) x-direction, and not in the (local) y- or z-direction. The tables
define the variation of the stress in a particular direction with the relative volume or the crush. The
relative volume is defined as (current volume)/(initial volume) and varies from 1.0
(uncompressed) to 0.0 (zero volume). Crush is defined as one minus the relative volume and
varies from 0.0 to 1.0. Since the tables should be defined with increasing x-values, it is convenient
to use the default value for type, which is CRUSH. When defining the curves, care should be taken
that the extrapolated values do not lead to negative yield stresses.
3. The elastic moduli (and the initial Poisson’s ratios only if they are supplied) vary linearly with the
relative volume from their initial uncompacted values to the fully compacted ones.
4. When the material is fully compacted, its behavior becomes isotropic with an elastic perfectly
plastic material characteristic.
5. This material can only be used with Lagrangian solid elements.
6. If the TIDSR option is used, you can supply a table including strain-rate effects. Strain rate is
defined here as the Euclidean norm of the deviatoric strain-rate tensor; i.e., e· = e· dev · d ev
ij e ij . The y-
values in this table are factors with which the stresses in the other tables are multiplied to
incorporate strain-rate effects.
7. The behavior of this material is described in Materials.
278 ENDDATA
Terminates the Input Data
Remarks
1. Anything after the ENDDATA entry is ignored.
2. An ENDDATA entry in an INCLUDE file is ignored.
EOSEX 279
User-defined Equation of State
Remarks
1. The EXEOS subroutine must be present in the file referenced by the USERCODE FMS statement.
2. See Chapter 7: User Subroutines in the manual for a description of how to use
user-written subroutines.
3. The equation of state name is passed to the EXEOS subroutine and can be used to identify the
equation of state.
4. This entry can only be used for Lagrangian and Eulerian solids. Viscosity is only available for
Eulerian solids.
5. The viscosity coefficient is the dynamic viscosity. It is the ratio between shear stress and velocity
Ns
gradient. The SI-unit of viscosity is Pa s = ------
2
.
m
6. For the single mat solver viscous stresses can be requested by the use of TXX through TZX. Also,
EFFSTS is available. For the multi-material solver viscous stresses are stored in TXX-VIS,
TYY-VIS, TZZ-VIS, TXY-VIS, TYZ-VIS, TZX-VIS. These viscous stresses only depend on
the current velocity gradients. The stresses like TXX are elastic-plastic stresses and depend on past
stresses. The total stress tensor in the element is given by the average of the viscous stress and
elastic-plastic stress. The weight factors are the material fraction of viscous fluid and the
remaining materials.
280 EOSEX1
User-specified Equation of State
Defines an equation of state specified by a user subroutine. The pressure can depend on the amount of
failure or damage of the Euler element and on the VOLPLS and SOFTE element variables. The amount
of damage can be either specified by the damage variable of theFAILJC entry or by a more general failure
estimate by using the FAILEX2 entry. The VOLPLS and SOFTE variables can also be filled by the
EXYLD1, FAILEX2 user-subroutine.
Remarks
1. This model is only supported by the multi-material Euler solver.
2. A FAILJC entry or FAILEX2 entry is required.
3. The EXEOS1 subroutine must be present in the file referenced by the USERCODE
FMS statement.
4. See User-written Subroutine Notes in Chapter 7: User Subroutines for a description of how to use
user-written subroutines.
5. The equation of state name is passed to the EXEOS1 subroutine and can be used to identify the
equation of state.
6. The viscosity coefficient is the dynamic viscosity. It is the ratio between shear stress and velocity
Ns
gradient. The SI-unit of viscosity is = Pa s = ------
2
.
m
7. For the single mat solver, viscous stresses can be requested by the use of TXX through TZX. Also
EFFSTS is available. For the multi-material solver, viscous stresses are stored in TXX-VIS,
TYY-VIS, TZZ-VIS, TXY-VIS, TYZ-VIS, TZX-VIS. These viscous stresses only depend on
the current velocity gradients. The stresses like TXX are elastic-plastic stresses and depend on past
stresses. The total stress tensor in the element is given by the average of the viscous stress and
elastic-plastic stress. The weight factors are the material fraction of viscous fluid and the
remaining materials.
EOSGAM 281
Gamma Law Gas Equation of State
Defines the properties of a Gamma Law equation of state where the pressure p is defined as
p = – 1 e
where
Remarks
1. This equation of state is discussed in Dytran Theory Manual, Chapter 4: Models, EOSGAM –
Gamma Law Equation of State.
2. The temperature of the gas is calculated when one of the gas constants, R , C v , or C p is specified.
When temperature is not mentioned in an output request, the constants can be omitted.
3. The Euler variable name for temperature is TEMPTURE.
4. Gamma, R , C v , and C p have the following relationships:
Cp
= ------ R = C p – C v
Cv
282 EOSGAM
Gamma Law Gas Equation of State
5. The viscosity coefficient is the dynamic viscosity. It is the ratio between shear stress and velocity
Ns- kg
gradient. The SI-unit of viscosity is Pa s = ------
2
= ------- .
M ms
6. If possible, use (in coupled analysis) the FASTCOUP coupling algorithm because viscous fluxes
are computed more accurately for fast coupling than for general coupling.
7. For the single mat solver, viscous stresses can be requested by the use of TXX through TZX. Also,
EFFSTS is available. For the multi-material solver, viscous stresses are stored in TXX-VIS,
TYY-VIS, TZZ-VIS, TXY-VIS, TYZ-VIS, TZX-VIS. These viscous stresses depend only on
the current velocity gradients. The stresses like TXX are elastic-plastic stresses and depend on past
stresses. The total stress tensor in the element is given by the average of the viscous stress and
elastic-plastic stress. The weight factors are the material fraction of viscous fluid and the
remaining materials.
EOSIG 283
Ignition and Growth Equation of State
Defines the properties of Ignition and Growth equation of state and the reaction rate equation used to
model high explosives.
Remarks
1. This equation of state can be used with solid Lagrangian and Eulerian elements.
EOSIG 285
Ignition and Growth Equation of State
2. The definition of the unit system in which the input values are defined is required information
only in case you wish to have an automatic conversion to a different unit system as defined by the
UNITCNV field. In case you are using the conversion mechanism, note that the density RHO in the
corresponding DMAT entry is interpreted in the unit system defined here.
Table 5-1 defines sets of units available:
3. The UNITCNV field defines the unit system to which the material parameters are converted. In
case you are not using one of the database material models, you also have to define the default
unit system (UNITDEF) in which you supplied the data.
4. You can use the database containing several detonation materials to start the analysis. The
material data are taken from Lee/Tarver (Ref.1.) and Murphy/Lee (Ref.2.) papers in the Dytran
Theory Manual. The equations of state parameters are given in the table 2.
5. The default setting for DBEXPL is NO, which means you should define the values in the input
fields (fields 3 to 18). If the database material name is defined, all values in the input fields will
be overridden. The reference density RHO defined on the corresponding DMAT entry is set to the
value from the database.
6. The default unit system for the material database parameters is the CGMS unit system. If you wish
to use the material base data in a different unit system, you can specify this by defining the target
unit system in the UNITCNV field.
7. You can define the shear property and yield model of the material with respectively SHXXX and
YLDXX entry. Note that the unit system of data required in these entries should be consistent with
the unit system defined in the UNITCNV field.
8. The IG equation of state cannot be used in combination with a spallation model.
286 EOSIG
Ignition and Growth Equation of State
9. The following JWL equation of state is used to calculate the pressure of the un-reacted explosive
(in “solid” state):
– R 1e –R2 e
e e ------------
-
e e ------------
-
p e = A e 1 – ------------ e e + B e 1 – ------------ e e + e e 0 E e
R 1e R 2e
where
e
e = ----- = the relative density of the un-reacted explosive
0
Ee = the specified internal energy per unit mass of the unreacted explosive
0 = the initial density of the explosive
A e , B e , e , R 1e , R 2e = the input constants of the un-reacted explosive.
Similarly, the pressure in the reaction products (in “gas” state) is defined by another JWL form
as follows:
– R 1p – R 2p
------------- -------------
p p p p p p
pp = A p 1 – ------------- e + B p 1 – ------------- e + p p 0 Ep
R 1p R 2p
where
p
p = ----- = the relative density of the reaction product.
0
Ep = the specified internal energy per unit mass of the reacted product.
A p , B p , p , R 1p , R 2p = the input constants of the reaction product.
The chemical reaction rate for conversion of un-reacted explosive to reaction products is
described by the following reaction rate equation:
F
------- = I 1 – F x e – 1 – a y + G 1 – F x F y P z
t
Here F denotes the burn fraction that is defined as the fraction of the explosive that has already
reacted. For more details concerning the implementation of this equation of state, please refer to
the Dytran Theory Manual.
EOSIG 287
Ignition and Growth Equation of State
10. You can access the results of the un-reacted explosive and reaction products for IG elements.
These EOSIG specific output variables are:
Keyword Description
SIE-E Specific internal energy per unit mass of un-reacted explosive part
SIE-P Specific internal energy per unit mass of reaction products part
FMAT Volume fraction
RHO-E Density of un-reacted explosive part
RHO-P Density of reaction products part
MASS-E Mass of un-reacted explosive part
MASS-P Mass of reaction products part
Table 5-2 Coefficients for the IG Model of Several Explosions in the Database
PBX- Cast LANL Military PBX-
Explosive 9404 (a) TATB PETN TNT COMP B COMP B 9404 (b) LX-17
Un-reacted Equation of State and Constitutive Values:
RHO (g/cm3) 1.842 1.90 1.842 1.61 1.712 1.630 1.842 1.903
AE (bar) 69.69 108.2 37.46 17.98 778.1 1479. 9522. 778.1
BE (bar) -1.727 -2.406 -1.313 -0.931 -0.05031 -0.05261 -0.5944 -0.05031
R1E 7.8 8.2 7.2 6.2 11.3 12. 14.1 11.3
R2E 3.9 4.1 3.6 3.1 1.13 1.2 1.41 1.13
OMGE 0.8578 1.251 1.173 0.8926 0.8938 0.9120 0.8867 0.8938
Reacted Product Equation of State Values:
AP (bar) 8.524 6.5467 6.17 3.712 5.242 5.5748 8.524 6.5467
BP (bar) 0.1802 0.071236 0.16926 0.032306 0.07678 0.0783 0.1802 0.071236
R1P 4.6 4.45 4.4 4.15 4.2 4.5 4.6 4.45
R2P 1.3 1.2 1.2 0.95 1.1 1.2 1.3 1.2
OMGP 0.38 0.35 0.25 0.30 0.34 0.34 0.38 0.35
ECHEM 0.0554 0.0363 0.0548 0.0435 0.0496 0.04969 0.0554 0.03626
bar-cm3/g)
Reaction Rate Parameters:
I (s-1) 44.0 50.0 20.0 50.0 44.0 44.0 44.0 50.0
G (bar-z s-1) 200.0 125.0 400.0 40.0 414.0 514.0 850.0 500.0
A 0.01 0.01 0.01 0.01 0.01 0.01 0.01 0.0
Z 1.6 2.0 1.4 1.2 2.0 2.0 2.0 3.0
X 2/9 2/9 2/9 2/9 2/9 2/9 2/9 2/9
Y 2/3 2/3 2/3 2/3 2/3 2/3 2/3 2/3
R 4.0 4.0 4.0 4.0 4.0 4.0 4.0 4.0
EOSJWL 289
JWL Explosive Equation of State
Defines the properties of a JWL equation of state commonly used to calculate the pressure p of the
detonation products of high explosives
–R1 –R2
---------- ----------
p = p 0 + A 1 – -------- e + B 1 – -------- e + 0 e
R1 R2
p0 = initial pressure
A , B , R1 , R2 are constants.
Remarks
1. This equation of state can be used only with Eulerian elements.
2. A DETSPH entry must be used to specify the detonation model.
3. This equation of state is discussed in Dytran Theory Manual, Chapter 4: Models, EOSJWL – JWL
Equation of State.
290 EOSJWL
JWL Explosive Equation of State
4. In simulations with ideal gases, the JWL material needs to have an initial pressure to counter
balance the pressure of the ideal gas. Similarly, in case of under calculations where an explosive
is located at a certain depth, P0 should be preset to equal the initial hydrostatic pressure.
EOSMG 291
Mie-Gruneisen Equation of State
Defines the properties of a Mie-Gruneisen equation of state commonly used to calculate the pressure p
in high strain rate processes.
0 c 2 0
p = ----------------------2- 1 – ---------- + 0 0 e
1 – s 2
0
= 1 – -----
1
1 = min RM
where
e = specific internal energy per unit mass. For material at zero pressure, e has to be initialized
as zero.
0 = reference density
= overall material density
0 = Gruneisen parameter at reference density
s = definition by U s = c 0 + sU p where U s and U p are the linear shock velocity and particle
velocity, respectively, as obtained from the shock data.
c = sound speed at reference density
RM = cut-off value for density
Remarks
1. This equation of state can only be used with Eulerian elements.
2. This equation of state is discussed in Dytran Theory Manual, Chapter 4: Models, EOSMG - Mie-
Gruneisen Equation of State.
3. The cut off value RM is only used for limiting the pressure. To prevent division by zero, RM
s
should be less than ----------- ref . RM can be set slightly below this value. In case the simulation gets
s–1
unstable because of too large pressures, RM can be decreased.
EOSPOL 293
Polynomial Equation of State
Defines the properties of a polynomial equation of state where the pressure p is defined as follows:
In compression 0 ,
2 3 2 3
p = a 1 + a 2 + a 3 + b 0 + b 1 + b 2 + b 3 0 e
In tension i 0 ,
p = a 1 + b 0 + b 1 0 e
where
= –1
= 0
+ HVL VISC
+ 1.1
Remarks
1. When the relative volume 0 exceeds HVL, the pressure is cut off to
P HVL = f HVL
with
1
HVL = ------------ – 1
HVL
2. When the PARAM,HVLFAIL is set to YES, the elements where the relative volume 0
exceeds HVL fail completely. Their stress state is zero.
3. This equation of state is discussed in Dytran Theory Manual, Chapter 4: Models, EOSPOL –
Polynomial Equation of State.
4. The viscosity coefficient is the dynamic viscosity. It is the ratio between shear stress and velocity
Ns kg
gradient. The SI-unit of viscosity is Pa s = ------
- = ------- .
2M ms
5. If possible, use in coupled analysis the FASTCOUP coupling algorithm, because viscous fluxes
are computed more accurately for fast coupling than for general coupling.
EOSPOL 295
Polynomial Equation of State
6. For the single mat solver, viscous stresses can be requested by the use of TXX through TZX. Also
EFFSTS is available. For the multi-material solver, viscous stresses are stored in TXX-VIS,
TYY-VIS, TZZ-VIS, TXY-VIS, TYZ-VIS, TZX-VIS. These viscous stresses only depend on
the current velocity gradients. Stresses like TXX are elastic-plastic stresses and depend on past
stresses. The total stress tensor in the element is given by the average of the viscous stress and
elastic-plastic stress. The weight factors are the material fraction of viscous fluid and the
remaining materials.
296 EOSTAIT
Tait Equation of State
Defines the properties of an equation of state based on the Tait model in combination with a cavitation
model where the pressure p is defined as follows:
No cavitation e ,
p = a0 + a1 – 1
Cavitation c ,
p = pc
where
= 0
= overall material density
0 = reference density
c = critical density which produces the cavitation pressure p c
Remarks
1. The pressure can not fall below the cavitation pressure p c = a 0 + a 1 -----c – 1 , although the
0
density can continue to decrease below its critical value c .
2. The Tait equation of state can not be used in combination with a spallation model.
3. For a more detailed description, see the Dytran Theory Manual, Chapter 4: Models, EOSTAIT –
Tait Equation of State.
4. The viscosity coefficient is the dynamic viscosity. It is the ratio between shear stress and velocity
Ns- kg
gradient. The SI-unit of viscosity is Pa s = ------
2
= ------- .
M ms
5. If possible, use in coupled analysis the FASTCOUP coupling algorithm, because viscous fluxes
are computed more accurately for fast coupling than for general coupling.
6. For the single mat solver, viscous stresses can be requested by the use of TXX through TZX. Also
EFFSTS is available. For the multi-material solver, viscous stresses are stored in TXX-VIS,
TYY-VIS, TZZ-VIS, TXY-VIS, TYZ-VIS, TZX-VIS. These viscous stresses only depend on
the current velocity gradients. Stresses like TXX are elastic-plastic stresses and depend on past
stresses. The total stress tensor in the element is given by the average of the viscous stress and
elastic-plastic stress. The weight factors are the material fraction of viscous fluid and the
remaining materials.
298 FABRIC
Woven Fabric Material
Defines the properties of a bi-directional woven fabric material for shell elements.
COMPFIB Scale factor for fiber compression stresses 1.0 R 0.0 1.0
See Remark 4.
LOCKANG1 Locking angle 1 for change in fiber cross-over angle R 0.0 10.0
See Remark
11.
LOCKANG2 Locking angle 2 for change in fiber cross-over angle R 0.0 15.0
See Remark
11.
Remarks
1. For a description of the bi-directional woven fabric model, see Dytran Theory Manual, Chapter
3: Materials.
2. When a coating is defined (PERC>0), two out of three values need to be specified for ECOAT,
NUCOAT, and GCOAT.
3. For air bag modeling the following values of DAMPCOAT and DAMPFIB are suggested:
DAMPCOAT= 0.05
DAMPFIB= 0.05
4. The compressive stresses in the fibers are scaled with the value of COMPFIB. Putting
COMPFIB = 0.0 results in a tension only fiber model.
The compressive stresses in the coating are scaled with the value of COMPCOAT. Putting
COMPCOAT = 0.0 results in a tension only coating model.
300 FABRIC
Woven Fabric Material
The compressive stresses are scaled in the direction of the principal stresses.
When PERC = 100%, and the coating of this fabric model is used to simulate an isotropic air bag
material, it is best to scale down the compressive stresses of the coating. A suggested value is
COMPCOAT = 0.1.
5. Since this is a model which tracks warp and weft directions and uses total warp/weft strain as a
state variable, the initial warp and weft directions must be specified. There are two ways to
indicate the initial warp and weft directions:
a. THETA1 and THETA2
Orientation angles between the element coordinate system and the warp/weft ends. If no
orientation angle is specified, vectors will be used to indicate the warp/weft directions of the
fabric material with respect to the basic coordinate system.
b. XWARP, YWARP, ZWARP and XWEFT, YWEFT, ZWEFT
Vectors indicating the warp/weft directions of the fabric material with respect to the basic
coordinate system. The projection of these vectors on the surface of each element is used to
determine the angle between the element and the material coordinate system. If the orientation
angles are defined, these vectors are ignored.
6. For shell element properties (PSHELL1), when the material is FABRIC, the material angle
THETA is ignored. The orientation of the fabric fibers is defined completely on the FABRIC entry.
For layered composite element properties (PCOMP), when the material of a ply is FABRIC, the
angle THETAi is ignored. The orientation of the fabric fibers is defined completely on the
FABRIC entry.
7. The maximum shear stress is given by a friction coefficient of the fabric (SCOF) times the RMS
value of the direct fiber stresses.
8. If the field G12 is left blank, the shear modulus is computed from the RMS value of the two linear
stiffness coefficients.
9. When Fabric material is referenced by shell elements, the Spin Rate method (SPIN) is applied
automatically when no stress-rotation correction is specified on SPINCOR option. See PSHELL
entry for the details on SPINCOR option.
10. There are a number of specific output sublayer variables useful for this material:
11. When a fabric is being sheared, the angle between the fibers changes. At a certain moment, the
fibers will reach a locking angle, after which a further change in the fiber angle is no
longer possible.
The simulation models this behavior as follows:
a. Change in Fiber Crossover Angle < LockAng1
The shear stress between the fibers is cut off based on the friction coefficient SCOF
b. LockAng1 < Change in Fiber Crossover Angle < LockAng2
The shear stress between the fibers is linearly increased.
c. Change in Fiber Crossover Angle > LockAng2
The shear stress between the fibers is no longer cut off.
This situation is equal to an infinite friction coefficient SCOF.
302 FAILEST
Maximum Equivalent Stress and Minimum Time Step Failure Model
FAILEST Maximum Equivalent Stress and Minimum Time Step Failure Model
Defines the properties of a failure model where total failure occurs when the equivalent stress exceeds
the specified value and the element time step drops below the specified limit.
Remarks
1. This failure model is valid for Lagrangian solid (CHEXA) orthotropic materials. (See also the
DMATOR entry.)
2. The FAILEST failure model is a two-stage failure. The first stage retains the hydrodynamic
properties of the material. The second stage is reached when the global time step falls below the
specified value. The element is then removed from the calculation.
FAILEX 303
User Failure Subroutine
Specifies that a user subroutine is being used to define the failure model.
Remarks
1. The subroutine must be present in the file referenced by the USERCODE FMS statement.
2. See Chapter 7: User Subroutines in this manual for a description of how to use
user-written subroutines.
304 FAILEX1
Extended User Failure Subroutine
Remarks
1. The subroutine must be present in the file referenced by the USERCODE FMS statement.
2. The failure model is available for orthotropic materials only. The FAILEX1 entry must be
referenced on the DMATOR entry.
3. The failure model allows for an extensive description of the failure of composite materials in
three-dimensional elements. It includes the possibility to have property degradation according to
material damage.
4. See Chapter 7: User Subroutines for a description of how to use user-written subroutines.
FAILEX2 305
User Failure Subroutine
Defines a damage model specified by a user subroutine. In addition, the VOLPLS and SOFTE element
variables can be set by this routine.
NOFAIL No failure
Remarks
1. This model is only supported by the Multi-material solver with strength.
2. The subroutine must be present in the file referenced by the USERCODE FMS statement.
3. See User-written Subroutine Notes in Chapter 7: User Subroutines for a description of how to use
user-written subroutines.
4. For each material and for each Euler element a variable will be created that monitors the degree
of failure of the material. This variable is denoted by DAMAGE and is between 0 and 1. The
EXFAIL2 routine allows updating this damage variable due to the plastic strain increment of the
current cycle.
5. There are two ways in which this damage variable can model failure These are:
• Continuous failure: The yield stress is reduced by a factor (1-D). When D exceeds 1, the yield
stress equals zero and the element fails.
• Discrete failure: the element fails when D equals one.
When NOFAIL is set, positive damage values will not lead to failure. This is useful if the failure
modeling is done by an EXYLD1 routine. Then the yield stress can be reduced depending on the
magnitude of the damage variable.
306 FAILJC
Johnson-Cook Failure Model
Defines the properties of a failure model where failure is determined by a damage model. The damage
model is given by:
p
D = ------------
frac
-
time
·
pl
frac = D 1 + D 2 exp D 3 * 1 + D 4 ln ------
- 1 + D 5 T *
·0
pl
m
* = -------
T – T room
T * = ---------------------------------
T melt – T room
The summation is performed over all past time increments. The variable D measures the damage; T is
the temperature, m the mean stress, is the von Mises equivalent stress, and frac is the fracture strain.
The fracture strain depends on a nondimensional plastic strain rate · pl · pl0 . If D exceeds one it set equal
to one.
The damage variable D is transported along with the Eulerian material.
There are two methods to determine when elements fail:
• Continuous failure: The yield stress is reduced by a factor 1 – D . When D exceeds 1 the yield
stress equals zero and the element fails.
• Discrete failure: the element fails when D equals one.
This failure model applies to high-strain rate deformation of metals. It is less suitable for
quasi-static problems.
+ TMELT CP MTH
+ 1495 450 CONT
FAILJC 307
Johnson-Cook Failure Model
Remarks
1. This failure model is only available for Eulerian materials. The use of the multi-material solver
with strength is required.
2. The variable D can be visualized by adding DAMAGE to the Output request for Euler elements.
308 FAILMES
Maximum Equivalent Stress Failure Model
Defines the properties of a failure model where failure occurs when the equivalent stress exceeds the
specified value.
Remark
This failure model is valid for Lagrangian solid element materials. (See also the DMAT and
DMATOR entries.)
FAILMPS 309
Maximum Plastic Strain Failure Model
Defines the properties of a failure model where failure occurs when the equivalent plastic strain exceeds
the specified value.
Remark
This failure model is valid for Eulerian, shell (CQUAD4 and CTRIA3), Hughes-Liu beams, and
Lagrangian solid element materials. (Also see the DMAT and DMATEP entries.)
310 FAILPRS
Maximum Pressure Failure Model
Defines the properties of a failure model where failure occurs when the hydrodynamic pressure exceeds
the specified value.
Remark
This failure model is valid for Lagrangian solid element orthotropic materials. (See also the
DMATORentry.)
FAILSDT 311
Maximum Plastic Strain and Minimum Time-Step Failure Model
Defines the properties of a failure model where total failure occurs when the equivalent plastic strain
exceeds the specified value and the element time step falls below the specified limit.
Remarks
1. This failure model is valid for Lagrangian solid element materials. (See also the DMAT entry.)
2. The FAILSDT failure model is a two-stage failure. The first stage retains the hydrodynamic
properties of the material. The second stage is reached when the global time step falls below the
specified value. The element then is removed from the computation.
312 FFCONTR
Closed Volume Intended for Fluid Filled Containers
Defines the pressure within a closed volume. Intended for the use in (partially) filled containers, where
dynamic fluid effects are negligible; e.g. top loading and hot filling.
Remarks
1. The gas above the fluid is assumed to be an ideal, iso-thermal gas: p V = C , where C is a
constant. If TEMPTAB is set, the temperature is applied to both the fluid as well as the gas. Then,
the gas satisfies p V T = C , where T is the temperature of the fluid.
2. The fluid is assumed incompressible.
3. The pressure is based on the uniform pressure gas bag algorithm, where the pressure is uniform
in the volume, but variable in time.
4. Output for the fluid-filled container is available through a GBAGOUT definition. The available
variables are: PRESSURE, VOLUME, TEMPTURE, VOLGAS, VOLFLUID, GAUGEPRES,
and RHOFLUID.
5. The normals of the surface referenced by SID are automatically reversed if required.
6. Modeling guidelines are described in the “Getting Started” section.
FFCONTR 313
Closed Volume Intended for Fluid Filled Containers
Here, T 0 and V 0Fluid are initial values for temperature and fluid volume, is the fluid density, and
T denotes the current temperature. If TEMPTAB is not set, the DENSTAB entry will not be used.
8. At time = TACTIVE, the gas is assumed to be in contact with the ambient pressure for the last time.
This means that at Time = TACTIVE, the pressure in the bottle equals the ambient pressure for the
last time. After TACTIVE, the bottle has been closed and there is no longer contact between
ambient and gas inside the bottle. Any change in volume of the bottle or temperature or fluid will
result in change of pressure of the gas inside the bottle.
314 FLOW
Flow Boundary Condition
+ TYPE4 VALUE4
+
Remarks
1. LID must be referenced by a TLOAD1entry.
2. Any material properties not specifically defined have the same value as the element with the flow
boundary condition.
3. TLOAD entries referencing FLOW entries must have the TID field blank or zero.
4. In the case of material flow into a multi-material Euler mesh, the density and specific energy have
to be set. On the other hand, when material flows out of a multi-material Euler mesh, it is assumed
that each of the materials present in the outflow Euler element contributes to the out-flow of mass.
The materials are transported in proportion to their relative volume fractions.
5. Prescribing both pressure and velocity may lead to the instabilities.
6. For TYPE=HYDSTAT, the pressure is set using HYDSTAT; the velocity equals the element
velocity. In case of inflow, the density follows from the hydrostatic pressure by using the EOS.
316 FLOWC
Cyclic Flow Boundary Condition
Remarks
1. FLOWC can be used to specify flow boundaries for CHEXA’s and also for Euler element created
by the MESH,BOX option.
2. FLOWC is only supported by the multi-material Euler solver.
3. The boundary condition FID2 has also to be defined by means of a FLOWCDR or FLOWCSQ.
definition. The outflow values of FID2 will be used as the inflow values for FID and vice versa.
4. To enable using the outflow values of FID2 as the inflow values for FID, the boundary faces of
FID and FID2 are mapped onto each other. For this mapping, only translations and rotations
around coordinate axes are permitted.
5. For fully cyclic boundary conditions, METHOD can be left blank. The default value 1 will be
taken.
6. Consider a cubic Euler mesh and that material flows from the left to the right. At the right side,
the boundary condition is imposed
FLOWC,4,30,,5
and at the left side
FLOWC,5,40,,4
These definitions cause all material that flows out of the right side boundary into the left side
boundary. Moreover, the Euler element pressures on the right side are put on the Euler elements
of the left boundary condition.
In practice, it may be useful to skip the coupling between the two boundaries with regard to
pressure. This can be done by setting METHOD equal to 2.
With these definitions, material from boundary 4 still flows into boundary 5 but pressure
boundaries are transmitting.
7. ISCALE is useful if several objects have identical outflow that is used as inflow by another object.
Then only one object has to be modeled. To account for the other objects when defining inflow,
the scale factor can be used. It can also be used to turn off in and outflow. When ISCALE is set
either METHOD=2 or METHOD=3 are recommended. METHOD=1 should not be used.
8. It is allowed that the definition of the FLOWC entry overlaps with FLOWSQ, FLOW, or FLOWDIR
definitions. In that case, the FLOWC definition overrules the other ones.
318 FLOWCDR
Cyclic Flow Boundary Condition for All Faces in Certain Direction
FLOWCDR Cyclic Flow Boundary Condition for All Faces in Certain Direction
Defines the properties of a material for the boundaries of an Eulerian mesh. The boundary consists of all
Eulerian faces that are pointing into a specific direction.
Inflow values can be taken from another boundary condition. This allows cyclic or periodic boundary
conditions. Likewise, the outflow of material goes into the other boundary condition.
FLOWC* entries have to be defined in pairs. The FID on one entry has to be equal to FID2 of the other
entry. For example
FLOWCDR,10,MMHYDRO,,10,POSX,2,...
FLOWCDR,20,MMHYDRO,,20,NEGX,1,..
It is allowed to couple a FLOWCDR with a FLOWC or a FLOWCSQ.
For both flow boundaries, mass flow summaries can be created as time history.
Remarks
1. FLOWCDR can be used to specify flow boundaries for CHEXA’s and also for Euler element
created by the MESH,BOX option.
2. In the OUT file, the total area of boundary faces is printed.
3. FLOWCDR is only supported by the multi-material Euler solver.
4. The boundary condition FID2 has also to be defined by means of a FLOWC or FLOWCSQ
definition. The outflow values of FID2 will be used as the inflow values for FID and vice versa.
5. To enable using the outflow values of FID2 as the inflow values for FID, the boundary faces of
FID and FID2 are mapped onto each other. For this mapping, only translations and rotations
around coordinate axes are permitted.
6. For fully cyclic boundary conditions, METHOD can be left blank. The default value 1 will be
taken.
7. Consider a cubic Euler mesh and that material flows from the left to the right. At the right side,
the boundary condition is imposed
FLOWCDR,4,MMHYDRO,1,POSX,5
and at the left side
FLOWCDR,5,MMHYDRO,2,NEGX,4
These definitions cause all material that flows out of the right side boundary into the left side
boundary. Moreover, the Euler element pressures on the right side are put on the Euler elements
of the left boundary condition.
In practice, it may be useful to skip the coupling between the two boundaries with regard to
pressure. This can be done by setting METHOD equal to 2.
With these definitions, material from boundary 4 still flows into boundary 5 but pressure
boundaries are transmitting.
8. ISCALE is useful if several objects have identical outflow that is used as inflow by another object.
Then only one object has to be modeled. To account for the other objects when defining inflow,
the scale factor can be used. It can also be used to turn off in and outflow. When ISCALE is set
either METHOD=2 or METHOD=3 are recommended. METHOD=1 should not be used.
320 FLOWCDR
Cyclic Flow Boundary Condition for All Faces in Certain Direction
9. It is allowed that the definition of the FLOWCDR entry overlaps with FLOWSQ, FLOW, or
FLOWDIR definitions. In that case, the FLOWCDR definition overrules the other ones. It is not
allowed that a square of one FLOWCDR overlaps a square of another FLOWCDR entry.
10. The MESH-ID is only used when multiple Euler domains have been defined. If multiple Euler
domains have been defined but if the MESH-ID is blank, all Euler domains will be considered in
assigning the boundary condition.
FLOWCSQ 321
Cyclic Flow Boundary Condition using a Square Definition
Defines the properties of a material for the boundaries of an Eulerian mesh. The boundary consists of all
Eulerian faces that are inside a specified square.
Inflow values can be taken from another boundary condition. This allows cyclic or periodic boundary
conditions. Likewise, the outflow of material goes into the other boundary condition.
FLOWC* entries have to be defined in pairs. The FID on one entry has to be equal to FID2 of the other
entry. For example
FLOWCSQ,10,MMHYDRO,10,,2
FLOWCSQ,20,MMHYDRO,20,,1
It is allowed to couple a FLOWCSQ with a FLOWC or a FLOWCDR.
For both flow boundaries, mass flow summaries can be created as time history.
1. FLOWCSQ can be used to specify flow boundaries for CHEXA’s and also for Euler element
created by the MESH,BOX option.
2. In the OUT file the total area of boundary faces is printed.
3. FLOWCSQ is only supported by the multi material Euler solver.
4. The boundary condition FID2 has also to be defined by means of a FLOWC or FLOWCDR
definition. The outflow values of FID2 will be used as the inflow values for FID and vice versa.
5. To enable using the outflow values of FID2 as the inflow values for FID the boundary faces of
FID and FID2 are mapped onto each other. For this mapping only translations and rotations around
coordinate axes are permitted.
6. For fully cyclic boundary conditions, METHOD can be left blank. The default value 1 will be
taken.
7. Consider a cubic Euler mesh and that material flows from the left to the right. At the right side
the boundary condition is imposed
FLOWCSQ,4,MMHYDRO,,5
and at the left side
FLOWCSQ,5,MMHYDRO,,4
These definitions cause all material that flows out of the right side boundary into the left side
boundary. Moreover, the Euler element pressures on the right side are put on the Euler elements
of the left boundary condition.
In practice, it may be useful to skip the coupling between the two boundaries with regard to
pressure. This can be done by setting METHOD equal to 2.
With these definitions, material from boundary 4 still flows into boundary 5 but pressure
boundaries are transmitting.
FLOWCSQ 323
Cyclic Flow Boundary Condition using a Square Definition
8. ISCALE is useful if several objects have identical outflow that is used as inflow by another object.
Then only one object has to be modeled. To account for the other objects when defining inflow,
the scale factor can be used. It can also be used to turn off in and outflow. When ISCALE is set
either METHOD=2 or METHOD=3 are recommended. METHOD=1 should not be used.
9. If neither the MIN or MAX value has been set, the default value is respectively -1E+20 and 1e+20
for the MIN and MAX value. If the MIN value has been set, the default value of the MAX value is the
MIN value.
10. It is allowed that the definition of the FLOWCSQ entry overlaps with FLOWSQ, FLOW, or
FLOWDIR definitions. In that case, the FLOWCSQ definition overrules the other ones. It is not
allowed that a square of one FLOWCSQ overlaps a square of another FLOWCSQ entry.
11. The MESH-ID is only used when multiple Euler domains have been defined. If multiple Euler
domains have been defined but if the MESH-ID is blank, all Euler domains will be considered in
assigning the boundary condition.
324 FLOWDEF
Default Flow Boundary
Remark
1. If this entry is not specified, a default wall boundary condition is applied to all Eulerian free faces.
2. For TYPE=HYDSTAT, the pressure is set using HYDSTAT; the velocity equals the element
velocity. In case of inflow, the density follows from the hydrostatic pressure by using the EOS.
326 FLOWDIR
Flow Boundary Condition for all Eulerian Boundary Faces in a Specific Direction
Defines the properties of a material for the boundaries of an Eulerian mesh. The boundary consists of all
Eulerian boundary faces that point in a specific direction.
Remarks
1. FLOWDIR can be used to specify flow boundaries for CHEXA’s and also for Euler element
created by the MESH,BOX option.
2. In the OUT file, the total area of boundary faces is printed.
3. FLOWDIR is not supported by the single material strength Euler solver.
4. FLOWDIR overrules FLOW definitions, but FLOWSQ overrules FLOWDIR.
5. The MESH-ID is only used when multiple Euler domains have been defined. If multiple euler
domains have been defined but if the MESH-ID is blank all Euler domains will be considered in
assigning the boundary condition.
6. Any material properties not specifically defined have the same value as the element with the flow
boundary condition.
7. TLOAD entries referencing FLOW entries must have the TID field blank or zero.
8. In the case of material flow into a multi-material Euler mesh, the density and specific energy have
to be set. On the other hand, when material flows out of a multi-material Euler mesh, it is assumed
that each of the materials present in the outflow Euler element contributes to the out flow of mass.
The materials are transported in proportion to their relative volume fractions.
9. Prescribing both pressure and velocity may lead to the instabilities.
10. For TYPE = HYDSTAT, the pressure is set using HYDSTAT, the velocity equals the element
velocity. In case of inflow the density follows from the hydrostatic pressure by using the equation
of state.
328 FLOWEX
User-defined Flow Boundary
Remarks
1. LID must be referenced by a TLOAD1 entry.
2. The EXFLOW user subroutine must be present in the file referenced by the USERCODE FMS
statement. The EXFLOW user subroutine must be present in case single hydrodynamic materials,
or materials with strength are used. For multimedia problems, the EXFLOW2 subroutine must
be used.
3. See Chapter 7: User Subroutines for a description of how to use user-written subroutines.
4. TLOAD1 entries referencing FLOWEX entries must have the TID field blank or zero.
5. The flow boundary name is passed to the EXFLOW subroutine and can be used to identify
the boundary.
6. The EXFLOW2 subroutine allows for the definition of any material to flow into the Eulerian mesh.
The outflow can only be of materials present in the mesh.
7. There are two methodologies available to define an inflator model for an eulerian calculation:
a. as a boundary condition for a subsurface on a coupling surface (see the COUPLE, COUPOR,
and INFLATR entries)
b. as a FLOWEX boundary condition for an Euler face.
The second method can be activated by using a predefined name on the FLOWEX entry. The
following name must be used:
FLOWEX 329
User-defined Flow Boundary
Defines the properties of a material for the boundaries of an Eulerian mesh. The boundary consists of all
Eulerian faces that are inside a specified square.
Remarks
1. FLOWSQ can be used to specify flow boundaries for CHEXA’s and also for Euler element created
by the MESH,BOX option.
2. In the OUT file, the total area of boundary faces is printed.
3. FLOWSQ is not supported by the single material strength Euler solver.
4. If Neither the MIN or MAX value has been set the default value is respectively -1E+20 and 1e+20
for the MIN and MAX value. If the MIN value has been set the default value of the MAX value is the
MIN value.
5. It is allowed that the defined square of a FLOWSQ entry overlaps with FLOW definitions or FLOWDIR
definitions. In that case, the FLOWSQ definition overrules the other ones. It is not allowed that a
square of one FLOWSQ overlaps a square of another FLOWSQ entry.
6. The MESH-ID is only used when multiple Euler domains have been defined. If multiple euler
domains have been defined but if the MESH-ID is blank all Euler domains will be considered in
assigning the boundary condition.
7. Any material properties not specifically defined have the same value as the element with the flow
boundary condition.
8. In the case of material flow into a multi-material Euler mesh, the density and specific energy have
to be set. On the other hand when material flows out of a multi-material Euler mesh it is assumed
that each of the materials present in the outflow Euler element contributes to the out flow of mass.
The materials are transported in proportion to their relative volume fractions.
9. Prescribing both pressure and velocity may lead to the instabilities.
10. For TYPE = HYDSTAT, the pressure is set using HYDSTAT, the velocity equals the element
velocity. In case of inflow, the density follows from the hydrostatic pressure by using the EOS.
332 FLOWT
Time-dependent Flow Boundary
Definition of the material properties for the inflow or outflow through the boundary of an Euler mesh.
Inflow velocity and material properties can be chosen as time dependent.
Remarks
1. FID must be referenced by a TLOAD1 entry.
2. TLOAD1 entries referencing FLOW entries must have the TID field blank or zero.
3. Any material properties not specifically defined have the same value as the element with that
boundary condition.
4. In the case of material flow into a multi-material Euler mesh, the material number, the density,
and specific energy have to be set. On the other hand, when material flows out of a multi-material
Euler mesh, it is assumed that each of the materials present in the outflow Euler element
contributes to the outflow of mass. The materials are transported in proportion to their relative
volume fractions.
5. The boundary condition initiates or determines a wave in compressible material like gas and
water. This can be either an outgoing or an ingoing wave. For stability, it is important that the
waves created are compatible with the flow type near the boundary. Relevant flow types are
subsonic inflow, subsonic outflow, supersonic inflow, and supersonic outflow. For example, for
subsonic inflow, prescribing both pressure and velocity would initiate outgoing waves. Outgoing
waves for an inflow boundary condition is known to be instable. However, for supersonic inflow,
you can specify both pressure and velocity since there are no outgoing waves at a supersonic
inflow boundary.
6. When a TABLEEX is referenced, the EXFUNC user subroutine must be created. See TABLEEX for
more details.
FLOWTSQ 335
Time dependent Flow Boundary
Defines the material properties for the in- or outflow of material trough the boundary of an Euler mesh.
Inflow velocity and material properties can be chosen time dependent.
Remarks
1. FLOWTSQ can be used to specify flow boundaries for CHEXA’s and also for Euler element created
by the MESH,BOX option.
2. In the OUT file, the total area of boundary faces is printed.
3. FLOWTSQ is not supported by the single material strength Euler solver.
4. If neither the MIN nor MAX value has been set the default value is respectively -1E+20 and 1e+20
for the MIN and MAX value. If the MIN value has been set the default value of the MAX value is the
MIN value.
5. It is allowed that the defined square of a FLOWTSQ entry overlaps with FLOW definitions or
FLOWDIR definitions. In that case, the FLOWTSQ definition overrules the other ones. It is not
allowed that a square of one FLOWTSQ overlaps a square of another FLOWSQ entry.
6. The MESH-ID is only used when multiple Euler domains have been defined. If multiple euler
domains have been defined but if the MESH-ID is blank, all Euler domains are considered in
assigning the boundary condition.
7. Any material properties not specifically defined have the same value as the element that with the
boundary conditions.
8. In the case of material flow into a multi-material Euler mesh, the material number, the density and
specific energy have to be set. On the other hand when material flows out of a multi-material Euler
mesh it is assumed that each of the materials present in the outflow Euler element contributes to
the out flow of mass. The materials are transported in proportion to their relative volume fractions
9. The boundary condition initiates/determines a wave in compressible material like gas and water.
This can be either an outgoing or an ingoing wave. For stability it is important that the waves
created are compatible with the flow type near the boundary. Relevant flow types are subsonic
inflow, subsonic outflow, supersonic inflow and supersonic outflow. For example for subsonic
inflow prescribing both pressure and velocity would initiate outgoing waves. Outgoing waves for
an inflow boundary condition is known to be instable. However, for supersonic inflow one can
specify both pressure and velocity since there are no outgoing waves at a supersonic inflow
boundary.
10. When a TABLEEX is referenced, the user-subroutine EXFUNC must be created. See TABLEEX
for more details.
338 FOAM1
Foam Material Properties
Defines the properties of an isotropic, crushable material where Poisson’s ratio is effectively zero.
Remarks
1. If BULKTYP, BULKQ, or BULKL are blank or zero, the default values are used.
2. The continuation line with bulk-viscosity data can be omitted.
3. Poisson’s ratio for this model is effectively zero. Therefore, only one other elastic constant can be
defined which can be G , the shear modulus, or K , the bulk modulus.
FOAM1 339
Foam Material Properties
4. For this model, the stress-strain curve is independent of the experimental test performed to obtain
the material data (uniaxial, shear, or volumetric). The most common test is the uniaxial
compression test where the stress-strain characteristic can either be defined in terms of the amount
of crush, which is minus the engineering strain, or in terms of the true strain. Since Poisson’s ratio
is effectively zero the amount of crush is defined as 1 – -----
V V
- , with ------ as the relative volume, and
V0 V0
the true strain is defined as
t
- or In ------ .
dV V
-----
V V 0
t0
The crush factor must be between 0 and 1. The true strain must always be negative and the stress
positive (absolute value).
5. The yield surface in three-dimensional space is a sphere in principal stresses, and is defined by
2 2 2 2
22 + 22 + 33 = R s
with
2 2 2 2
11 + 22 + 33 = R e
Defines the properties of an isotropic, elastic foam material with user-specified hysteresis response for
unloading, with strain rate dependency, and where Poisson’s ratio is effectively zero.
Remarks
1. If BULKTYP, BULKQ, or BULKL are blank or zero, the default values are used.
2. The continuation line with bulk-viscosity data can be omitted.
3. Poisson’s ratio for this model is effectively zero. Therefore, only one other elastic constant can be
defined which can be G, the shear modulus, or K, the bulk modulus.
4. For this model, the stress-strain curve is independent of the experimental test performed to obtain
the material data (uniaxial, shear, or volumetric). The most common test is the uniaxial
compression test where the stress-strain characteristic can either be defined in terms of the amount
of crush, which is minus the engineering strain, or in terms of the true strain. Since Poisson’s ratio
is effectively zero, the amount of crush is defined as 1 – -----
V V
- , with ------ as the relative volume, and
V0 V0
the true strain is defined as
t
- or In ------ .
dV V
-----
V V 0
t0
The crush factor must be between 0 and 1. The true strain must always be negative and the stress
positive (absolute value).
5. The yield surface in three-dimensional space is a sphere in principal stresses, and is defined by
2 2 2 2
22 + 22 + 33 = R s
where the radius of the sphere R s depends on the strains and strain rates as follows:
R s = f 1 R e f 2 R r
with
2 2 2 2
11 + 22 + 33 = R e
and
·2 ·2 ·2 2
11 + 22 + 33 = R r
342 FOAM2
Foam Material Properties
and f 1 is the function supplied in the stress-strain table and f 2 (if defined) is the function supplied
in the factor-strain rate table.
6. A minimum (SMIN) or failure (SFRAC) tensile stress can be defined. In the first case this
corresponds to a tensile cut-off where the stress cannot fall below the minimum value. In the
second case, if the stress falls below the failure stress the element fails and cannot carry tensile
loading for the remainder of the analysis. Thus the stress can never become negative again.
7. If TABY is blank, the stress does not vary with strain rate. If TABY has a value, then it references
to a TABLED1 entry, which gives the variation with strain rate of the scale factor applied to
the stress.
8. The unloading behavior is piecewise linear (LINEAR), quadratic (QDRATIC) or exponential
(EXPTIAL). The unloading curve is constructed such that the ratio of the dissipated energy (area
between compressive loading and unloading curve) to total energy (area under the loading curve)
is equal to the energy dissipation factor alpha. In the case of piecewise linear unloading, Dytran
constructs an unloading curve whose segments are parallel to the supplied compression table,
except for the first and last segments, which pass respectively through the origin and the point P
on the compression curve where the unloading starts. In the case of quadratic unloading, Dytran
constructs a quadratic curve starting in the origin and ending in point P. If the quadratic unloading
curve falls below the strain axis, then the unloading stress is set to zero. In the case of exponential
unloading, the unloading curve is constructed in a similarly to quadratic unloading except for the
shape of the curve, which is created from an exponential function instead of a
quadratic polynomial.
9. This material can only be used with Lagrangian solid elements.
10. The behavior of this material is described in Materials.
FORCE 343
Concentrated Load or Velocity
This entry is used in conjunction with a TLOADn entry and defines the location where the load or
enforced motion acts, the direction in which it acts, and the scale factor.
Remarks
1. At time t , the load F t is given by F t = SCALE N T t where SCALE is the factor; N is the
vector given by N 1 , N 2 , and N 3 ; and T t is the value at t interpolated from the table referenced
on the TLOADn entry.
2. Concentrated loads can also be defined on the DAREA entry.
3. LID must be referenced by a TLOADn entry.
4. If G references a MATRIG, an RBE2-FULLRIG, or a RIGID surface, the load is applied to the
center of the rigid body. If G references a MATRIG, G must be MR<id>, where id is the MATRIG
number. If G references an RBE2-FULLRIG, G must be FR<id>, where id is the RBE2 number.
If G references a RIGID surface, G is the RIGID surface number.
5. If CID is specified, velocity prescriptions are processed in the local coordinate system referenced
by CID. Only velocity prescriptions can be defined in the local coordinate system.
6. If a component field N1, N2, and/or N3 is left blank,
Force prescription: The component of the force is equal to zero.
Velocity prescription: The component of the velocity is not restrained.
7. If the TYPE field on the TLOADn entry is 0, it defines a force applied to a grid point. If the TYPE
field is 2, it defines an enforced motion on the grid point. If the TYPE field is set to 12, it defines
an enforced motion applied to the center of a rigid body, and if the TYPE field is 13, it defines a
force applied to the center of a rigid body.
344 FORCE1
Follower Force, Form 1
This entry is used in conjunction with a TLOADn entry and defines a follower force with direction that
is determined by two grid points. FORCE1 applies to any type of grid point.
Remarks
1. At time t , the load F t ) is given by:
F t = SCALE N T t
where SCALE is the scale factor, N is the unit vector in the direction from G1 to G2, and T t is
the value at time t interpolated from the table referenced in the TLOAD entry.
2. LID must be referenced by a TLOAD entry.
3. The FORCE1 entry defines a follower force in that the direction of the force changes as the grid
points G1 and G2 move during the analysis.
FORCE2 345
Follower Force, Form 2
This entry is used in conjunction with a TLOADn entry and defines a follower force with a direction that
is determined by four grid points. FORCE2 can be applied to any type of grid point.
Remarks
1. At time t, the load F t is given by F t = SCALE N T t where SCALE is the scale factor, N is
the vector product of the vectors from G1 to G2 and G3 to G4 respectively, and T t is the value
at time t interpolated from the table referenced by the TLOADn entry.
2. LID must be referenced by a TLOADn entry.
3. The FORCE2 entry defines a follower force in that the direction of the force changes as the grid
points G1, G2, G3, and G4 move during the analysis.
346 FORCE3
Grid Point Velocity Definition
Defines the velocity of a grid point in a local coordinate system or in a cascade of two local
coordinate systems.
+ CID2 SCALE2 M1 M2 M3
+
Remarks
1. SCALE2 defines the enforced rigid-body motion of the coordinate system referenced by CID1
with respect to the coordinate system referenced by CID2.
2. This boundary condition can be used only to define the enforced velocities of grid points. Thus,
the TYPE field in the TLOAD1 or TLOAD2 entry should be set to 2.
3. LID is referenced by a TLOAD entry.
4. If CIDx is specified, the velocity components are defined in the local coordinate directions, for
example, if a cylindrical system is referenced, the velocity components define a radial, angular,
and axial velocity.
FORCE3 347
Grid Point Velocity Definition
5. If a component field N1, N2, N3, M1, M2, and/or M3 is left blank, that component of the velocity
is not restrained.
6. The FORCE3 entry is valid for both Lagrangian as Eulerian grid points.
348 FORCEEX
User-defined Enforced Motion at Grid Points
+ G1 G2 G3 G4 THRU G5 -etc.-
+ 100 319 728 429 THRU 457
Remarks
1. LID must be referenced by a TLOAD1 entry.
2. FORCEEX can only be used to specify enforced velocities for grid points. The TYPE field on the
TLOAD1 entry must be set to two. The TID on the TLOAD1 entry must be set to zero or blank (no
time variation).
3. The EXTVEL user subroutine must be present in the file referenced by the USERCODE
FMS statement.
4. See Chapter 7: User Subroutines for a description of how to use user-written subroutines.
5. The constraint name is passed to the subroutine and can be used to identify the constraint.
6. A THRU specification, including the start and finish points in the range, must be on one line.
7. If the THRU specification is used, all the points in the sequence do not have to exist. Those that
do not exist are ignored. The first point in the THRU specification must be a valid grid point. BY
can be used to exclude grid points.
8. None of the fields in the list of grid points can be blank or zero, since this designation marks the
end of the list.
9. Any number of continuation lines can be used to define the list of grid points.
GBAG 349
Gas Bag Pressure Definition
+ TINIT TENV +
+ 293. +
Remarks
1. The SURFACE entry referenced by the SID field must form a closed volume.
2. The pressure in the gas bag is applied to all the faces of the SURFACE.
3. TABLEEX is valid also in all entries where TABLED1 is used.
4. TINIT is the temperature of the inflowing gas at time = 0 . At time = 0 , the mass of the gas
inside the gas bag is calculated as
p init V
m = ---------------
RT init
where, p init the initial pressure, V the volume, R the gas constant, and T init the initial gas
temperature.
5. The flow through exhaust openings, leakage areas and user-specified outflow rate is accumulated.
The volumetric porosity contributes to the outflow of gas as
p
m· out = * Q = ----------- * Q
R*T
where
R = gas constant
T = temperature inside the bag
m· out = mass outflow rate
4 4
q rad = eA r T – T env Radiation
where h is the convection heat-transfer coefficient (CONVEC, CONVECV), e the gas emissivity
coefficient (RADIAT, RADIATV), A c the air bag surface area for convective heat transfer, A r the
air bag surface area for radiation, and T env the environmental temperature.
GBAGC 357
Gas Bag Connection
Remarks
1. Both gbags are triggered before flow between the two gas bags begins.
2. The energy balance and mass flow is as shown in the following graphic:
where
P max = maximum Eulerian pressure exerted on the SURFAE
P min = minimum Eulerian pressure exerted on the SURFACE
P average =average Eulerian pressure exerted on the SURFAE
PERCENT Value used in validity check as defined above. R>0 5%
Remarks
1. The SURFACE SID referenced by the COUPLE entry CID and by the GBAG entry GID must be
equal.
2. All Eulerian and general coupling calculations are deactivated after transition from gas dynamics
to uniform pressure.
GBAGHTR 361
Heat Transfer Model to be used With GBAG Entry
Remarks
1. A combination of multiple GBAGHTRs with different HTRTYPEs is allowed.
2. All options of HTRTYPE can also be referenced by a COUHTR. It allows for setting up the exact
same model for either a uniform pressure model (GBAG to GBAGHTR) or an Eulerian model
(COUPLE to COUHTR). It is then possible to set up the model using the switch from full gas
dynamics to uniform pressure (GBAGCOU).
3. For the same SUBSURF multiple, different types of heat transfer may be defined.
4. A more detailed description can be found in Dytran User’s Guide, Chapter 6: Air Bags and
Occupant Safety, Porosity in Air Bags for more details.
GBAGINFL 363
Inflator Model to be used with GBAG Entry
Bulk Data Entry Descriptions defines an inflator model suited for air bag analyses using the uniform
pressure approach (GBAG). The inflator model is defined as part of the GBAG surface.
Remarks
1. The INFLATR, INFLATR1, INFLHYB, or INFLHYB1 inflator geometry and location is defined
by a subsurface (SUBID). The area of the hole through which the gas enters is equal to the area
of the subsurface multiplied by COEFFV. A value of COEFFV = 1.0 opens up the complete
subsurface area, while a value of COEFFV = 0.0 results in a closed inflator area with no inflow.
2. The same INFTYPE entry referenced from this GBAGINFL entry can be referenced by a
COUINFL entry. This allows for setting up the exact same model for either a uniform pressure
model or an Euler Coupled model:
This makes it possible to set up the model using the switch from full gas dynamics to uniform
pressure (GBAGCOU).
3. One GBAG entry can reference more than one COUINFL entry. This allows for modeling of
multiple inflators in an air bag module.
GBAGPOR 365
Gas Bag Porosity
Remarks
1. The combination of multiple GBAGPORs with different PORTYPEs is allowed.
2. All options of PORTYPE can also be referenced by a COUPOR. It allows for setting up the exact
same model for either a uniform pressure model (GBAG to GBAGPOR) or an Eulerian model
(COUPLE to COUPOR). It is then possible to set up the model using the switch from full gas
dynamics to uniform pressure (GBAGCOU).
3. The options PORFGBG and PERMGBG can be used to model air bags with
different compartments.
368 GRAV
Gravity Field
Remarks
1. The gravity acceleration g t is defined as
g t = SCALE N T t
where SCALE is the gravity scale factor; N is the vector defined by NX, NY, and NZ; and T t is
the value interpolated at time t from the table referenced by the TLOADn entry.
2. LID must be referenced by a TLOADn entry.
3. The type field on the TLOADn entry must be set to zero.
4. One gravitational field can be defined per problem.
5. The gravitational accelerations are applied to all masses in the problem.
GRDSET 369
Grid Point Default
Remarks
1. Any GRID entry with a blank value of PS is set to the value given on this entry. Note that the
constraints on the GRID and GRDSET entries are not cumulative; i.e., if there is a GRDSET entry
with constraint code 34 and a GRID entry with constraint code 2, the grid point is constrained only
in direction 2.
2. There can only be one GRDSET entry in the input data.
370 GRID
Grid Point
Defines the location of a geometric grid point in the model and its constraints.
Remarks
1. All grid-point numbers must be unique.
2. If CP or PS is blank or zero, the value given on the GRDSET entry is used.
3. Grid points can also be constrained using the SPC and SPC1 entries.
4. The values of X, Y and Z depend on the type of the coordinate system CP. Their meaning in each
type of coordinate system is listed below.
Type X Y Z
Rectangular X Y Z
Cylindrical R Z
Spherical R
Defines the hourglass suppression method and the corresponding hourglass damping coefficients.
+C RBRCOR VALUE
+ YES 10000
Cont
Field ents Type Default
HID Hourglass suppression definition number I>0 Required
PROP Property type C See Remark 1.
PID Property number I>0 See Remark1.
HGTYPE Hourglass suppression method: C See Remark 2.
FBV for shells only (default for shells)
FBS for shells and solids (default for solids)
Dyna for solids only
HGCMEM Membrane damping coefficient 0.0 R 0.15 0.1
HGCWRP Warping damping coefficient 0.0 R 0.15 0.1
HGCTWS Twisting damping coefficient 0.0 R 0.15 0.1
HGCSOL Solid damping coefficient 0.0 R 0.15 0.1
RBRCOR Rigid body rotation correction: C NO
NO No rigid-body rotation correction is applied to
hourglass resisting forces.
YES Rigid-body rotation correction is applied to
hourglass resisting forces.
See Remark 3.
VALUE Number of steps R > 0.0 See Remark 3.
HGSUPPR 373
Hourglass Suppression Method
Remarks
1. The property type definition and the property number are required. Since property numbers are
unique within a certain class of element types, the property type and the property number uniquely
define to what elements the hourglass suppression method and coefficients apply. The following
property types are valid entries:
It must be noted however, that only shell CQUAD4 and Lagrangian CHEXA and CPENTA
elements can suffer from undesired hourglass modes. All HGSUPPR entries referring to other
types of elements are ignored.
2. There are three types of hourglass suppression methods available in Dytran. These are standard
DYNA viscous (DYNA) hourglass damping, the Flanagan-Belytschko Stiffness (FBS) hourglass
damping, and the Flanagan-Belytschko Viscous (FBV) hourglass damping.
Lagrangian solid elements can address DYNA and FBS suppression; shell elements can address
DYNA and FBV suppression. The default for the Lagrangian solid elements is FBS. The default
for the shell elements is FBV.
The default hourglass suppression method can be globally changed by the PARAM,HGTYPE.
3. The rigid-body rotation correction on the hourglass forces is only necessary in cases where shell
elements undergo a large rigid-body rotation. If the RBRCOR field is set to YES, and the VALUE
field is left blank, the correction is applied during each time step. If the VALUE field is set to a
number, the rotation correction is applied only when the rigid-body rotation would result in a
rotation of the element over 90° in less than VALUE time steps. Usually, if the rigid-body rotation
correction is necessary; 10000 is a good value. This option saves some CPU time.
The RBRCOR option applies to the Key-Hoff shell formulation only; for all other element types
and formulations, the option is ignored.
374 HGSUPPR
Hourglass Suppression Method
4. The membrane, warping and twisting coefficients apply to shell elements only; for all other
element types, the data is ignored. The solid damping coefficient applies to solid Lagrangian
elements only; for all other element types, the data is ignored.
The default value of the damping coefficients can be globally changed by PARAM,HGCOEFF.
5. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on
hourglass suppression.
HTRCONV 375
Air Bag Convection
Defines the heat transfer through convection for a COUPLE and/or GBAG (sub)surface.
Convection is heat transfer from the air bag to the environment through the air bag surface.
Remarks
1. The HTRCONV entry can be referenced from a COUHTR and/or GBAGHTR entry.
2. When used with Euler, the entry can only be used with the single material hydrodynamic Euler
solver using an EOSGAM (ideal gas) equation of state. Two of the four gas constants ( , R , c v
and/or c p ) have to be defined on the EOSGAM entry.
3. Either HTRCF-C or HTRCF-T must be specified.
4. Energy only transfers out of the air bag if the temperature inside the air bag is higher than the
environmental temperature.
5. A more detailed description of heat transfer by convection can be found in Dytran User’s Guide,
Chapter 6: Air Bags and Occupant Safety, Heat Transfer in Air Bags.
376 HTRRAD
Air Bag Radiation
Defines the heat transfer through radiation for a COUPLE and/or GBAG (sub)surface.
Radiation is heat transfer from the air bag to the environment through the air bag surface.
Remarks
1. The HTRRAD entry can be referenced from a COUHTR and/or GBAGHTR entry.
2. When used with Euler, the entry can only be used with the single material hydrodynamic Euler
solver using an EOSGAM (ideal gas) equation of state. Two of the four gas constants ( , R , c v
and/or c p ) have to be defined on the EOSGAM entry.
3. Either GASEMI-C or GASEMI-T must be specified.
4. Energy only transfers out of the air bag if the temperature inside the air bag is higher than the
environmental temperature.
5. A more detailed description of heat radiation can be found in Dytran User’s Guide, Chapter 6: Air
Bags and Occupant Safety, Heat Transfer in Air Bags.
HYDSTAT 377
Hydrostatic Preset of Density in Euler Elements
Remarks
1. It is assumed that each Euler domain contains at most two Eulerian materials and includes the
GRAV option. One material has to be a fluid using EOSPOL; the other a gas or void. This
EOSPOL material is given by the MID entry. The interface between gas and fluid is the free
surface and is assumed to be normal to the gravity vector as specified on the GRAV entry. For
example if the gravity vector points in the z-direction then the interface between the gas and the
fluid has to be horizontal.
2. The hydrostatic preset changes the density of the fluid like material in order to conform to the
hydrostatic preset. It overrules the material densities as specified on the TICEL and TICVAL
options. Densities of the gas like material are not changed.
3. The free surface has to match with material fractions as defined in the initialization of Euler
elements by the TICEL and TICEUL options. The hydrostatic preset only changes densities; it does
not change material fractions.
4. There are two options to enter the location of the free surface. The first option is to enter a grid
point number. In that case, the CID and XCG-ZCG fields must be left blank. The gridpoint entry
already has the option of using a local coordinate system. When coordinates are used, the GID
field has to be left blank.
5. If there is no structural grid point indicating the free surface, a new grid point can be defined that
is only used for determining the free surface level. If the gravity vector points in the z-direction,
only the z-coordinate of the grid point is used. The x and y coordinate can be chosen arbitrarily.
Similar remarks hold when the gravity vector is in one of the other coordinate directions. The
same holds when using coordinates instead of a grid point.
378 HYDSTAT
Hydrostatic Preset of Density in Euler Elements
Remarks
1. The coupling surface will interact with all Euler elements except the ones defined by the SET1
referring to the SETID.
2. This option can only be used in combination with PARAM, FASTCOUP.
380 INCLUDE
Starts Reading a New Input File
Switches reading of the input data to another file. Once that file is read, processing reverts back to the
original file immediately after the INCLUDE statement.
Remarks
1. The file must be present in the area where Dytran is executing.
2. A comma cannot be used to separate the fields.
3. BEGIN BULK and ENDDATA can be present in the INCLUDE file.
INFLATR 381
Air Bag Inflator Model
Remarks
1. The INFLATR entry can be referenced from a COUINFL and/or GBAGINFL entry.
2. When used in combination with the single material hydrodynamic Euler solver, an EOSGAM
(ideal gas) equation of state is required. In that case, the material number, MID, can be left blank.
When using the Multi-material solver, the material number, MID, has to point to one of the
Eulerian materials and the equation of state of that material has to be of type EOSGAM.
382 INFLATR
Air Bag Inflator Model
3. Either TEMP-C or TEMP-T must be specified. The INFLATR entry uses the specified
temperature as the dynamic temperature of the inflowing gas. The dynamic temperature is the
temperature of the moving gas, as opposed to the static temperature which is also known in
literature as total-, rest-, or stagnation temperature and refers to the temperature of the gas when
brought to rest from its moving condition. The INFLATR1 entry uses the static temperature of the
inflowing gas.
4. If the , GASNAM field contains a real entry real or is left blank, the inflator gas constants are
given on the INFLATR entry itself, see Remark 5. Otherwise, the entry is read as the name of an
INFLGAS entry. In this case, the remaining entries must be left blank.
5. Specify only two of the four gas constants. They are related as:
cp
= ----- > R = cp – cv
cv
INFLATR1 383
Air Bag Inflator Model
Remarks:
1. The INFLATR1 entry can be referenced from a COUINFL and/or GBAGINFL entry.
2. When used in combination with the single material hydrodynamic Euler solver, an EOSGAM
(ideal gas) equation of state is required. In that case, the material number, MID, can be left blank.
When using the Multi-material solver, the material number, MID, has to point to one of the
Eulerian materials and the equation of state of that material has to be of type EOSGAM. The Multi-
material solver does not allow the use of gas fractions.
384 INFLATR1
Air Bag Inflator Model
3. Either TEMP-C or TEMP-T must be specified. The INFLATR1 entry uses the specified
temperature as the static temperature of the inflowing gas. In literature the static temperature is
also known as total-, rest-, or stagnation temperature and refers to the temperature of the gas when
brought to rest from its moving condition, as opposed to the dynamic temperature which refers to
the temperature of the moving gas. The INFLATOR entry uses the dynamic temperature of the
inflowing gas.
4. If the , GASNAM field contains a real entry real or is left blank, the inflator gas constants are
given on the INFLATR1 entry itself (see Remark 5.). Otherwise, the entry is read as the name of
an INFLGAS entry. In this case, the remaining entries must be left blank.
5. Specify only two of the four gas constants. They are related as:
cp
= ----- R = cp – cv
cv
INFLCG 385
Airbag Cold Gas Inflator Model
Remarks
1. The INFLTANK entry can be referenced from a COUNIFL and/or GBAGINFL entry.
2. When used in an Euler coupled analysis, the entry can only be used with the single material
hydrodynamic Euler solver using an EOSGAM (ideal gas) equation of state.
3. Either INITPRES or INITMAS has to be specified, but not both. The relation between INITMAS
and INITPRES is given by:
IINITMAS
INITPRES = R ----------------------------- INITTEMP
TANKVOL
4. The cold gas inflator is a reservoir filled with high pressure gas. It is assumed that the volume
stays constant at TANKVOL. The mass inside the inflator will steadily decrease due to flow into the
Euler domain or to a GBAG. Due to inertia, it can happen that the pressure of the inflator becomes
less than the outside pressure. In that case, some inflow into the inflator occurs. Transport between
inflator and the Euler domain or GBAG is based on the constancy of total temperature. This is
equivalent to the pressure method.
386 INFLCG
Airbag Cold Gas Inflator Model
5. If this field contains a real entry real or is left blank, the inflator gas constants are given on the
INFLATR1 entry itself (see Remark 5.). Otherwise, the entry will be read as the name of an
INFLGAS entry. In this case, the remaining entries must be left blank.
6. Specify only two of the four gas constants. They are related as:
cp
= ----- R = cp – cv
cv
INFLFRAC 387
Hybrid Inflator Gas Fraction Definition
Specifies mass fractions or molar fractions as a function of time for a hybrid inflator definition.
Remarks
1. The INFLFRAC entry must be referenced from an INFLHYB or INFLHYB1 entry.
2. Fraction values of the inflowing gas is linearly interpolated between the specified
time increments.
3. Use as many continuation lines as necessary to completely define the gas fractions. The data for
a time step are preceded by a TIME keyword. Missing entries are set to 0.
4. The order of the gases for which the fractions are specified is identical to the order in which the
gases are specified on the INFLHYB or INFLHYB1 entry.
5. At least one line of gas fractions must be given.
6. If molar fractions are to be used, the universal gas constant must be specified through
PARAM,UGASC.
7. At least one of the fractions for each time step must have a value greater than 0.0.
8. Fractions for each time step should add up to 1.0. If this is not the case, they are scaled so that
they do.
388 INFLGAS
Inflator Gas Definition
Remarks
1. INFLGAS can be referenced by an INFLATR,INFLATR1, INFLHYB, INFLHYB1, or
INITGAS entry.
2. When the molar weight is given, the universal gas constant R uni must be specified using PARAM,
UGASC, so that:
R spec = R uni MOLWT
INFLGAS 389
Inflator Gas Definition
Remarks
1. The INFLHYB entry can be referenced from a COUINFL and/or GBAGINFL entry.
2. When used in an Euler coupled analysis, the entry can only be used with the single material
hydrodynamic Euler solver using an EOSGAM (ideal gas) equation of state.
3. Either TEMP-C or TEMP-T must be specified. The INFLHYB entry uses the specified
temperature as the dynamic temperature of the inflowing gas. The dynamic temperature is the
temperature of the moving gas, as opposed to the static temperature which is also known in
literature as total-, rest-, or stagnation temperature and refers to the temperature of the gas when
brought to rest from its moving condition. The INFLHYB1 entry uses the static temperature of the
inflowing gas.
4. At least one inflator gas must be specified using an INFLGAS entry. There is no limit to the
number of inflator gases per INFLHYB.
INFLHYB1 391
Hybrid Inflator Model
Remarks
1. The INFLHYB1 entry can be referenced from a COUINFL and/or GBAGINFL entry.
2. When used in an Euler coupled analysis, the entry can only be used with the single material
hydrodynamic Euler solver using an EOSGAM (ideal gas) equation of state.
3. Either TEMP-C or TEMP-T must be specified. The INFLHYB1 entry uses the specified
temperature as the static temperature of the inflowing gas. In literature the static temperature is
also known as total-, rest-, or stagnation temperature and refers to the temperature of the gas when
brought to rest from its moving condition as opposed to the dynamic temperature that refers to the
temperature of the moving gas. The INFLHYB entry uses the dynamic temperature of the
inflowing gas.
4. At least one inflator gas must be specified using an INFLGAS entry. There is no limit to the
number of inflator gases per INFLHYB1.
392 INFLTANK
Air Bag Tanktest Inflator Model
Remarks
1. The INFLTANK entry can be referenced from a COUINFL and/or GBAGINFL entry.
2. When used in an Euler coupled analysis, the entry can only be used with the single material
hydrodynamic Euler solver using an EOSGAM (ideal gas) equation of state.
3. The initial tank pressure entry (INITPRES) is interpreted as an absolute pressure and used to
define reference pressure at t=0 in the tank. The different between INITPRES and the pressure
value at t=0 from the table will be added to the entire pressure curve of TPTABLE.
4. The end tank pressure entry (ENDPRES) is interpreted as an absolute pressure at t=tend of tank
pressure table (TPTABLE). This value is used for calculation of total generated mass in the tank.
5. This field must be specified only when Inflator Pressure Method (INFPRES) is defined in the
METH-TANK field.
6. The initial inflator pressure entry (INFLPRES) is interpreted as an absolute pressure and used to
define reference pressure at t = 0 in the inflator. The different between INFLPRES and the
pressure value at t = 0 from the table is added to the entire pressure curve of IPTABLE.
7. Specify only two of the four gas constants. They are related as:
cp
= ----- R = cp – cv
cv
394 INITGAS
Gas Bag or Coupling Surface Initial Gas Fraction Definition
Specifies the initial gas composition inside a gas bag or Euler coupling surface.
Remarks
1. The INITGAS entry can be used to specify the initial gas composition for a gas bag or for an
Eulerian coupling surface. The INTID must be referenced either from a GBAG cad or a
COUPLE entry.
2. Use as many continuation lines as necessary to completely define the gas fractions.
3. At least one INFLGAS reference must be given.
4. Fractions should add up to 1.0. If this is not the case, they will be scaled so that they do.
JOIN 395
Hinge-type Join of Six DOF Grid Points with Three DOF Grid Points
JOIN Hinge-type Join of Six DOF Grid Points with Three DOF Grid Points
Defines a hinge-type join of Lagrangian elements with six degrees of freedom grid points (for example
CHEXA CQUAD4, CBAR etc.) to Lagrangian elements with three degrees of freedom grid points.
Remarks
1. Grid points with the same number of degrees of freedom (DOF) can be equivalenced in the
preprocessing phase.
2. The JOIN gives rise to a hinge connection. A stiff connection can be achieved by using KJOIN.
396 KJOIN
Kinematic Join of Six DOF Grid Points with Three DOF Grid Points
KJOIN Kinematic Join of Six DOF Grid Points with Three DOF Grid Points
Defines the joining of Lagrangian elements with six degrees of freedom grid points (for example, CHEXA
CQUAD4, CBAR, etc.) to Lagrangian elements with three degrees of freedom grid points.
Remarks
1. To change the stiffness of the join, the STIFFNESS field can be defined.
2. Stiffness is increased by setting INTERFERE to none.
3. The kinematic join acts as a locally inserted stiff element.
4. The STIFFNESS field defines a relative stiffness where the value should be in the interval (-1/2,
1/2). Values less than zero reduce the stiffness, and values greater than zero increase the stiffness.
5. Geometric aspects are automatically taken into account.
6. In cases where the set of grid points for the KJOIN is too large to fit in one SET1 entry, you can
define multiple SET1 entries with the same set number. The SET1 entries that have the same set
number are automatically merged into one set.
7. You can define a hinge connection by using the JOIN entry.
MADGRP 397
Group Name for Extended Coupling to MADYMO
Conte
Field nts Type Default
GRPNAME Name of the group. This will be transferred to Madymo. In C Required.
Madymo, this name is used to define contact between the FE
data and MADYMO objects.
GRPTYPE Type of group to be transferred to Madymo: C Required.
ELEM Group of elements
GRID Group of nodes
GRPID The ID of a SET1 that contains the element or node IDs. I>0 Required.
Remarks
1. For details of how to use extended coupling to, please refer to the Dytran User’s Guide,
Chapter 7: User Subroutines, Using Dytran with MADYMO and the Madymo Users Manual.
2. Please specify exactly one element group and one node group when using extended coupling.
3. Only shell elements are supported for extended coupling.
398 MAT1
Material Property Definition, Form 1
Remarks
1. The material number must be unique for all MAT1 and MAT8 entries.
2. The following rules apply when E , G , or v are blank:
a. E and G cannot both be blank.
b. If v and E or v and G are both blank, then both are set to 0.0.
c. If only one of E , G , or v is blank, it is computed from the equation:
E = 2 1 + v G
3. Implausible data on one or more MAT1 entries results in a User Warning Message. Implausible
data is defined as any of the following:
E 0.0 or G 0.0 and v 0.5 or v 0.0 .
4. It is strongly recommended that only two of the values be specified on the MAT1 entry.
MAT2 399
Anisotropic Material for Shells
Defines anisotropic material for shells. The shell cross-section properties are constant throughout
the analysis.
Remarks
1. This material can only be used in combination with a PSHELL entry to activate the classical
lamination theory for shell-structure analysis. If this material is used as transverse shear, then only
G11, G12, and G22 are read. Other material data is ignored. This option is only available for
C0-TRIA, BLT and KEYHOFF shell formulation.
The convention for the GIJ in fields 3 through 8 are represented by the matrix relationship
as follows:
1 G 11 G 12 G 13 1
2 = G 12 G 22 G 23 2
12 G 13 G 23 G 33 12
Remarks
1. An approximate value for G1,Z and G2,Z is the in-plane shear modulus G12. If test data is not
available to accurately determine G1,Z and G2,Z if the material and transverse shear calculations
are deemed essential, the value of G12 may be supplied for G1,Z and G2,Z. The MD Nastran
defaults for G1,Z and G2,Z are infinite if left blank. Dytran assumes the transverse shear moduli
to be equal to G12.
2. Excess data as defined in the MD Nastran MAT8 continuation lines is ignored. Equivalent entries
can be defined in the MAT8A Bulk Data entry.
3. This material model can only be referenced from a PCOMP entry.
MAT8A 401
Orthotropic Failure Material Properties
Defines the failure properties for an orthotropic material for shell elements.
+ +
+ +
Remarks
1. The material number must refer to a MAT8 material definition.
2. If a failure theory is selected other than USER or COMBINAT, the theory defines the following
failure modes:
For an element to fail completely, both fiber and matrix in all sublayers must fail.
3. This material model can only be referenced from a PCOMP entry.
4. Failure stresses are required if a failure theory is selected.
5. ALPHA is used for all failure theories to define a nonlinear stress-strain relation.
6. The individual failure modes are defined according to the corresponding mode in the theory as
listed under FT. To be relevant, the theory must define the failure mode (see Remark 2.). You
must enter data if FT is set to COMBINAT.
7. The property degradation rules due to the various failure modes are listed below:
Material
Constant Failure Mode
Fiber Tens Fiber Comp Matrix Tens Matrix Comp Shear
E1 X X
E2 X X X
V12 X X X X
G12 X X
8. NV is required input and NV new user variables are automatically created. User variables for
sublayers are used on restart and archive output. Refer to them as USRnLxx where n is the user
ID and xx is the sublayer number (see Dytran User’s Guide, Chapter 9: Running the Analysis,
Running Dytran Using the dytran Command). The user variables are available in the EXCOMP
user subroutine.The values S, XT, XC, YT, and YC are also required input when FT is set to USER.
For the model USER1, the routine EXCOMP1 has to be used.
9. The PFD entry indicates how the stresses are degraded to zero. The PFDST indicates when the
stresses start to degrade.
Using ALL means that degradation starts when all material constants ( E 1 , E 2 , Nu12 , G 12 ) are
degraded to zero as specified by the FT entry and the property degradation rules. Note that
property degradation means that the stress increments are zero but that the stresses degrade
according to PFD.
INDV means that stress degradation starts for the fiber stress if E 1 = 0 , for matrix stress if
E 2 = 0 , and for shear stress if G 12 = 0 .
10. Any failure theory introduces five additional sublayer variables. The PFDST entry introduces
three additional variables. The number of user variables is defined by NV.
MATINI 405
Eulerian Initialization Surface
Defines a surface that is used for initialization of regions inside an Eulerian mesh with user-defined
initial conditions.
Remarks
1. All initialization surfaces must form a multifaceted closed volume.
2. In case the surface is defined as a set of segments attached to shell elements you must define the
elements as dummy elements by choosing the DUMMY option on the FORM entry of the
PSHELL1 entry.
3. An initialization surface can only be used to initialize regions in an Eulerian mesh with
appropriate initial conditions. An initialization surface can not be used as a coupling surface,
contact surface or as a rigid surface.
4. The normals of all the segments that form the initialization surface must point in the same general
direction and results in a positive closed volume. Setting the REVERSE option to ON ensures that
this condition is satisfied, regardless of how the segments are defined initially.
5. The COVER option determines how Eulerian elements that are (partially) inside or outside of the
initialization surface are processed.
MATRIG 407
Rigid-Body Properties
+ VX VY VZ WX WY WZ +
+ 13.3
Remarks
1. All coordinates are defined in the basic coordinate system.
2. If MASS is blank or zero, the mass is calculated from the density and the geometry of the mesh
defining the rigid body.
3. The continuation lines are not required.
4. The MATRIG definition is used instead of a DYMATn definition and is referenced by properties
PSOLID, PSHELL, PBAR, and PBEAMn. Different properties can refer to the same MATRIG entry
forming one rigid body. The matrmerg or matrmrg1 option (see PARAM,MATRM(E)RG(1))
can be used for merging different MATRIG and RBE2-FULLRIG definitions into one single rigid
body.
5. By using PARAM,RBE2INFO,GRIDON, the grid points of the MATRIG will be listed in the
output file.
6. If the fields VX, VY, VZ, WX, WY, and WZ are blank, the initial conditions of the rigid body are
calculated from the initial velocities on the TIC and TIC1 entries referring to grid points attached
to the rigid body. The net initial conditions are the average of those for all the grid points attached
to the rigid body.
If the initial conditions are set using the VX, VY, VZ, WX, WY, and WZ fields, the TIC and TIC1
entries referring to grid points attached to the rigid body are ignored.
7. If the inertia tensor or the coordinates of the center of gravity are undefined, then they are
computed from the density or mass and the geometry of the mesh defining the rigid body.
8. The inertia tensor can only be defined in a local rectangular coordinate system. If the entry for a
local coordinate system is left blank, then the inertia tensor is defined in the global
coordinate system.
MATRIG 409
Rigid-Body Properties
Defines a mesh.
+ X0 Y0 Z0 DX DY DZ +
+ +
Remarks
1. The grid points of the mesh are generated at the following locations:
Type = ADAPT:
x y z = XREF + i * DXEL YREF + j * DYEL ZREF + k * DZEL
Grid points and elements located a certain distance outside the coupling surface are not created.
This saves memory and CPU time.
When (XREF, YREF, ZREF) are outside the coupling surface, no actual grid point is created at
this location, but the mesh is shifted appropriately.
MESH 415
Mesh Generator
Type = BOX:
x y z = X0 + i * DXEL Y0 + j * DYEL Z0 + k * DZEL
Nodes and elements are always created, even if the MESH is referenced from the MESHID of a
COUPLE entry.
One of the following input combinations is required:
TYPE=ADAPT
a. DXEL, DYEL, DZEL or
b. DX, DY, DZ and NX, NY, NZ
DXEL = DX/NX; DYEL = DY/NY; DZEL = DZ/NZ
TYPE=BOX
a. DXEL, DYEL, DZEL and NX, NY, NZ or
b. DX, DY, DZ and NX, NY, NZ
DXEL = DX/NX; DYEL = DY/NY; DZEL = DZ/NZ
2. When the starting grid point and/or element number is left blank, the default start number for the
elements and grid-points is equal to the maximum number used +1. For simulations with multiple
coupling surfaces, two methods of treating transport between the Euler meshes are available. One
method supports meshes of TYPE = ADAPT, but does not allow the specification of starting
element or starting grid-point number. This method is the default. The other method only supports
meshes of TYPE = BOX but does allow for the specification of starting element number and
starting grid-point number. This method is activated by PARAM, FLOW-METHOD, FACET.
3. The PID should refer to an existing property id, which can handle the property type given
by PROP.
4. To avoid that the Euler mesh is resized every time-step, the functions defined by TID-X, TID-Y,
TID-Z must describe a ‘step-function’, as such in this example:
i. TABLED1,1,,,,,,,,+1
ii. +,0.0,1.0,,,,,,,+
iii. +,1.E-3,1.0,,,,,,,+
iv. +.1.E-3,1.1,,,,,,,+
v. +,2.E-3,1.1,,,,,,,+
vi. +,2.E-3,1.2,,,,,,,+
5. Care must be taken when refining the Euler mesh. To avoid instabilities, it is advised to stay
within the following guidelines.
a. For each refining step, use a scale factor larger than 0.5.
b. Allow the solution to become smooth again after each refining step. For air bag simulations,
use an interval larger than 5 * diameter_airbag /soundspeed .
6. Resizing is not available for the Multi-material solver.
7. In most cases, METHOD=ALL is the preferred method. Using METHOD=MATERIAL may be
helpful in case of instabilities due to presence of void regions.
8. A biased mesh has nonconstant element sizes in selected directories. Neighbor element size can
have a constant ratio or have identical size. In literature, this type of mesh is also referred to as a
nonuniform mesh or a locally refined mesh.
9. A block mesh consists of number of planes in all three directions. For a nonbiased mesh, these
planes are at fixed distance from each other. In a biased mesh, the distance between subsequent
planes can differ. The varying element size is determined by 1. IBIDX. or 2. GROWX or 3.
The constant step size specified by X0, NX, DX. Here, IBIDX overrules GROWX and GROWX
overrules the X0, NX, DX specification. Likewise for the other directions. The locations of the
planes are written out in the OUT file. Intersecting an x-plane with a y-plane and z-plane will give
a grid point. By carrying out all intersections, the grid points are constructed.
10. SUBMESH is used to replace part of the mesh by a finer mesh. It is meant for use with multiple
coupling surfaces. If this is not the case, then PARAM, GRADED-MESHshould be used. It is
required that overlap between the mesh and submesh consists of, at least, one layer of fine
elements. Also, the boundary of the submesh should not be on the top of faces of the mesh. To
check the element replace,ent, the simulation can be run with constant pressure. Then velocities
should remain virtually zero. For both the mesh as well as the submesh, a distinct archive is
written out. Visualizing by Patran can be done by:
a. Reading in the archive for the mesh. Delete any elements that show zero mass or pressure and
that are covered by the submesh.
b. Reading in the submesh.
c. Two sets of results are now in the data base.
MESH 417
Mesh Generator
By selecting the results of the mesh and then the results of the submesh, a fringe plot of the whole
domain can be obtained. Since the two meshes do not share grid points, it is better to plot fringe
plots using element values.
11. To determine a suitable size for the static output box the simulation can be run first without the
STATBOX option. In the OUT file each summary of adaptive meshing gives the smallest box
surrounding all adaptive elements so far. The last summary then yields the dimension of the static
output box. To accommodate for elements that are not completely inside the box, the actual static
output box is automatically extended a little. The actual dimensions are written in the out file after
the first adaptive meshing summary. Is not needed to set the XREF, YREF, and ZREF options. If
they are set the static output box will be compatible with the defined reference point.
12. Static output supports resizing. After each resizing, the current Euler archive is closed and a new
one is opened. Next cycles in the output request are written to this newly opened archive until the
next resize.
418 MOMENT
Concentrated Moment or Enforced Motion
This entry is used in conjunction with a TLOADn entry and defines the location where the moment or
enforced motion acts as well as the direction and scale factor.
Remarks
1. At time t , the moment M t is given by M t = SCALE * N * T t
where SCALE is the scale factor; N is the vector given by N1, N2, and N3; and T t is the value
at time t interpolated from the table referenced on the TLOADn entry.
2. Moments can also be defined on the DAREA entry.
3. LID must be referenced by a TLOADn entry.
4. If a component field N1, N2, and/or N3 is left blank:
Moment prescription – The component of the moment is equal to zero.
Velocity prescription – The component of the angular velocity is not restrained.
5. If G references a MATRIG, an RBE2-FULLRIG, or a RIGID surface, the load is applied to the
center of the rigid body. If G references a MATRIG, G must be MR<id>, where id is the MATRIG
number. If G references a RBE2-FULLRIG, G must be FR<id>, where id is the RBE2 number.
If G references a RIGID surface, G is the RIGID surface number.
6. If the TYPE field on the TLOAD entry is 0, this defines a moment applied to a grid point. If the
TYPE field is 2, it defines an enforced motion on the grid point. If the TYPE field is 12, it defines
an enforced motion applied to the center of the rigid body, and if the TYPE field is 13, it defines
a moment applied to the center of a rigid body.
MOMENT1 419
Follower Moment, Form 1
This entry is used in conjunction with a TLOADn entry and defines a follower moment with direction that
is determined by two grid points. MOMENT1 can be applied to any type of grid point.
Remarks
1. At time t , the moment M t is given by
M t = SCALE * N * T t
where SCALE is the scale factor, N is the vector from G1 to G2, and T t is the value at time t
interpolated from the table referenced by the TLOADn entry.
2. LID must be referenced by a TLOADn entry.
3. The MOMENT1 entry defines a follower moment in that the direction of the moment changes as
the grid points G1 and G2 move during the analysis.
420 MOMENT2
Follower Moment, Form 2
This entry is used in conjunction with a TLOADn entry and defines a follower moment with direction that
is determined by four grid points. MOMENT2 can be applied to any type of grid point.
Remarks
1. At time t , the moment M t is given by:
M t = SCALE*N*T t
where SCALE is the scale factor, N is the vector product of the vectors from G1 to G2 and G3 to
G4. respectively, and T t is the value at time t interpolated from the table referenced by the
TLOADn entry.
2. LID must be referenced by a TLOADn entry.
3. The MOMENT2 entry defines a follower moment in that the direction of the moment changes as
the grid points G1, G2, G3, and G4 move during the analysis.
NASINIT 421
MD Nastran Initialization
Remarks
1. The time step is constant during the displacement phase and is defined by PARAM,INISTEP.
2. Damping is optional and is not always necessary.
3. The deformed geometry grid-point data is written out after the displacement phase, if no damping
is requested, or after the relaxation phase, when the DAMP field is set to YES. The same applies
to the solution file. (See also the SOLUOUT and BULKOUT FMS statements.)
4. The displacements from an MD Nastran solution are imposed by an enforced velocity field
calculated from the displacements and control parameters.
5. All boundary conditions and loads defined are deactivated during the displacement phase and are
activated after the displacement phase ends.
6. Note that although the deformed geometry after the displacement phase is exactly the same as the
MD Nastran geometry, the actual stress state may differ due to differences in Dytran and MD
Nastran element formulations.
7. Lagrangian CHEXA, CQUAD4, and CTRIA3 elements can be initialized, but the shell
membranes cannot.
8. For prestressing rotating structures, it is recommended that a centrifugal force field be used, rather
than a rotational velocity field. In the actual transient dynamic analysis, the centrifugal force field
can be replaced by a rotational velocity field with consistent boundary conditions.
9. Make the problem setup for the final transient analysis consistent with the prestress analysis.
422 PARAM
Parameter
PARAM Parameter
Remarks
1. A list of the parameters that can be set, along with the parameter names and values, is given in
Chapter 6: Parameters.
2. PARAM entries do not necessarily have to be located in the Bulk Data Section.
3. PARAM values can be redefined during restarts.
PBAR 423
Simple Beam Property
Defines the properties of a simple beam (bar) that is used to create bar elements via the CBAR entry.
Remarks
1. I1 is the moment of inertia about the element z-axis, I zz .
I2 is the moment of inertia about the element y-axis, I yy .
2. This element is solved as a Belytschko-Schwer beam.
424 PBCOMP
Beam Alternate Form of PBEAM
Alternate form of the PBEAM entry to define properties of a uniform cross-sectional beam referenced by
a CBEAM entry. This entry is also used to specify lumped areas of the beam cross section for nonlinear
analysis and/or composite analysis.
+ SHFACT N1 N2 SYMOPT +
+ 1 +
+ Y1 Z1 C1 MID1 +
+ -0.5 1.2 0.1 18 +
+ Y2 Z2 C2 MID2 +
+ 0.2 0.9 0.15 +
+ Yi Zi Ci MIDi
+ ... ... ...
Figure 5-12 PBCOMP Entry SYMOPT Type Examples with Eight Lumped Areas.
Remarks
1. The PID number must be unique with respect to other PBCOMP entries as well as PBEAM entries.
The second continuation entry may be repeated 18 more times. If SECTION = 5 a maximum of
21 continuation entries is allowed; that is, a maximum of 20 lumped areas may be input. If
SECTION=1 through 4, the total number of areas input plus the total number generated by
symmetry must not exceed 20.
2. If the MIDi field on a continuation entry is blank, the value will be that of MID on the parent entry.
MIDi values may be input on continuations without the corresponding Yi, Zi, and Ci values to
allow different stress-strain laws.
426 PBEAM
Beam Property
+ +
+ +
Remarks
1. This entry is an alternative to thePBARentry and defines exactly the same element and properties.
It is more complicated to use than PBAR and has no advantages. PBEAM is retained for
compatibility with MD Nastran and those modeling packages that write PBEAM entries. Use the
PBAR entry if you can.
2. A Belytschko-Schwer beam is used with a shear factor of 0.83333. The plastic moduli are
assumed to be those for a rectangular section
Zp y = 0.75 * A * I2
Zp z = 0.75 * A * I1
Defines complex beam properties that cannot be defined using the PBAR or PBEAM entries. These entries
are to be used only for Belytschko-Schwer elements.
+ A I1 I2 J ZPZ ZPY +
+ +
Remarks
1. Only the entries that are relevant for Belytschko-Schwer beam definition are listed. PBEAM1
entries that apply to Hughes-Liu beams appear earlier in this PBEAM1 discussion.
2. Note the following:
I 1 = I zz I 2 = I yy J = I xx
Defines more complex beam properties that cannot be defined using the PBAR or PBEAMentries. The
following entries are for Hughes-Liu beam elements only.
+ V1 V2 V3 V4
+ 30.1 30.1 10.0 10.0
Remarks
1. Only the entries that are relevant for the Hughes-Liu beam definition are listed here. PBEAM1
entries that apply to Belytschko-Schwer beams are provided in the previous PBEAM1 description.
For more complex cross-sections with the Hughes-Liu beam definition, please use the Predefined
Hughes Liu Section (HLSECTS) option.
434 PBEAM1
Beam Properties (Predefined Hughes-Liu Cross Sections)
Defines more complex beam properties that cannot be defined using the PBAR or PBEAM entries. The
following entries are for predefined cross sections of Hughes-Liu beam elements only.
+ V1 V2 V3 V4 V5 V6 V7 V8 +
+ 30.1 30.1 10.0 10.0 +
Remarks
1. Only the entries that are relevant for the predefined Hughes-Liu beam definition are listed here.
PBEAM1 entries that apply to Belytschko-Schwer beams are provided in PBEAM1 (Belytschko-
Schwer).
2. The cross sections TUBE and RECT can be defined in the regular Hughes-Liu PBEAM1entry.
3. The following cross sections can be defined using the Dytran database.
PBEAM1 437
Beam Properties (Predefined Hughes-Liu Cross Sections)
.
438 PBEAM1
Beam Properties (Predefined Hughes-Liu Cross Sections)
PBEAML 439
Beam Cross-Section Properties
Remarks
1. For structural problems, PBEAML entries must reference a MAT1 orDMATEP material entry.
2. The property number PID must be unique with respect to all other PBEAMand PBEAML
property numbers.
3. The PBEAML entry is automatically translated into a Hughes-Liu PBEAMentry.
4. See the PBEAM1entry description for a discussion of beam-element geometry. The BAR and
TUBE sections are translated into Hughes-Liu PBEAM1definition with the Gaussian quadrature.
The others are divided into a predefined pattern of integration points.
440 PBEAML
Beam Cross-Section Properties
5. Following is an overview of the available cross sections and the specific definitions valid for these
cross sections.
PBEAML 441
Beam Cross-Section Properties
442 PBELT
Belt Property
UNLOAD Number of a TABLED1 defining the force as a function of strain I>0 Required
during unloading. The strain at time n is specified as engineering
strain:
length n – length 0
strain n = ----------------------------------------------------------------
length 0
DENSITY Density of the belt elements as mass per unit length R > 0.0 Required
DAMP1 A damping force is added to the internal force of the belt elements R > 0.0 0.1
to damp out high frequency oscillations. The damping force is
equal to:
F damp = DAMP1 * mass * dvel dt
where
F damp = damping force
DAMP1 = damping coefficient
mass = mass of belt element
dvel = velocity of elongation
dt = time step
DAMP2 The damping force is limited to: R > 0.0 0.1
DAMP2 * F belt
where
F belt = is the internal force in the belt element.
PBELT 443
Belt Property
The force in the element is zero until the element strain exceeds
the slack.
PRESTRES Number of a TABLED1defining a prestress strain as a function of I>0 Blank
S time. The prestress strain must be specified as engineering strain
and will be added to the element strain at time n as:
strain n = strain n + PRESSTRESS n
Remarks
1. The loading and unloading curves must start at (0.0, 0.0).
2. During loading, the loading curve is applied to determine the force in the belt element. At
unloading, the unloading curve is shifted along the strain axis until it intersects the loading curve
at the point from which unloading commences. The unloading table is applied for unloading and
reloading, until the strain again exceeds the intersection point. Upon further loading, the loading
table is applied. For subsequent unloading, the sequence is repeated.
3. Belt elements are tension only elements.
4. Instantaneous slack of an element can also be initialized per element using theTICEL entry with
the keyword SLACK and a corresponding VALUE.
444 PCOMP
Layered Composite Element Property
Remarks
1. The default under MID2, MID3, . . ., is the last-defined material, in this case MID1; for T2,
T3, . . ., all these thicknesses are equal to T1.
2. At least one of the three values (MIDi, Ti, THETAi) must be present for a ply to exist. The
minimum number of plies is one.
3. The symmetric laminate option is currently not available.
4. The thickness of the element is the sum of the ply thicknesses regardless of the values on the
CTRIA3 or CQUAD4 Bulk Data entries.
446 PCOMPA
Additional Data for Layered Composite Element Property
+ SPINCOR
+ YES
Remarks
1. For CQUAD4 elements, the default formulation is Key-Hoff. For CTRIA3 elements, the default
formulation is C0-TRIA. See the Dytran User’s Guide, Chapter 5: Application Sensitive
Default Settingon application sensitive defaults.
2. If the failure mode is such that fiber and shear strength or matrix and shear strength are lost in all
layers, the element is not included in the time-step calculation. If the element fails completely, the
element is omitted from the time-step calculations, irrespective of the value entered in this field.
3. If the STRNOUT field is NO, the strain cannot be output.
4. If ICLT is set to 1, the analysis is performed with classical lamination theory (For more detail
about the classical lamination theory, see the Dytran Theory Manual, Chapter 5: Classical
Lamination Theory (CLT) for Multilayered Shells In this case, it is not possible to request the total
strain output. The (transverse) shear correction factor input is ignored since it is calculated inside
Dytran. There is no update of the cross-sectional properties due to failure. The failure flag only
indicates that the failure condition is satisfied. Additional output for element variables is
available, namely the stress resultants (NXX, NYY, NXY, MXX, MYY, MXY, QYZ, and QZX). Also
the ABD-Q matrices of each element can be requested for output. These data are only stored in
the first layer. The variable names are AijM, BijM, DijM, and QsijM for the components of the
A-, B-, D- and Q-matrices, respectively. For example, to request the A11 of the A-matrix, the
variable name is A11M01.
5. The options for SPINCOR are:
When SPINCOR = NO, slight asymmetric forces are applied to the shell element’s grid points.
This approach is, in general, acceptable up to about 10° in plane shear angle.
The SPINCOR option is required for fabric models and is turned on by default to accurately keep
track of the fiber directions.
448 PDAMP
Linear Damper Properties
Remarks
1. This entry defines a linear viscous damper.
2. For a discussion of the various types of damper elements, see Lagrangian Elements.
PELAS 449
Elastic Spring Property
Defines the stiffness coefficient, the damping coefficient, and the stress coefficient of an elastic spring.
Remarks
1. Be cautious when using negative spring-stiffness values because values are defined directly on
some of the CELASn entry types.
2. One or two elastic spring properties may be defined on a single entry.
3. For a discussion of the various types of spring elements, see Dytran User’s Guide,
Chapter 2: Elements, Lagrangian Elements.
450 PELAS1
Nonlinear Elastic Spring with Hysteresis Property
Remarks
1. The values in the table are either force and displacement or moment and rotation, depending on
whether the spring connects translational or rotational degrees of freedom.
2. The values in the table are interpolated to determine the force/moment for a particular
displacement/rotation.
3. If UNLOAD table is not defined, unloading occurs corresponding to the LOAD curve.
4. Input for loading and unloading must be consistent. Both curves must be either completed defined
or have only positive values (start from (0.,0.)). When only positive values are defined, the curves
are mirrored automatically.
5. For a discussion of the various types of spring elements, see Dytran User’s Guide,
Chapter 2: Elements, Lagrangian Elements.
PELASEX 451
User-defined Spring Properties
Defines the properties for CELASn scalar spring elements used with user-written spring subroutines.
Remarks
1. The seven user values are passed to the EXELAS user subroutine.
2. Dytran does no checking on the user values.
3. For a discussion of the various types of spring elements, see Dytran User’s Guide,
Chapter 2: Elements, Lagrangian Elements.
For a discussion of user-written subroutines, see Chapter 7: User Subroutines in this manual.
452 PELASEX
User-defined Spring Properties
PERMEAB 453
Air Bag Permeability
Typ
Field Contents e Default
PID Unique number of a PERMEAB entry I>0 Required
PERM-C Permeability is a linear function of the pressure difference. R > 0 See Remark 3.
permeability = PERM – C*abs (Pinside – PENV)
For Pinside > PENV: outflow
For Pinside < PENV: inflow
PERM-T Permeability is a tabular function of the pressure difference: I>0 See Remark 3.
table contains: permeability versus |Pinside – PENV|
For Pinside > PENV: outflow
For Pinside < PENV: inflow
FLOW Defines the allowed directions of the flow. C BOTH
BOTH In- and outflow are allowed.
IN Only inflow allowed.
OUT Only outflow allowed.
PENV Environmental pressure R > 0 Required
RHOENV Environmental density R > 0 Required
SIEENV Environmental specific internal energy R > 0 Required
CP Environmental specific heat at constant pressure R > 0 See Remark 5.
Remarks
1. The PERMEAB entry can be referenced from a COUPOR and/or GBAGPORentry.
2. When used with Euler, the entry can only be used with the single material hydrodynamic Euler or
Roe solver using an EOSGAM (ideal gas) equation of state.
3. Either PERM-C or PERM-T must be specified.
454 PERMEAB
Air Bag Permeability
4. The values for the environment p env PENV , env RHOENV , e env SIEENV must be defined
consistent with an ideal gas equation of state:
p env = env – 1 env e env
The env is calculated by Dytran, and is used when inflow occurs. Inflow occurs when
p env p inside .
5. CP is only required if updating of Euler or gas bag gas constants is done, for example if hybrid
inflators are defined.
PERMGBG 455
Air Bag Permeability
Defines a permeable area of a couple and/or GBAG (sub)surface, connected to another GBAG.
The velocity of the gas flow through the (sub)surface is defined as a linear or tabular function of the
pressure difference.
Remarks
1. The PERMGBG entry can be referenced from a COUPOR and/or GBAGPOR entry.
2. When used with Euler, the entry can only be used with the single material hydrodynamic Euler
solver, using an EOSGAM (ideal gas) equation of state.
3. Either PERM-C or PERM-T must be specified.
456 PEULER
Eulerian Element Properties
Remarks
1. Make the property number unique with respect to all other property numbers.
2. The elements that reference this property use the Eulerian formulation.
3. If TYPE is set to HYDRO, only one material number for all the Eulerian elements of TYPE is used
and a hydrodynamic yield model is chosen.
4. If the TYPE is set to either 1stOrder or 2ndOrder, only one material for all Eulerian elements
of TYPE is used and the Riemann solution-based solver is chosen.
5. If TYPE is set to STRENGTH, only one material number for all the Eulerian elements of TYPE is
used and a nonhydrodynamic yield model is chosen.
6. If TYPE is set to MMHYDRO, different material numbers for all Eulerian elements of TYPE are
used and a hydrodynamic behavior is chosen for each material.
7. If TYPE is set to MMSTREN, different material numbers for all Eulerian elements of TYPE are
used and a yield model is chosen for each material.
PEULER 457
Eulerian Element Properties
8. In a multimaterial Euler calculation, the options MMSTREN and MMHYDRO can not be mixed; they
are mutually exclusive.
9. If the material number is blank or zero, the corresponding elements are void. Note that this is not
allowed in the Riemann solution-based Euler solvers, as they do not handle void elements. If you
define void elements and select either the 1stOrder or 2ndOrder scheme, an error message
is issued and the analysis stops.
10. Initial conditions are defined on the TICEL Bulk Data entry.
458 PEULER1
Eulerian Element Properties
Eulerian element properties. The initial conditions of these elements are defined in geometric regions.
Remarks
1. Remarks 1 through 9 of PEULER apply also here.
2. Initial conditions and/or material assignments are defined on theTICEUL Bulk Data entry.
PLOAD 459
Pressure Loads on the Face of Structural Elements
Defines a pressure load on a triangular or quadrilateral shell or membrane element or on the face of a
Lagrangian solid element.
Remarks
1. For quadrilateral surfaces, order the grid points G1 through G4 around the perimeter of the
surface, and number them clockwise or counterclockwise.
2. The direction of positive pressure is calculated according to the right-hand rule using the sequence
of grid points. See Dytran User’s Guide, Chapter 2: Elements, Lagrangian Elements.
3. Reference LID from a TLOADn entry.
4. The pressure p t at time t is given by
p t = SCALE * T t
where SCALE is the scale factor and T t is the value interpolated from the function or table given
on the TLOADn entry at time t.
460 PLOAD4
Pressure Loads on the Face of Structural Elements
Remarks
1. For solid (CTETRA, CPENTACTETRA) elements, the direction of positive pressure is inwards.
2. For plate elements, (CQUAD4, CTRIA3 the direction of positive pressure is the direction of the
positive normal determined by applying the right-hand rule to the sequence of the element grid-
point connectivity.
3. G1 and G3 are ignored for CTRIA3 and CQUAD4 elements.
4. For the triangular faces of CPENTA elements, G1 is a corner grid-point number that is on the face
being loaded, and the G3 or G4 field is left blank. For the faces of CTETRA elements, G1 is a
corner grid-point number that is on the face being loaded, and G4 is a corner grid-point number
that is not on the face being loaded. Since a CTETRA has only four corner grid points, this grid
point G4 is unique and different for each of the four faces of a CTETRA element.
5. If the pressure is 9999., a pressure load is not applied. Instead, it is translated to a CFACE1 entry.
This makes it easy to generate CFACE1 entries using a standard preprocessor. See Dytran User’s
Guide, Chapter 9: Running the Analysis,Using a Modeling Program with Dytran for details. The
LID field is converted to the number of the set of faces.
PLOAD4 461
Pressure Loads on the Face of Structural Elements
where SCALE is the scale factor and T t is the value interpolated from the function or table given
on the TLOADn entry at time t .
462 PLOADEX
User-defined Pressure Load
Remarks
1. Reference LID by a TLOAD1entry.
2. The EXPLD user subroutine must be present in the file referenced by the USERCODE FMS
statement.
3. See Chapter 7: User Subroutines in this manual for a description of user-written subroutines.
PMARKER 463
Property Definition of a Marker Element
Content
Field s Type Default
ID Marker property ID; referred to by CMARK# entries I>0 Required
TYPE Behaviour of the marker grid points in the FV domain C FIXED
FIXED the marker does not move in the FV domain.
MOVING the marker is moved by velocities in the FV domain.
Remarks
1. The PMARKER entry is ignored for elements referring to structural grid points. These structural
grid points move with the structure and the FV velocities do not change their velocity.
2. Type = FIXED: means that the marker is stationary through out the simulation and is, therefore,
not moving with the Euler velocity. If the marker grid is located outside the Eulerian domain(s),
the Marker is allowed to exist. However, no variables are recorded and they appear as zero on the
Time History plots.
3. Type = Moving: marker is moving along with the Eulerian material. When the grid point
approaches a coupling surface, there is no mechanism that prevents the marker from passing
through the coupling surface. When this happens, the marker enters an element that is covered and
motion of the grid point stops. It is allowed that the grid point moves from one Euler domain to
the other through a porous hole or a coupling surface with interactive failure.
464 PMINC
Constant Spallation Model
Remarks
1. If the pressure in an element falls below the minimum pressure, the element spalls. The pressure
and yield stress are set to zero.
2. The default for the minimum pressure for Lagrangian solids is -1.E20. For Eulerian elements, the
default is 0.0.
3. If an element spalls a void is created. To prevent too small void fractions, a void fraction is put to
zero if it is smaller than FVTOL. The default for FVTOL is 1.E-4 and works only for Eulerian
elements. This value should be decreased in case of large mass increase of material without any
reason. Voids can be created during transport of material, because of a material failure and by
unloading.
PMINC 465
Constant Spallation Model
4. With FVTOL2 =0, any void fraction in an element will lead to failure, and then no tensile stresses
are possible. In simulations in which tensile conditions are present, it can be required to allow for
tensile stresses in the presence of a small void fraction not exceeding a threshold. This threshold
is given by FVTOL2. A good value for FVTOL2 = 2*FVTOL = 2.E-4. FVTOL2 is only used for
Eulerian materials. FVTOL2 should be larger than FVTOL.
466 POREX
User-defined Porosity Model Specified by a User Subroutine
Remarks
1. The porosity ID (PID) must be referenced by a COUPOR entry.
2. The EXPOR user subroutine must be present in a Fortran source file that is referenced by a
USERCODE File Management Statement in the input file.
3. See the explanation in Chapter 7: User Subroutines on how to use user-written subroutines.
4. The porosity name specified in the NAME field of the POREX entry is passed to the user-written
subroutine and can be used to identify the porosity model.
PORFCPL 467
Flow Between Two Coupling Surfaces Through a Hole
Defines an interaction between two coupling surfaces through a small hole. The velocity of the gas flow
through the hole is based on the pressure method.
Remarks
1. The PORFCPL entry can only be referenced from COUPOR entry.
2. This option can only be used in combination with PARAM, FASTCOUP, and EOSGAM material.
3. The pressure method used to calculate the material transport through a porous (sub) surface is
described in the Dytran User’s Guide, Chapter 4: Fluid Structure Interaction, General
CouplingFor more detail on modeling flow between Eulerian domains, see PARAM, FLOW-
METHOD.
468 PORFGBG
Flow Between Two Air Bags Through a Hole
Remarks
1. The PORFGBG entry can be referenced from a COUPOR and/or GBAGPORentry,
2. When used with Euler, this entry can only be used with the single material hydrodynamic Euler
solver, using an EOSGAM (ideal gas) equation of state.
PORFLCPL 469
Flow Between Two Coupling Surfaces Through a Large Hole
Defines an interaction between two coupling surfaces through a large hole. The velocity of the gas flow
through the hole is based on the velocity method.
Remarks
1. The PORFLCPL entry can only be referenced from COUPOR or GBAGPOR entry.
2. This option can only be used in combination with PARAM, FASTCOUP.
3. The velocity method used to calculate the material transport through a porous (sub) surface is
described in Dytran User’s Guide, Chapter 4: Fluid Structure Interaction, General Coupling.
470 PORFLGBG
Flow Between Two Air Bags Through a Large Hole
Remarks
1. The PORFLGBG entry can be referenced from a COUPOR and/or GBAGPORentry,
2. Once gas from a GBAG enters a Eulerian domain, it is treated as Eulerian material. For the single
material Euler solver, only one Eulerian material is present and the material number, MID, can be
left blank. Since GBAG material is an ideal gas, it is required that Eulerian material also uses an
EOSGAM (ideal gas) equation of sate. When using the multi-material solver, the material number,
MID, has to point to one of the Eulerian materials and the equation of state of that material has to
be of type EOSGAM.
3. The velocity method used to calculate the material transport through a porous (sub)surface are
described in Dytran User’s Guide, Chapter 4: Fluid Structure Interaction, General Coupling.
PORFLGBG 471
Flow Between Two Air Bags Through a Large Hole
4. For flow between two uniform pressure air bags, the material transport is based on the theory of
one-dimensional gas flow through a small orifice, and depends on the pressure difference. This is
equivalent to the PORFLGBG entry.
472 PORFLOW
Porous Flow Boundary
Defines the material properties for the in- or outflow of an Eulerian mesh through a porous
(SUBSURF)SURFACE.
Remarks
1. Reference FID by a COUPOR entry.
2. Any material properties not specifically defined have the same value as the element that the c
segment is intersecting.
3. The SURFACE can be only a general coupling surface (see the COUPLE entry).
4. The different methods used to calculate the material transport through a porous (sub)surface are
described in Dytran User’s Guide, Chapter 4: Fluid Structure Interaction, General Coupling.
5. METHOD=VELOCITY is valid for all equation of state models.
METHOD=PRESSURE is valid for EOSGAM (ideal gas) in combination with the single material
hydrodynamic Euler solver.
6. Alternative methods are available to define holes and permeable sections in an air bag. See the
entries: COUPOR, GBAGPOR, PORHOLE, PERMEAB, PORFGBG and PERMGBG
7. In the case of material flow into a multi-material Euler mesh, the material number, the density,
and specific energy have to be set. On the other hand, when material flows out of a multi-material
Euler mesh, it is assumed that each of the materials present in the outflow Euler element
contributes to the outflow of mass. The materials are transported in porportion to their relative
volume fractions.
8. Prescribing both pressure and velocity may lead to the instabilities.
474 PORFLOWT
Time-dependent Porous Flow Boundary
Remarks
1. Reference FID by a COUPOR entry.
2. Any material properties not specifically defined have the same value as the element that the
(SUBSURF)SURFACEsegment is intersecting.
3. The SURFACE can be only a general coupling surface (see the COUPLE entry).
4. The different methods used to calculate the material transport through a porous (sub)surface are
described in Dytran User’s Guide, Chapter 4: Fluid Structure Interaction, General Coupling.
These are METHOD=VELOCITY and METHOD=PRESSURE. For PORFLOWT, the VELOCITY
method is used. The PRESSURE method is not available.
5. Alternative methods are available to define holes and permeable sections in an air bag. See the
entries: COUPOR, GBAGPOR, PORHOLE, PERMEAB, PORFGBG, and PERMGBG.
6. In the case of material flow into a multi-material Euler mesh, the material number, the density,
and specific energy have to be set. On the other hand, when material flows out of a multi-material
Euler mesh, it is assumed that each of the materials present in the outflow Euler element
contributes to the outflow of mass. The materials are transported in porportion to their relative
volume fractions.
7. The boundary condition initiates or determines a wave in compressible material like gas and
water. This can be either an outgoing or an ingoing wave. For stability, it is important that the
waves created are compatible with the flow type near the boundary. Relevant flow types are
subsonic inflow, subsonic outflow, supersonic inflow, and supersonic outflow. For example, for
subsonic inflow, prescribing both pressure and velocity would initiate outgoing waves. Outgoing
waves for an inflow boundary condition is known to be instable. However, for supersonic inflow,
you can specify both pressure and velocity since there are no outgoing waves at a supersonic
inflow boundary.
8. When a TABLEEX is referenced, the EXFUNC user subroutine must be created. See TABLEEX for
more details.
PORHOLE 477
Holes in Air Bag Surface
Remarks
1. The PORHOLE entry can be referenced from a COUPOR and/or GBAGPORentry.
2. When used with Euler, this entry can only be used with the single material hydrodynamic Euler
solver, using an EOSGAM (ideal gas) equation of state.
3. The values for the environment p env (PENV), env (RHOENV), e env (SIEENV) must be defined
consistent with an ideal-gas equation of state:
p env = env – 1 env e env
The env is calculated by Dytran, and is used when inflow occurs. Inflow occurs when
p env p inside .
4. CP is only required if updating of Euler or gas bag gas constants is done, for example if hybrid
inflators are defined.
478 PORHYDST
Porous Flow Boundary
Remarks
1. Reference FID by a COUPOR entry.
2. The velocity and outflow density have the same value as the element that the
(SUB)SURFACEsegment is intersecting.
3. The SURFACE can be only a general coupling surface (see the COUPLE entry).
4. It is required that the coupling surface refers to a HYDSTAT entry. This HYDSTAT entry will be
used to prescribe a hydrostatic pressure profile on the subsurface. For example, the water level
and atmospheric pressure are taken from the HYDSTAT entry. This defines the pressure and the
inflow density.
5. In contributions of the surface to the Euler elements, the pressure gradient across the surface is
taken into account. Therefore, splitting up of the surface and creating new PORHYDST entries
does not increase the accuracy of the prescribed pressures. If the water level and atmospheric
pressure are the same in the whole region outside the coupling surface, using one PHORHYDST
entry is sufficient.
6. The atmospheric pressure is prescribed on those parts of the surface that are above the water level.
PORLHOLE 479
Large Hole in Air Bag Surface
+ MID
+ 3
Remarks
1. The PORLHOLE entry can be referenced from a COUPOR and/or GBAGPOR entry.
2. When used in combination with the single material hydrodynamic Euler solver, an EOSGAM
(ideal gas) equation of state is required. In that case, the material number, MID, can be left blank.
When using the multi-material solver, the material number, MID, has to point to one of the
Eulerian materials and the equation of state of that material has to be of type EOSGAM.
3. The values for the environment p env (PENV), env (RHOENV), e env (SIEENV) must be defined
consistent with an ideal-gas equation of state:
p env = env – 1 env e env
The env is calculated by Dytran, and is used when inflow occurs. Inflow occurs when
p env p inside .
480 PORLHOLE
Large Hole in Air Bag Surface
4. CP is only required if updating of Euler or gas bag gas constants is done, for example if hybrid
inflators are defined.
5. The velocity method used to calculate the material transport through a porous (sub)surface are
described in Dytran User’s Guide, Chapter 4: Fluid Structure Interaction, General Coupling.
6. For in and out flow of an uniform pressure air bag (GBAG), the material transport is based on the
theory of one-dimensional gas flow through a small orifice, and depends on the pressure
difference. This is equivalent to the PORHOLE entry.
PROD 481
Rod Property
Remark
All PROD entries must have unique property numbers.
482 PSHELL
Shell-Element Properties
+ MID4 ICLT
+ 103
Remarks
1. The property number must be unique with respect to all other properties.
2. Shell of constant thickness with three-point Gauss integration and a transverse shear correction
factor of 0.83333 are assumed. For shells using the classical lamination theory option no shear
correction factor is applied. The transverse shear stiffness is input as material property using a
MAT2 entry. For CQUAD4 elements, the formulation is Key-Hoff and for CTRIA3 elements the
formulation is C0-TRIA.
3. If the thickness is set to 9999, all the elements with this property ID are not treated as CQUAD4and
CTRIA3 elements but are converted to CSEGentries. This allows CSEG to be defined easily using
standard preprocessors. See Dytran User’s Guide, Chapter 9: Running the Analysis, Modeling of
Surfaces and Faces for details.
4. Material entries that can be referenced by shell elements defined on the PSHELL entry can be
found in Dytran Theory Manual, Chapter 3: Materials.
5. If the thickness is set to blank or 0.0, the thickness on the CTRIA3 and CQUAD4 must be defined.
6. See also Dytran User’s Guide, Chapter 5: Application Sensitive Default Setting.
PSHELL 483
Shell-Element Properties
7. If ICLT is set to 1, the shells will be analyzed using the classical lamination theory. In this case
MID1, MID2, MID3 and MID4 refer to membrane, bending, transverse shear and membrane-
bending coupling materials, respectively. All these materials must be filled in and they refer to a
MAT2 entry. In this case, the material angles in the element connectivity entries are ignored. More
information about Classical Lamination Theory for Shells can be found in the Dytran Theory
Manual, Chapter 5: Classical Lamination Theory (CLT) for Multilayered Shells
The element outputs are NXX, NYY, NXY, MXX, MYY, MXY, QYZ, and QZX. These are general
forces per unit length. For more detail description about these forces, see the Dytran
Theory Manual.
484 PSHELL1
Shell-Element Properties
Defines the properties of Lagrangian shell elements that are much more complicated than the shell
elements defined using the PSHELL entry.
Remarks
1. Shells of constant thickness with three-point Gauss integration are more easily defined using the
PSHELL entry.
2. Material entries that can be referenced by shell elements can be found in Materials.
3. For CQUAD4 elements, the default formulation is KEYHOFF. For CTRIA3elements, the default
formulation is CO-TRIA. See also Dytran User’s Guide, Chapter 5: Application Sensitive
Default Settings.
4. Make the property number unique with respect to all other properties.
5. If the thickness T is set to 9999., all elements with this property number are not treated as
CQUAD4 and CTRIA3 elements but are converted to CSEG entries. This conversion allows
CSEGs to be defined easily using standard preprocessors. See Dytran User’s Guide,
Chapter 9: Running the Analysis, Using a Modeling Program with Dytran for details.
6. Membrane elements can only be triangular and must reference a DMAT or DMATEL material
entry. In case the HUGHES shell formulation is used, only an elastic material can be referred to.
486 PSHELL1
Shell-Element Properties
7. Dummy elements are used to define rigid bodies or to achieve a closed volume when defining
coupling surfaces. Do not use them to create CSEG entries.
8. If the thickness is set to blank or 0.0, the thickness is defined on the CTRIA3and CQUAD4 entry.
9. Specifying QUAD and NUMB is not necessary if FORM is MEMB.
10. The following defaults apply:
11. When shell elements undergo large twisting, the linear transverse shear calculations must be used
(TRANSHR). It increases accuracy at the expense of more computer time.
12. The default vector length for vector machines is used whenever LENVEC is not defined.
Increasing the vector length is usually more efficient, but requires more memory. In some
problems a recurrence in the force update may inhibit vectorization on vector machines.
Decreasing the vector length may avoid the recurrence. Examine the problem output for
information on this recurrence.
13. The options for SPINCOR are:
NO No SPINCOR correction is applied
YES A SPINCOR correction is applied.
When SPINCOR = NO, slight asymmetric forces are applied to the shell element’s grid points.
This approach is, in general, acceptable up to about 10° in plane shear angle.
The SPINCOR option is required for fabric models and is turned on by default to accurately keep
track of the fiber directions.
14. REF defines the location of the integration pints in the thickness direction. An example for three
integration points (x):
x
REF= MID G1 *----------x-----------* G2
x
REF=TOP G1 *----------x-----------* G2
x
x
x
x
REF= BOT G1 *----------x-----------* G2
PSOLID 487
Lagrangian Solid-Element Properties
Remarks
1. The property number must be unique with respect to all other property numbers.
2. Material entries that can be referenced by Lagrangian solid elements are given in Dytran Theory
Manual,Chapter 3: Materials.
3. IN is a sort of minimum number of integration points in which the element does not have zero
energy displacement patterns. For CHEXA (CPENTA, it is 1 x 1 x 1. Therefore, the right value for
IN is 1 or 2. The ISOP option is for choosing how the element strains should eventually be
calculated. For now, when IN = 2, the right option for ISOP is 1 for full integration and 0 for
reduced integration. When IN = 1, the correct option for ISOP is 1.
The default for CTETRA uses linear tetrahedron FE scheme (IN = 1 and ISOP = 1). The
collapsed hexahedron scheme for CTETRA (IN = 2 and ISOP = 0) is deactivated. Please use
PARAM,OLDLAGTET,1 to activate it. If PARAM is set, then old scheme for CTETRA is default.
But, it is still possible to use the new TET by using a separate PSOLID with the right IN =1 and
ISOP = 1 combination.
488 PSOLID
Lagrangian Solid-Element Properties
The default for CHEXA and CPENTA uses reduced integration scheme (IN = 2 and
ISOP = 0). IN = 2 or TWO and ISOP = 1 or FULL means using two integration network.
If other combinations are used, they are set to default.
Only limited features are supported for elements with the IN = 2 and ISOP = FULL scheme.
The current version supports only MATRIG,DMATEL, DMAT-EOSPOL-SHREL-YDLVM, and
DMAT-EOSPOL-SHRLVE.
To activate the CTETRA element based on linear tetrahedrom FE formulation, use IN = 1 and
ISOP = 1.
4. Use the PEULER entry to define the properties of the Eulerian elements.
PSPR 489
Linear-Elastic Spring Properties
Remarks
1. This entry defines a linear-elastic spring with failure. PSPR1 can be used to define
nonlinear springs.
2. The behavior of this spring is discussed in Dytran User’s Guide, Chapter 2: Elements,
Lagrangian Elements.
490 PSPR1
Nonlinear-Elastic Spring with Hysteresis Properties
Defines the properties for a nonlinear spring where the stiffness varies with displacement.
Remarks
1. The values in the table are interpolated to determine the force for a particular displacement.
2. If the UNLOAD table is not defined, unloading occurs corresponding to the LOAD curve.
3. Input for loading and unloading must be consistent. Both curves must be either completed defined
or have only positive values (start from (0.,0.)). When only positive values are defined, the curves
are automatically mirrored.
4. The behavior of this spring is discussed in Dytran User’s Guide, Lagrangian Elements.
PSPREX 491
User-defined Spring Properties
Defines the properties for CSPR spring elements that are used with user-written spring subroutines.
Remarks
1. The seven user values are passed to the EXSPR user subroutine.
2. Dytran does no checking of the user values.
3. For a discussion of the various types of spring elements, see Dytran User’s Guide,
Chapter 2: Elements, Lagrangian Elements
4. For a discussion of how to use user-written subroutines, see Chapter 7: User Subroutines in
this manual.
492 PVISC
Linear-Damper Properties
Remarks
1. This entry defines a linear viscous damper. PVISC1can be used to define nonlinear dampers.
2. The behavior of this type of damper is discussed in Dytran User’s Guide, Chapter 2: Elements,
Lagrangian Elements
PVISC1 493
Nonlinear Damper Properties
Defines the properties of a nonlinear damper where the damping constant varies with the velocity.
Remarks
1. This entry defines the properties of a nonlinear damper. Use the PVISC entry to define
linear dampers.
2. The values in the table are interpolated to get the force for a particular velocity.
3. The behavior of this damper is discussed in Dytran User’s Guide, Chapter 2: Elements,
Lagrangian Elements.
494 PVISCEX
User-defined Damper Properties
Defines the properties for CVISC damper elements used with user-written subroutines.
Remarks
1. The seven user values are passed to the EXVISC user subroutine.
2. Dytran does no checking on the user-supplied values.
3. For a discussion of the various types of damper elements, see Dytran User’s Guide,
Chapter 2: Elements, Lagrangian Elements. For a discussion of user-written subroutines, see
Chapter 7: User Subroutines in this manual.
PWELD 495
Spotweld Property
Defines the properties of a spotweld connection between two grid points. It is referenced by the CROD
or CBAR entry.
+ FAILTIME
+
Remarks
1. A spotweld is treated as a rigid body with its inertia properties calculated by lumping the
properties of the end points.
A set of spotwelds and/or BJOINs connected to each other is treated as one rigid body.
Lumping of the initial positions and velocities:
The lumped rigid-body mass is not zero:
• The initial positions and velocities are lumped using mass-weighting.
• If a grid point has zero mass, it’s initial position and velocity is ignored.
The lumped rigid-body mass is zero:
• The initial positions and velocities are lumped by averaging.
• Boundary conditions allocated to the grid points are combined, if possible.
496 PWELD
Spotweld Property
When failure of a spotweld that is connected to other spotweld(s) and/or BJOINs occurs, the rigid-
body lumped properties and boundary conditions are redefined.
2. If the end points of a spotweld coincide, the direction vector cannot be determined. As a result,
no components of tension, compression, shear, torque, and bending can be calculated. Instead, the
total force or moment is used to check for failure against the specified failure criteria:
a. The total force acting on the spotweld is checked against:
FAILTENS
FAILCOMP
FAILSHEA
FAILTOTF
b. The total moment acting on the spotweld is checked against:
FAILTORQ
FAILBEND
FAILTOTM
The spotweld fails if one of the above criteria is satisfied.
3. All failure modes are checked simultaneously.
4. An overview of the generated spotwelds and BJOINs can be requested. See
PARAM,INFO-BJOIN.
5. You have access to the results of the spotweld elements by requesting for results of the
corresponding CROD or CBAR elements.
The variables are only calculated for spotwelds with a failure criterion. They are described
as follows:
Defines the properties of a skin-stringer connection with delamination or rupture criteria. The PWELD1
entry is referenced by a CROD entry.
+ FAILTIME POSITION
+ UPPER
Remarks
1. Connecting beam and shell grid points by a CROD element that references a PWELD1 entry
defines a spotweld connection. The PWELD1 entry defines the failure criteria for the
spotweld connection.
2. The spotweld connection is treated as a rigid body with the properties calculated by lumping the
properties of the end points it connects.
When the lumped rigid-body mass is not equal to zero:
• The initial positions and velocities are lumped using mass weighting.
PWELD1 499
Skin-Stringer Delamination
• If a grid point has a zero mass, its initial position and velocity are ignored.
When the lumped rigid-body mass is equal to zero:
• The initial positions and velocities are lumped by averaging.
• Boundary conditions defined for the grid points of the connection are combined
when possible.
3. The end point a of the CROD is the connecting point of the skin (shell element), and end point 2
is the connecting point of the stringer (beam element).
4. The failure force and/or moment criteria are defined per unit length, where the length is defined
by the length of all beam (stringer) elements connected to the spotweld element. Each stringer
contributes half of its length to the spotweld. The resulting forces and moments per unit length,
acting on the spotweld are checked against the failure criteria as defined on the PWELD1 entry.
5. The position of the beam (stringer) element with respect to the shell (skin) element it is connected
to, should be defined by considering the orientation of the element’s local y-z coordinate axes.
The normal to the skin coincides with the z s axis. The upper side of the skin is defined by the
direction the normal points to. Figure 5-13 illustrates the definition of the upper- and the lower-
side positioning of the connection.
6. The direction of the normal at the location of the spotweld connection is defined as the average
of the normal vectors of all connected shell (skin) elements. The average direction is used in
the calculation of the failure criteria. The length of the spotweld element is small and assumed to
be zero. As a result, the forces acting at the end points of the spotweld do not introduce
additional moments.
500 PWELD1
Skin-Stringer Delamination
7. In case the position is defined as MID, the direction of the spotweld element cannot be determined.
As a result, the tensile, compressive and shear force components, as well as the torque and
bending moment components cannot be computed. The failure criteria is based on the total force
and/or moment. Note that the output for the force components is the total force, and the output for
the moment components is the total moment.
8. The total force acting on the spotweld is checked against:
FAILTENSL
FAILCOMPL
FAILSHEAL
FAILTOTL
The total moment acting on the spotweld is checked against:
FAILTORQL
FAILBENDL
FAILTOTML
The spotweld connection fails if any of the above criteria is met.
9. All failure criteria are checked simultaneously. If any of the failure criteria is met, the connection
will fail.
10. Tensile and compressive loading is evaluated in the direction of the normal to the surface. The
shear load is evaluated in the plane of the surface. A positive load on the spotweld element in the
direction of the normal (the XFORCE) indicates tensile loading. A negative load indicates
compressive loading. Note that you input both the tensile and compressive failure criteria as
positive numbers.
11. The shear load is evaluated in the plane to the normal. The output value on the connecting element
is always positive, as the direction of the shear in the plane is irrelevant for failure.
12. The torque is evaluated as the moment about the normal to the surface. The bending moment is
evaluated in the plane to the normal. The output of the moments on the connecting element is
always positive, as the direction of the moments is irrelevant for failure.
13. An overview of the generated spotwelds can be requested by the entry PARAM,INFO-BJOIN.
See the reference page for more details.
14. You can access the results of the spotweld elements for output by requesting results for the
corresponding CROD elements. The variables listed below are available only for CROD elements
that have been used to define a spotweld element:
15. When you have not defined any failure criteria, the output results on the CROD elements that
define the connection are all zero. The failure evaluation and computation is skipped in this case
for performance reasons. If you want to see the actual load on the connecting elements, but do no
wish to introduce any failure, you have to define at least one criterion with a large enough value
to ensure there is no failure. Any value less than 1.0E20 suffices.
16. Spotwelds for a skin-stringer connection can also be defined using a BJOIN entry with the
TYPE set to RUPTURE. Note that in case you use the BJOIN option, you do not have access to
the results on the connection as you have when using the PWELD1 definition. The
BJOINconnection does not use the CRODelements as the connecting entities and therefore no
output on the connection is available.
502 PWELD2
Sandwich Structure Delamination
Defines the failure properties for delamination/peeling of the facing and core connection of a sandwich
structure. The PWELD2 entry is referenced by a CRODentry.
+ FAILTIME
Remarks
1. The PWELD2 connection can only be used for a shell (facing) to solid (core) element connection.
2. The sandwich structure is modeled using shell and solid elements. The connection of the facing
and the core is modeled by connecting the shell and solid element’s grid points with CROD
elements. The CROD elements should refer to a PWELD2 entry.
3. When the facing-core connection has not yet failed, it is treated as a rigid body with the properties
calculated by lumping the properties of the end points it connects.
When the lumped rigid-body mass is not equal to zero:
• The initial positions and velocities are lumped using mass weighting.
• If a grid point has a zero mass, its initial position and velocity are ignored.
When the lumped rigid-body mass is equal to zero:
• The initial positions and velocities are lumped by averaging.
PWELD2 503
Sandwich Structure Delamination
• Boundary conditions defined for the grid points of the connection are combined
when possible.
4. End point 1 of the CROD is the connecting point of the facing (shell element) and end point 2 is
the connecting point of the core (solid element).
5. The failure criteria are based on forces and moments per unit area. The area associated with a
connection is equal to the sum of the areas of the connected shell (facing) elements. Each facing
elements contributes one quarter of its area to the weld connection in case of a quad element
(CQUAD4), and one third in case of a triangular element (CTETRA). The resulting forces and
moments are checked against the failure criteria defined on the PWELD2 entry.
6. All failure criteria are checked simultaneously. If any of the failure criteria is met, the
connection fails.
7. Since the solid element grid points have only three degrees of freedom (translation only), there is
no contribution of moments or rotations to the spotweld element from the solid's grid points. The
contribution of the moment and rotation comes entirely from the connected shell elements.
8. The face of a solid element that is connected to the shell (facing) element determines the direction
of the normal to the surface. The normal to the surface always points outwards. The normal is used
as the direction vector in the computation of the failure criteria for compression and tension. The
direction of the normal is defined as the average of the normal vectors of the connected core
element's faces.
9. Tensile and compressive loading is evaluated in the direction of the normal to the surface. The
shear load is evaluated in the plane to the normal. A positive load on the spotweld element in the
direction of the normal (the XFORCE) indicates tensile loading. A negative load indicates
compressive loading. Note that you input both the tensile and compressive failure criteria as
positive numbers.
10. The shear load is evaluated in the plane to the normal. The output of the shear load on the
connecting element is always positive, as the direction of the shear in the plane is irrelevant
for failure.
11. The torque is evaluated as the moment about the normal to the surface. The bending moment is
evaluated in the plane to the normal. The output of the moments on the connecting element is
always positive, as the direction of the moments is irrelevant for failure.
12. An overview of the generated connections can be requested by the entry PARAM,INFO-BJOIN.
For more details, see the parameter BJOIN reference page.
13. You can access the results of the spotweld elements for output by requesting results for the
corresponding CRODelements. The variables listed below are available only for CROD elements
that have been used to define a spotweld element:
14. When you have not defined any failure criteria, the output results on the CROD elements that
define the connection will all be zero. The failure evaluation computations are skipped in this case
for performance reasons. If you want to see the actual load on the connecting elements, but do not
wish to introduce any failure, you have to define at least one criterion with a large enough value
to ensure there is no failure. Any value less than 1.0E20 suffices.
RBC3 505
Rigid-Body Constraint
+ X1 X2 X3 Y1 Y2 Y3 +
+ +
+ Z1 Z2 Z3
+
Remarks
1. If G1, G2, and G3 are specified, then the RBC3 coordinate system is determined by the grid points.
The position vectors for G1, G2, and G3 are denoted by v1, v,2 and v3, respectively. If G1, G2,
and G3 are not specified, then the coordinate system is either specified by the vectors v1 = (X1,
Y1, Z1), v2 = (X2, Y2, Z2) and v3 = (X3, Y3, Z3) if X1 through Z3 are specified, or by the
vectors v1 = (0, 0, 0), v2 (1, 0, 0), and v3 = (0, 1, 0), by default. The local x-axis is the normalized
vector v2-v1. The local z-axis is the normalized cross product of the vectors v2-v1 and v3-v1 and
is thus perpendicular to the plane spanned by these vectors. The local y-axis is the cross product
of the local z- and x-axis.
2. The grid points G1, G2, and G3 must be unique. Also, the vectors (X1, X2, X3), (Y1, Y2, Y3),
and (Z1, Z2, Z3) must be unique.
3. The translational and rotational constraints are applied to the center of gravity of the rigid body
in the local coordinate system.
RBE2 507
Rigid-Body Element
Remarks
1. The element number should be unique with respect to all other rigid element numbers.
2. The RBE2 definition allows particular degrees of freedom of a set of grid points to be coupled so
that the grid points always move the same amount. The motion of the set of grid points is the
weighted average of the motion of all the grid points for the degrees of freedom coupled through
the RBE2 definition.
3. The component numbers refer to the basic coordinate system.
4. Loads, initial velocities, or constraints should be applied to the first (master) grid point. They are
then applied to the coupled degrees of freedom for all the grid points defined on the RBE2 entry.
5. Both rotational and translational degrees of freedom can be coupled.
6. Grid points associated with rigid surfaces cannot be part of an RBE2 grid point list.
7. Instead of defining coupled components, it is possible to define the RBE2entry as a single rigid
body by using the FULLRIG option. The geometric properties of the rigid body are calculated
from the geometry and the mass of the grid points.
8. Grid points referred to by the JOIN entry cannot be part of an RBE2 grid point list.
508 RBE2
Rigid-Body Element
9. It is possible to merge an RBE2entry with a MATRIG entry by using the FULLRIG option and
PARAMMATRMERG or PARAM,MATRMRG1. A normal RBE2 entry (with constraint) however
cannot be merged with a MATRIG entry or an RBE2-FULLRIG entry.
10. By using PARAM,CFULLRIG, all 123456 constraints on a normal RBE2 are automatically
converted to the FULLRIG option.
11. By using PARAM,RBE2INFO,GRIDON, the grid points of the RBE2are listed in the output file.
12. Lagrangian Elements for a description of the use of RBE2.
RBHINGE 509
Rigid Body Hinge
Defines a hinge between a rigid body and a deformable structure on the common six degrees of freedom.
+ G5 -etc.-
+ 2
Remarks
1. When grid points are part of a rigid body and a deformable structure, they transfer rotational
momentum if they posses six degrees of freedom. This is the case when they are connected to a
beam/bar, tria or quad shell element. Using the RBHINGE entry specifies rotational degrees of
freedom that can be defined as behaving as a hinge.
RBHINGE is not needed for grid points that have only three degrees of freedom, since the hinge
is defined by default.
2. The component number refers to the global coordinate system.
510 RCONN
Rigid Connection
Defines a rigid connection between the different parts of Lagrangian meshes (tied surfaces).
+ +
+ +
Remarks
1. The RCONN entry can be used to define three types of connection as described in Dytran Theory
Manual, Chapter 3: Constraints and Loading, Lagrangian Elements.
2. Two Surfaces Tied Together
Define slave and master segments representing the two surfaces to be tied together. There
should not be a gap between the two sets of segments. The two surfaces are tied together during
the analysis.
3. Grid Points Tied to a Surface
If STYPE is set to GRID and OPTION is set to NORMAL, the slave entities comprise discrete
grid points that are tied to the master surface during the analysis. The grid points must lie on
the surface.
4. Shell Edge Tied to a Shell Surface
If STYPE is set to GRID and OPTION is set to SHELL, the edges of shell or beams elements can
be tied to the faces of other shells. The grid points attached to the edge of the shells/beams must
be selected as the slave grid points. The shell surface to which they are tied must be selected as
the master surface. The two sets will then be tied together throughout the analysis. All degrees of
freedom will be coupled.
5. The CLSGAP entry enables you to define two different meshes that are not coincident over the
master/slave interface. If the option is set to YES, the slave surface becomes coincident (according
to projections) with the master surface.
512 RCONN
Rigid Connection
6. The search method of the contact algorithm is used to find the closest master face. The tolerance
defined with the GAPDIS/GAPDISV fields is similar to the monitoring distance defined on the
CONTACT entry with the MONDIS/MONDISV fields.
7. The use of the gap closing CLSGAP can cause an element to collapse. This may happen if the
GAPDISV tolerance is set to a value greater than the length of the side of an element.
8. When a solid and a shell mesh are tied together, the rotational degrees of freedom of the shell grid
points are not coupled.
9. If STYPE is set to GRID, the option FACTOR in the GAPDIS field is not allowed.
10. Avoid the following situation when using the RCONN entry:
Defines a connection between a rigid ellipsoid and Lagrangian grid points or rigid bodies.
Conte
Field nts Type Default
RID Unique number of an RCONREL entry I>0 Required
SIDC Number of a SETC entry giving the name of the rigid ellipsoid to I>0 Required
which entities are connected. See Remark.
TYPE The type of entities that are connected to the rigid ellipsoid. C Required
GRID Grid points.
RIGID Rigid surface, RBE2-FULLRIG, and MATRIG.
SID The number of a SET1 entry listing the grid points or rigid surfaces I>0 Required
that are connected to the rigid ellipsoid. In case a MATRIG or an
RBE2-FULLRIG entry is connected to the rigid ellipsoid, SID
refers to a SET1entry listing MR<id> or FR<id>, where id refers
to a MATRIGor an RBE2-FULLRIG entry, respectively.
Remark
The SETC entry can only contain the name of one ellipsoid.
514 RELEX
External Definition of a Rigid Ellipsoid
Defines a rigid ellipsoid whose properties and motion are defined by either ATB or MADYMO.
Content
Field s Type Default
NAME This name is used within the Dytran input file to define the C Required
interactions between the external ellipsoid and Dytran grid points
and rigid bodies. This name is also used in the output requests.
When coupled to ATB, the name must correspond to the name of the
ATB segment.
When coupled to MADYMO, the name doesn't need to correspond
to the name of the ellipsoid in the MADYMO input file.
PROG Name of the external program: C Required
MADYMO Dytran runs coupled with MADYMO V5.1.1
ATB Dytran runs coupled with ATB C Required
LABEL Identification label when running coupled to MADYMO. The label I Required
is not used by Dytran, it is only received from MADYMO to identify
the ellipsoid. The value must be equal to the value used in the
MADYMO input file:
Force models
Coupling
Ellipsoids
LABEL system ellipsoid var1...varN
End ellipsoids
End coupling
End force models
Remarks
1. This entry should only be used when Dytran is used with MADYMO or ATB.
2. Rigid ellipsoids can be defined directly within Dytran using the RELLIPS entry.
3. RELEX and RELLIPSentries can not be mixed in the same model. A mixture of MADYMO and
ATB ellipsoids is not allowed.
RELEX 515
External Definition of a Rigid Ellipsoid
4. For ATB, only the segment contact ellipsoid can be used. The name of the contact ellipsoid is
equal to the name of the segment, as specified on the first field of the B.2 entry in the ATB
input file.
5. See Dytran User’s Guide, Chapter 7: Interface to Other Applications, ATB Occupant Modeling
Program for instructions on how to use ATB.
516 RELLIPS
Rigid Ellipsoid
+ XL YL ZL XS YS ZS +
+ 0. 0. 1. 1. 0. 0. +
+ VX VY VZ WA WB WC
+ -0.1
Remark
RELEX and RELLIPS entries cannot be mixed in the same model.
RFORCE 517
Rotational Force Field
Remarks
1. The rotational velocity is calculated as
W t = T t * SCALE * N
where SCALE is the scale factor, N the directional vector (NX, NT, NZ), and T t the value at
time t interpolated from the table or function referenced by the TLOADn entry.
2. LID must be referenced by a TLOADn entry.
3. The type field on the TLOADn entry must be set to zero.
4. Only one centrifugal force field can be defined in the problem.
5. Centrifugal forces act on all Lagrangian structural elements and rigid surfaces.
6. The rotation is input in revolutions per unit time.
518 RIGID
Rigid Surface
+ VX VY VZ CID WX WY WZ +
+ +
Remarks
1. A CID of zero references the basic coordinate system.
2. The default for IXX, IYY, and IZZ is 1.E10; the default for IXY, IXZ, and IYZ is zero.
3. The mass of the rigid surface is distributed to the grid points on the surface.
RJCYL 519
Cylindrical-Joint Constraint Between Rigid Bodies
Remarks
1. The geometry of the joint changes during the analysis as the grid points move.
2. G1 and G3 are grid points belonging to the first rigid body; G2 and G4 are grid points belonging
to the second rigid body.
3. The vector from G1 to G3 determines the axis of sliding. Spring forces are calculated between G1
and G2 and between G3 and G4 to keep all four points on the axis of sliding.
4. If the initial position of grid points G2 and/or G4 is off the axis of sliding a force in the joint
is initialized.
5. The absolute stiffness of the rigid body joints is calculated automatically by Dytran. The stiffness
of the joints is taken such that a stable solution is guaranteed. This stiffness calculation takes into
account the fact that a rigid body can be constrained by more than one joint.
520 RJCYL
Cylindrical-Joint Constraint Between Rigid Bodies
6. The absolute stiffness of the rigid-body joints is multiplied by a factor defined on PARAM,
RJSTIFF. By default, RJSTIFF = 1.0. This parameter can be used to increase or decrease the
stiffness of the joints. Care must be taken by using this parameter because too high a value might
lead to an unstable calculation.
7. Although the joint is designed for usage with rigid bodies, it is allowed to use finite-element
grid points.
8. RJCYL can be applied to rigid bodies defined by the RIGID entry as well as to rigid bodies defined
by the MATRIG or RBE2-FULLRIG entries.
RJPLA 521
Planar-Joint Constraint Between Rigid Bodies
Remarks
1. The geometry of the joint changes during the analysis as the grid points move.
2. G1 and G3 are grid points belonging to the first rigid body; G2 and G4 are grid points belonging
to the second rigid body.
3. The vector from G1 to G3 defines the normal to the plane on which the two bodies can slide
relative to each other. G2 should lie on the plane through G1. Spring forces are calculated between
G1 and G2 and between G3 and G4 to keep all four points in the plane of sliding.
4. If the initial position of grid points G2 and/or G4 is off the normal to the plane of sliding, a force
in the joint is initialized.
5. The absolute stiffness of the rigid-body joints is calculated automatically by Dytran. The stiffness
of the joints is taken such that a stable solution is guaranteed. This stiffness calculation takes into
account the fact that a rigid body can be constrained by more than one joint.
522 RJPLA
Planar-Joint Constraint Between Rigid Bodies
6. The absolute stiffness of the rigid-body joints is multiplied by a factor defined on PARAM,
RJSTIFF. By default, RJSTIFF = 1.0. This parameter can be used to increase or decrease the
stiffness of the joints. Care must be taken by using this parameter because too high a value might
lead to an unstable calculation.
7. Although the joint is designed for usage with rigid bodies, it is allowable to use finite-element
grid points.
8. RJPLA can be applied to rigid bodies defined by the RIGID entry as well as to rigid bodies defined
by the MATRIG or RBE2FULLRIG entries.
RJREV 523
Revolute-Joint Constraint Between Rigid Bodies
Defines a revolute joint (hinge) between grid points on two rigid bodies.
Remarks
1. The geometry of the joint changes during the analysis as the grid points move.
2. G1 and G3 are grid points belonging to the first rigid body; G2 and G4 are grid points belonging
to the second rigid body. G1 and G2 should be coincident, and G3 and G4 should be coincident.
3. The vector from G1 to G3 determines the axis about which the two bodies can rotate. Spring
forces are calculated between G1 and G2 and between G3 and G4 to keep all four points on the
axis of rotation.
4. The absolute stiffness of the rigid-body joints is calculated automatically by Dytran. The stiffness
of the joints is calculated so that a stable solution is guaranteed. This stiffness calculation takes
into account the fact that a rigid body can be constrained by more than one joint.
524 RJREV
Revolute-Joint Constraint Between Rigid Bodies
5. The absolute stiffness of the rigid-body joints is multiplied by a factor defined on PARAM,
RJSTIFF. By default, RJSTIFF = 1.0. This parameter can be used to increase or decrease the
stiffness of the joints. Care must be taken by using this parameter because too high a value might
lead to an unstable calculation.
6. Although the joint is designed for usage with rigid bodies, it is allowed to use finite-element
grid points.
7. RJREV can be applied to rigid bodies defined by the RIGID entry as well as to rigid bodies defined
by the MATRIG or RBE2-FULLRIG entries.
RJSPH 525
Spherical-Joint Constraint Between Rigid Bodies
Defines a spherical (ball) joint between grid points on two rigid bodies.
Remarks
1. The geometry of the joint changes during the analysis as the grid points move.
2. G1 belongs to the first rigid body, G2 belongs to the second rigid body. G1 and G2 should be
coincident. Spring forces are calculated between G1 and G2 so that the two bodies can rotate
about the joint.
3. The absolute stiffness of the rigid-body joints is calculated automatically by Dytran. The stiffness
of the joints is taken such that a stable solution is guaranteed. This stiffness calculation takes into
account the fact that a rigid body can be constrained by more than one joint.
4. The absolute stiffness of the rigid-body joints is multiplied by a factor defined on PARAM,
RJSTIFF. By default, RJSTIFF = 1.0. This parameter can be used to increase or decrease the
stiffness of the joints. Care must be taken by using this parameter because too high a value might
lead to an unstable calculation.
526 RJSPH
Spherical-Joint Constraint Between Rigid Bodies
5. Although the joint is designed for usage with rigid bodies, it is allowable to use finite-element
grid points.
6. RJSPH can be applied to rigid bodies defined by the RIGID entry as well as to rigid bodies defined
by theMATRIG or RBE2-FULLRIG entries.
RJTRA 527
Translational-Joint Constraint Between Rigid Bodies
Defines a translational joint, which allows relative sliding but no rotation, between grid points on two
rigid bodies.
Remarks
1. The geometry of the joint changes during the analysis as the grid points move.
2. G1, G3, and G5 are grid points belonging to the first rigid body; G2, G4, and G6 are points
belonging to the second rigid body.
3. The vector from G1 to G3 determines the axis along which the two bodies can slide relative to
each other. The vectors from G1 to G5 and from G2 to G6 are perpendicular to the axis of sliding.
Spring forces are calculated between G1 and G2, between G3 and G4, and between G5 and G6 to
keep the first four grid points on the axis of sliding and the other two grid points on a vector that
is parallel to the axis of sliding.
4. If the initial position of grid points G2 and/or G4 is off the axis of sliding a force in the joint is
initialized. If the initial vector from G5 to G6 is not parallel to the vector from G1 to G3, a force
in the joint is initialized.
528 RJTRA
Translational-Joint Constraint Between Rigid Bodies
5. The absolute stiffness of the rigid-body joints is calculated automatically by Dytran. The stiffness
of the joints is calculated so that a stable solution is guaranteed. This stiffness calculation takes
into account the fact that a rigid body can be constrained by more than one joint.
6. The absolute stiffness of the rigid body joints is multiplied by a factor defined on PARAM,
RJSTIFF. By default, RJSTIFF = 1.0. This parameter can be used to increase or decrease the
stiffness of the joints. Care must be taken by using this parameter because too high a value might
lead to an unstable calculation.
7. The grid points used in the definition of the joint do not have to be rigid-body joints, but may also
be finite-element grid points.
8. RJTRA can be applied to rigid bodies defined by the RIGID entry as well as to rigid bodies defined
by the MATRIGor RBE2-FULLRIG entries.
RJUNI 529
Universal-Joint Constraint Between Rigid Bodies
Remarks
1. The geometry of the joint changes during the analysis as the grid points move.
2. G1 and G3 are grid points belonging to the first rigid body; G2 and G4 are grid points belonging
to the second rigid body. G1 and G2 should be coincident, while G3 and G4 cannot be coincident.
3. G3 and G4 define the orientation of the rotation of the joint, as shown in the figure above. Spring
forces are calculated between G1 and G2 as in the spherical joint and between G3 and G4, based
on the Pythagorean theorem.
4. The absolute stiffness of the rigid-body joints is calculated automatically by Dytran. The stiffness
of the joints is taken such that a stable solution is guaranteed. This stiffness calculation takes into
account the fact that a rigid body can be constrained by more than one joint.
5. The absolute stiffness of the rigid body joints is multiplied by a factor defined on PARAM,
RJSTIFF. By default, RJSTIFF = 1.0. This parameter can be used to increase or decrease the
stiffness of the joints. Care must be taken by using this parameter because too high a value might
lead to an unstable calculation.
530 RJUNI
Universal-Joint Constraint Between Rigid Bodies
6. Although the joint is designed for usage with rigid bodies, it is allowable to use finite-element
grid points.
7. RJUNI can be applied to rigid bodies defined by the RIGIDentry as well as to rigid bodies defined
by the MATRIG or RBE2-FULLRIG entries.
RPLEX 531
External Definition of a Rigid Plane
Defines a rigid plane whose properties and motion are defined by MADYMO.
FORCE MODELS
COUPLING
PLANES
LABEL system ellipsoid var1...varN
END PLANES
END COUPLING
END FORCE MODELS
Remarks
1. This entry should only be used when Dytran is used with MADYMO.
2. All planes attached to an ellipsoid in ATB are automatically visualized when the ellipsoid is asked
for in an output request.
3. The mesh density of the plane can be changed by using PARAM,MESHPLN,x, where x is the
mesh density. See also PARAM,MESHPLN.
4. Rigid ellipsoids can be defined directly within Dytran using the RELLIPS entry.
5. RELEX and RELLIPS entries can not be mixed in the same model. A mixture of MADYMO and
ATB ellipsoids is not allowed.
532 RPLEX
External Definition of a Rigid Plane
6. For ATB, only the segment contact ellipsoid can be used. The name of the contact ellipsoid is
equal to the name of the segment, as specified on the first field of the B.2 entry in the ATB
input file.
7. See Dytran User’s Guide, Chapter 7: Interface to Other Applications, ATB Occupant Modeling
Program for instructions on how to use ATB.
RUBBER1 533
Mooney-Rivlin Rubber Material
Cont
Field ents Type Default
MID Unique material number I>0 Required
RHO Density R > 0.0 Required
A Strain-energy density function constant R Required
B Strain-energy density function constant R Required
NU Poisson’s ratio 0.0 R < 0.5 Required
BULKTYP Bulk-viscosity model C DYNA
DYNA Standard DYNA3D model
BULKQ Quadratic bulk-viscosity coefficient R 0.0 1.0
BULKL Linear bulk-viscosity coefficient R 0.0 0.0
Remarks
1. The continuation line with the bulk-viscosity data can be omitted.
2. The constitutive behavior of this material is defined as a total stress/total strain relationship. The
nonlinear elastic material response is formulated by a strain-energy density function for large-
strain components rather than by Hooke’s law.
The strain-energy density function is formulated according to the Mooney-Rivlin model and is
defined as
1 2
W I 1 ,I 2 ,I 3 = A I 1 – 3 + B I 2 – 3 + C ---2- – 1 + D I 3 – 1
I3
Remarks
1. The cross sections for which output is required are referenced in a SET command in Case Control
Section. The SET entry is referenced by the CSECS Case Control command.
2. The cross section is defined as a consecutive sequence of elements extending across the model.
In addition, a consecutive sequence of grid points attached to one side of the elements must be
defined. The GID field is required together with EID, the list of elements.
3. For compatibility with Dyna, the method of specifying three EIDs (i.e. one for one-dimensional
elements, one for plate elements and one for hexahedral elements) is retained.
4. Cross sections cannot be defined for Eulerian models.
536 SET1
Set of Numbers
Defines a set of grid points, elements, etc., for use by other entries (e.g., WALL, SURFACE).
Remarks
1. Use as many continuation lines as necessary.
2. If the THRU specification is used, all the items in the sequence between the beginning and the end
of the range do not have to exist. Items that do not exist are ignored. BY can be used as an
increment to exclude grid points.
3. SET1 Bulk Data entries with the same number are merged into one set.
SETC 537
List of Names
Remarks
1. Use as many continuations as required to define the complete list of names. A blank field
terminates the list.
2. The SETC entry may be referred to from outside the Bulk Data Section.
538 SETTING
Application-Sensitive Defaults
Defines application-sensitive defaults for element formulation, element options, hourglass control and
material behavior.
Remarks
1. The application-sensitive defaults are set according to the specification in the TYPE field. If
no application type is specified, the setting is STANDARD. The default settings concern the
element formulation, element formulation options, hourglass control, material-plasticity
calculation method, and strain dependency of the thickness of shell elements. See Dytran
User’s Guide, Chapter 5: Application Sensitive Default Setting for more details on
application-sensitive defaults.
SETTING 539
Application-Sensitive Defaults
2. If no property type and property number are supplied, the setting is done for all properties in the
model. If the property type and the property number are defined, the setting applies to the
elements that have the specified property. As such it is possible to define a global application
setting and have a different setting for certain properties in the model.
3. See Dytran User’s Guide, Chapter 5: Application Sensitive Default Setting for more details on
application-sensitive defaults.
540 SHEETMAT
Sheet-Metal Material
Defines the properties of an anisotropic plastic material for Lagrangian shell elements.
+ a b c n k m +
+ 0.0 570E3 0.017 0.359 0.014 0.389 +
+ TYPEHRD +
+ ISO +
+ C1 C2 C3 C4 C5 +
+ 0.244 -0.195 0.857 3.439 -11.92 +
+ D2 D3 D4 D5
+ -0.417 -1.567 -4.849 -6.061
See Remark 3.
ISO ISOtropic material
PLANISO PLANar ISOtropic material
XMAT, Vector indicating the rolling direction of the material R (0., 0., 0.)
YMAT,
ZMAT See Remark 4.
a Power-law stress constant R 0.0 Required
See Remark 5.
b Power-law hardening parameter R 0.0 0.0
c Power-law strain offset R 0.0 0.0
n Power-law, strain-hardening exponent R 0.0 1.0
k Power-law, strain-rate sensitivity constant R 0.0 0.0
See Remark 6.
m Power-law, strain-rate exponent R 0.0 1.0
TYPEYLD Type of yielding criterion. C ISO
See Remark 7.
ISO ISOtropic yielding (von Mises)
NORMANI NORMal ANIsotropic yielding
PLANANI PLANar ANIsotropic yielding
R0, Anisotropic yielding parameters (Lankford parameters) R > 0.0 See Remark 8.
R45, defined in 0, 45, and 90 degrees with respect to the rolling
R90 direction
TYPEHRD Type of hardening rule. C ISO
ISO ISOtropic hardening
NORMANI NORMal ANIsotropic hardening
C1-C5 Engineering coefficients in limit function for e2 > 0. R C1 = 1.0
See Remark 9.
D2-D5 Engineering coefficients in limit function for e2 < 0. R 0.0
See Remark 9.
542 SHEETMAT
Sheet-Metal Material
Remarks
1. SHEETMAT materials may only be referenced by PSHELL and PSHELL1 entries.
2. The necessary number or combination of elasticity constants depends on the field ELASTIC. If
ELASTIC = ISO then only EXX and NUXY (or GXY) must be defined. For ELASTIC = PLANISO,
only EXX (or EYY), EZZ, NUXY (or GXY), NUXZ (or NUYZ), and GXZ (or GYZ) must be defined.
3. The field ELASTIC provides you with an input check on the consistency of the elasticity
constants. Planar isotropic material is equivalent to transversely isotropic material, which means
that the through-the-thickness (elastic) properties may differ from the in-plane isotropic
(elastic) properties.
4. Due to anisotropic behavior, the rolling direction must be specified. The projection of the vector
(XMAT, YMAT, ZMAT) on the surface of each element is used to determine the angle between the
element and the material coordinate system. This angle can be overwritten using the THETA field
on the CQUAD4 and CTRIA3 entries. Both the constitutive law and the output of variables are
applied with respect to this material coordinate system (see Remark 10.).
5. For a description of the anisotropic-plastic model including the power-law yield function, see
Dytran Theory Manual, Chapter 3: Materials. The power-law stress constant, a, is not necessarily
the initial yield stress: the value of a is allowed to be equal to zero if the value of the hardening
parameter, b, and the strain offset, c, are unequal to zero.
6. Strain-rate dependence is not accounted for by default.
7. The field TYPEYLD provides you with an input check on the consistency of the anisotropic
parameters. Normal anisotropic material is equivalent to transversely anisotropic or planar
isotropic material which means that the through-the-thickness yielding properties may differ from
the in-plane, isotropic, yielding properties. Planar anisotropic material is characterized by three
orthogonal axes of anisotropy (in rolling, transverse and through-the-thickness direction), about
which the yielding properties have twofold symmetry.
8. The necessary number of anisotropic-yielding parameters depends on the field TYPEYLD. For
TYPEYLD = ISO, all fields for R0, R45, and R90 can be left blank because the default
corresponds to von Mises yielding (R0 = R45 = R90 = 1.0). For TYPEYLD = NORMANI, only
R0 must be defined while the other two fields can be left blank due to their equality. The input of
all three anisotropic parameters is needed for TYPEYLD = PLANANI.
9. C1 through C5 and D2 through D5 do not affect the material behavior but are used to fit the lower
bound of experimental results for diffuse and localized necking represented by two
polynomial lines:
FLD e2 = C1 + C2e2 + C3e22 + C4e23 + C5e24 for e2 0
FLD e2 = C1 + D2e2 + D3e22 + D4e23 + D5e24 for e2 0
10. The output of variables related to SHEETMAT is defined with respect to the material coordinate
system (see Remark 4.). There are a number of specific output variables useful for this material:
Element Variables
Q1, Q2 Direction cosines/sines between the element coordinate system and the
material coordinate system
SHEETMAT 543
Sheet-Metal Material
Sublayer Variables
TXX Stress - XX component
TYY Stress - YY component
TXY Stress - XY component
TYZ Stress - YZ component
TZX Stress - ZX component
EFFST Effective Stress
EFFPL Effective Plastic Strain
YLDRAD Radius of Yield Surface
EPSXX Strain - XX component
EPSYY Strain - YY component
EPSXY Strain - XY component
EPSZZ Strain - ZZ component
EPZZ Plastic Strain – ZZ component
EPSMX Strain - Major Principal Strain
EPSMN Strain - Minor Principal Strain
FLP Forming-Limit Parameter
544 SHREL
Elastic Shear Model
Remark
Shear model numbers must be unique.
SHREX 545
User-specified Shear Model
Specifies that a user subroutine is being used to define the shear modulus.
Remarks
1. The subroutine must be present in the file referenced by the USERCODE FMS statement.
2. See Chapter 7: User Subroutines for a description of how to use user-written subroutines.
3. This shear model is applicable only for Lagrangian solid elements and Eulerian elements with
shear strength.
546 SHRLVE
Isotropic Linear Viscoelastic Shear Model
Defines an isotropic linear viscoelastic shear model where the mechanical analog is a spring, a dashpot,
and a Maxwell element connected in parallel.
Remarks
1. Shear model numbers must be unique.
2. The spring-damper analog of this model is
SHRLVE 547
Isotropic Linear Viscoelastic Shear Model
The above equation for the deviatoric stress is the integral form of the differential equation
· ·· ·
' ij + ' ij = 2 0 + 2 0 + 2G 0 + 2G
A special case is 0 = G = 0 , for which is often written
·
· · ' ij
= elastic + viscous = ---------- + ---------- ' ij
2G 0 2G 0
This shear model is further described in Dytran Theory Manual, Chapter 4: Models, Shear
Models.
4. A yield model cannot be used in combination with this shear model.
5. The element formulation for this material is in a corotational frame. The default CORDROT
definition is G1 = 1, G2 = 5, G3 = 2. (See also DMATand CORDROT entries.)
548 SHRPOL
Polynomial Shear Model
Remarks
1. Shear model numbers must be unique.
2. The shear modulus is computed from
G = G0 + G 1 + G2 2 + G3 3
where = effective plastic shear strain
and G 0 , G 1 , G 2 , and G 3 are constants
SPC 549
Single-Point Constraint
Remarks
1. SPC degrees of freedom may also be specified as permanent constraints on the GRID entry.
2. Continuation lines are not allowed.
3. Select single-point constraints in the Case Control Section (SPC = SID) to be used by Dytran.
4. A single-point constraint is treated as a zero-velocity boundary condition. For this reason, make
SPCs consistent with other velocity boundary conditions and velocity initial conditions.
550 SPC1
Single-Point Constraint
Remarks
1. As many continuation lines as desired may appear.
2. SPC degrees of freedom may be redundantly specified as permanent constraints on the
GRIDentry.
3. If the THRU specification is used, grid points in the sequence between the beginning and the end
of the range are not required. Grid points that do not exist are ignored. BY can be used to exclude
grid points within this range.
4. Single-point constraints must be selected in the Case Control Section (SPC = SID) if they are to
be used by Dytran.
5. None of the fields in the list of grid points can be blank or zero, since this marks the end of the list.
6. A single-point constraint is treated as a zero-velocity boundary condition. For this reason, make
SPCs consistent with other velocity boundary conditions and velocity initial conditions.
SPC2 551
Single-Point Constraint
+ TYPE2 VALUE2 +
+ CONSTANT 0. +
+ G1 G2 THRU G3 BY G5 -etc-
+ 10 13 THRU 56 BY 4
Remarks
1. The angular velocity is specified in radians per unit time.
2. The SPC2 entry is valid for both Lagrangian as Eulerian grid points.
3. If the TYPE2 field is set to FREE, the referenced grid points move in a radial direction according
to the acceleration caused by forces in the radial direction.
4. You can use as many continuation lines as required.
5. If the THRU specification is used, grid points in the sequence between the beginning and the end
of the range are not required to exist. Grid points that do not exist are ignored.
6. Select the rotational constraints in the Case Control Section (SPC = SID) if they are to be used
by Dytran.
7. None of the fields in the list of grid points can be blank or zero, since this marks the end of the list.
8. Both Lagrangian and Eulerian grid points can have a rotational constraint. In the case of Eulerian
grid points, this results in a moving Eulerian mesh.
9. For six degree of freedom grid points, the angular velocities are also constrained consistent with
the defined velocity field.
10. The velocity in axial direction is constrained to zero.
SPC3 553
Single-Point Constraint
+ G1 G2 THRU G3 BY G4 -etc.-
+ 5 6 THRU 18 BY 3
Remarks
1. CID1 references the primary system. In this system the grid point constraints are applied. The
CID2 system defines a secondary system that constrains the motion of the primary system and
the grid points defined on the entry.
2. The SPC3 entry is valid for both Lagrangian as Eulerian grid points.
3. As many continuation lines as desired may appear.
4. If the THRU specification is used, grid points in the sequence between the beginning and the end
of the range are not required. Grid points that do not exist are ignored. (See Remark 3. of SPC1.)
5. Select the single-point constraint in the Case Control Section (SPC = SID) if it is to be used
by Dytran.
6. None of the fields in the list of grid points can be blank or zero, since this marks the end of the list.
7. If CID1 or CID2 is blank, the basic system is used. If C1 is blank, no constraints are applied in
the primary system. If C2 is blank, no constraints are applied in the primary system with respect
to the secondary system.
554 SPC3
Single-Point Constraint
8. If CID1, CID2, and C2 are left blank, the constraint acts as defined by an SPC1 entry.
9. If a component references an angular velocity, the units are radians per unit time.
10. A single-point constraint is treated as a zero velocity boundary condition. For this reason, make
SPCs consistent with other velocity boundary conditions and velocity initial conditions.
11. CID2 = 0 is not allowed. Instead define a new local coordinate system at (0., 0., 0.) and refer to
this coordinate system on CID2.
SPHERE 555
Defines the Shape of a Sphere
Spherical shape used in the initial condition definition on the TICEUL entry.
Remarks
1. You can use as many continuation lines as necessary to define all of the segments in the surface.
2. CSEGs are defined indirectly using CQUAD4 and/or CTRIA3elements with a 9999. thickness.
CFACE1 are entries defined indirectly using PLOAD4 entries with a 9999. pressure. This allows
CSEG and CFACE1 entries to be easily defined using standard preprocessors that can generate
CQUAD4, CTRIA3 and PLOAD4 entries.
3. The subsurface SSID can be referenced from the following entries:
SURFACE To define a surface that has the same segments as this subsurface.
CONTINI To define the initial contact between Lagrangian surfaces. The surface SID must
then be used in a CONTACT entry.
COUPOR To define the porosity of a coupling surface. The surface SID must then be used
in a COUPLE entry.
COUOPT To define the options used in a coupling surface. The surface SID must then be
used in a COUPLE entry.
558 SURFACE
Multifaceted Surface
Defines a multifaceted surface for contact and coupling interfaces as well as rigid-surface geometry.
Remarks
1. You can use as many continuation lines as necessary to define all of the segments in the surface.
2. CSEGs are defined indirectly using CQUAD4 and/or CTRIA3elements with a 9999. thickness.
CFACE1are entries defined indirectly using PLOAD4entries with a 9999. pressure. This allows
CSEG and CFACE1 entries to be easily defined using standard preprocessors that can generate
CQUAD4 CTRIA3, and PLOAD4 entries.
560 TABFILE
Text File Defined Function
Remark
The text file has to consist of a number of data lines and may include comment lines. Each comment line
has to start with $. Every data line has to consist of two numbers. These will be interpreted as XVALUE
and the YVALUE of a TABLED1. Examples 3.4 and 3.5 illustrate the use. The table can be checked in the
Out file. Blank lines are not supported. The first line of a file can start with XYDATA. It will be ignored.
Example
TABFILE,200,rho.xyd
Contents rho.xyd:
$ density as function of radius
0.00125 0.50041467
0.0037499995 0.52369827
0.0062499996 0.52935588
TABLED1 561
Table
TABLED1 Table
+ X1 Y1 X2 Y2 X3 Y3 X4 Y4 +
+ -3.0 6.9 2.0 5.6 3.0 5.6 XSMALL ENDVAL +
+ X5 Y5 X6 Y6 X7 Y7 X8
+ XLARGE EXTRAP XOFFSET .05 YOFFSET .04 ENDT
Remarks
1. The values of Xi must be in ascending or descending order but not both.
2. At least two entries must be present.
3. The end of the table is marked by the characters ENDT in the field following the last table entry
or by a blank field.
4. The table is used according to
y = fx
where x is input to the table and y is output. Linear interpolation is used within the table to
determine y . Outside the table, the last entry for y is taken.
5. Instead of a numerical value for a y entry, the keyword FREE can be entered. The value of FREE
in the table can be used together with constraints and loading to switch these on and off. FREE
means that the constraint or loading is not active during the time interval for which the FREE entry
is defined.
562 TABLED1
Table
Xi Yi Meaning
XSMALL ENDAVL or If x if outside the table from the smallest value, the first entry for y
is taken.
EXTRAP If x is outside the table from the smallest value, y is extrapolated.
XLARGE ENDAVL or If x is outside the table from the largest value, the last entry for y
is taken.
EXTRAP If x is outside the table from the largest value, y is extrapolated.
XOFFSET value x-axis of table is offset by the specified value.
YOFFSET value y-axis of table is offset by the specified value.
XSCALE value x-axis of table is multiplied by the specified value.
YSCALE value y-axis of table is multiplied by the specified value.
TABLEEX 563
User-defined Function
Remarks
1. The EXFUNC user subroutine must be present in the file referenced by the USERCODE
FMS statement.
2. See Chapter 7: User Subroutines in this manual for a description of how to use
user-written subroutines.
3. Since tables and user-defined functions belong to the same group, the table numbers must
be unique.
564 TIC
Transient Initial Velocities of Grid Points
Defines the initial velocities of Lagrangian grid points at the beginning of the analysis.
Remarks
1. Initial conditions for grid points that are not specified on TICn or TICGP entries are assumed to
be zero.
2. Initial conditions to be used by Dytran must be selected in the Case Control Section (TIC = SID).
3. Only Lagrangian grid points can have initial conditions specified by the TIC Bulk Data entry.
4. Only one TIC entry per grid point is allowed. When more than one velocity component needs to
be initialized, TICGP offers a more general way of initializing grid-point velocities.
TIC1 565
Transient Initial Velocities of Grid Points
Defines the initial velocities of Lagrangian grid points at the beginning of the analysis.
+ G5 G6 THRU G7 BY G8 -etc.-
+ 2 8 THRU 17 BY 3
Remarks
1. Initial conditions for grid points that are not specified on TICn or TICGP entries are assumed to
be zero.
2. Only one TIC1 entry per grid point is allowed. When more than one velocity component needs
to be initialized, TICGP offers a more general way of initializing grid-point velocities.
3. If the THRU specification is used, all grid points in the sequence between the beginning and
the end of the range do not have to exist. Grid points that do not exist are ignored. The first grid
point in the THRU specification must be a valid grid point. BY enables grid points to be ignored
in this range.
4. None of the fields in the list of grid points can be blank or zero since this marks the end of the list.
The initial conditions to be used by Dytran must be selected in the Case Control Section
(TIC = SID).
5. Only Lagrangian grid points can have initial conditions specified by the TIC1 Bulk Data entry.
566 TIC2
Transient Initial Velocities of Grid Points
Defines the initial velocities of grid points consistent with a rotational field.
+ G1 G2 THRU G3 BY G4 -etc.-
+ 1 2 THRU 10000 BY 23
Remarks
1. The rotational velocity w is calculated as:
w = SCALE * N
where SCALE is the scale factor and N is the vector defined by NX, NY, NZ.
2. Any number of TIC2 entries can be used.
3. The rotational velocity is defined in radians per unit time.
4. For six degree of freedom grid points, the angular velocities are also initialized.
5. Initial conditions for grid points that are not specified on TIC or TICGP entries are assumed to be
zero.
6. If the THRU specification is used, all grid points in the sequence between the beginning and
the end of the range do not have to exist. Grid points that do not exist are ignored. The first grid
point in the THRU specification must be a valid grid point. BY enables grid points to be ignored
in this range.
7. None of the fields in the list of grid points can be blank or zero, since this marks the end of the list.
8. The initial conditions to be used by Dytran must be selected in the Case Control Section
(TIC = SID).
TIC3 567
General Form of Transient Initial Velocities of Grid Points
Allows for the definition of a velocity field of grid points consisting of a rotation and a
translation specification.
+ G1 G2 THRU G3 BY G4 -etc.-
+ 1 2 THRU 1000 BY 23
Remarks
1. Any number of TIC3 entries can be used.
2. The rotational velocity components are defined in radians per unit time.
3. For six degree of freedom grid points, the angular velocity components are also initialized.
4. Initial conditions for grid points that are not specified on TIC or TICGP entries are assumed to
be zero.
568 TIC3
General Form of Transient Initial Velocities of Grid Points
5. If the THRU specification is used, the grid points in the range definition are not required to exist.
Grid points that do not exist are ignored. The first grid point in the THRU specification must be a
valid grid point. The BY option enables grid points to be ignored in this range.None of the fields
in the list of grid points can be blank or zero, since this indicates the end of the list.
6. The initial conditions to be used by Dytran must be selected in the Case Control Section
(TIC = SID).
TICEEX 569
User-defined Transient Initial Conditions of Elements
Defines the initial values of element variables at the beginning of the analysis by a user-
written subroutine.
Remarks
1. The EXINIT user subroutine must be present and referenced in the input file by the USERCODE
FMS statement.
2. See Chapter 7: User Subroutines in this manual for a description of how to use
user-written subroutines.
3. Initial conditions to be used by Dytran must be selected in the Case Control Section
(TIC = SID).
570 TICEL
Transient Initial Conditions of Elements
Defines the initial values of element variables at the beginning of the analysis.
Remarks
1. Initial conditions for elements that are not specified on TICEL entries are assumed to be zero
except density, which is set to the reference density.
2. Initial conditions to be used by Dytran must be selected in the Case Control Section
(TIC = SID).
3. As many continuation lines as required can be used to specify all the variables being initialized.
A blank field terminates the list.
4. Element variables for Eulerian elements can be initialized with a TICEL or a TICEULentry. The
TICEL entry initializes a set of elements, while theTICEUL entry initializes either a set of
elements or geometrical regions (sphere, cylinder,...). When a Euler element is part of both a
TICEL and a TICEUL entry, the TICEL entry takes precedence, and overrules the TICEUL
initialization for the element.
TICEUL 571
Transient Initial Conditions of Eulerian Regions
Defines the initial value sets for Eulerian regions. The Eulerian regions are defined by geometric shapes.
Remarks
1. When the material number is left blank or zero, the Eulerian elements inside the region will
be void.
2. All level indicators LEVELi must have different values. The level indicator can be negative.
3. See also the MICRO parameter for the accuracy of the initial value generation.
4. See Dytran User’s Guide, Chapter 3: Constraints and Loading, Eulerian Loading and Constraints
for instructions on how to use the geometric shapes on the TICEUL entry for arbitrary initial value
generation in Eulerian regions.
5. Element variables for Eulerian elements can be initialized with a TICELor a TICEUL entry. The
TICEL entry initializes a set of elements, while the TICEUL entry initializes either a set of
elements or geometrical regions (sphere, cylinder, box, ...). When an Euler element is part of both
a TICEL and a TICEUL entry, theTICEL entry takes precedence and overrules the TICEUL
initialization for the element.
6. For the Euler solvers, you can, in addition to the “normal” element variables that the solver has
defined, also define an initial radial velocity field. You have to enter the location of the center
from where the radial emerges, the velocity to be applied to the element center and the decay
coefficient for the velocity field. The center is defined by the keywords X-CENTER, Y-CENTER,
Z-CENTER, the radial velocity by R-VEL and the decay coefficient by DECAY. You have to input
these keywords in the above order, and have every keyword followed by its value. For more
information, please refer to the Dytran User’s Guide, Chapter 3: Constraints and Loading,
Eulerian Loading and Constraints and the TICVAL or TICEL information in this manual.
TICGEX 573
User-defined Transient Initial Conditions of Grid Points
Defines the initial values of grid-point variables at the beginning of the analysis by a user-written
subroutine.
Remarks
1. The EXINIT user subroutine must be present in the input file, and it must be referenced by the
USERCODE FMS statement.
2. See Chapter 7: User Subroutines in this manual for a description of how to use
user-written subroutines.
3. Initial conditions must be selected in the Case Control Section (TIC = SID) to be used
by Dytran.
574 TICGP
Transient Initial Conditions for Grid Points
Defines the initial conditions of grid points at the beginning of the analysis.
Remarks
1. Initial conditions for grid-point components that are not specified on TIC or TIGGP entries are
assumed to be zero.
2. Select initial conditions to be used by Dytran in the Case Control Section (TIC = SID).
3. Use as many continuation lines as required to specify all the variables being initialized. A blank
field terminates the list.
4. The NAMEi on the TICGP entry can also be CID1 or CID2. In that case, VALUEi denotes the
number of a defined coordinate system. Velocities are initialized according to the type of defined
coordinate system. If coordinate systems are used, the velocity components must follow the CID
definition immediately. All other variables must be defined before the first CID definition. Only
for Lagrangian grid points the velocity can be defined in a local coordinate system.
For example:
TICGP, 1, 1,PMASS,10.,CID1,1,YVEL,10.
5. All velocity components defined and preceding a coordinate system reference are overruled by
the definition following the coordinate system reference.
TICVAL 575
Transient Initial Condition Set
Remarks
1. Initial conditions for geometric regions that are not specified on TICVAL entries are assumed to
be zero except density, which is set to the reference density.
2. For the Euler solvers, one can, in addition to the “normal” element variables that the solver has
defined, also define an initial radial velocity field. You have to enter the location of the center
from where the radial emerges, the velocity to be applied to the element center, and the decay
coefficient. The center is defined by the keywords X-CENTER, Y-CENTER, Z-CENTER, the
radial velocity by R-VEL and the decay coefficient by DECAY. You have to input these keywords
in the above order, and have every keyword followed by its value. For more information, please
refer to the Dytran User’s Guide, Chapter 3: Constraints and Loading, Eulerian Loading and
Constraints. Note that the dimension of RVEL changes with the value of DECAY. For example
when DECAY equals 2, the dimension of RVEL is 1/length2.
3. Note that the initialization of geometric regions is based on the fraction of the element that lies
within the region. When, for example, an element is only partly covered by the geometric region,
the initialization will be done according to the mass that lies within the defined region.
4. As many continuation lines as required can be used to specify all the variables to be initialized. A
blank field terminates the list.
576 TICVAL
Transient Initial Condition Set
5. TYPE = RADIAL allows to map results of a spherical symmetric 1-D solution onto a full 3-D
model. For each initialized variable, a 1-D table has to be defined that specifies the variable value
for a number of distances from the center. The center is by default (0,0,0) but can be changed by
setting X-CENTER, Y-CENTER, Z-CENTER. The velocity is a radial velocity and has to be
specified as R-VEL. Its value is a TABLE ID.
6. PARAM SPHERSYM can be used to define a proper 1-D spherical mesh and speeds up the run by
taking only the mesh-size in radial direction into account. With Patran, radial profiles can be
created and written out to .xyd files. These files can be used to define tables by the TABFILE
entry. For details refer to Examples 3.4 and 3.5.
7. Radial initialization of JWL is supported. The entries DESTPH and the JWL entry from the 1-D
spherical solution stage have to be included in the remap run. Alternatively, the 1-D solution may
be run with JWL and the follow-up run with ideal gas, provided that all JWL material has fully
ignited. Radial initialization of EOSIG is not supported. In the follow-up run, ideal gas material
has to be used instead of IG material.
TLOAD1 577
Transient Dynamic Load
Remarks
1. See the FORCEn, MOMENTn, DAREA, PLOADn, GRAV, RFORCE,ATBACC FLOW, FORCEEX,
and FLOWEX, entries for a description of how the loading or motion is calculated.
2. There can be one or more TLOAD1 entries in a set.
3. Transient loads to be used by Dytran must be selected in the Case Control Section
(TLOAD = SID).
4. TID must be blank if it references a FLOW or FLOWEX entry.
578 TLOAD1
Transient Dynamic Load
5. If TYPE is 0, the LID field can reference any of the entries: FORCEn, MOMENTn, GRAV,
RFORCE, DAREA, or PLOADn and apply the appropriate type of load.
If TYPE is 2, the LID field can only reference DAREA, FORCE, MOMENT, FORCE3, or
FORCEEX entries and applies enforced velocity to the specified grid points.
If TYPE is 4, the LID field can only reference FLOW or FLOWEX entries and applies a flow
boundary condition to the specified Eulerian faces.
If TYPE is 12, the LID field can only reference the DAREA, FORCE, or MOMENT entries and
applies an enforced velocity to the center of the specified rigid body.
If TYPE is 13, the LID field can only reference the FORCE or MOMENT entries and applies a
force or moment to the center of the specified rigid body.
6. If more than one velocity boundary condition (TYPE = 2) is applied to a grid point, the boundary
conditions can only be merged when the boundary conditions are consistently defined.
TLOAD2 579
Transient Dynamic Load, Form 2
P
Y t = At B e ct cos 2Ft + --------- for 0 t T 2 – T 1
180
+ C B
+ .0 2.
Remarks
1. See the FORCEn, MOMENTn, DAREA, PLOADn, GRAV, RFORCE, ATBACC, FLOW, FORCEEX,
and FLOWEX entries for a description of how the loading or motion is calculated.
2. There can be one or more TLOAD1 and TLOAD2 entries in a set.
3. Select transient loads to be used by Dytran in the Case Control Section (TLOAD = SID).
4. If TYPE is 0, the LID field can reference any of the entries: FORCEn, MOMENTn, DAREA,
PLOAD, GRAV, or RFORCE and applies the appropriate type of load.
If TYPE is 2 or 3, the LID field can only reference DAREA, FORCE, MOMENT, or FORCEEX
entries and applies enforced velocity or acceleration to the specified grid points.
If TYPE is 12, the LID field can only reference the DAREA, FORCE, or MOMENT entries and
applies an enforced motion to the center of gravity of the specified rigid bodies.
If TYPE is 13, the LID field can only reference the FORCE or MOMENT entries and applies a
force or moment to the center of the specified rigid body.
5. If more than one velocity boundary condition (TYPE = 2) is applied to a grid point, the boundary
conditions are constant velocity boundary conditions and are consistently defined.
VISCDMP 581
Dynamic Relaxation
Defines the dynamic relaxation for the various types of Lagrangian elements, rigid bodies, and ellipsoids.
Remarks
1. A dynamic relaxation factor defined for a certain element type applies to all elements of that type
present in the problem.
2. See also Dytran Theory Manual, Chapter 4: Models, Dynamic Relaxation for general information
on dynamic relaxation in Dytran.
WALL 583
Lagrangian Rigid Wall
Defines a rigid plane through which specified Lagrangian grid points cannot penetrate.
+ METHOD FS FK EXP
PENALTY 0.2
Remarks
1. A rigid plane of infinite size is generated that the grid points cannot penetrate. The plane is fixed
in space.
2. The grid points can slide on the wall and separate from it.
3. A (moving) rigid plane of finite size can be modeled by using a rigid surface and a
master-slave contact.
584 WALL
Lagrangian Rigid Wall
4. For the wall definition using penalty method, output can be requested by referencing it in a SET
command in the Case Control Section. The keywords for output are WALLS and WALLOUT.
5. The coefficient of friction is given by:
– v
= k + s – k e
where
Defines a barrier for transport in an Eulerian mesh. The boundary consists of all Eulerian boundary faces
that point in a specific direction. Useful to define a barrier when a FLOWDEF has been defined. Can be
used to model a floor in blast wave simulations.
Remarks
1. WALLDIR can be used to specify flow boundaries for CHEXA’s and also for Euler element
created by the MESH,BOX option.
2. In the OUT file, the total area of boundary faces is printed.
3. WALLDIR is not supported by the single material strength Euler solver.
4. WALLDIR overrules FLOW and WALLET definitions, but FLOWSQ overrules WALLDIR.
5. The MESH-ID is only used when multiple Euler domains have been defined. If multiple euler
domains have been defined but if the MESH-ID is blank, all Euler domains will be considered in
assigning the boundary condition.
586 WALLET
Barrier for Eulerian Transport
Remarks
1. Material cannot pass through any of the faces referenced by the SID field.
2. Barriers can be modeled on the outside as well as the inside of an Eulerian mesh.
3. See Dytran User’s Guide, Chapter 3: Constraints and Loading, Eulerian Loading and Constraints
for a more detailed description of the use of Eulerian barriers.
YLDEX 587
User-defined Yield Model
Specifies that a user subroutine is being used to define the yield model.
Remarks
1. The subroutine must be present in the file referenced by the USERCODE FMS statement.
2. See User-written Subroutine Notes in Chapter 7: User Subroutines in this manual for a description
of how to use user-written subroutines.
3. This yield model is applicable only for Lagrangian solid elements and Eulerian elements with
shear strength.
588 YLDEX1
User-Specified Yield Model
Defines an yield model by a user subroutine. The yield strength can depend on the amount of failure or
damage of the Euler element and on the VOLPLS and SOFTE element variables. This amount of damage
can be either specified by the damage variable of the FAILJC entry or by a more general failure estimate
by using the FAILEX2 entry. The VOLPLS and SOFTE variables can also be filled by the EXYLD1,
EXFAIL2 user-subroutine.
YLDEX1 YID
YLDEX1 200
Remarks
1. This model is only supported by the multi-material Euler solver with strength.
2. The subroutine must be present in the file referenced by the USERCODE FMS statement.
3. See User-written Subroutine Notes in Chapter 7: User Subroutines in this manual for a description
of how to use user-written subroutines.
4. This yield model is applicable only Eulerian elements with shear strength.
5. The damage variable is determined by either FAILJC or FAILEX2. In the EXYLD1 user subroutine,
the yield stress can be reduced depending on the magnitude of the damage variable. In that case
the NOFAIL option should be set on the FAILJC or FAILEX2 entry.
YLDHY 589
Hydrodynamic Yield Model
Remark
This yield model should be used for fluids that have no shear strength.
590 YLDJC
Johnson-Cook Yield Model
Defines a Johnson-Cook yield model where the yield stress is a function of effective plastic strain, strain
rate, and temperature.
+ TMELT TROOM
+ 1500. 273.
Remarks
1. This yield model is described in Dytran Theory Manual, Chapter 4: Models, Yield Models.
The yield stress is computed from
·
y = A + B p 1 + C ln ----
n
- 1 – T* m
·
0
where
·
= effective strain rate
YLDJC 591
Johnson-Cook Yield Model
·
0 = reference strain rate
T = temperature
Tr = room temperature
Tm = melt temperature
A, B, n, C, and m are constants.
Remarks
1. For a description of the yield models, see Dytran Theory Manual, Chapter 4: Models, Yield
Models.
The yield stress depends on the pressure as:
y = MIN Y1 Y2 + Y3 * P
2. This yield model is applicable only for Eulerian materials with shear strength.
YLDMSS 593
Multisurface Yield Model for Snow
Defines the yield model for snow material. This option must be used in combination with DMAT,
EOSPOL, and SHREL.
+ ALP0 Ds
+ -0.37 0.0
Remarks
1. This material model can be used to model Snow material.
2. In addition to deviatoric plastic strain there is also volumetric plastic strain. This volumetric strain
is stored in the VOLPLS output variable. The deviatoric strain is stored in the EFFPLS variable.
3. For detail description of each parameter in this model, the user should refer to the Theory Manual
in which the mechanical properties of snow are described.
4. If Cc is set to zero, then the material behaves as a Drucker-Prager model. Ac, Bc, Fc*, and ALP0
are ignored.
5. The T value must be consistently converted from the cohesion data, C DP , of the Drucker-Prager
model as follows:
T = C DP K c
594 YLDMSS
Multisurface Yield Model for Snow
6. FTU, hydrostatic tensile strength, may not be greater than T divided by 3. Otherwise, it is set to
that value.
7. The softening modulus is used to update the hardening parameter q t ; see Theory Manual. It can
be requested as output using the FTU variable. The corresponding accumulated-plastic-
volumetric-tensile-strain variable is SOFTE.
8. This material model is valid for the Euler with Strength processor and the Multi-material Euler
with Strength solver.
YLDPOL 595
Polynomial Yield Model
Defines a polynomial yield model where the yield stress is a function of effective plastic strain.
Remarks
1. This yield model is described in Yield Models at the beginning of this chapter.
The yield stress is computed from
y = MIN max A + B p + C p2 + D p3 + E p4 + F p5
where
2. For a description of all of the yield models, see Yield Models in Chapter 4: Models of the Dytran
Theory Manual.
596 YLDRPL
Rate Power Law Yield Model
Defines a rate power law yield model where the yield stress is a function of effective plastic strain and
strain rate.
Remarks
1. This yield model is described in Yield Models at the beginning of this chapter.
The yield stress is computed from
·
y = MAX C A + B pn m
where
2. For a description of all of the yield models, see Yield Models in Chapter 4: Models of the
Dytran Theory Manual.
YLDSG 597
Steinberg-Guinan Yield Model
Defines the Steinberg-Guinan yield model where the yield stress is a function of effective plastic strain,
pressure and temperature.
+ TMELT TROOM
1500 273
Remarks
1. This material model can be used to model metals for a wide range of strain rates.
2. This yield model is described in Yield Models in Chapter 4: Models of the Dytran Theory Manual.
The yield stress is computed from:
A4
AT = A1 1 + A3 p
y = min A 2 ,A T 1 – H T – T r + Bp --------- , T T m
ref
y = 0 T T m
where
= density.
A 1 ,A 4 ,H and B are constants.
3. The reference and quasi-static strain rate are per unit time.
4. For a description of all of the yield models, see Yield Models at the beginning of this chapter.
YLDTM 599
Tanimura-Mimura Yield Model
Defines the Tanimura-Mimura yield model where the yield stress is a function of effective plastic strain,
strain rate and temperature.
Remarks
1. This material model can be used to model metals for a wide range of strain rates.
2. This yield model is described in Yield Models at the beginning of this chapter.
The yield stress is computed from
· ·
A + B p k
y = A + B p + C + D p 1 – -------------------- ln ---- 1 – T *m + E ----
-
cr · s ·
0
600 YLDTM
Tanimura-Mimura Yield Model
where
T = temperature
Tr = room temperature
T mr = melt temperature
A, B, D, m, E, and k are constants
3. The reference and quasi-static strain rate are per unit time.
4. For a description of all of the yield models, see Yield Models at the beginning of this chapter.
YLDVM 601
von Mises Yield Model
Defines a bilinear or piecewise-linear yield model with isotropic hardening, using the von Mises
yield criterion.
Remarks
1. A bilinear stress-strain characteristic is used by specifying YIELD and EH:
where
2. A piecewise linear, stress-strain characteristic is used by specifying TABLE and TYPE (beams
and shells only)
ij = i – i – 1 – i – 1 i – i – 1 + i – 1
The stress-strain characteristic used internally in Dytran is in terms of true stress and equivalent
plastic strain. However, for convenience, the stress-strain characteristic can be input in any of the
following ways (see Dytran Theory Manual, Chapter 4: Models, Yield Models):
3. For a description of all of the yield models, see Dytran Theory Manual, Chapter 4: Models, Yield
Models.
4. With Lagrangian and Eulerian solid elements, only an elastic perfectly plastic yield model is
currently used. Only the YIELD field is used.
5. If TABLE is blank or zero, a bilinear stress-strain curve is assumed. If TABLE has a value, it refers
to a TABLED1 entry giving the stress-strain curve for the material.
YLDVM 603
von Mises Yield Model
6. If TABLE is defined, the value of YIELD is left blank, since it is determined from the
stress-strain curve.
7. If TABY is blank or zero and D and P are blank or zero, the yield stress does not vary with strain
rate. If TABY has a value, then it references a TABLED1 entry, which gives the variation of the
scale factor applied to the yield stress with strain rate. (D and P must be blank or zero.)
If TABY is blank or zero and D and P are defined, the enhancement of the yield stress with strain
rate is calculated as
·
d 1p
------ = 1 + ----p-
y D
where d is the dynamic stress, y is the static yield stress (YIELD), and · p is the equivalent
plastic strain rate.
8. If TYPE is PLAST or PMOD, Young’s modulus must be defined. If TYPE is ENG or TRUE and
Young’s modulus is defined it overrides the value calculated from the stress-strain curve. See
Dytran Theory Manual, Chapter 4: Models, Yield Models for more details.
9. Note that for values exceeding the maximum x-value of either of the TABLED1 entries (see
TABLE and TABY fields), linear extrapolation is used based upon the last two points specified in
the TABLED1.
604 YLDZA
Zerilli-Armstrong Yield Model
Defines the Zerilli-Armstrong yield model where the yield stress is a function of effective plastic strain,
strain rate and temperature.
+ D
+ 0.0
Remarks
1. This material model can be used to model to model Fcc (iron and steels) and Bcc (aluminum and
alloys) metals.
2. This yield model is described in Yield Models at the beginning of this chapter.
The yield stress is computed from
·
– mT + CT ln -----
·
0
y = A + B pn for Fcc metals
·
– mT + CT ln -----
·
0
y = A + B pn + De for Bcc metals
YLDZA 605
Zerilli-Armstrong Yield Model
where
6 Parameters
CONTACT 635
COSUBCYC 639
COSUBMAX 640
COUFRIC 641
DELCLUMP 642
ELDLTH 643
ERRUSR 644
EULER-BOUNDARY 645
EULERCUB 646
EULERPR 647
EULSTRESS 648
EULTRAN 649
EXTRAS 653
FAILDT 654
FAILOUT 655
FASTCOUP 656
FBLEND 658
FLOW-METHOD 659
FMULTI 662
GEOCHECK 663
GRADED-MESH 664
HGCMEM 665
HGCOEFF 666
HGCSOL 667
HGCTWS 668
HGCWRP 669
HGSHELL 670
HGSOLID 671
Chapter 6: Parameters 609
HGTYPE 672
HICGRAV 673
HVLFAIL 674
IEEE 676
IGNFRCER 677
IMM 678
INFO-BJOIN 679
INISTEP 680
INITFILE 681
INITNAS 683
LIMCUB 684
LIMITER 685
MATRMERG 686
MATRMRG1 687
MAXSTEP 688
MESHELL 689
MESHPLN 690
MICRO 691
MINSTEP 692
MIXGAS 693
NASIGN 694
NZEROVEL 695
OLDLAGTET 696
PARALLEL 697
PLCOVCUT 698
PMINFAIL 699
RBE2INFO 700
RHOCUT 701
RJSTIFF 702197
610 Dytran Reference Manual
RKSCHEME 703
ROHYDRO 704
ROMULTI 705
ROSTR 706
RSTDROP 707
SCALEMAS 708
SHELLFORM 709
SHELMSYS 710
SHPLAST 711
SHSTRDEF 712
SHTHICK 713
SLELM 714
SNDLIM 718
SPHERSYM 719
STEPFCT 720
STEPFCTL 721
STRNOUT 722
TOLFAC 724
UGASC 725
VARACTIV 726
VDAMP 728
VELCUT 729
VELMAX 730
VISCOPLAS 731
Chapter 6: Parameters 611
Overview
Overview
The PARAM entry in the Bulk Data Section of the input file is used to change a number of the values that
control the analysis. This section describes all possible options and values that can be set with the
PARAM entry.
All the options are set to default values if no PARAM entry with that option is present in the input file.
You therefore only need to include a PARAM entry if you want to change one of the defaults. Normally,
the default values work well and need not be altered.
612 Dytran Reference Manual
Parameters Summary
Parameters Summary
The following PARAM entries are available:
Contact Control
CONTACT Sets the contact defaults
LIMCUB Contact cube-sort algorithm
Coupling Subcycling
COSUBCYC Growth of subcycling in coupling
COSUBMAX Subcycle limit
Blending Control
DELCLUMP Delete clump factor
FBLEND Blend fraction
CLUMPENER Kinetic energy calculation method for Eulerian blended clumps
Time-Step Control
INISTEP Initial time step
MAXSTEP Maximum time step
MINSTEP Minimum time step.
SCALEMAS Mass scaling definition
STEPFCT Time-step scale factor
Limits
FMULTI Dimensioning of multimaterial overflow array
MICRO Microzoning parameter
RHOCUT Global minimum density for Eulerian elements
ROHYDRO Minimum density for hydrodynamic, single-material Eulerian elements
ROMULTI Minimum density for multimaterial Eulerian elements
ROSTR Minimum density for single material Eulerian elements with strength
SNDLIM Minimum value of speed of sound
Chapter 6: Parameters 613
Parameters Summary
Restart Control
RSTDROP Type of elements dropped when restarting
Miscellaneous
AUTHQUEUE Licensing queuing control
CFULLRIG Converts 123456 constraints to FULLRIG for RBE2
EULTRAN Switch for the multimaterial Euler transport scheme
EXTRAS Extra input constants
FASTCOUP Fast coupling algorithm
GEOCHECK Defines geometry consistency check
HYDROBOD Defines a body force for single hydro material in Euler
LIMITER Defines type of scheme used in the Euler solver
MATRMERG Merges MATRIG and RBE2FULLRIG assemblies
MATRMRG1 Merges MATRIG and RBE2 FULLRIG assemblies
614 Dytran Reference Manual
Parameters Summary
Shell Options
SHELMSYS Shell-element system definition
SHPLAST Type of plane-stress plasticity for shells
SHTHICK Shell-thickness modification option
SHELLFORM Sets the default shell formulation
Dynamic Relaxation
VDAMP Defines dynamic-relaxation parameter
Airbag Control
PLCOVCUT Defines time that PLCOVER will be cut
UGASC Universal gas constant
ATB Positioning
ATBSEGCREATE Creates grids and elements for ATBSEG
Output Control
ATB-H-OUTPUT Writes ATB output to Dytran time-history files
ATBTOUT Frequency of output written to main output file of ATB
ATBTOUT Frequency of output written to the time-history files of ATB
Chapter 6: Parameters 615
Parameters Summary
Prestressing Analysis
INITFILE Defines method of initialization from a solution file
INITNAS Defines the type of displacement initialization file
Parameter Descriptions
The parameters are listed in alphabetical order. The entry and the examples are shown in free format,
although small or large fixed format entries can also be used.
The default value indicates the value used if no PARAM entry is present. The type column indicates the
type of data you must supply. This can be I (Integer), R (Real), or C (Character). In addition, a range of
permissible values may also be indicated for example, I > 0 means that you must supply an integer that
is greater than zero.
616 ALEITR
Number of ALE Mesh Iterations
Defines the number of mesh iterations to be used to move the free ALE grid points.
Remarks
1. In most applications, one iteration should be sufficient. If not, the number of iterations can be
increased to a maximum of six.
2. Less mesh iterations reduce the computational effort.
ALETOL 617
Tolerance at ALE Interface
Defines the tolerance in matching Eulerian and Lagrangian grid points in the ALE interface surface
.
Remark
Grid points in the ALE interface with coordinates that fall within the tolerance are recognized to be an
ALE interface pair.
618 ALEVER
ALE Volume Computation Method
Remark
The V2.2 option should be used in problems where the pressure levels are expected to be low. The V2.1
method is faster and consumes less CPU time, but it can lead to spurious pressure levels in a low pressure
level calculation.
ATB-H-OUTPUT 619
Write ATB Output to Dytran Time-History Files
An Dytran time-history file is created containing the output as requested in the ATB input file on cards
H.1 to H.11.
Defines the frequency at which output is written to the main output file of ATB.
Remarks
1. Only active when field 3 on the A5 card of the ATB input file is set to a value of -1.
2. Controls the frequency of the output of segment acceleration, velocity and displacement, joint
forces and moments.
ATBSEGCREATE 621
Create Grids and Elements for ATBSEG
A Bulk Data file is created containing grid points and elements visualizing the initial position and
orientation of the coordinate systems of the ATB segment and its joints.
Defines the frequency at which output is written to the time-history files of ATB.
Remarks
1. Only active when field 26 on the A5 card of the ATB input file is set to a value of –1.
2. Controls the frequency of all output requested on the H-cards, and of the tabular time-histories
that are controlled by field 18 on the A5 card of the ATB input file.
AUTHINFO 623
Licensing Information Control
Defines the amount of information FLEXlm licensing writes to the output file.
Remark
You can use this parameter to obtain extra licensing information if a FLEXlm licensing problem is
experienced. Under normal circumstances, where FLEXlm licensing is not a problem, this parameter is
not used.
624 AUTHQUEUE
Licensing Queuing Control
Remarks
1. When a job is waiting for a seat to become available, it consumes computer resources such as
memory, disk space, etc. Too many jobs waiting for licenses could have a severe impact on
the system.
2. A maximum of 100 Dytran jobs can be queued.
3. If queueing is enabled, Dytran waits in the queue until the license of the desired type has been
released by any other job(s) currently holding it. If queueing is disabled, Dytran searches for any
next applicable free Dytran license with which the run could be started. When no more of
the desired Dytran licenses are found, the job terminates. Note that a job requiring a 'basic' license
could also run using a 'standard' license although that one would obtain more tokens
than necessary.
AXIALSYM 625
Axial Symmetric Analyses
Enables an efficient and accurate 2-D axial symmetry for Eulerian materials. A much larger time step
becomes possible by not taking into account the mesh-size in circumferential direction.
PARAM,AXIALSYM,RECT,X,XY,2.5,YES,0 PHI: 0
ALIG: YES
PHI2: 0
The other fields
have to be set.
For MESHTYPE=AXIAL:
Remark
1. Only available for Eulerian elements and does not support Lagrange elements. The effect of this
parameter is not limited to the solvers. Also, Euler archives will reflect the modified Euler
mesh geometry.
2. The Euler mesh cannot only be symmetric but can also be a rectangular mesh comprising of one
layer. Using the angle specified by PHI, this Euler mesh is mapped into a 2-D axial
symmetric mesh.
3. The Euler mesh has to consist of one layer.
4. Rectangular meshes that can be made 2d symmetric using the angle PHI should satisfy:
• All boundary Euler faces are aligned with a coordinate direction
• Only one layer thick
• The axial symmetry axis is either on the boundary of the Euler mesh or outside the Euler mesh.
It is not allowed that the axial axis is inside the Euler mesh.
Initialization of Euler element using geometric regions as defined by the TICEUL entry is carried
out onto the transformed 2d axial mesh.
5. In the time step computation the circumferential mesh-size will not be taken into account.
6. Use the PHI2 option with caution. Euler initialization is done using the mesh rotated by the angle
PHI2. So after including the angle PHI2 or modifying its value, the Euler initialization should
be revised.
BULKL 627
Linear Bulk Viscosity Coefficient
Remarks
1. The default value works well for the majority of problems.
2. The value defined on this entry is used as the default whenever BULKL is blank on the DMATxx
material entries.
3. When BULKL is specified on a material definition entry, the default value is overridden for that
specific material.
4. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on bulk viscosity.
628 BULKQ
Quadratic Bulk Viscosity Coefficient
Remarks
1. The default value works well in the majority of situations.
2. The value defined on this entry is used as the default whenever BULKQ is blank on the DMATxx
material entries.
3. When BULKQ is specified on a material definition entry, the default value is overridden for that
specific material.
4. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on bulk viscosity.
BULKTYP 629
Bulk Viscosity Type
Remark
See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on bulk viscosity.
630 CFULLRIG
Converts 123456 Constraints to FULLRIG on RBE2 Entries
In some cases, airbag runs become instable. Often, this is caused by a much too large volume strain rate
in a clump that consists of too many elements. These clumps typically have a small average volume
uncovered fraction. The large volume strain rate causes a huge compression work and this blows up the
specific internal energy. When this happens it is clearly visible in the OUT file and in the results. This
PARAM activates a limiter that scales down the volume strain rate for clumps with a small average
uncovered fraction. It can keep an instable airbag run stable, just like PARAM, VELMAX can keep
runs stable.
PARAM, CLUFLIM,0.22
Remark
DIV
----------- = min 1 ,----------------------------- -----------
U DIV
t Lim CLUFLIM t
Uncf el * Vol el
clump
U = el
-----------------------------------------------------------
-
Vol el
el cl ump
Here Uncf and Vol denote the uncovered fraction and volume of an element inside the clump.
Therefore, only when the average uncover fraction falls below CLUFLIM, the volume strain rate
is limited.
632 CLUMPENER
Switch for Kinetic Energy Calculation Scheme of Blended Clumps
Sets the definition of the kinetic energy calculation method for Eulerian blended clumps.
Remarks
1. With the release of Dytran 2002 R1, the default method switched from SUM to AVERAGE to
minimize the possible occurrence of negative internal energy locally in Eulerian elements during
the analysis.
2. For normal analysis, the default method AVERAGE works correctly. Only in cases of repeating an
older analysis is desired, should the method SUM be used to obtain the same results as before.
COHESION 633
Cohesion for Coulomb Friction
Allows friction and sticking during tensile conditions at the coupling surface.
Remarks
1. Only used when Coulomb friction coefficients have been specified for a COUPLE entry.
2. During tension any relative tangential velocity between coupling surface and Eulerian material
V
will yield a shear stress whose magnitude equals FRIC min 1 ,--------------------------------
rel , tan gential
- . This is a viscous-like
REFVEL
friction law.
3. This shear force opposes the relative tangential movement along the coupling surface.
634 CONM2OUT
CONM2 Summary Output
Determines if a summary of concentrated masses and their energy and momentum is written to the
output file.
Remark
When PARAM,CONM2OUT is set to NO, there is no summary of the concentrated mass. This means that
the mass, momentum, and energy of the concentrated masses, is not added to the material and cycle
summaries. Setting PARAM,CONM2OUT,NO saves memory and CPU time.
CONTACT 635
Sets Defaults for CONTACT
(Default = 10)
TYPE Contact force limitation.
FMAXF F new_check (where nonallowable
forces are not taken into account)
ZERO 0.0
(Default = 0)
See Remark 3.3.
Remarks
1. This parameter is important for initialization of BPLANE contact. The faces of the contact surface
will be enlarged with a value of TOLPR1. However, this might not be enough when the air bag is
offset folded. On the other hand, a large value of TOLPR1 might induce hooking. Therefore, a
new parameter is introduced called TOLFAC. The value of TOLFAC scales the value of TOLPR1
only at initialization, such that the contact is correctly found.
638 CONTACT
Sets Defaults for CONTACT
3. .The PARAM, FORCE check takes up some CPU time and, therefore, do not make this value too
small. Furthermore, when the check is performed at each cycle, the force will be too limited and
the bag will not unfold. Recommended values are between 5 and 200. The same problems can
occur for SCALE. In case this value is too small, the bag will not unfold either. The minimum
value for air bags that should be used is about 5. The maximum is about 20. When this value is
too big a difference will not be noticed. TYPE ZERO is a bigger restriction. In some cases, TYPE
FMAXF might yield better results.
COSUBCYC 639
Growth of Subcycling Interval in Coupling
Remarks
1. The subcycling algorithm automatically estimates the number of subcycles to be used. This is
updated throughout the calculation. This parameter controls how much the number of subcycles
can grow. For example, COSUBCYC is set to 1, and the current number of time steps between
updates of the coupling geometry is 4. If Dytran estimates that the subcycling interval should be 7,
the subcycling interval is increased by 1 until a value of 7 is reached.
2. There is no control on the amount by which the subcycling interval can decrease.
640 COSUBMAX
Subcycle Limit in Euler/Lagrange Coupling
Defines the maximum number of subcycles that can occur in Euler/Lagrange coupling. During a
subcycle, the geometry of the coupling surface is not updated.
Remarks
1. Updating the coupling geometry takes a lot of CPU time. Subcycling gives substantial savings in
CPU time for coupled calculations.
2. The smaller the value of this parameter, the greater the accuracy of the analysis and the greater
the cost. Conversely, larger values offer significant CPU savings, but very large values give
incorrect results.
3. If the geometry of the coupling surface is changing rapidly, smaller values of PARAM,
COSUBMAX should be used.
COUFRIC 641
Coupling Surface Friction for Nonmetallic Eulerian Solids
In Dytran 2005r3, the Coulomb friction scheme was updated to fully reflect friction between metals. The
Coulomb friction of Dytran 2005 is more suitable for friction with nonmetals like soil and sticky fluids.
This PARAM deactivates the Dytran 2005r3 scheme and uses the Dytran 2005 scheme instead. The main
difference between the schemes is the treatment of tensile reconditions. In Dytran 2005r3 and beyond, a
tensile condition will result in zero load on the structure part. In Dytran 2005 under tensile condition, a
tensile load was applied. In addition the onset of sliding in the friction model was applied differently. In
stead of using this PARAM one may also consider using PARAM,COHESION.
PARAM,COUFRIC,NO-METAL
Remarks
Only used when Coulomb friction coefficients have been specified for a COUPLE entry.
642 DELCLUMP
Delete Clump Fraction
Remark
Also see the FBLEND parameter.
ELDLTH 643
Show List of Lagrangian Elements with Time Step in Ascending Order
When you include this parameter in the input file, a list of “n” elements with the time step in ascending
order is listed to the output file at the end of time step zero.
Remarks
1. When the value is set to zero, a list of all Lagrangian (structural) elements is printed to the
output file.
2. Spring and damper elements are not shown in the list.
3. When you use this feature to determine the initial time step, you should be aware that the time
step listed includes the time-step safety factor.
644 ERRUSR
Redefinition of Severity and Number of Error Message Prints
Remarks
1. An error name consists of a maximum of eight characters. The entry is also used as a wildcard by
entering less than eight characters. The string then is matched with the actual names, and every
match redefines the actual message.
2. See Chapter 8: Diagnostic Messages in this manual.
EULER-BOUNDARY 645
Euler Boundary Treatment
Remarks
1. The finite volume representation, in general, assumes that element values are constant within each
element. While this assumption is adequate for the large majority of applications, fluid models
involving hydrostatic pressure gradients require that the pressure gradient also be recognized to
exist within the element. When element-internal hydrostatic gradients are not accounted for, the
calculation is less accurate and suffers from numerical symptoms like pair forming of element
pressures. By activating the EXTRAPOLATION option, hydrostatic gradients inside the element
are taken into account. For meshes without bias, EXTRAPOLATION option only modifies the
numerical schemes along the boundary.
2. When coupling surfaces are used, PARAM,FASTCOUP has to also be activated.
646 EULERCUB
Cube Sorting for Euler Domains
Remarks
1. By setting NELCUBE equal to 2000, optimal use is made of memory caching during Euler
computation. This can give a speedup of 1.5.
2. If NBX is defined, also NBY and NBZ need to be defined. Defining NBX overrules the definition of
NELCUBE.
3. There are several ways to distribute cubes across processors. Some ways may lead to bad load
balancing. To avoid this it is possible to control the way cubes are distributed across processors
by defining PARAM,EULERPR . To check the load balancing the number of active Euler elements
on each processor is written out every 1000 cycles.
4. Only supports Euler domains created by MESH,BOX. Limitations are:
• No MESH,ADAPT and no CHEXA’s.
• No FLOW or WALLET. Boundary conditions have to be defined by FLOWDIR, FLOWTSQ, or
WALLDIR.
• Time history output of Euler elements is not supported.
5. When several cubes are on each processor, it may be useful to switch on option 5 of
PARAM,FASTCOUP with VALUE=ALL.
EULERPR 647
Euler Cube Partition Control
Remarks
1. There are several ways to distribute cubes across processors. Some ways may lead to bad load
balancing. To avoid this it is possible to control the way Euler cubes are distributed across
processors by defining PROCDIR.
2. When option PROCDIR=USER, the values for NBX, NBY, and NBZ must be such that NBX is equal
or a multiple of NPX, NBY is equal or a multiple of NPY and NBZ is equal or a multiple of NPZ. Also
for this option, NPX*NPY*NPZ must be equal to the number of processors used in the cluster.
3. For option PROCDIR=SIMPLE, the values NBX, NBY, and NBZ on DYPARAM,EULERCB must be
such that NBX*NBY*NBZ is equal or a multiple of the number of processors used. For instance, if
the number of processors in the cluster is 4, NBX*NBY*NBZ must be equal to either 4 or 8 or 12,
etc. Otherwise, the calculation will terminate prematurely with an error message.
4. Only supports Euler domains created by MESH,BOX. Limitations are:
• No MESH,ADAPT and no PEULERx/CHEXA’s
• No FLOW or WALLET entries are allowed. Boundary conditions have to be defined by
FLOWDIR, FLOWTSQ, or WALLDIR.
648 EULSTRESS
Stress Update Method
Defines the update logic for stresses when material is transported in Euler elements
.
Remarks
1. Only used for the MMSTREN solver.
2. Stresses are a material property and when material flows in or out an element the stress state in
the element is changed. This is analogous to temperature and energy. Not the temperature is
transported, but energy. After transporting energy the temperature is recomputed by dividing the
energy by element mass and specific heat. In case of stress, the “energy” is given by mass times
stress. After transporting this “energy” the new stress follows by dividing it by mass. As shown
in Dytran Theory Manual, Chapter 6: The Standard Euler Solver, Euler With Strength, this gives
a correct updating procedure for stresses. There it also proven that stress times mass is conserved
during transport.
3. In most simulations, variations in density are small and one can replace multiplication by mass by
a multiplication by volume. This method is activated by the VOLUME option which is also the
default option. Using the MASS option may have some influence on simulations with large density
variations. The MASS option gives the most accurate results.
4. The transport logic of the effective plastic strain is identical to that of stresses. When using the
MASS option, the plastic strain is computed more accurately when material is compressed.
5. The Euler with Strength solver always uses the MASS option, by default.
EULTRAN 649
Switch for the Euler Transport Scheme of the Multi-material Solver and the Single Material Strength
Solver
Sets the definition of the face velocity used in the transport scheme of the Multi-material solver and the
single material strength solver.
Remarks
1. The default value of IMPULSE is sufficient for most Euler problems. Especially problems where
the reference density of the different materials varies widely (for example, orders of magnitude)
are required to use the default option.
2. In case the IMPULSE option (default) is used, the Euler transport scheme computes that the face
velocity uses an impulse weighted average of the material velocity in the left and the right element
adjacent to the face.
3. In case the AVERAGE option is used, the Euler transport scheme computes the face velocity as
one-half times the sum of the material velocity in the left and the right element adjacent to
the face.
4. Does not apply to the single material hydrodynamic solver and the Roe solver.
5. The FAIL option requires a failure model for at least one Eulerian material. In case of the default
NOFAIL, then failed Euler material can support shear stress again as soon as new material enters
the Euler element. Thus the information that part of the material inside the Euler element has
failed is lost. The FAIL option activates transport of fail fraction and thereby keeps track of
material that has failed. In this way only the failed part of the element can no longer supports shear
stresses. In more detail, the yield stress in the material is scaled by (1-failfrac), where failfrac
denotes the fail fraction of the material. The fail fraction of the first material in an element can be
retrieved from Euler archive or time-history results files in the DAMAGE variable. The value of
fail fraction DAMAGE is between zero and one.
6. The FAIL option cannot be combined with the Johnson-Cook failure model (FAILJC).
650 EUSUBCYC
Growth or Subcycling Interval in Euler Computations
Remarks
1. The subcycling algorithm automatically estimates the number of subcycles to be used. This is
updated throughout the calculation. This parameter controls how much the number of subcycles
can grow. For example, EUSUBCYC is set to 1, and the current number of time steps between
updates of the Euler variables. If Dytran estimates that the subcycling interval should be 7, the
subcycling interval is increased by 1 until a value of 7 is reached.
2. There is no control on the amount by which the subcycling interval can decrease.
EUSUBMAX 651
Subcycle Limit in Euler Solver
Defines the maximum number of subcycles that can occur in the Euler solver. During a subcycle, the
Euler computations are skipped.
If coupling surface computations are more expensive than Euler computations, then use of COSUBMAX
should be considered first. In that case, the optimal setting of EUSBMAX is LINKCS = BOTH and FVUMAX
is blank.
As with COSUBMAX, use of EUSUBMAX can lead to loss of accuracy for certain simulations. It is
recommended to validate the use of EUSUBMAX by comparing the difference in results between using
EUSUBMAX and not using EUSUBMAX for some typical target simulations.
.
Remarks
1. Updating the coupling geometry can take a lot of CPU time. Subcycling can give substantial
savings in CPU time for coupled calculations.
2. The smaller the value of DFVUMAX, the greater the accuracy of the analysis and the greater the cost.
Conversely, larger values offer significant CPU savings, but very large values give incorrect
results.
3. When the Euler time step is considerably larger than the Lagrange time step, it can be worthwhile
to skip the Euler computation for several cycles. This can reduce computational costs
considerable.
4. Skipping the Euler computation for several cycles leads to postponed time steps. When the Euler
computations are done, these have to be taken into account by fluxing with an accumulated time
step. Skipping the Euler computation is stopped as soon as the accumulated time step becomes
larger than the stable Euler time step. The total number of skipped cycles is limited by NSUBMAX.
NSUBMAX is required input.
652 EUSUBMAX
Subcycle Limit in Euler Solver
5. In skipping the Euler computation, the movement of the coupling surface has to also be
monitored. To estimate this movement, the change in uncovered fraction of the elements is used.
If the change in uncovered, volume fraction from one cycle to the other is larger than DFVUMAX;
then the Euler computation is not skipped that cycle. DFVUMAX has to be left blank if coupling
surface subcycling is used. Coupling surface subcycling already monitors the movement of the
coupling surface. Choosing too large values for DFVUMAX can make results inaccurate.
6. EUSUBMAX is only supported by the multi-material Euler solver.
7. EUSUBMAX can be used with COSUBMAX. LINKCS specifies how the two subcycling processes
influence each other. Allowed values for LINKCS are:
BOTH The Euler computations will not be skipped when the coupling surface
computations have been done. On the other hand, if an Euler computation is to be
done, a coupling surface computation is done also. The number of times that the
Euler computation is skipped equals the number of times that the coupling surface
computation has been done.
COUPLE If an Euler computation is to be done, also a coupling surface computation is done.
EULER The Euler computations will not be skipped when the coupling surface
computations have been done.
NONE The Euler subcycling and coupling surface subcycling are independent. DFVUMAX
has to be defined
Input of extra constants that you can access from within other user-written subroutines
.
Remark
Usage in a user subroutine as follows:
SUBROUTINE EXCOMP (...)
COMMON/MSCD_EXTRAS/NMEXTR, IDEXTR
.
.
.
CHARACTER*16 CARGET, CVAR
.
.
.
IF (IDEXTR.GT.0) THEN
DO NV = 1,NMEXTR
CVAR = CARGET (IDEXTR, NV,’USER’)
IF (CVAR(1:8).EQ.’MASSFLOW’) THEN
VALMF = XARGET (IDEXTR, NV,’USER’)
ELSEIF (CVAR(1:4).EQ.’MASS’) THEN
VALMS = XARGET (IDEXTR, NV,’USER’)
ENDIF
ENDDO
ENDIF
RETURN
.
.
.
END
654 FAILDT
Element Time-step Based Failure Model
Defines the property of a failure model where element failure occurs when the element’s time step falls
below the specified limit.
Remarks
1. This failure model is valid for all Lagrangian solid (CHEXA)and shell (CQUAD4)elements.
2. All elements for which the time step falls below the specified value are removed from
the computation.
3. Although it is not usually necessary to limit the element time-step for Lagrangian elements, there
are occasions where specifying a minimum time-step can be advantageous for computational
performance, for example, when adaptive contact is used.
4. Note that this parameter should be used with care as you may influence the results of the analysis
when you set the time-step criterion to a too high value. You then run the risk that elements are
removed from the analysis while they may still be relevant.)
FAILOUT 655
Failed Element Output Parameter
Defines whether failed elements are written to the output file (ARCHIVES).
Remarks
1. When the NO option is chosen, the archives are written out as one file per requested time step
regardless of the number set in the SAVE command for the archive files that appear in the Case
Control Section.
2. Failed elements are NOT filtered when written to a RESTART file or a TIMEHISTORY file.f
656 FASTCOUP
Fast Coupling Algorithm
Remarks
1. Default value for option1 is INPLANE and for option2 NOFAIL.
2. When option1 is set to INPLANE or when option 1 is blank, a small offset is given to coupling
surface segments that are on top of a face of an Eulerian element. This is done because coupling
surfaces segments on Eulerfaces make the Euler element volume computation invalid. Also
boundary conditions on these segments are not correctly imposed. The net effect of these
problems is unpredictable. The problem can either run correctly, or remain stable but give false
results or become instable. The option NO-OFFSET is obsolete and should not be used.
3. Option2 can only be used in combination with PARAM, LIMITER, ROE, or MMHYDRO or
MMSTREN. The coupling surface must consist of CQUADs and/or CTRIAs and a failure model for
the material of the surface must be defined.
4. This parameter can only be used when the Eulerian mesh is aligned with the basic coordinate
system axes.
5. Options 5 and 6 can be useful for runs with distributed memory. In these runs, the Euler mesh is
divided into a number of cubes. By default, the coupling surface computations are done per cube.
By switching on option 5, the coupling surface computation is done for all cubes in one run.
Option 6 is limited to skipping segments and generally has less effect. The number of cubes can
be controlled by using PRAM,EULERCUB.
658 FBLEND
Blend Fraction
Eulerian elements with uncovered fractions smaller than FBLEND are blended with adjacent elements to
form a clump so that they do not control the time step.
Remarks
1. The default value is satisfactory for virtually all calculations.
2. Elements are blended only if they would have controlled the time step otherwise.
3. Elements with uncovered fractions greater than FBLEND are not blended and are allowed to
control the time step.
4. Large values of FBLEND produce a larger time step but many blends. Small values produce a
smaller time step and fewer blends.
5. In a calculation with a coupling surface, STEPFCT is smaller or equal FBLEND to avoid
instabilities (see PARAM,STEPFCT).
FLOW-METHOD 659
Flow-Method Between Two Euler Domains Across Open Areas in Coupling Surfaces
Defines the method for simulating material flow between two Euler domains across open areas in
coupling surfaces.
Remarks
1. For a detailed description of the theory involved, see Reference [18.].
2. This parameter applies to simulations where:
• two coupling surfaces share a common set of facets.
• each coupling surface has it’s own Euler domain.
• material flows from one Euler domain into the other through the open area represented by the
common set of facets.
Flow will only occur if:
• the common facets are defined as ‘open’, using PORFLCP or PORFCPL.
• the common facets open up due to failure of a shell structure, using COUP1INT.
660 FLOW-METHOD
Flow-Method Between Two Euler Domains Across Open Areas in Coupling Surfaces
Material COUP1INT/COUP1
flow FL
through a FLOW- FLOW- PORFLCP PORFCPL (Failure of shell
coupling METHOD = METHOD L (velocity (Pressure elements creates
Euler Solver surface POLPACK = FACET based based) the opening)
HYDRO YES YES NO YES YES Only for flow-
method = polpack
HYDRO – YES YES YES YES YES YES
Roe solver –
1st Order
HYDRO – YES YES YES YES YES YES
Roe solver –
2nd Order
MMHYDRO YES YES NO YES NO Only for flow-
method = polpack
STRENGTH NO - - - - -
MMSTREN YES YES NO YES NO Only for flow-
method = polpack
4. The Euler domains are shown below with the support types for each:
5. An Euler domain is associated with a coupling surface by specifying the MESHID or SET1ID on
the COUPLE option.
FLOW-METHOD 661
Flow-Method Between Two Euler Domains Across Open Areas in Coupling Surfaces
Remark
The multimaterial Eulerian elements use an overflow array in which to store material data. This array can
hold FMULTI times the total number of Eulerian elements. In a problem where more than 10% of the
elements have more than one material, the default value of FMULTI must be increased.
GEOCHECK 663
Define Geometry Consistency Check
This parameter forces a check of the geometry for consistent connectivity of the defined hexagonal
elements and correction if needed.
Remarks
1. The defined geometry is checked for consistent connectivity of the hexagonal elements. If an
inconsistency is detected, the connectivity is corrected. CFACE entries with references to
elements that have been corrected are corrected as well.
2. If a hexagonal mesh is generated with other commercial preprocessors, this parameter can correct
the connectivity of the hexagonal elements in case problems are encountered with face generation
or volume computation.
664 GRADED-MESH
Glue Sets of Euler Elements
Glues fine meshes to coarse meshes. See the section on Graded meshes in the user manual for
further information.
PARAM,GRADED-MESH,MINVOLUME
Remarks
1. This parameter can be used to build block-structured meshes.
2. It does not support multiple coupling surfaces.
3. All Euler elements have to be orthogonal.
HGCMEM 665
Shell Membrane Hourglass Damping Coefficient Parameters
Remarks
1. The default value applies to all types of hourglass suppression methods and should be used unless
there is a good reason to define the hourglass damping coefficient by another means.
2. The value specified on this entry is used whenever the coefficient is not explicitly defined on the
HGSUPPR entry.
3. If this entry is omitted, the default value of the coefficient used in the hourglass suppression
method for shell elements is either equal to the default value of 0.1 or is equal to the default value
defined on a PARAM,HGCOEFF entry.
4. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on hourglass
suppression methods.
666 HGCOEFF
Hourglass Damping Coefficient
Remarks
1. The default applies to all types of hourglass suppression methods and should be used unless there
is good reason to define the hourglass damping coefficient by another means.
2. The value specified on this entry is used whenever the coefficients are not explicitly defined on
HGSUPPR entries or on a HGCMEM HGCWRP, HGCTWS, or HGCSOL entry.
3. If this entry is omitted, the default value of the hourglass damping coefficients is either equal to
the default value of 0.1 or is equal to the value specified on a HGCMEM, HGCTWS, HGCWRP,
or HGCSOL PARAM entry.
4. The value of the coefficients can be explicitly defined for each property by using an
HGSUPPR entry.
5. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on hourglass
suppression methods.
HGCSOL 667
Solid Hourglass Damping Coefficient
Remarks
1. The default value applies to all types of hourglass suppression methods and should be used unless
there is a good reason to define the hourglass damping coefficient by another means.
2. The value specified on this entry is used whenever the coefficient is not explicitly defined on the
HGSUPPR entry.
3. If this entry is omitted, the default value of the coefficient used in the hourglass suppression
method for solid elements is either equal to the default value of 0.1 or is equal to the default value
defined on a PARAM,HGCOEFF entry.
4. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on hourglass
suppression methods.
668 HGCTWS
Shell Twisting Hourglass Damping Coefficient
Remarks
1. The default value applies to all types of hourglass suppression methods and should be used unless
there is a good reason to define the hourglass damping coefficient by another means.
2. The value specified on this entry is used whenever the coefficient is not explicitly defined on the
HGSUPPR entry.
3. If this entry is omitted, the default value of the coefficient used in the hourglass suppression
method for shell elements is either equal to the default value of 0.1 or is equal to the default value
defined on a PARAM,HGCOEFF entry.
4. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on hourglass
suppression methods.
HGCWRP 669
Shell Warping Hourglass Damping Coefficient
Remarks
1. The default value applies to all types of hourglass suppression methods and should be used unless
there is a good reason to define the hourglass damping coefficient by another means.
2. The value specified on this entry is used whenever the coefficient is not explicitly defined on the
HGSUPPR entry.
3. If this entry is omitted, the default value of the coefficient used in the hourglass suppression
method for shell elements is either equal to the default value of 0.1 or is equal to the default value
defined on a PARAM,HGCOEFF entry.
4. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on hourglass
suppression methods.
670 HGSHELL
Shell Hourglass Suppression Method
Remarks
1. The type of hourglass suppression method defined on this entry is used as the default whenever
the type fields on the HGSUPPR for shell properties are left blank.
2. If this entry is omitted, the default suppression method used for shell elements is either FBV or
the default method defined on the PARAM,HGTYPE entry.
3. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on hourglass
suppression methods.
HGSOLID 671
Solid Hourglass Suppression Method
Remarks
1. The type of hourglass suppression method defined on this entry is used as the default whenever
the type fields on the HGSUPPR for solid properties are left blank.
2. If this entry is omitted, the default suppression method used for solid elements is either FBS or
the default method defined on the PARAM,HGTYPE entry.
3. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on hourglass
suppression methods.
672 HGTYPE
Hourglass Suppression Method
Remarks
1. The type of the hourglass suppression method defined on this entry is used as the default
whenever the type fields in the HGSUPPR entries are left blank.
2. If this entry is omitted, the type can be defined on a PARAM,HGSHELL entry for shell elements,
a PARAM,HGSOLID entry for solid elements, or on the HGSUPPR entries; otherwise the defaults
apply. For shell elements the default is FBV; for solid elements, the default is FBS.
3. See Dytran Theory Manual, Chapter 4: Models, Artificial Viscosities for details on hourglass
suppression methods.
HICGRAV 673
Gravity Used by HIC Calculations
Remark
1. The value set by this parameter will be used by all HIC output requests.
2. This parameter can only be set once in the input deck.
674 HVLFAIL
Failure at Hydrodynamic Volume Limit
Remarks
1. Lagrangian elements (CHEXA) that have a material model with a failure model fail when the
hydrodynamic volume limit is reached and the parameter is set to YES.
The elements can fail only when the following items are presented in the input:
a. The material model has a hydrodynamic volume limit (HVL).
b. A failure model is defined.
c. PARAM, HVLFAIL, YES
Example
PARAM, HVLFAIL, YES
DMAT, 1, 7850, 101, 102, 103, 104
EOSPOL, 101, 175.E9,,,,,,+
+, 1.1
SHREL, 102, 80.77E9
YLDVM, 103, 1.E20
FAILMPS, 104, 1.E20
2. The hydrodynamic volume limit by default allows for 10% expansion.
HYDROBOD 675
Hydrodynamic Body Force
Remark
This parameter defines a constant body force load in Euler for single hydro material only.
676 IEEE
IEEE Binary Data Output Format
On CRAY computers, archive and time-history output is defined in IEEE format rather than in Block
Data format
.
Remarks
1. On computers that, by default, write binary data in IEEE format, the parameter will have no effect.
2. Binary IEEE files can be transported to all IEEE computer systems. (Note that this in only valid
for ARCHIVE and TIMEHISTORY files.)
IGNFRCER 677
Ignores Warnings
Option Meaning
No option Some warnings that are given when using the FORCE1 FORCE2, MOMENT1,
or MOMENT2 entries are normally accompanied by an additional error message.
By using this PARAM, the warnings are still issued, but the error message is
not issued.
678 IMM
Initial Metric Method Formulation
Remarks
1. Method ZERO is best suitable when initially more than a couple of elements with zero or near zero
area are present in the model.
2. The Initial Metric Method is described in the Dytran User’s Guide in Chapter 6: The Standard
Euler Solver, Initial Metric Method for Air Bags.
3. The default for Option2 depends on Option1.
Additional information about the BJOIN and spotweld connectivity will be listed in the output file. The
information listed is:
• Grid point pairs forming a BJOIN or a spotweld.
• BJOINs and spotwelds initially connected.
Remarks
1. This parameter is required to start an analysis.
2. See Chapter 9: Running the Analysis, Controlling the Analysis in the Dytran User’s Guide for
details on time step control.
INITFILE 681
Method of Initialization Definition
Defines the method of initializing a transient analysis from a Dytran solution file.
• One-dimensional elements
• Shell elements (including composites)
• Membrane elements
• Lagrangian solid elements
V2 Version of initialization, where the prestress and the transient input files C
must obey the following rules:
• One-dimensional elements
• Shell elements (including composites)
• Membrane elements
• Lagrangian solid elements
• Eulerian elements
Remarks
1. The user is responsible for consistency upon choosing the V2 definition.
2. See Chapter 9: Running the Analysis, Restarts and Prestress Analysis in the Dytran User’s Guide
for more detailed information about prestress analyses.
INITNAS 683
Defines the Type of Displacement Initialization File
Defines the type of file to be used for initialization from an MD Nastran prestress analysis.
Remarks
1. When Dytran uses the results of an MD Nastran analysis to start a transient analysis from a
prestressed state, the grid-point displacement field, as computed by MD Nastran, is read from a
formatted file written either by MSC.XL, MD Patran, or MD Nastran.
The format of the formatted import files is as follows:
MSC.XL Export File:
Record 1: Header 1
Record 2: Header 2
Record 3: Header 3
Record 4: Header 4
Record 5: Header 5
Record 6: Header 6
Record 7: Header 7
Record 8: Header 8
Record 9 to n+8: Grid point X-Dis Y-Dis Z-Dis(A8, 3A15)
Defines the maximum number of cubes used to sort the grid points in a contact definition.
Remark
Each slave node has to search for master nodes that are close enough to have potential contact. It is too
expensive to have each slave node check each master node. To limit the number of checks, the space in
which the nodes reside is subdivided into cubes. This subdivision is done so that the slave nodes have to
check only the master nodes in their own cube and those in the neighboring cubes. The maximum number
of cubes used to subdivide the space is equal to the value of LIMCUB.
LIMITER 685
Euler Solver Scheme
Defines the type and the spatial accuracy of scheme used in the Euler solver.
Remarks
1. By default, the standard Euler solver is used.
2. By default, second order spatial accuracy is used. The temporal accuracy is defined using the
PARAM,RKSCHEME entry.
3. When type ROE is defined, no void elements are allowed and it cannot be used in combination
with EOSJWL. Also, ALE and options concerning air bag analyses are not supported.
4. For more details on the Euler solver see Dytran Theory Manual, Chapter 6: Standard Euler Solver.
686 MATRMERG
Merges MATRIG and RBE2-FULLRIG Assemblies
Parameters
Merges MATRIG and/or RBE2-FULLRIG rigid bodies into a new FULLRIG assembly.
Remarks
1. FR<id1> must be a nonexisting RBE2-FULLRIG. The properties of FR<id1> (as mass, center
of gravity, and moments of inertia) are computed by Dytran from the properties of each rigid body
mentioned on the entry. Rigid body output can be asked for FR<id1>, and loads or rigid body
constraints can be applied to FR<id1>. The other MATRIGs and RBE2-FULLRIGs mentioned
on the MATRMERG entry disappear after they have been merged.
2. Instead of supplying rigid body names, the AUTO option can be used. After all the normal
PARAM,MATRMERG and PARAM,MATRMRG1 entries have been applied, a
PARAM,MATRMERG,AUTO merges all the resulting MATRIGs and RBE2-FULLRIGs which
have common grid points into a new rigid assembly called FM<id>, where the id is a new FM
number starting from 1. As it is not known at the start of an Dytran analysis how many FM-
assemblies will be created, no rigid body output can be asked for FM<id>, and no constraints or
loads can be applied to FM<id>. The MATRIGs and RBE2-FULLRIGs, which have been merged
by the AUTO option into a new FM<id> assembly, disappear.
3. To supply predefined properties for the merged assembly, PARAM,MATRMRG1 can be
used, where the first rigid body mentioned on the entry must be an existing RBE2-FULLRIG
or MATRIG.
MATRMRG1 687
Merges MATRIG and RBE2-FULLRIG Assemblies
Merges MATRIG and/or RBE2-FULLRIG rigid bodies into one existing MATRIG or RBE2-FULLRIG
assembly with predefined properties.
Remark
MR<id1> or FR<id1> must be an existing MATRIG or RBE2-FULLRIG, respectively. For a
FULLRIG, the properties of FR<id1> (as mass, center of gravity and moments of inertia) are computed
by Dytran from the properties of each rigid body mentioned on the entry. For a MATRIG, the mass of
MR<id1> is either the predefined mass on the MATRIG (id1) entry or the predefined density on the
MATRIG (id1) entry times the total volume of all MATRIG members in the MATRMRG1 entry. The
center of gravity and moments of inertia of MR<id1> are either predefined on the MATRIG (id1) entry,
or are otherwise computed from the properties of each rigid body on the entry. The other MATRIGs and
RBE2 FULLRIGs mentioned on the MATRMRG1 entry disappear after they have been merged.
688 MAXSTEP
Maximum Time Step
Remark
If the time step calculated by Dytran is greater than MAXSTEP, the time step is set to MAXSTEP.
MESHELL 689
Mesh Density for Covering Ellipsoids
Defines the factor that determines the mesh density for ellipsoids in contact and for output purposes
.
Remarks
1. The mesh density factor is applied for both ellipsoids in a contact definition and for output
purposes. For ellipsoids in contact, the default value results in 18 by 36 elements. When you have
ellipsoids for output only, the default value results in 8 by 16 elements.
2. The default value is sufficient for most cases. When you increase the value, the representation of
the (hyper) ellipsoids is better, but the contact computation will be more expensive, and the
archive files will be larger.
3. In case the ellipsoids are meshed for output purposes only, the number of elements in the direction
of the ellipsoid’s short axis equals 2 . (value-1). The number of elements in the direction of the
ellipsoid’s long axis is twice the number in the direction of the ellipsoid’s short axis.
4. When the ellipsoids are meshed for contact purposes, the number of elements in the direction of
the ellipsoid’s short axis equals 2 . (2 . value-1). The number of elements in the direction of the
ellipsoid’s long axis is twice the number in the direction of the ellipsoid’s short axis.
690 MESHPLN
Mesh Density for Covering Rigid Planes
Remark
The default is sufficient in most cases.
MICRO 691
Micro-zoning Parameter
Defines the accuracy of the initial conditions in Eulerian elements, when using the geometrical
shape definition
Remarks
1. MICRO3 is the number of micro zones into which an element is subdivided during initial
condition generation.
2. The default MICRO = 10 results in material fractions as accurate as 0.001. If a higher accuracy is
required, a greater value for MICRO can be used, but the CPU time for the generation
increases rapidly.
3. Micro zoning is only used when the initial conditions of the Eulerian material are specified on a
TICEUL entry.
692 MINSTEP
Minimum Time Step
Defines the minimum time step that causes the analysis to terminate.
.
Remarks
1. When the elements become very distorted, in a poorly designed mesh for example, or when they
have endured a very large distortion, the time step may drop dramatically. The analysis continues,
however, and a lot of computer resources may be wasted. This option allows you to specify a
minimum time step that causes the analysis to terminate.
2. See Chapter 9: Running the Analysis, Terminating the Analysis for details on analysis termination.
MIXGAS 693
Controls Updating of Gas Fractions
Specifies whether the gas constants of the Euler material or of gas bags are updated based on the gas
composition and temperature.
Remarks
1. This parameter is only defined for use with GBAG gas bag definitions and/or the single-material
Euler solver.
2. This parameter can be used in conjunction with INFLATR, INFLATR1, INFLHYB, and INFLHYB1
inflator definitions and with PORHOLE, PERMEAB, PORFGBG, and PERMGBG
porosity definitions.
3. By default, PARAM,MIXGAS is set to YES if any INFLHYB, INFLHYB1, or INFLGAS entries
are present.
694 NASIGN
Echo Ignored Data Entries
Toggles the echo of valid MD Nastran and/or Dyna data entries that are ignored by Dytran.
Remarks
1. The echo of the ignored data entries is output to a file with the extension IGN.
2. Large input that originates from MD Nastran or Dytran may produce a large amount of output and
slow down the input processing.
NZEROVEL 695
Auto Constrain Failed Nodes
Set the velocity of a node to zero in case all attached elements have failed.
Remarks
1. This parameter applies only to nodes of Lagrangian elements.
2. Specifying NO reduces the CPU overhead time.
3. When the velocity of a node is set to zero, effectively the node is constraint, like an SPC or SPC1.
4. Special attention is necessary for the contact definition. If the failed node is not taken out of the
contact, it behaves as a rigid boundary constraint. Choose the appropriate METHOD for the
SLVACT entry on the CONTACT bulk data entry option.
696 OLDLAGTET
Use Collapsed Hexahedron Scheme for CTETRA
Activate the collapsed hexahedron scheme as default for lagrangian CTETRA elements
Remark
The current default integration scheme for Lagrangian CTETRA elements use linear tetrahedron FE one.
It is more consistent (in terms of accuracy) and efficient (both in memory and CPU time) compared with
the collapsed hexahedron scheme. The old scheme based on collapsed hexahedron with reduced
integration is deactivated. If the old scheme is activated, it is used as default. But, it is still possible to use
the new scheme for CTETRA by using separate PSOLID with IN = 1 and ISOP = 1 combination.
PARALLEL 697
Parallel Execution Information
The option allows you to gather information on the parallel section of Dytran.
Remarks
1. A summary on the parallel operation when using the shared-memory mode can be requested by
including a PARAM,PARALLEL,INFPAR,ON entry in the input file. This request is not
available in a restart of an analysis.
2. Currently, the information on the parallel sections is available for the shell solver only.
698 PLCOVCUT
Pressure Cut Off Time
Remark
See also the COUPLE and COUOPT Bulk Data entries.
PMINFAIL 699
Switches Failure at Spall Limit
Remarks
1. Lagrangian elements (CHEXA) that have a material definition with a failure model will fail when
the parameter is set to YES and the spall limit (minimum pressure) is reached, even when the other
failure criterion is not yet reached.
2. The spall limit is set on the PMINC entry. (See also the DMATentry).
700 RBE2INFO
Lists MATRIG and RBE2 Grid Points
The grid points attached to MATRIG and RBE2assemblies are listed to the output file.
Remarks
1. Any Eulerian element with a density less than RHOCUT is considered to be empty. All of its
variables are set to zero, and the equation of state is bypassed.
2. In the Eulerian transport calculation, if the material is flowing from element A to element B, and
a. If the density of element B after transport is less than RHOCUT, then no transport is done.
b. If the density of element A after transport is less than RHOCUT, then all of the mass is
transported to element B.
3. A reasonable value of RHOCUT is 1.E–5 times the initial density.
4. If only RHOCUT is defined, all Eulerian elements use the RHOCUT value as cutoff density. If
RHOCUT is omitted, all Eulerian elements use a cutoff density automatically set to 1.E–5 times a
characteristic density. For single-material Eulerian elements, this characteristic density is the
reference density.
702 RJSTIFF
Rigid-joint Stiffness
Remarks
1. The absolute stiffness of rigid joints is calculated automatically by Dytran. The stiffness of joints
is taken so that a stable solution is guaranteed. The stiffness calculation takes into account the fact
that a rigid body can be constrained by more than one joint.
2. This parameter can be used to increase or decrease the stiffness of the joints. Care must be taken
because too high a value may lead to an unstable calculation.
RKSCHEME 703
Runge-Kutta Time-Integration Scheme
Remarks
1. This parameter can only be used in combination with PARAM,LIMITER,ROE. The default
number of stages depends on the spatial accuracy of the solution scheme. One stage is used for
first order spatial accuracy, and three stages for second order spatial accuracy.
2. For more details on the Runge-Kutta time-integration scheme see Dytran Theory Manual,
Chapter 6: Standard Euler Solver.
704 ROHYDRO
Density Cut-Off Value
Remarks
1. Hydrodynamic, single-material Eulerian elements with a density less than ROHYDRO are
considered to be empty. All of the variables are set to zero, and the equation of state is bypassed.
2. In the Eulerian transport calculation, if the material is flowing from element A to element B, and
a. If the density of element B after transport is less than ROHYDRO, then no transport is done.
b. If the density of element A after transport is less than ROHYDRO, then all of the mass is
transported to element B.
3. By default, the cutoff density for hydrodynamic Eulerian elements is set to 1.E–5 times the
material reference density.
ROMULTI 705
Density Cut-Off Value
Remarks
1. Multimaterial Eulerian elements with a density less than ROMULTI are considered to be empty.
All of the variables are set to zero, and the equation of state is bypassed.
2. In the Eulerian transport calculation, if the material is flowing from element A to element B, and
a. If the density of a specific material in element B after transport is less than ROMULTI, no
transport is done.
b. If the density of a specific material in element A after transport is less than ROMULTI, all of
the mass of that material is transported to element B.
3. By default, the cut-off density is set for each material separately as 1.E–5 times the material
reference density.
706 ROSTR
Density Cut-Off Value
Defines the minimum density for single-material Eulerian elements with shear strength.
Remarks
1. Single-material Eulerian elements with shear strength with a density less than ROSTR are
considered to be empty. All of the variables are set to zero, and the equation of state is bypassed.
2. In the Eulerian transport calculation, if the material is flowing from element A to element B, and
a. If the density of element B after transport is less than ROSTR, then no transport is done.
b. If the density of element A after transport is less than ROSTR, then all of the mass is
transported to element B.
3. By default the cut-off density for Eulerian elements with shear strength is set to 1.E–5 times the
material reference density.
RSTDROP 707
Type of Elements Dropped at Restart
Defines the type of elements to be removed from the calculation when restarting an analysis.
Remarks
1. All elements of the specified type are removed from the calculation. It is not possible to drop a
part of a Eulerian or Lagrangian mesh.
2. If Lagrangian solids or membranes are dropped from a coupled calculation, the surfaces should
also be dropped to prevent surfaces being present that are not attached to anything.
3. The EULER option only works for a Eulerian mesh containing a single hydrodynamic material.
708 SCALEMAS
Mass Scaling Definition
Parameters
Defines the activation of mass scaling.
X
Remarks
1. Numerical mass is added to all Lagrangian solid, triangular, quadrilateral, rod, bar and beam
elements such that its time step never becomes less than:
dt = STEPFCT*DTMIN.
where
dt = timestep of calculation
STEPFCT = timestep safety factor (see PARAM,STEPFCT)
DTMIN = value specified on the PARAM,SCALEMAS entry
If the added mass of a certain element exceeds the maximum percentage (MXPERC) of its
original mass, no more mass will be added, and subsequently, the time step may decrease again.
2. The value of STEPS determines the checking frequency against the mass scaling criterion; the
check is done for every defined number of STEPS. STEPS = 1 is recommended.
3. The values for DTMIN, MXPERC, and STEPS are required input.
4. By requesting MSMASS in an output request, the ratio of scaled mass to original mass of the
elements can be retrieved. By making fringe plots of this parameter, a check can be made if mass
has not been added in a critical area.
5. See Dytran User’s Guide, Chapter 8: Prestress Analysis and Example Input Data, Mass Scaling
Definition for instructions on how to use this entry.
SHELLFORM 709
Sets the Default of the Shell Formulation
Sets the default for the shell formulation for quadrilateral elements.
Remarks
1. The PARAM,SHELLFORM changes the default formulation for quadrilateral shell elements. All
shell properties entries that do not explicitly define the formulation, use the default as specified
on the PARAM entry.
2. Triangular shell elements have only one formulation (C0-TRIA). Therefore, the PARAM is
ignored for triangular elements.
3. For more information, see also Dytran User’s Guide, Chapter 5: Application Sensitive
Default Setting.
710 SHELMSYS
Shell Element System Definition
Remarks
1. SIDE21 puts the x-axis along side21 of the element, whereas MIDSIDES puts the x-axis along
the vector connecting the midpoints of the side14 and side32.
2. Using the SIDE21 option for the BLT shell will result in the same Belytschko-Lin-Tsay
implementation as BELY.
SHPLAST 711
Type of Plane-Stress Plasticity for Shells
Specifies the type of calculation used to determine the plane-stress plasticity method for shells.
Remarks
1. The RADIAL approach does not require iterations and, therefore, is the most efficient. It is,
however, an approximation.
2. The other two approaches iterate to find the solution. ITER is the best since it takes as many
iterations as are necessary. On vector machines, such as CRAY, this is inefficient since it cannot
be vectorized. VECT always performs three vectorized iterations, which is more efficient.
However, three iterations may not be enough, and inaccuracies could occur.
3. For more information, see Dytran User’s Guide, Chapter 5: Application Sensitive Default Setting.
712 SHSTRDEF
Composite Shell Stress and Strain Output Definition
Specifies the default coordinate system for the stress and strain output of composite shells.
Remark
The default setting can be overruled per property on a PCOMPA entry on the STRDEF field.
SHTHICK 713
Shell-Thickness Modification Option
Specifies whether or not the thickness of the shell changes with membrane straining.
Remarks
1. The YES option gives a true large-strain shell but requires some extra computation.
2. The NO option should give adequate results as long as the membrane strains are not very large
(i.e., not more than 5–10%).
3. This option applies to all the formulations of the shell elements, except for the PCOMP. The
thickness of PCOMP shell elements will always remain constant.
4. For more information, see Dytran User’s Guide, Chapter 5: Application Sensitive Default Setting.
714 SLELM
Store Shell Sublayer Variables
Defines whether shell sublayer variables are to be stored in the element arrays.
Remarks
1. This parameter applies only to shell elements.
2. The shell sublayer variables are primarily stored in sublayer arrays. They can be copied into the
element arrays only for specific output purposes.
3. Specifying NO reduces the CPU overhead time.
4. Irrespective of the entry on this parameter, sublayer variables are accessible in the sublayer arrays.
For example, requesting TXX1 retrieves the stress from the element array, whereas TXX01
retrieves it from the sublayer arrays.
5. MD Nastran initialization always causes SLELM = YES.
SMP, ,BATCHSIZE 715
SMP Batchsize and CPULOOP Definition
Define batch size and number of CPU loops, per entity type.
PARAM,SMP,BEAMS,BATCHSIZE,AUTOMATIC
PARAM,SMP,BEAMS,BATCHSIZE,256
Remarks
1. The batchsize may be defined per entity type. The SMP parts of Dytran uses the batchsize to
assign a certain number of batches to each CPU. Example:
• Batchsize = 63 (default)
• Number of Beam elements = 580
• Number of CPUs = 4
As a results, Dytran:
• Needs to process 10 batches (9x63 + 1x13)
• To spread this evenly over four CPUs, Dytran increases this to 12 batches because then each
CPU can process 3 batches.
• As a result, the batch size is recalculated for 12 batches to: batchsize = 49
• This means that:
CPU# 1,2,3 process three batches of 49 elements each (3x3x49 = 441 elements)
CPU# 4 processes two batches of 49 elements and one batch of 41
716 SMP, ,BATCHSIZE
SMP Batchsize and CPULOOP Definition
It is clear that the user-defined batchsize may not be used ultimately. The reason for this is that
each CPU is allocated the same number of batches in order to optimize the work done by
each processor.
2. When the batchsize is set to AUTOMATIC, Dytran computes an initial batchsize based on the
number of batches processed by each CPU. By default, Dytran processes two batches per CPU.
In the example above, this means that based on:
• Batchsize = AUTOMATIC
• Number of batches per CPU = 2 (default)
• Number of Beam elements = 580
• Number of CPUs = 4
As a result, Dytran:
• Computes an initial batchsize of 72 (=580/(4*2))
• Increases this batchsize to a higher number to make sure the number of batches fits in the fixed
number of CPU’s: batchsize = 72 + (580 – 4*2*72) = 72 + 4 = 76 elements
• Based on this initial batchsize, the number of batches would be: 1 + (580-1)/76 = 8 batches
• This fits nicely on four CPU’s as expected
• The CPUs process:
CPU# 1,2,3 processes two batches of 76 elements each (3x2x76 = 456 elements)
CPU# 4 processes one batch of 76 elements and 1 batch of 48 elements.
3. By default, Dytran does not use the AUTOMATIC batchsize algorithm. Testing has shown that an
initial batchsize of 63 yields the fastest results. This may vary depending on the problem
simulated and the number of elements and may be worth adjusting.
The reason for this may be found in the fact, that with many elements in the model, the number
of elements per batch increases significantly when the AUTOMATIC batchsize algorithm is used.
Each CPU will have to process two batches (by default) with many elements. Based on the cache
memory, this is usually not optimal for a CPU processor. Shorter batchsizes (< 128) will do a
better job.
SMP, ,CPUINFO 717
SMP CPU Information
PARAM,SMP,CONTACT,CPUINFO,ON
PARAM,SMP,FSCOUP,CPUINFO,ON
Remark
By default, Dytran does not give any SMP CPU timings per entity. In order to judge the efficiency of the
different algorithms in Dytran, this parameter may be used to judge the speedup acquired by processing
on multiple CPUs.
718 SNDLIM
Sound Speed Minimum Value
Remarks
1. This parameter is used to avoid the possibility of division by zero in the time step calculation.
2. SNDLIM has the units of velocity.
SPHERSYM 719
Spherical Symmetric Analyses
Enables an efficient and accurate 1D spherical symmetric solution for Eulerian materials. A much larger
time step becomes possible by basing the time step only on the mesh-size in radial direction.
PARAM,SPHERSYM,RECT,X,2 PHI: 0
Remarks
1. Only available for Eulerian elements and does not support Lagrange elements. The effect of this
parameter is not limited to the solvers. Also Euler archives will reflect the modified Euler mesh
geometry.
2. The Euler mesh can already be symmetric but also a rectangular mesh comprising of one row of
elements can be used. Using the angle specified by PHI this Euler mesh is mapped into a 1D
spherical symmetric mesh.
3. The Euler mesh has to consist of one row of elements.
4. In the time step computation only the mesh-size in radial direction will be taken into account.
720 STEPFCT
Time Step Scale Factor
Remarks
1. The actual time step used in Dytran is the product of the internal time step and the time step
safety factor.
2. The default value works well in the majority of situations and gives an efficient solution while
maintaining a stable solution.
3. In a calculation with a coupling surface,FBLEND must be greater than or equal to STEPFCT to
avoid instabilities (see PARAM,FBLEND).
4. For many calculations, STEPFCT can be set to 0.9, unless you are running a problem that has
coupling surfaces defined.
5. A different parameter can be used to set the time step safety factor for Lagrangian elements (see
PARAM, STEPFCTL).
STEPFCTL 721
Time-step Scale Factor for Lagrangain Elements
Defines a scale factor to be used on the internally calculated time step of Lagrangian elements only.
Remarks
1. For many calculations, STEPFCTL can be set to 0.9
2. PARAM,STEPFCT can be used to set the time step safety factor for all elements (see
PARAM,STEPFCT). The default for STEPFCT is 0.666
3. The actual time step used in Dytran is the product of the internal time step and the time-step
safety factor. If STEPFCTL is used, the Lagrangian elements will use this value for the safety
factor. The Eulerian elements will still use STEPFCT. The timestep used in Dytran is the
minimum value of the two products. To this end, an efficient solution, while also maintaining a
stable solution, is achieved.
722 STRNOUT
Shell Sublayer Strain Output
Saves the total strains and equivalent effective stress (von Mises stress) at shell sublayers for output.
Remarks
1. A limited output set saves memory.
2. Perfectly elastic materials only have the limited output set.
3. Total strain output for shell composite materials can be requested from the PCOMPA Bulk
Data entry.
TOLCHK 723
Tolerance for Fast Coupling
Fast coupling requires that Euler elements are orthogonal. This means that normals of Euler element
faces have to be in a coordinate direction. In practice there can be small errors in the geometry of the
Euler element and Euler face normals do not always exactly point into a coordinate direction. Small
deviations from the coordinate direction do not give problems and are allowed by fast coupling.
To check the direction of an Euler face, the face normal vector is projected onto the closest coordinate
direction. If this projection is 1, the normal is exactly in the coordinate direction. When this projection is
within a sufficient small tolerance of 1, the face can be handled by fast coupling. The tolerance used is
TOLCHK. If the projection is smaller than 1-TOLCHK, the face cannot be handled by fast coupling and
the analysis terminates. Options are then to slightly increase TOLCHK , write out double precision format
in PATRAN, use general coupling, or use the MESH entry. Increasing TOLCHK too much can make the
coupling surface computation less accurate. To keep the computation accurate, the maximal allowed
value of TOLCHK is 1e-6. If PARAM,TOLCHK is not used, the tolerance used is 1e-14.
This parameter is a scale factor for the values of TOLPR1 of the CONTACT options that use
BPLANE option.
Remarks
1. This parameter is important for initialization of BPLANE contact. The faces of the contact surface
are enlarged with a value of TOLPR1. However, this might not be enough when the air bag is
offset folded. On the other hand, a large value of TOLPR1 might induce hooking. Therefore a new
parameter is introduced called TOLFAC. The value of TOLFAC scales the value of TOLPR1 only
at initialization, such that the contact is correctly found.
2. A correct value of TOLFAC can be up to 1000. or even higher.
UGASC 725
Universal Gas Constant
Remarks
1. This entry must be used if the molar weight is used on an INITGAS entry, or if molar gas fractions
are given on an IINFLFRAC entry.
2. Specify only one universal gas constant per problem.
3. In SI units, R equals 8.3145 J mol-1 K-1.
Using the tonne, mm, s system of units R has a value of 8314.5 tonne mm2 s-2 mol-1 K-1.
In imperial units, R equals 1.9859 Btu lbmol-1 ºR-1 or 1545.3 ft lbf lbmol-1 ºR-1.
726 VARACTIV
Activation or Deactivation of Grid-Point, Element, or Face Variables
Grid point, element, or face variables are activated or deactivated by the Bulk Data entry, as well as the
definition of new user variables. The name of the variable is redefined as well.
Remarks
1. The ALL entry activates all variables for all elements, regardless of whether they are used or not.
The ALLPRINT prints a summary of all element variables, regardless whether there are any
elements of a certain type or not. If ALL or ALLPRINT is entered, then no subsequent entries
are required.
2. All entries are required if ALL or ALLPRINT are not specified, except for newname, which
defaults to the original name.
3. When a variable is renamed, all subsequent references must be made to the new name; e.g., in
output requests.
4. The deactivate option is potentially dangerous, since some options may require the variable in an
indirect way. It is advised, therefore, not to deactivate standard Dytran variables.
5. This PARAM entry is a convenient way to introduce new variables to an entity, which can be used
in user subroutines. The new variables is written to restart files and can be requested for output.
6. See the EEXOUT e subroutine as an example of how to address a newly created variable.
7. In the print file of an Dytran run, a summary is given for all variables of the element types that are
used in the calculation (except when ALLPRINT was specified). The format of the printout is:
###-(CHAR)-NAME
where
### = the variable ident number when the variable is active. If the variable has been
deactivated, ### is printed as <~>
CHAR = N if the variable is standard Dytran
Remarks
1. The dynamic relaxation parameter is connected to the system natural frequency, , as = t ,
where denotes a percentage of critical damping. The damping occurs by factoring the velocities
every time step as follows:
F1 = 1 – 1 +
F2 = 1 1 +
n+12 n–12 n n
v = F1 v + F 2 a t
where v is the velocity, a is the acceleration, and is the dynamic relaxation parameter.
2. At the restart of an analysis with dynamic relaxation, the dynamic relaxation can be switched off
by PARAM,VDAMP or PARAM,VDAMP,OFF.
3. For a more comprehensive description of dynamic relaxation, see Dytran Theory Manual,
Chapter 4: Models, Dynamic Relaxation.
VELCUT 729
Velocity Cutoff
Remark
Any velocity less than VELCUT is set to zero. It is mainly used to eliminate harmless but annoying small
values of velocity caused by round-off error and numerical dispersion.
730 VELMAX
Maximum Velocity
Remarks
1. For Eulerian elements, VELMAX is applied to the velocity components separately. Therefore, the
magnitude of the velocity vector is limited to 3 VELMAX. For Lagrangian elements, all
components are scaled down by the same factor to ensure that the maximal magnitude of the
velocity vector does not exceed VELMAX.
2. Although it is not usually necessary to limit the velocity in Eulerian meshes, there are occasions,
in regions of near-vacuous flow for example, where specifying a maximum velocity can be
advantageous. The same applies to Lagrangian meshes, in contact regions for example. This
parameter should be used with care.
3. Because very high velocities occur mostly in Eulerian elements with very small mass, the mass
in these elements can be removed to keep the analysis stable. This option is not available for
Lagrangian solid elements.
4. VELMAX must be greater than the minimum velocity specified by PARAM,VELCUT.
VISCOPLAS 731
Use Overstress Formula to Update Strain-rate Dependent Plasticity
Activate the overstress formula to update strain-rate dependent plasticity. This formula is normally used
for viscous-plastic material.
Remarks
1. The strain rate dependent plasticity is normally calculated by scaling up the basic yield stress
without strain rate effect. Then the trial stresses are mapped back to the scaled-up yield surface.
This algorithm may lead to premature instability. Another technique is to calculate the so-called
viscous-plastic strain rate using “overstress” formula. And then the stresses are updated based on
this viscous-plastic strain. This technique seems to be more stable then the previous one. For shell
elements, this option works when combined with PARAM,SHPLAST,RADIAL. Only
DYMAT24 and Johnson-Cook models are supported. For solid elements, this option works only
for DYMAT24.
2. For shell elements, PARAM,VISCOPLAS,1, in combination with
PARAM,SHPLAST,RADIAL, will use consistent plane stress plasticity algorithm both for
strain rate dependent and independent plasticity. This new algorithm is more accurate than
3-D approach.
732 VISCOPLAS
Use Overstress Formula to Update Strain-rate Dependent Plasticity
Chapter 7: User Subroutines
Dytran Reference Manual
7 User Subroutines
EEXOUT 739
EXALE 743
EXBRK 746
EXCOMP 748
EXCOMP1 755
EXELAS 767
EXEOS 770
EXEOS1 775
EXFAIL 779
EXFAIL1 781
EXFAIL2 785
EXFLOW 788
EXFLOW2 791
EXFUNC 795
EXINIT 797
EXPBAG 800
EXPLD 802
EXPOR 803
EXPOR2 809
734 Dytran Reference Manual
EXSHR 813
EXSPR 816
EXTLU 819
EXTVEL 821
EXVISC 823
EXYLD 826
EXYLD1 829
GEXOUT 834
Chapter 7: User Subroutines 735
Overview
Overview
User-written subroutines are a powerful feature in Dytran that allow you to customize the program to
your particular needs and provide capabilities that are not possible with the standard program.
The following user subroutines may be used:
The user-written subroutines are very simple to use. Some knowledge of Fortran programming is
required to write the subroutine, but the incorporation of the routines into Dytran is automatic on most
computers. Any Dytran user with a working knowledge of Fortran should not have problems using this
facility. Dytran uses a Fortran 90 compiler and there is no guarantee that another Fortran complier version
will link properly.
Care should be exercised when using user-written subroutines, however. It is possible to corrupt the data
stored within Dytran, rendering the results meaningless. User subroutines should be used only if you are
experienced in the use of Dytran and fully understand the implications of what you are doing.
736 Dytran Reference Manual
Overview
RETURN
END
Calling Sequence
CALL EEXOUT (NAME, LENNAM, NEL, CEL, NETYPE, LIEL, LXEL)
Input
NAME Character string. Output name specified on the ELEXOUT entry.
LENNAM Integer variable. Length of NAME.
NEL (*) Integer array. Element number.
CEL (*) Character *8 array. Unused.
NETYPE Integer variable. Type of element:
2 One-dimensional element
3 Triangular shell
4 Quadrilateral shell
5 Triangular membrane
6 Dummy triangle
7 Dummy quadrilateral
8 Lagrangian solid
9 Eulerian solid (hydrodynamic)
10 Eulerian solid (with strength)
11 Eulerian solid (multimaterial)
LIEL(*) Integer array
Base address of element in the main integer storage array ILGDAT
LXEL(*) Integer array
Base address of element in the main real storage array XLGDAT
Remarks
1. This subroutine must be included if there are any ELEXOUT Case Control commands.
2. The subroutine can be used to calculate results based on the data available in Dytran.
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
740 EEXOUT
User-defined Element Output
4. This subroutine is vectorized. All the input data is stored in arrays that must be dimensioned. The
start and end of the arrays are given by the variables LST and LFIN in the common block
/MSCD_LOCLOP/. All of the entries in the arrays between LST and LFIN must be output. See
the following examples.
Example 1
This example calculates the magnitude of the velocity in Eulerian elements and stores the result in the
user variable EXUSER2.
SUBROUTINE EEXOUT
+(NAME, LENNAM, NEL, CEL, NETYPE, LIEL, LXEL)
*
IMPLICIT DOUBLE PRECISION (A-H, O-Z)
*
DIMENSION NEL (*), LIEL (*), LXEL (*)
CHARACTER *(*) CEL (*), NAME
*
COMMON/MSCD_LOCLOP/LST, LFIN
COMMON/MSCD_ILGMEM/IDUM1,IDUM2,IDUM3,IDUM4,ILGDAT(1)
COMMON/MSCD_XLGMEM/XLGDAT(1)
*
IF (NETYPE.NE.9) GOTO 9900
*
*The magnitude of the velocity of the Eulerian elements is computed
*and stored in the user variable EXUSER2
*
DO 100 NZ = LST, LFIN
XVEL = XLGDAT (LXEL (NZ)+1)
YVEL = XLGDAT (LXEL (NZ)+2)
ZVEL = XLGDAT (LXEL (NZ)+3)
VEL = XVEL*XVEL + YVEL*YVEL + ZVEL*ZVEL
XLGDAT (LXEL (NZ) + 25) = SQRT (VEL)
*
100 CONTINUE
*
9900 RETURN
END
Example 2
This example shows how the shell element sublayer data can be retrieved from memory to organize
user-defined editing. The example applies to any shell element either defined by a PSHELLn or
PCOMPn entry.
SUBROUTINE EEXOUT
+(EDTNAM,LENNAM,NZONE,CZONE,NZTYPE,LBIZON,LBXZON)
*
* single or double defined below
IMPLICIT DOUBLE PRECISION (A-H,O-Z)
*
DIMENSION NZONE(*),LBIZON(*),LBXZON(*)
CHARACTER*(*) EDTNAM
EEXOUT 741
User-defined Element Output
CHARACTER*(*) CZONE(*)
*
COMMON /MSCD_LOCLOP/ LST,LFIN
COMMON /MSCD_NCYVAR/ IDUM1,NCYCLE
COMMON /MSCD_XCYVAR/ RDUM1,RDUM2 ,RDUM3,RDUM4,RDUM5,TIME
*
CHARACTER*16 CVAR
DIMENSION CVAR(6)
*
DIMENSION XVAR(1024)
DIMENSION DATA(5,1024,6)
*
LOGICAL LHERE
*
DATA LHERE /.TRUE./
*
* Define the sublayer output here by variable name
*
CVAR(1) = ’TXX’
CVAR(2) = ’TYY’
CVAR(3) = ’TXY’
CVAR(4) = ’FAIL’
CVAR(5) = ’EXY’
CVAR(6) = ’MXTFI’
*
*********************************************************************
*
* Make a loop over the sublayers, variables
* The routine will retrieve the variable from the designated
* sublayer for the entire string of elements in one call
* The data array will contain all requested data after the
* loops over the sublayers and the variables requested
*********************************************************************
*
*
* Loop over the sublayers
*
DO 300 ISUB = 1,5
*
* Loop over the variables
*
DO 200 NVAR = 1,6
*
* Call a predefined user routine
*
CALL GET_ELEMENT_SUBL_VARS
+ (NZONE,XVAR,CVAR(NVAR),ISUB)
*
* Arguments: element list, float data list, variable name
list,
* and sublayer number
*
* Make a loop over the elements in the edit list
*
742 EEXOUT
User-defined Element Output
DO 100 NZ = LST,LFIN
*
* Store all data for the list in the data array
*
DATA(ISUB,NZ,NVAR) = XVAR(NZ)
*
100 CONTINUE
200 CONTINUE
300 CONTINUE
*
* If we come here for the first time write the header
*
IF (LHERE) THEN
OPEN(UNIT=90,FILE=’SUBLAYERS’,STATUS=’UNKNOWN’)
WRITE(90,’(9A)’,IOSTAT=IOS)
+ ’ Time ’,
+ ’ Element ’,
+ ’ Sublayer ’,
+ ’ Txx ’,
+ ’ Tyy ’,
+ ’ Txy ’,
+ ’ Fail ’,
+ ’ Exy ’,
+ ’ Mxtfi ’
*
* And a dummy line
*
WRITE(90,’(A)’) ’ ’
LHERE = .FALSE.
ENDIF
*
* Write it all to a file
*
DO 400 ISUB=1,5
DO 500 NZ=LST,LFIN
NZON = NZONE(NZ)
WRITE(90,’(E15.8,2I15,6E15.8)’,IOSTAT=IOS)
+ TIME,NZON,ISUB,(DATA(ISUB,NZ,NVAR),NVAR=1,6)
500 CONTINUE
400 CONTINUE
*
9900 CONTINUE
*
RETURN
END
EXALE 743
User-defined ALE Grid Point Motion
Calling Sequence
CALL EXALE (CNAME, LENNAM, TIME, NCYCLE, ISTART, IEND,
+ IUSER, XPOS, YPOS, ZPOS, XVG, YVG, ZVG)
Input
CNAME Character string
Name specified on the ALEGRID entry
LENNAM Integer variable
Length of CNAME
TIME Real variable
Time at the current time step
NCYCLE Integer variable
Number of the current time step
ISTART, IEND Integer variables
Grid-point loop counters
IUSER(*) Integer array
Grid-point numbers
XPOS(*), Real arrays
YPOS(*), Grid-point coordinates in basic coordinate system
ZPOS(*)
XVG(*), Real arrays
YVG(*), Grid-point velocity components during last time step
ZVG(*)
Output
XVG(*), Real arrays
YZG(*), Grid-point velocity components for current time step
ZVG(*)
Remarks
1. This subroutine must be included if there are any ALEGRID entries with the TYPE set to USER.
2. The subroutine is used to calculate the grid-point motion in an ALE calculation according to a
user-specified prescription.
744 EXALE
User-defined ALE Grid Point Motion
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
4. This routine is part of a vectorized process. As a result, the routine can be called more than once
per time step.
Example
SUBROUTINE EXALE( CNAME,LENNAM,TIME,NCYCLE,ISTART,IEND,
+ IUSER,XPOS,YPOS,ZPOS,XVG,YVG,ZVG )
*
* single or double defined below
IMPLICIT DOUBLE PRECISION (A-H,O-Z)
*
* declare argument as arrays and data-type here....
CHARACTER*(*) CNAME
*
* ---------------------------------------------------------------
*
* cname = name of the exale definition
* lennam = length of the character string
* time = current problem time
* ncycle = current time step number
* istart = start of the grid point loop
* iend = end of the grid point loop
* iuser = array with grid point user numbers
* xpos = x-position of the list of grid points
* ypos = y-position of the list of grid points
* zpos = z-position of the list of grid points
* xvg = x-velocity of the list of grid points
* yvg = y-velocity of the list of grid points
* zvg = z-velocity of the list of grid points
*
* ---------------------------------------------------------------
*
*
* local dimensions and declarations
*
DIMENSION IUSER(*)
DIMENSION XPOS(*),YPOS(*),ZPOS(*)
DIMENSION XVG(*) ,YVG(*) ,ZVG(*)
*
* data statements
*
* statement functions
*
* executable statements
*
FACTOR = 1.51
X = 18.02775637
*
* compute cosine and sine for this cycle
RXCOS = X*COS(FACTOR*TIME)
RXSIN = X*SIN(FACTOR*TIME)
*
EXALE 745
User-defined ALE Grid Point Motion
The EXBRK user subroutine defines the failure criterion or criteria for a breakable join between pairs of
grid points.
Calling Sequence
CALL EXBRK(TIME, ICYCLE,NMSETS,ILIST,IFAIL,CSETNM,
+ FX1,FY1,FZ1,FX2,FY2,FZ2,
+ XM1,YM1,ZM1,XM2,YM2,ZM2,
+ FAIL1,FAIL2,FAIL3,FAIL4,FAIL5,FAIL6,
+ ICONN1,ICONN2)
Input
TIME Real Variable. Current time in computation.
ICYCLE Integer variable. Current time-step number.
NMSETS Integer variable. Number of “bjoin” pairs in the current user-defined string.
ILIST Integer array. Contains the set numbers of the “bjoin” pairs in the string.
CSETNM Character array. Contains the name of the user-defined criterion for the
“bjoin” pair.
FX1,FY1,FZ1 Real arrays. Contain the force components of the first grid point of the
“bjoin” pairs.
FX2,FY2,FZ2 Real arrays. Contain the force components of the second grid point of the
“bjoin” pairs.
XM1,YM1,ZM1 Real arrays. Contain the moment components of the first grid point of the
“bjoin” pairs.
XM2,YM2,ZM2 Real arrays.Contain the moment components of the second grid point of the
“bjoin” pairs.
ICONN1,ICONN2 Integer arrays. Contain connectivity data for the first and the second grid point
of the “bjoin” pairs. Data concerns the grid point user number, the number of
connected elements, and the connected element user numbers.
Output
IFAIL Integer array. Global failure flag for the “bjoin” pairs.
FAIL1-FAIL6 Real arrays. Contain the component failure flags for the “bjoin” pairs. The data
is used for degradation of the join. Forces and moments are multiplied by
these values.
EXBRK 747
User-defined Failure of Breakable Joins
Remarks
1. This subroutine must be included if there are any references to the EXBRK in the input data file.
2. The subroutine is called every time step. The forces and moment on the grid points of the “bjoin”
pairs are passed to the subroutine. You must return the global failure flag and the component
failure switches. Dytran uses them upon return from the subroutine.
3. There can be more than one failure criterion defined in the EXBRK subroutine. The criteria can be
distinguished by their user-defined names.
Example
This subroutine defines a failure criterion on the force x-components.
SUBROUTINE EXBRK
+ (TIME,ICYCLE,NMSETS,ILIST,IFAIL,CSETNM,
+ FX1,FY1,FZ1,FX2,FY2,FZ2,
+ XM1,YM1,ZM1,XM2,YM2,ZM2,
+ ICONN1,ICONN2 )
*
#include "spdbl"
*
DIMENSION ILIST(*),IFAIL(*)
DIMENSION ICONN1(8,*),ICONN2(8,*)
DIMENSION FX1(*),FY1(*),FZ1(*)
DIMENSION FX2(*),FY2(*),FZ2(*)
DIMENSION XM1(*),YM1(*),ZM1(*)
DIMENSION XM2(*),YM2(*),ZM2(*)
DIMENSION FAIL1(*),FAIL2(*),FAIL3(*)
DIMENSION FAIL4(*),FAIL5(*),FAIL6(*)
CHARACTER*8 CSETNM(*)
*
FMAX = 12000.0 ** 2
DO 100 N=1,NMSETS
NPAIR = ILIST(N)
IF (IFAIL(NPAIR).EQ.0) GOTO 100
DFX = (FX1(NPAIR)-FX2(NPAIR))**2
IF (CSETNM(N).EQ.’CRIT_1’) THEN
IFAIL(NPAIR) = 0
WRITE(6,*)
+ ‘Grid point pair (Point 1 =’,ICONN1(1,N),
+ ‘Point 2 = ‘,ICONN2(1,N),’) Failure.’
ENDIF
CONTINUE
RETURN
END
748 EXCOMP
User-defined Orthotropic Failure Model
Calling Sequence
CALL EXCOMP (CNAME, YMX, YMY, XNUY, SXY, SYZ, SZX,
+ FBTEN, FBCOM, XMXTEN, XMXCOM, SHRF, CAPA, XMAT,
+ TIME, NSTEP, IPREC, LAST, NADVAR, ISUBLY, LBUSER,
+ DLTH, SIG1, SIG2, SIG4, SIG5, SIG6, D1, D2, D3,
+ D4, D5, D6, DOUT1, DOUT2, DOUT4, EFAIL, EFT, EFC,
+ ESF, EMT, EMC, Q1, Q2, FAIL, FAIL2, USRVAR)
Input
CNAME Character string. Material name.
YMX Real variable. Young’s modulus in fiber direction.
YMY Young’s modulus in matrix direction
XNUY Poisson’s ratio v yx
SXY In-plane shear modulus
SYZ Transverse shear modulus
SZX Transverse shear modulus
FBTEN Fiber tensile strength
FBCOM Fiber compressive strength
XMXTEN Matrix tensile strength
XMXCOM Matrix compressive strength
SHRF Shear strength
CAPA Shear correction factor
XMAT Extra material data
TIME Current problem time
NSTEP Step number
IPREC Single/double precision check:
1 = library is single precision.
2 = library is double precision.
LAST Length of element string
NADVAR Number of additional variables (see MAT8 Bulk Data)
EXCOMP 749
User-defined Orthotropic Failure Model
Input
ISUBLY Sublayer number
LBUSER List of pointers to the user variables
DLTH Time step
SIG1 Sigma xx in fiber system
SIG2 Sigma yy in fiber system
SIG4 Sigma xy in fiber system
SIG5 Sigma yz in fiber system
SIG6 Sigma zx in fiber system
D1 Strain increment xx
D2 Strain increment yy
D3 Strain increment zz
D4 Shear angle = 2.0 strain increment xy
D5 Strain increment yz
D6 Strain increment zx
DOUT1 Total xx-strain for output
DOUT2 Total yy-strain for output
DOUT4 Total xy-strain for output
EFAIL User fail switch
EFT User fail switch
EFC User fail switch
ESF User fail switch
EMT User fail switch
EMC User fail switch
Q1 Fiber axis relative to element system
Q2 Matrix axis
USRVAR User variable
Output
New Stresses
SIG1 Sigma xx in fiber system
SIG2 Sigma yy in fiber system
SIG4 Sigma xy in fiber system
SIG5 Sigma yz in fiber system
SIG6 Sigma zx in fiber system
750 EXCOMP
User-defined Orthotropic Failure Model
Output
Fail Switches
FAIL Overall element fail switch
FAIL2 One-dimensional element time step suppression
Remarks
1. This subroutine must be included if USER is specified on the FT field on the MAT8A Bulk
Data Entry.
2. The subroutine returns the stress tensor and failure flags.
3. Failure flags FAIL and FAIL2 are used by Dytran to zero out the hourglass forces and to enforce
time step skipping for “1D elements” (if requested).
4. The total strains are supplied only if requested on the PCOMPA entry. Do not use the total strains
when they are turned off.
5. Additional sublayer variables are only available when requested on the PCOMPA entry. The
pointers LBUSER are set to a large value if the variables are not defined.
6. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
7. If IPREC = 1, the Dytran object library is single precision; if IPREC = 2, it is double precision.
8. If your input refers to EXCOMP on a MAT8A entry and the material number (MID) is set to
99999999, the demo example will run.
9. EXCOMP does not necessarily need to define a composite material. Any material model can be
programmed. EXCOMP is used for each sublayer on the PCOMPA Bulk Data entry that refers to it.
10. In XMAT, extra material data from the MAT8A option is available.
PFD = nint( MATE(32 ):1 = STEPS
2 = TIME
3 = VELOC
VALUE = XMAT(33)
Example
This subroutine swaps the stresses into the user variables:
SUBROUTINE EXCOMP
+ ( CNAME , YMX , YMY , XNUY , SXY , SYZ , SZX ,
+ FBTEN , FBCOM , XMXTEN , XMXCOM , SHRF ,
+ CAPA , XMAT , TIME , NSTEP , IPREC ,
+ LAST , NADVAR , ISUBLY , LBUSER ,DLTH ,
+ SIG1 , SIG2 , SIG4 , SIG5 , SIG6 ,
+ D1 , D2 , D3 , D4 , D5 , D6 ,
+ DOUT1 , DOUT2 , DOUT4 , EFAIL ,
+ EFT , EFC , ESF , EMT,EMC, Q1, Q2 ,
+ FAIL , FAIL2 , USRVAR )
*
EXCOMP 751
User-defined Orthotropic Failure Model
Calling Sequence
CALL EXCOMP1 (CNAME, LENVEC, ISHRPR,
+ YMX, YMY, XNUY, SXY, SYZ, SZX,
+ XT, XC, YT, YC, SC,
+ CAPA, CM,TIME, NCYCLE, IPREC,,
+ LAST, NADVAR, ISUBLY, LBUSER,DLTH,
+ SIG1, SIG2, SIG4,
+ SIG5, SIG6, SIG51, SIG62,
+ D1, D2, D3, D4, D5, D6, D87, D8,
+ DOUT1, DOUT2, DOUT4,
+ EFT, EFC,ESF, EMT, EMC, Q1, Q2,
+ EINC,FACP,
+ FAIL, FAILNM1, EFAIL, FAIL2 , USER,
+ EFIB, EMTX, ESHR)
Input
CNAME Material name (character).
LENVEC Vector Length
ISHRPR Shear property
YMX Young’s modulus in fiber direction.
YMY Young’s modulus in matrix direction
XNUY Poisson’s ratio v yx
SXY In-plane shear modulus
SYZ Transverse shear modulus
SZX Transverse shear modulus
XT Fiber tensile strength
XC Fiber compressive strength
YT Matrix tensile strength
YC Matrix compressive strength
SC Shear strength
756 EXCOMP1
User-defined Orthotropic Failure Model that allows to model Property Degradation
Input
CAPA Shear correction factor
CM Extra material data
TIME Current problem time
NCYCLE Step number
IPREC Single/double precision check:
1 = library is single precision.
2 = library is double precision.
LAST Length of element string
NADVAR Number of additional variables (see MAT8A Bulk Data)
ISUBLY Sublayer number
LBUSER List of pointers to the user variables
DLTH Time step
SIG1 Sigma xx in fiber system
SIG2 Sigma yy in fiber system
SIG4 Sigma xy in fiber system
SIG5 Sigma yz in fiber system
SIG6 Sigma zx in fiber system
SIG51
SIG62
D1 Strain increment xx
D2 Strain increment yy
D3 Strain increment zz
D4 Shear angle = 2.0 strain increment xy
D5 Strain increment yz
D6 Strain increment zx
D7
D8
DOUT1 Total xx-strain for output
DOUT2 Total yy-strain for output
DOUT4 Total xy-strain for output
EFAIL User fail switch
EFT User fail switch
EFC User fail switch
EXCOMP1 757
User-defined Orthotropic Failure Model that allows to model Property Degradation
Input
ESF User fail switch
EMT User fail switch
EMC User fail switch
Q1 Fiber axis relative to element system
Q2 Matrix axis
EINC For transverse shear correction
FACP For transverse shear correction
EFIB Property degradation fiber mode
EMTX Property degradation matrix mode
ESHR Property degradation shear mode
USER User variable
Output
New Stresses
SIG1 Sigma xx in fiber system
SIG2 Sigma yy in fiber system
SIG4 Sigma xy in fiber system
SIG5 Sigma yz in fiber system
SIG6 Sigma zx in fiber system
Fail Switches
EFAIL User fail switch
FAIL Overall element fail switch
FALNM1
FAIL2 One-dimensional element time step suppression
Remarks
1. This subroutine must be included if USER is specified on the FT field on the MAT8A Bulk
Data Entry.
2. The subroutine returns the stress tensor and failure flags.
3. Failure flags FAIL and FAIL2 are used by Dytran to zero out the hourglass forces and to enforce
time step skipping for “1D elements” (if requested).
4. The total strains are supplied only if requested on the PCOMPA entry. Do not use the total strains
when they are turned off.
5. Additional sublayer variables are only available when requested on the PCOMPA entry. The
pointers LBUSER are set to a large value if the variables are not defined.
758 EXCOMP1
User-defined Orthotropic Failure Model that allows to model Property Degradation
6. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
7. If IPREC = 1, the Dytran object library is single precision; if IPREC = 2, it is double precision.
8. If your input refers to EXCOMP on a MAT8A entry and the material number (MID) is set to
99999999, the demo example will run.
9. EXCOMP does not necessarily need to define a composite material. Any material model can be
programmed. EXCOMP is used for each sublayer on the PCOMPA Bulk Data entry that refers to it.
10. In XMAT, extra material data from the MAT8A option is available.
PFD = nint( MATE(32 ):1 = STEPS
2 = TIME
3 = VELOC
VALUE = XMAT(33)
Example
*
PARAMETER( NERM= 3 )
DIMENSION IERM(NERM)
DATA (IERM(I),I=1,NERM) /NERM*0/
*
#include "call_hello"
*
****************************************************
*
IF (LAST.GT.256) THEN
*-----error_message_start_1
if ( ierm ( 3 ) .ge. 0 ) then
*-----error_message_end_1..
WRITE(CERMSG,'(2A,I8)',IOSTAT=IOS)
+ 'EXCOMP:INSUFFICIENT MEMORY ALLOCATION',
+ '/INCEASE SIZE TO',LAST
CALL ERMESG( CSUBNM,1,IERM,CSUB06, 3)
*-----error_message_start_2
endif
*-----error_message_end_2..
ENDIF
*
IF ( CNAME.NE.'99999999' ) THEN
*-----error_message_start_1
if ( ierm ( 1 ) .ge. 0 ) then
*-----error_message_end_1..
WRITE(CERMSG,'(A,A)',IOSTAT=IOS)
+ 'A USER SUPPLIED ROUTINE EXCOMP IS MISSING',
+ '/FOR DEMO VERSION, SET MATID TO 99999999'
CALL ERMESG( CSUBNM,4,IERM,CSUB06, 1)
*-----error_message_start_2
endif
*-----error_message_end_2..
ELSE
*-----error_message_start_1
if ( ierm ( 2 ) .ge. 0 ) then
*-----error_message_end_1..
WRITE(CERMSG,'(A)',IOSTAT=IOS)
+ 'USING EXAMPLE VERSION OF EXCOMP1'
CALL ERMESG( CSUBNM,1,IERM,CSUB06, 2)
*-----error_message_start_2
endif
*-----error_message_end_2..
ENDIF
*
IF1DDT = 0
IFMSFL = NINT ( CM(12) )
MX = 0
ALP =CM(MX+30)
D13 =CM(MX+22)
D23 =CM(MX+23)
*
* the derivative of the non-linear eq
* produces 3*alp
762 EXCOMP1
User-defined Orthotropic Failure Model that allows to model Property Degradation
AP3 =THREE*ALP
AP34=.75*ALP
OD2G=.5/SXY
*
* derived values
XTSQI =ONE/(XT*XT)
YTSQI =ONE/(YT*YT)
SCSQ =SC*SC
SD2 =QUART/SCSQ
*
XMLT1=ONE/(SCSQ*(OD2G+AP34*SCSQ))
XMLT2=(YC*YC*SD2-ONE)/YC
*
* post failure theory
IPOST = NINT( CM(32) )
XPOST = CM(33)
*
* property degaradation rules
TRNSFL = CM(13)
*
* checks done only at first step
*
* make sure we have the strain output on and 6
* defined user variables
*
* failure theory for tentative stress update
*
* set the material constants appropraite to the failure
* flags last time
*
* ef = tensile failure in a-dir
* ec = comp failure in a-dir
* em = tensile failure in b-dir
* ed = comp failure in b-dir
* es = plain shear failure
* efail = complete element failure
*
* zero is failure , one is not
DO 40 I = 1,LAST
IF ( EFT(I).GT.ZERO ) THEN
EF(I) = ONE
ELSE
EF(I) = ZERO
ENDIF
IF (EFC(I).GT.ZERO ) THEN
EC(I) = ONE
ELSE
EC(I) = ZERO
ENDIF
IF ( EMT(I).GT.ZERO ) THEN
EM(I) = ONE
ELSE
EM(I) = ZERO
ENDIF
EXCOMP1 763
User-defined Orthotropic Failure Model that allows to model Property Degradation
IF ( EMC(I).GT.ZERO ) THEN
ED(I) = ONE
ELSE
ED(I) = ZERO
ENDIF
IF ( ESF(I).GT.ZERO ) THEN
ES(I) = ONE
ELSE
ES(I) = ZERO
ENDIF
40 CONTINUE
*
XNUX = XNUY * YMX/YMY
DO 41 I = 1,LAST
EX(I) = YMX * EF(I)*EC(I)
EY(I) = YMY * EF(I)*EM(I)*ED(I)
PRX(I) = XNUX * EF(I)*EC(I)*EM(I)*ED(I)
GXY(I) = SXY * EF(I)*ES(I)
PXY(I) = ONE/(ONE - XNUY*PRX(I) )
41 CONTINUE
*
* update to a tentative stress state
DO 50 I = 1,LAST
C11=PXY(I)*EX(I)
C12=PXY(I)*PRX(I)*EY(I)
C22=PXY(I)*EY(I)
C44=GXY(I)/( ONE + AP3*GXY(I)*SIG4(I)*SIG4(I) )
* d3(i) =-(d13*d1(i)+d23*d2(i))
STG1(I)=SIG1(I)+C11*D1(I)+C12*D2(I)
STG2(I)=SIG2(I)+C12*D1(I)+C22*D2(I)
STG4(I)=SIG4(I)+C44*D4(I)
SG42(I)=STG4(I)*STG4(I)
* check and the formula is ok (although terrible fumbled)
SG44(I)=XMLT1*SG42(I)*(OD2G+AP34*SG42(I))
EF2(I) = -ONE
EC2(I) = -ONE
EM2(I) = -ONE
ED2(I) = -ONE
ES2(I) = -ONE
50 CONTINUE
*
*------------failure-
*
* tsai-hill
XTMAX = MAX( XT,XC )
XTMXSI = ONE/(XTMAX*XTMAX)
YTMAX = MAX( YT,YC )
YTMXSI = ONE/(YTMAX*YTMAX)
DO 110 I = 1,LAST
EF2(I) = XTMXSI*STG1(I)**2 - XTMXSI*STG1(I)*STG2(I) +
+ YTMXSI*STG2(I)**2 + SG42(I)/SCSQ - ONE
EC2(I) = EF2(I)
EM2(I) = EF2(I)
ED2(I) = EF2(I)
764 EXCOMP1
User-defined Orthotropic Failure Model that allows to model Property Degradation
ES2(I) = EF2(I)
110 CONTINUE
*
* update the failure flags
*
DO 55 I = 1,LAST
EFT(I) = EF(I)*MAX(ZERO,-EF2(I))
EFC(I) = EC(I)*MAX(ZERO,-EC2(I))
EMT(I) = EM(I)*MAX(ZERO,-EM2(I))
EMC(I) = ED(I)*MAX(ZERO,-ED2(I))
ESF(I) = ES(I)*MAX(ZERO,-ES2(I))
*
EF(I) =EF(I)*(HALF-SIGN(HALF,EF2(I)))
EM(I) =EM(I)*(HALF-SIGN(HALF,EM2(I)))
ED(I) =ED(I)*(HALF-SIGN(HALF,ED2(I)))
EC(I) =EC(I)*(HALF-SIGN(HALF,EC2(I)))
ES(I) =ES(I)*(HALF-SIGN(HALF,ES2(I)))
55 CONTINUE
*
* set the overall failure flags if the whole layer has failed
* note that this is reduced from 1 (not failed) to 0 (failed) over
* 100 timesteps to get a smooth failure (the stress are scaled by
* this value)
*
DO 65 I = 1,LAST
EX(I) = YMX * EF(I)*EC(I)
EY(I) = YMY * EF(I)*EM(I)*ED(I)
PRX(I) = XNUX * EF(I)*EC(I)*EM(I)*ED(I)
GXY(I) = SXY * EF(I)*ES(I)
PXY(I) = ONE/(ONE - XNUY*PRX(I) )
65 CONTINUE
*
DO 80 I = 1,LAST
EF2(I) = MAX( EX(I) , EY(I) , PRX(I) , GXY(I) )
IF ( EF2(I) .NE. ZERO ) THEN
EF2(I) = ONE
ENDIF
80 CONTINUE
*
* 1d situations take away the time step
IF ( IF1DDT.EQ.1 ) THEN
DO 81 I = 1,LAST
XFIB = MAX( GXY(I) , EX(I) )
XMTX = MAX( GXY(I) , EY(I) )
FAIL3 = XFIB*XMTX
IF ( FAIL3 .GT. ZERO ) THEN
FAIL3 = ONE
ELSE
FAIL3 = ZERO
ENDIF
FAIL2(I) =MAX(FAIL3,FAIL2(I))
81 CONTINUE
ENDIF
*
EXCOMP1 765
User-defined Orthotropic Failure Model that allows to model Property Degradation
*
* transverse shear stresses
TOTFL = TRNSFL * FALNM1(I)
TRFAIL = MAX ( TOTFL , EFAIL(I) )
SIG5(I) = TRFAIL*SIG5(I)
SIG6(I) = TRFAIL*SIG6(I)
7010 CONTINUE
*
ELSE
DO 7011 I = 1,LAST
SIG1(I) = EFAIL(I)*SIG1(I)
SIG2(I) = EFAIL(I)*SIG2(I)
SIG4(I) = EFAIL(I)*SIG4(I)
*
* transverse shear stresses
TOTFL = TRNSFL * FALNM1(I)
TRFAIL = MAX ( TOTFL , EFAIL(I) )
SIG5(I) = TRFAIL*SIG5(I)
SIG6(I) = TRFAIL*SIG6(I)
7011 CONTINUE
ENDIF
*
* for both failure modes , transverse fail is same
IF ( ISHRPR.EQ.2 ) THEN
DO 7012 I = 1,LAST
* fail the transverse correction stress
TOTFL = TRNSFL * FALNM1(I)
TRFAIL = MAX ( TOTFL , EFAIL(I) )
SIG51(I) = TRFAIL*SIG51(I)
SIG62(I) = TRFAIL*SIG62(I)
7012 CONTINUE
ENDIF
*
*
#include "call_byebye"
*
RETURN
END
EXELAS 767
User-defined CELAS1 Spring Element
Calling Sequence
CALL EXELAS (N, M, IX, IC, PROP, HISV, FORCEO, C, DI,
+ V, A, UREL, DUREL, VREL, XMASS, FORCE, STIFF)
Input
N Integer variable
Element number
M Integer variable
Property number
IX(2) Integer array
Connectivity:IX(1) = grid point at end 1
IC(2) Integer array.
Component:IC(1) = component at end 1 (between 1 and 6)
IC(2) = component at end 2 (between 1 and 6)
PROP(7) Real array
Properties as input on the PELASEX entry
HISV(6) Real array
History variables for the element. This array can be used by the user to store variables
from one time step to the next.
FORCEO Real variable
Force in the element at the previous time step
C(3,2) Real array
Deformed coordinates in the basic coordinate system:
C(1:3,1) x, y, z, coordinates at end 1
C(1:3,2) x, y, z, coordinates at end 2
DI (6,2) Real array
Incremental displacements in the basic coordinate system
DI(1:3,1) = x, y, z, translational displacements of end 1
DI(4:6,1) = x, y, z, rotational displacements of end 1
DI(1:3,2) = x, y, z, translational displacements of end 2
768 EXELAS
User-defined CELAS1 Spring Element
Input
DI(4:6,2) = x, y, z, rotational displacements 2
These are incremental displacements; i.e., the displacements for this time step only.
V(6,2) Real array
Velocities in the basic coordinate system
V(1:3,1) = x, y, z, translational velocities of end 1
V(4:6,1) = x, y, z, rotational velocities of end 1
V(1:3,2) = x, y, z, translational velocities of end 2
V(4:6,2) = x, y, z, rotational velocities of end 2
A(6,2) Real array
Accelerations in the basic coordinate system
A(1:3,1) = x, y, z translational accelerations of end 1
A(4:6,1) = x, y, z rotational accelerations of end 1
A(1:3,2) = x, y, z, translational accelerations of end 2
A(4:6,2) = x, y, z, rotational accelerations of end 2
UREL Real variable
Relative displacement of the element; i.e., the displacement of end 2 in the spring
direction minus the displacement of end 1
DUREL Real variable
Relative incremental displacement of the element VREL real variable
VREL Real variable
Relative velocity of the end points of the element in the direction of the element
XMASS(2) Real array
Mass of the grid points at ends 1 and 2
Output
FORCE Real variable
Force in the element
STIFF Real variable
Current stiffness of the element
Remarks
1. This subroutine must be included if the PELASEX entry is specified in the Bulk Data Section.
2. The velocities (V) and accelerations (A) of the end points can be updated by the user subroutine
when required.
3. The stiffness is used by Dytran to estimate the time step. A nonzero value must be returned.
EXELAS 769
User-defined CELAS1 Spring Element
4. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
Example
This example defines a stiffness and a corresponding force for a spring element.
SUBROUTINE EXELAS
+(N,M,IX,IC,PROP,HISV,FORCEO,C,DI,V,A,UREL,DUREL,
+VREL,XMASS,FORCE,STIFF)
*
* single or double defined below
IMPLICIT DOUBLE PRECSION (A-H,O-Z)
*
* declare argument as arrays and data-type here....
DIMENSION IX(2),IC(2),PROP(7),HISV(6),C(3,2),
+DI(6,2),V(6,2),A(6,2),XMASS(2)
*
* define the stiffness and the force on the spring
STIFF = 1.E3
FORCE = STIFF * DUREL
*
RETURN
END
770 EXEOS
User-defined Equation of State
Calculates the equation of state for Lagrangian and Eulerian solid elements.
Calling Sequence
CALL EXEOS (CNAME, LENNAM, ISTART, IEND, RHO, DV,
+ DEVIS, XMASS, FBURN, POLD, SIEOLD, PNEW, SIENEW, CLNEW, GRUNGM)
Input
CNAME Character string
Name specified on the EOSEX entry
LENNAM Integer variable
Length of CNAME
ISTART, IEND Integer variables
Grid-point loop counters
RHO(*) Real array
Density of element
DV(*) Real array
Change in volume of element
DEVIS(*) Real array
Viscous work term of element
XMASS(*) Real array
Mass of element
FBURN(*) Real array
Burn fraction of element (not for Lagrangian elements)
POLD(*) Real array
Old pressure of element
SIEOLD(*) Real array
Old specific internal energy of element
Output
PNEW(*) Real array
New pressure of element
SIENEW(*) Real array
New specific internal energy of element
EXEOS 771
User-defined Equation of State
Output
CLNEW(*) Real array
New sound speed of element
GRUNGM(*) Real array
Gruneisen gamma of element (only for multi-material elements)
Remarks
1. This subroutine must be included if there are any EOSEX entries.
2. The subroutine is used to calculate the pressure PNEW for Lagrangian and/or Eulerian elements
according to a user-specified description. In most cases the equation of state is energy dependent,
the new pressure must be solved therefore simultaneously with the energy equation:
PNEW = f RHO,SIENEW
where S denotes that the adiabatic derivative is required, l is the longitudinal stress, is the
density, p is the pressure, G is the shear modulus, 0 is the reference density and = 0 . Care
must be used in defining this quantity, because an error can cause an instability in the calculation.
The Gruneisen gamma GRUNGM must be computed for multi-material elements and can be
calculated as follows:
p = A f ----- + B f e
0
Example
This example calculates the equation of states of an explosive in water using multi-material
Eulerian elements.
SUBROUTINE EXEOS(CNAME,LENNAM,ISTART,IEND,RHO,DV,DEVIS,XMASS,
+ FBURN,POLD,SIEOLD,PNEW,SIENEW,CLNEW,GRUNGM)
*
* single or double defined below
IMPLICIT DOUBLE PRECISION (A-H,O-Z)
*
* declare argument as arrays and data-type here....
CHARACTER*(*) CNAME
*
* ----------------------------------------------------------
*
* input:
* cname = name of the exale definition
* lennam = length of the character string
* istart = start of the grid point loop
* iend = end of the grid point loop
* rho = density
* dv = change in volume
* devis = viscous work term
* xmass = mass
* fburn = burn fraction (not used for Lagrangian elements)
* pold = old pressure
* sieold = old specific internal energy
*
* output:
* pnew = new pressure
* sienew = new specific internal energy
* clnew = new soundspeed
* grungm = Gruneisen gamma
*
* ----------------------------------------------------------
*
* local dimensions and declarations
*
DIMENSION RHO(*),DV(*),DEVIS(*)
DIMENSION XMASS(*),FBURN(*),POLD(*),SIEOLD(*)
DIMENSION PNEW(*),SIENEW(*),CLNEW(*),GRUNGM(*)
*
ZERO = 0.0
ONE = 1.0
HALF = 0.5
*
* first water
IF (CNAME(1:LENNAM) .NE. 'WATER') GOTO 1000
*
* variables
E = 2.2E9
RHOREF = 1000.
HVLM = 1.0/1.1 - 1.0
SSPD = SQRT(E/RHOREF)
EXEOS 773
User-defined Equation of State
TERM3 = MAX(SMALL,ONE+HALF*BB*DVOVH/ETA)
TERM4 = SIEOLD(NZ) + DEVIS(NZ) -
+ HALF*(POLD(NZ)+AA)*DVOVH/RHO(NZ)
*
* calculation of new pressure, specific internal energy
* and speed of sound
SIENEW(NZ) = TERM4/TERM3
PNEW(NZ) = AA + RHOREF*MAX(ZERO,SIENEW(NZ)*BB)
SSPD = CC/RHOREF + SIENEW(NZ)*DD +
+ PNEW(NZ)*BB*RHOREF/RHO(NZ)/RHO(NZ)
SSPD = MAX(DMIN6,SSPD)
CLNEW(NZ) = SQRT(SSPD)
*
* in this case the gruneisen gamma should be calculated
GRUNGM(NZ) = BB*RHOREF/RHO(NZ)
200 CONTINUE
*
9900 CONTINUE
*
RETURN
END
EXEOS1 775
User-specified Equation of State
Calculates the equation of state for Lagrangian and Eulerian solid elements. The pressure can depend on
a damage variable and the SOFTE and VOLPLS variables. These last two variables can be set in for
example an EXFAIL2 routine or in an EXYLD1 routine.
Calling Sequence
CALL EXEOS1 (CNAME, LENNAM, ISTART, IEND, RHO, DV,
+ DEVIS, XMASS, FBURN, POLD, SIEOLD, PNEW, SIENEW, CLNEW, GRUNGM,
+ DAM,SOFTE,VOLPLS)
Input
CNAME Character string
Name specified on the EOSEX entry
LENNAM Integer variable
Length of CNAME
ISTART, IEND Integer variables
Grid-point loop counters
RHO(*) Real array
Density of element
DV(*) Real array
Change in volume of element
DEVIS(*) Real array
Viscous work term of element
XMASS(*) Real array
Mass of element
FBURN(*) Real array
Burn fraction of element (not for Lagrangian elements)
POLD(*) Real array
Old pressure of element
SIEOLD(*) Real array
Old specific internal energy of element
DAM(*) Real array
Damage of the element
776 EXEOS1
User-specified Equation of State
Input
SOFTE(*), Arrays that allow the user to store an additional variable. Contents are
VOLPLS(*) transported and clumped. These arrays can also be accessed within exfail2
and exyld1.
Output
PNEW(*) Real array
New pressure of element
SIENEW(*) Real array
New specific internal energy of element
CLNEW(*) Real array
New soundspeed of element
GRUNGM(*) Real array
Gruneisen gamma of element (only for multi-material elements)
Remarks
1. This subroutine must be included if there are any EOSEX entries.
2. The subroutine is used to calculate the pressure PNEW for Lagrangian and/or Eulerian elements
according to a user-specified prescription. In most cases, the equation of state is energy
dependent; therefore, the new pressure must be solved simultaneously with the energy equation:
1 DV
SIENEW = SIEOLD + DEVIS – --- POLD + PNEW --------------------
2 XMASS
where S denotes that the adiabatic derivative is required, l is the longitudinal stress, is the
density, p is the pressure, G is the shear modulus, 0 is the reference density and = 0 . Care
must be used in defining this quantity because an error can cause an instability in the calculation.
The Gruneisen gamma GRUNGM must be computed for multi-material elements and can be
calculated as follows:
p = A f ----- + B f ,e
0
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Execution Guide.
4. This routine is part of a vectorized process. As a result, the routine can be called more than once
per time step.
Example
SUBROUTINE EXEOS1(CNAME,LENNAM,ISTART,IEND,RHO,DV,DEVIS,XMASS,
+ FBURN,POLD,SIEOLD,PNEW,SIENEW,CLNEW,GRUNGM,DAM,
+ SOFTE, VLPL )
*
* single or double defined below
#include “spdbl”
*
* declare argument as arrays and data-type here....
CHARACTER*(*) CNAME
*
* ---------------------------------------------------------------
*
* input:
* cname = name of the exale definition
* lennam = length of the character string
* istart = start of the grid point loop
* iend = end of the grid point loop
* rho = density
* dv = change in volume
* devis = viscous work term
* xmass = mass
* fburn = burn fraction (not used for Lagrangian elements)
* pold = old pressure
* sieold = old specific internal energy
*
* output:
* pnew = new pressure
* sienew = new specific internal energy
* clnew = new soundspeed
* grungm = Gruneisen gamma
*
* ---------------------------------------------------------------
*
* local dimensions and declarations
*
DIMENSION RHO(*),DV(*),DEVIS(*)
DIMENSION XMASS(*),FBURN(*),POLD(*),SIEOLD(*)
DIMENSION PNEW(*),SIENEW(*),CLNEW(*),GRUNGM(*),DAM(*)
DIMENSION SOFTE(*),VLPL(*)
*
ZERO = 0.0
ONE = 1.0
HALF = 0.5
*
* first water
IF (CNAME(1:LENNAM) .NE. 'WATER') GOTO 1000
778 EXEOS1
User-specified Equation of State
*
* variables
E = 2.2E9
RHOREF = 1000.
HVLM = 1.0/1.1 - 1.0
SSPD = SQRT(E/RHOREF)
*
* the simple bulk equation of state
DO 100 NZ = ISTART, IEND
TMU = (RHO(NZ)-RHOREF)/RHOREF
AMU = MAX(TMU,HVLM)
IF (XMASS(NZ) .LE. 0.0) GOTO 100
*
* calculation of new pressure, specific internal energy
* and soundspeed
PNEW(NZ) = E*AMU*(1-DAM(NZ))
SIENEW(NZ) = SIEOLD(NZ) + DEVIS(NZ) -
+ HALF*(POLD(NZ)+PNEW(NZ))*DV(NZ)/XMASS(NZ)
CLNEW(NZ) = SSPD
*
* gruneisen gamma can be neglected
GRUNGM(NZ) = ZERO
100 CONTINUE
*
1000 CONTINUE
*
*
9900 CONTINUE
*
RETURN
END
EXFAIL 779
User-defined Failure Model
Returns a failure flag FFAIL to Dytran for all elements in the string (LST....LFIN).
Calling Sequence
CALL EXFAIL(MATNAM,LENNAM,LST,LFIN,EPLAS,EFFSTS,PRES,
EDIS,RHO,FFAIL,IZONE)
Input
MATNAM Character variable
Material number
LENNAM Integer variable
Length of MATNAM
LST,LFIN Integer array
First and last number of the loop over the elements in the list
EPLAS Real array
Plastic strain of an element
EFFSTS Real array
Effective stress of an element
PRES Real array
Pressure of an element
EDIS Real array
Distortional energy of an element
RHO Real array
Density of an element
IZONE Integer array
List of element user-number, see Remark 4.
Output
FFAIL Real array
Failure flag of an element:
FFAIL = 0 Element failed
FFAIL = 1 Element not failed
780 EXFAIL
User-defined Failure Model
Remarks
1. The subroutine must be included if there are any FAILEX entries in the input.
2. The pressure array is only used for Eulerian material with strength.
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
4. The IZONE array is only filled for Lagrange Solid Element
Example
In this example, the material fails when the maximum plastic strain exceeds 50%. The routine returns the
FFAIL flag to the code (FFAIL = 1 no failure and FFAIL = 0 failure).
SUBROUTINE EXFAIL
+(MATNAM,LENNAM,LST,LFIN,EPLAS,EFFSTS,PRES,SIE,RHO,
FFAIL,IZONE)
C
#include “spdbl”
C
DIMENSION EPLAS(*),EFFSTS(*),PRES(*),SIE(*),RHO(*),FFAIL (*)
C
CHARACTER*80 MATNAM
C
C Example of failure if the maximum plastic strain exceeds 50%
C
DO 100 NZ = LST, LFIN
IF (EPLAS (NZ) . GT. 0.5) THEN
FFAIL (NZ) = 0.
ELSE
FFAIL (NZ) = 1.
ENDIF
100 CONTINUE
*
RETURN
END
EXFAIL1 781
User-defined Orthotropic Failure Model
The EXFAIL1 user subroutine defines a general failure model for orthotropic
three-dimensional elements.
Calling Sequence
CALL EXFAIL1 (MATNAM,LENNAM,LST,LFIN,IZONE,TXX,TYY,TZZ,TXY,
+ TYZ,TXZ,DEPSXX,DEPSYY,DEPSZZ,DEPSXY,DEPSYZ,DEPSXZ,
+ EPSXX ,EPSYY , EPSZZ ,EPSX ,EPSXZ ,EPSYZ,
+ EXX,EYY,EZZ,EXY,EYZ,EXZ,GXY,GYZ,GZX,
+ USRVR1,USRVR2,TSTEP,FFAIL)
Input
MATNAM Character variable
Material number
LENNAM Integer variable
Length of MATNAM
LST,LFIN Integer array
The first and last number of the loop over the elements in the list
IZONE Integer array
Element user number
TXX, TYY, TZZ Real arrays
Element normal stress components
TXY, TXZ, TYZ Real arrays
Element shear stress components
DEPSXX, DEPSYY, DEPSZZ Real arrays
Element normal strain increments
DEPSXY, DEPSXZ, DEPSYZ Real arrays
Element shear strain increments
EPSXX, EPSYY, EPSZZ Real arrays
Element normal (last cycle) strain components
EPSXY, EPSXZ, EPSYZ Real arrays
Element shear (last cycle) strain components
782 EXFAIL1
User-defined Orthotropic Failure Model
Input
EXX, EYY, EZZ, EXY, EYZ, Real arrays
EXZ, GXY, GYZ, GZX Element elasticity matrix components
USRVR1, USRVR2 Real arrays
Element user variables
Output
TSTEP Real array
Element time step
FFAIL Real array
Element failure flag
FFAIL = 0 means element has failed
FFAIL = 1 means element has not failed.
Remarks
1. The user subroutine exfail1.f must be included if there are any FAILEX1 entries in the input data.
2. The FAILEX1 entry can only be used in combination with orthotropic solid (Lagrangian) elements.
The material definition for these elements is done using DMATOR.
3. The access to the element’s elasticity matrix allows for inclusion of degradation of the material
on an element-by-element basis. Any changes made to the elasticity matrix components of an
element are stored in the element memory and are used during the next time step in the evaluation
of the new stress state. When the properties of the elasticity matrix depend on the strain, you
define the full constitutive model.
4. The strain components are the last time-step strains. To get the current strain, the increments
must be added. The increments are used to detect the direction of the loading (i.e., loading
or unloading).
5. Dytran does not store changes you make to the strain tensor.
6. The stress tensor is always represented in the material coordinate system, which is based on the
element topology for the materials that refer to the FAILEX1 entry.
7. Dytran stores the changes that you make to the stress tensor components. Note that this may result
in an inconsistent relation of stress state and strain field.
8. The user variables are used to store element data that is not standard part of Dytran storage. When
these variables are used by other user subroutines, this may cause definition conflicts. The content
of the user variables is stored at return from the EXFAIL1 user subroutine. Additional user
variables can be defined by using the parameter PARAM, VARACTIV.
9. The precision of the calculations should be appropriate for the computer being used.
EXFAIL1 783
User-defined Orthotropic Failure Model
Example
In the example that follows, a failure model is defined that is based on maximum strain, depending on
the direction of the strain. The example includes material degradation prior to failure.
SUBROUTINE EXFAIL1
+(MATNAM,LENNAM,LST,LFIN,IZONE,
+ TXX,TYY,TZZ,TXY,TYZ,TXZ,
+ DEPSXX,DEPSYY,DEPSZZ,DEPSXY,DEPSYZ,DEPSXZ,
+ EPSXX ,EPSYY, EPSZZ ,EPSXY ,EPSXZ ,EPSYZ ,
+ EXX,EYY,EZZ,EXY,EYZ,EXZ,GXY,GYZ,GZX,
+ USRVR1,USRVR2,TSTEP,FFAIL)
*
#include "spdbl"
*
*Stress tensor
DIMENSION TXX(*),TYY(*),TYY(*)
DIMENSION TXY(*),TXZ(*),TYZ(*)
*
* Strain increments
DIMENSION DEPSXX(*),DEPSYY(*),DEPSZZ(*)
DIMENSION DEPSXY(*),DEPSXZ(*),DEPSYZ(*)
*
* Last time step total strain tensor
DIMENSION EPSXX(*),EPSYY(*),EPSZZ(*)
DIMENSION EPSXY(*),EPSXZ(*),EPSYZ(*)
*
* Elasticity matrix
DIMENSION EXX(*),EYY(*),EZZ(*)
DIMENSION EXY(*),EYZ(*),EXZ(*)
DIMENSION GXY(*),GYZ(*),GZX(*)
*
* Element user numbers
DIMENSION IZONE(*)
*
* Current time step and element failure flag
DIMENSION TSTEP(*),FFAIL(*)
*
* User variables
DIMENSION USRVR1(*),USRVR2(*)
*
*
#include "constants"
*
CHARACTER*80 MATNAM
CHARACTER*80 CFLRNM
LOGICAL LFIRST
*
* Set the failure name for groups
IF (MATNAM(1:LENNAM).EQ.’100’) THEN
CFLRNM = ‘COMPOSITE’
ENDIF
*
* Check the material name
IF (CFLRNM.EQ.’COMPOSITE’) THEN
784 EXFAIL1
User-defined Orthotropic Failure Model
Updates the damage variable for all elements in the string (LST....LFIN). Failure can depend on a
damage variable and the SOFTE and VOLPLS variables. These variables can be set in, for example, an
EXEOS1 routine or in an EXYLD1 routine. The damage variable can also be determined by a
FAILJC entry.
Calling Sequence
CALL EXFAIL2 (MATNAM,LENNAM,LST,LFIN,EPLAS,EFFSTS,PRES,
SIE,RHO,DAM,SOFTE,VOLPLS,DEPI,DLTH,SXX,SYY,SZZ,SXY,SYZ,SXZ,
SXXO,SYYO,SZZO,SXYO,SYZO,SXZO,SHEAR)
Input
MATNAM Character variable
Material number
LENNAM Integer variable
Length of MATNAM
LST,LFIN Integer array
First and last number of the loop over the elements in the list
EPLAS Real array
Plastic strain of an element
EFFSTS Real array
Effective stress of an element
PRES Real array
Pressure of an element
RHO Real array
Density of an element
DAM Real array
Damage of an element
DEPI Real array
Plastic strain increment of the current cycle
DLTH Time step
SXX-SXZ Deviatoric stress tensor of the current cycle after radial scale back
SXXO-SXZO Deviatoric stress tensor from the previous cycle
786 EXFAIL2
User-defined Failure Model
Input
SHEAR Shear modulus
SOFTE,VLPLS Arrays that allows the user to store an additional variable. Contents are transported
and clumped. This array can also be accessed within exfail2
Output
DAM Updated Damage
Remarks
1. The subroutine must be included if there are any FAILEX2 entries in the input.
2. EXFAIL2 is only supported by the multi-material Euler solver with strength.
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
4. The damage variable is available in EXEOS1 and the EXYLD1 subroutine.
Example
This example illustrated how FAILJC can be implemented by means of EXFAIL2.
SUBROUTINE EXFAIL2
+ (MATNAM,LENNAM,LST,LFIN,EPLAS,EFFSTS,PRES,SIE,RHO,DAMT,
+ SOFTE,VOLPLS,DEPI,DLTH, SXX , SYY , SZZ , SXY , SYZ , SXZ ,
+ SXXO, SYYO, SZZO, SXYO, SYZO, SXZO,
+ SHEAR)
*
#include "spdbl"
SAVE IERM
DIMENSION EPLAS(*),EFFSTS(*),PRES(*),SIE(*),RHO(*)
DIMENSION DAMT(*),DEPI(*)
*
*
#include "params"
#include "ermsg"
*
CHARACTER*(*) MATNAM
*
CHARACTER*31 CSUBNM
CHARACTER*6 CSUB06
PARAMETER (CSUBNM='EXFAIL2')
PARAMETER (CSUB06 = 'INIT')
*
PARAMETER( NERM= 1 )
DIMENSION IERM(NERM)
DATA (IERM(I),I=1,NERM) /NERM*0/
*
D1 =
D2 =
D3 =
D4 =
EXFAIL2 787
User-defined Failure Model
D5 =
DEPREF=
TROOM =
TMELT =
CP =
EPCUTOF =
SMALL = 1e-20
*
ONE = 1.0d0
*
DO 400 NZ=LST,LFIN
TEMP = SIE(NZ)/CP
TEMP = MAX(TEMP,ZERO)
TEMP = MIN(TEMP,TMELT)
THL = (TEMP - TROOM)/(TMELT-TROOM)
EFPMIN = MIN(EPLAS(NZ),DEPI(NZ))
IF (EPLAS(NZ).LT.EPCUTOF) GOTO 400
IF(EFFSTS(NZ).GT.ZERO .AND. EFPMIN.GT.ZERO) THEN
SCPR = -PRES(NZ)/EFFSTS(NZ)
SCPR = MIN(SCPR,1.5D0)
EPDAM = (D1 +D2*EXP(D3*SCPR))
DEPDT = DEPI(NZ)/DLTH
DEPDT = DEPDT/DEPREF
EPDAM = EPDAM*(ONE+D4*LOG(DEPDT))
EPDAM = EPDAM*(ONE+D5*THL)
EPDAM = MAX(EPDAM,SMALL)
DAM(NZ) = DAM(NZ) + DEPI(NZ)/EPDAM
DAM(NZ) = MIN(DAM(NZ),ONE)
ENDIF
400 CONTINUE
9900 CONTINUE
RETURN
END
788 EXFLOW
User-defined Flow Boundary
Returns the velocity, pressure, density, and specific internal energy at a single material Eulerian user-
defined flow boundary.
Calling Sequence
CALL EXFLOW (FLNAME, LENNAM, NELEM, PELEM, QELEM,
+ UXELEM, UYELEM, UZELEM, RHOEL, SIEEL, PFACE,
+ UXFACE, UYFACE, UZFACE, RHOFAC, SIEFAC)
Input
FLNAME Character string
Name of the boundary
LENNAM Integer variable
Length of FLNAME
NELEM(*) Integer array
Element number
PELEM(*) Real array
Pressure in the element
QELEM(*) Real array
Artificial quadratic viscosity of element
UXELEM(*) Real array
x-velocity of element
UYELEM(*) Real array
y-velocity of element
UZELEM(*) Real array
z-velocity of element
RHOEL(*) Real array
Density of element
SIEEL(*) Real array
Specific internal energy of element
Output
PFACE(*) Real array
Pressure at boundary
EXFLOW 789
User-defined Flow Boundary
Output
UXFACE(*) Real array
x-velocity at boundary
UYFACE(*) Real array
y-velocity at boundary
UZFACE(*) Real array
z-velocity at boundary
RHOFAC(*) Real array
Density of inflowing material
SIEFAC(*) Real array
Specific internal energy of inflowing material
Remarks
1. This subroutine must be included if there are any FLOWEX entries in the input file.
2. The pressure and velocity at the boundary must be specified. If there is flow into the mesh, the
density and specific internal energy must also be defined.
3. This subroutine is called twice every time step for every Euler face referenced on the FLOWEX
entry. The first call is for the material transport calculation, the second is for the impulse
calculation.
4. This subroutine is vectorized. All the input data is stored in arrays, which must be dimensioned.
The start and end of the arrays are given by the variables LST and LFIN in the common block
/MSCD_LOCLOP/. Calculations must be done for all of the entries in the arrays between LST
and LFIN. See the following example.
5. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
Example
This example simulates a non-reflecting boundary by defining the velocity and pressure at the boundary
to be the same as that in the element.
SUBROUTINE EXFLOW (FLNAME, LENNAM, NELEM, PELEM, QELEM,
+UXELEM, UYELEM, UZELEM, RHOEL, SIEEL,
+PFACE, UXFACE,UYFACE, UZFACE, RHOFAC,
+PFACE, SIEFAC)
IMPLICIT DOUBLE PRECISION (A-H, 0-Z)
DIMENSION NELEM(*), PELEM(*), QELEM(*), UXELEM(*),
+UYELEM(*), UZELEM(*), RHOEL(*), SIEEL(*)
DIMENSION PFACE(*), UXFACE(*), UYFACE(*), UZFACE(*),
+RHOFAC(*), SIEFAC(*)
CHARACTER*(*) FLNAME
COMMON /MSCD_LOCLOP/LST, LFIN
790 EXFLOW
User-defined Flow Boundary
C
C Do the vector loop from the LST to LFIN
DO 100 I = LST, LFIN
PFACE (I) = PELEM (I)
XFACE(I) = UXELEM (I)
UYFACE (I) = UYELEM(I)
UZFACE (I) = UZELEM (I)
RHOFAC(I)= RHOEL (I)
SIEFAC(I) = SIEEL (I)
100 CONTINUE
RETURN
END
EXFLOW2 791
User-defined Flow Boundary
Returns the velocity, pressure, density, and specific internal energy at a multimaterial Eulerian user-
defined flow boundary.
Calling Sequence
CALL EXFLOW2 (FLNAME, LENNAM, TIME, NCYCLE, NELEM,
+ PELEM, QELEM, UXELEM, UYELEM, UZELEM,RHOEL,
+ SIEEL, PFACE, UXFACE, UYFACE, UZFACE, RHOFAC,
+ SIEFAC, SX, SY, SZ, CMATNO, IFLWTP)
Input
FLNAME Character string
Name of the boundary
LENNAM Integer variable
Length of FLNAME
NELEM(*) Integer array
Element number
PELEM(*) Real array
Pressure in the element
QELEM(*) Real array
Artificial quadratic viscosity of element
UXELEM(*) Real array
x-velocity of element
UYELEM(*) Real array
y-velocity of element
UZELEM(*) Real array
z-velocity of element
RHOEL(*) Real array
Density of element
SIEEL(*) Real array
Specific internal energy of element
SX(*) Real array
Face area x-component
792 EXFLOW2
User-defined Flow Boundary
Input
SY(*) Real array
Face area y-component
SZ(*) Real array
Face area z-component
Output
PFACE(*) Real array
Pressure at boundary
UXFACE(*) Real array
x-velocity at boundary
UYFACE(*) Real array
y-velocity at boundary
UZFACE(*) Real array
z-velocity at boundary
RHOFAC(*) Real array
Density of inflowing material
SIEFAC(*) Real array
Specific internal energy of inflowing material
CMATNO Character array
Material name of material for in- or outflow at the faces in the list
IFLWTP Integer variable
Flow type switch:
0 in/outflow
1 outflow
2 inflow
Remarks
1. This subroutine is valid for multimaterial Euler only. For hydrodynamic single material, or single
material with strength, use EXFLOW.
2. This subroutine must be included if there are any FLOWEX entries in the input file and the Euler
processor used is the multimaterial Euler processor.
3. The pressure and velocity at the boundary must be specified. If there is flow into the mesh, the
density and specific internal energy must also be defined.
EXFLOW2 793
User-defined Flow Boundary
4. This subroutine is called twice every time step for every Euler face referenced on the FLOWEX
entry. The first call is for the material transport calculation, the second is for the
impulse calculation.
5. This subroutine is vectorized. All the input data is stored in arrays that must be dimensioned. The
start and end of the arrays are given by the variables LST and LFIN in the common block
/MSCD_LOCLOP/. Calculations must be done for all of the entries in the arrays between LST
and LFIN. See the following example.
6. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
Example
SUBROUTINE EXFLOW2
+ (FLNAME, LENNAM, TIME, NCYCLE, IUSRZN,
+ PZON, QZON, UXZON, UYZON, UZZON, RHOZON, SIEZON,
+ PFAC, UXFAC, UYFAC, UZFAC, RHOFAC, SIEFAC,
+ SX, SY, SZ, CMATNO, IFLWTP )
*
IMPLICIT DOUBLE PRECISION (A-H,O-Z)
*
DIMENSION PZON(*),QZON(*),UXZON(*),UYZON(*),UZZON(*),
+ RHOZON(*),SIEZON(*)
DIMENSION
PFAC(*),UXFAC(*),UYFAC(*),UZFAC(*),RHOFAC(*),SIEFAC(*)
DIMENSION SX(*),SY(*),SZ(*)
DIMENSION IUSRZN(*)
*
CHARACTER*80 FLNAME
CHARACTER*8 CMATNO(*)
*
COMMON/MSCD_LOCLOP/LST,LFIN
*
CHARACTER*80 FLNAME
*
DATA SMALL /1.E-15/
DATA ZERO /0./
DATA ONE /1./
*
*
* mass flow
DATA DMASS /10./
*
DO 100 NF = LST,LFIN
*
FACX = ONE
FACY = ONE
FACZ = ONE
IF (ABS(SX(NF)).LE.SMALL) FACX = ZERO
IF (ABS(SY(NF)).LE.SMALL) FACY = ZERO
IF (ABS(SZ(NF)).LE.SMALL) FACZ = ZERO
794 EXFLOW2
User-defined Flow Boundary
*
* Material at Inflow
CMATNO (NF) = ’100’
*
* Density at Inflow
RHOFAC (NF) = 1000.
*
* Internal Energy at Inflow
SIEFAC (NF) = 2.E5
*
* Pressure on the face is the element pressure
PFAC (NF) = PZON(NF)
*
* normal on the face points outward
* .... transport of material ....
*
UXFAC (NF) =
+ -FACX * DMDT / ( RHOFAC(NF) * SX(NF) )
UYFAC (NF) =
+ -FACY * DMDT / ( RHOFAC(NF) * SY(NF) )
UZFAC (NF) =
+ -FACZ * DMDT / ( RHOFAC(NF) * SZ(NF) )
*
100 CONTINUE
*
RETURN
END
EXFUNC 795
User-defined Function
Calling Sequence
CALL EXFUNC (CFNAME, XVAL, YVAL, NMSTR)
Input
CFNAME Character variable. The name of the function defined on input.
XVAL (NMSTR) Real array.
The x-value that the function requires (time).
NMSTR Number of values
Output
YVAL (NMSTR) Real array.The value to be returned by the function.
Note that the y-value is multiplied by the scale factor defined on the load entry.
Remarks
1. This subroutine must be included if there are any TABLEEX entries in the input.
2. The subroutine is called every time step. The time is passed to the subroutine. The outcome (y-
value) is returned.
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
4. There can be more than one function defined in the EXFUNC user routine; these functions can be
distinguished by their names.
Example
This subroutine defines six different functions that can be referred to from the input by a TABLEEX entry.
These functions can be used for a variety of dynamic loads.
SUBROUTINE EXFUNC
+(FNAME, XVAL, YVAL, NMSTR)
*
IMPLICIT DOUBLE PRECISION (A-H,O-Z)
*
DIMENSION XVAL(*),YVAL(*)
*
CHARACTER*16 CFNAME
*
IF (CFNAME.EQ.’FUNC1’) THEN
YVAL = LOG (ABS (XVAL) )
ELSE IF (CFNAME. EQ.’FUNC2’) THEN
796 EXFUNC
User-defined Function
Defines an initial condition for elements and/or grid points at the beginning of the analysis.
Calling Sequence
CALL EXINIT (CNAME, LENNAM, TIME, NCYCLE, NGPEL, NUMENT,
+ ISTART, IEND)
Input
CNAME Character variable
Name specified on the TICEEX or TICGEX entry
LENNAM Integer variable
Number of characters in CNAME
TIME Real variable
Time at the current time step
NCYCLE Integer variable
Number of the current time step
NGPEL(*) Integer array
Element or grid point user number
NUMENT Integer variable
Length of array and number of elements or grid points defined on the TICEEX or
TICGEX entry
ISTART, IEND Integer variables
Element loop counters
Remarks
1. This subroutine must be included if there are any TICEEX or TICGEX entries.
2. This subroutine is used to initialize the variables of elements and/or grid points.
Example
This example shows how to initialize a gravitational field in water.
SUBROUTINE EXINIT
+(CNAME, LENNAM, TIME, NCYCLE, NGPEL, NUMENT, LST, LFIN)
*
* single or double defined below
IMPLICIT DOUBLE PRECISION (A-H,O-Z)
*
798 EXINIT
User-defined Initial Condition
IZVAR(5) = IPN(1)
CVAR = ’NODE6’
CALL RETRIEVE_ELEMENT_INT_VAR(1,NZU,IPN,CVAR)
IZVAR(6) = IPN(1)
CVAR = ’NODE7’
CALL RETRIEVE_ELEMENT_INT_VAR(1,NZU,IPN,CVAR)
IZVAR(7) = IPN(1)
CVAR = ’NODE8’
CALL RETRIEVE_ELEMENT_INT_VAR(1,NZU,IPN,CVAR)
IZVAR(8) = IPN(1)
* Find the eight nodes of the zone
YMID = 0.0
DO 100 IC = 1,8
IPI = IZVAR(IC)
* get user numbers
CALL PX_GET_USR_PNT_FROM_INT_PNT
+ ( IPU(1) , IPI )
* get ypos
CVAR = ’YPOS’
CALL RETRIEVE_GRIDPOINT_FLOAT_VAR(1,IPU,XPVAR,CVAR)
YMID = YMID + XPVAR(1)
100 CONTINUE
* Compute the z-coordinate of the center of the zone and
* compute the pressure for the distance under the water level
YMID = YMID/8.
DH = YSURF - YMID
PRES = RHOREF * ACCG * DH
* To this pressure belongs a density
RHO = RHOREF + PRES*RHOREF/BULK
* Only change the density in non_void zones
IUNUS = ISVOID(NZU(1))
IF(IUNUS.EQ.0) then
NZV = NZV+1
NZONEU(NZV) = NZU(1)
XVAR(NZV) = RHO
ENDIF
200 CONTINUE
*
CVAR=’DENSITY’
CALL STORE_ELEMENT_FLOAT_VAR(NZV,NZONEU,XVAR,CVAR)
*
9900 CONTINUE
RETURN
END
800 EXPBAG
User-defined Air Bag Pressure
Calling Sequence
Call EXPBAG (NAME, LENNAM, TIME, VOLUME, PRES)
Input
NAME Character variable
Name of the gas bag
LENNAM Integer variable
Number of characters in NAME
TIME Real variable
Problem time
VOLUME Real variable
Volume inside the gas bag
Output
PRES Real variable
Pressure inside the gas bag
Remarks
1. This subroutine must be included if there are any GBAGEX entries in the input file.
2. The subroutine is called every time step. The volume of the gas bag is calculated and passed to
the subroutine. The pressure in the gas bag is returned.
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
Example
This subroutine simulates an air bag with the pressure inside initially at 100 N/m2 and updated using the
equation P V = constant.
SUBROUTINE EXPBAG
+(PBNAME, LENNAM, TIME, VOLUME, PRES)
C
IMPLICIT DOUBLE PRECISION (A-H, O-Z)
C
SAVE IFIRST, CONST
CHARACTER *(*) PBNAME
DATA IFIRST /0/
C
EXPBAG 801
User-defined Air Bag Pressure
IF (IFIRST.EQ.0) THEN
PRES = 1000.
CONST = PRES * VOLUME
IFIRST = 1
ELSE
PRES = CONST/VOLUME
ENDIF
C
RETURN
END
802 EXPLD
User-defined Pressure Load
Calling Sequence
CALL EXPLD (NAME, LENNAM, TIME, PRES, SIGN)
Input
NAME Character variable
Name of a set of pressures
LENNAM Integer variable
Number of characters in NAME
TIME Real variable
Problem time
SIGN Real variable
Unused
Output
PRES Real variable
The magnitude of the pressure
Remarks
1. This subroutine must be included if there are any PLOADEX entries in the input file.
2. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
Example
The EXPOR user subroutine defines a general porosity model for coupling surfaces.
Calling Sequence
CALL EXPOR (CEXPOR,LENNAM,NMENTR,NMFACE,IEUL,IFACE,PRESS,DENSTY,
+ SIE,XVEL,YVEL,ZVEL,UX,UY,UZ,AREA,SX,SY,SZ,
+ QVISC,DLTH,VTRANS,DMASS,
+ FDENS,FSIE,XVELF,YVELF,ZVELF,COEEFV)
Input
CEXPOR Character array
Name of the porosity definition
Length: NMENTR
LENNAM Integer variable
Length of the CEXPOR name variable
NMENTR Integer variable
Number of segments in the current batch
NMFACE Integer variable
Number of face segments
IEUL Integer array
User Euler element number connected to the segment
Length: NMENTR
IFACE Integer array
Internal face number connected to the segment
Length: NMENTR
PRESS, DENSTY, SIE Real arrays
Pressure, density and specific internal energy in the element connected
to the segment
Length: NMENTR
XVEL, YVEL, ZVEL Real arrays
X-, Y- and Z-velocity components in the element connected to
the segment
Length: NMENTR
804 EXPOR
User-defined Porosity Model
Input
UX, UY, UZ Real arrays
X-, Y- and Z-velocity components of the moving face the segment is
part of
Length: NMENTR
AREA, SX, SY, SZ Real arrays
Total segment area and the X-, Y- and Z-components of the
segment normal
Length: NMENTR
QVISC Real array
Artificial viscosity of the element connected to a segment
Length: NMENTR
DLTH Real variable
Time step at current cycle
Output
VTRANS, DMASS Real arrays
Transported volume and transported mass through the segment
Length: NMENTR
FPRESS, FSIE Real arrays
Pressure and specific internal energy at the segment face
Length: NMENTR
XVELF, YVELF, ZVELF Real arrays
Velocity components at the segment face
Length: NMENTR
COEFFV Real array
Porosity coefficient of the segment
Length: NMENTR
Remarks
1. The expor.f user subroutine must be included if there are any POREX entries in the input data.
2. The POREX entry can only be used in combination with a coupling and porosity definition
(COUPLE and COUPOR).
3. User-defined porosity can only be used with the single mat hydrodynamic Euler solver, the Roe
solver, and the multi-material Euler solver. For use with the multi-material solver, the EXPOR2
user subroutine has to be included.
EXPOR 805
User-defined Porosity Model
4. The user-defined subroutine must be compiled with a Fortran 90 compiler for compatibility.
There is no guarantee that a Fortran 77-compiled object will link properly with the Fortran 90
compiled library objects provided on the Dytran distribution.
5. The porosity is computed according to the user-defined model. The output must consist of the
volume and mass flow through the segment faces, the pressure, specific internal energy and the
velocity components at the face. The porosity coefficient is also required output as it is used in
the impulse computation.
6. The volume and mass flow are defined to be positive for outflow and negative for inflow. They
should be consistently defined. In case of elements containing (partial) voids, the void fraction is
taken into account automatically by Dytran.
7. The area coefficient COEFFV represents the open fraction of the surface area. The coefficient
must be in the range [0.0, 1.0], where a value of 1.0 means entirely open to flow and 0.0 means
entirely closed to flow. The coefficient is subsequently used for the impulse calculation on
the surface.
8. The segment face values for the velocity components, the pressure and the specific internal energy
are by default set to the centroidal values of the Euler element the segment is connected to.
9. The volume and mass flow and the porosity factor are to zero by default.
10. The precision of the computations should be appropriate for the computer being used. You can
use the include file “spdbl” to automatically define the proper accuracy.
11. The EXPOR user subroutine is part of a “vectorized” computation process and may be called
several times within a time step.
Example
In the example that follows, the subroutine contains two different porosity models called PERM and
FLOW, respectively.
The PERM porosity model is analogous to the Dytran PERMEAB implementation. It represents a porous
surface where the flow is the porosity factor times the pressure difference.
The FLOW porosity model mimics the Dytran standard PORFLOW implementation with pressure-
dependent porosity.
SUBROUTINE EXPOR
+( CEXPOR,LENNAM,NMENTR,NMFACE,IEUL,
+IFACE,PRESS,DENSTY,SIE,
+ XVEL,YVEL,ZVEL,UX,UY,UZ,AREA,SX,SY,SZ,
+ QVISC,DLTH,VTRANS,DMASS,
+ FDENS,FSIE,XVELF,YVELF,ZVELF,COEEFV )
*
#include "spdl"
*
* input arguments
CHARACTER*(*) CEXPOR(*)
DIMENSION IEUL (*),IFACE (*)
DIMENSION PRESS (*),DENSTY(*),SIE (*)
DIMENSION XVEL (*),YVEL (*),ZVEL (*)
806 EXPOR
User-defined Porosity Model
VALUEP = VALP*PRSDIF
VALPMB = MIN(VALCRT,VALUEP)
*
* mass-flow rate and transported volume
* NOTE: Outflow is positive
FLWOUT = XINOUT*VALPMB*RHO*AREAN
VTRANS(NSEG) = DLTH*FLWOUT/RHO
DMASS (NSEG) = RHO*VTRANS(NSEG)
*
*sie, pressure and velocity at the face
FSIE (NSEG) = SIECRT
FPRESS(NSEG) = POUT
XVELF (NSEG) = XINOUT*VALPMB*SX(NSEG)
YVELF (NSEG) = XINOUT*VALPMB*SY(NSEG)
ZVELF (NSEG) = XINOUT*VALPMB*SZ(NSEG)
*
*next segment
GOTO 100
*
* porflow model
1000 CONTINUE
*
* outside values
PFACE = 1.0E5
RHOFAC = 1.2
GAMMA = 1.4
*
*porosity coefficient
*NOTE: porous area is open to the flow
COEFFV(NSEG) = 0.5
*
* effective open area
AREAN = AREA(NSEG)*COEFFV(NSEG)
*
*in- or outflow depends on pressure diff
IF (PRESS(NSEG).GT.PFACE) THEN
PRES = PRESS (NSEG)
RHO = DENSTY(NSEG)
PENV = PFACE
XINOUT = 1.0
ELSE
PRESS = PFACE
RHO = RHOFAC
PENV = PRESS(NSEG)
XINOUT = -1.0
ENDIF
*
* constants
GAMP1 = GAMMA + 1.0
GAMM1 = GAMMA – 1.0
*
* critical pressure
PCRIT = PRES*((2.0/GAMP1)**(GAMMA/GAMM1))
IF (PENV.GT.PCRIT) THEN
808 EXPOR
User-defined Porosity Model
PEXH = PENV
ELSE
PEXH = PCRIT
ENDIF
*
* determine flow depending on the pressure
CHK = 0.0
IF (PRES.NE.0.0) THEN
CHK = 2.0*PRES*RHO*GAMMA/GAMM1*
+ ((PEXH/PRES)**(2.0/GAMMA) -
+ (PEXH/PRES)**(GAMP1/GAMMA))
ENDIF
*
* mass-flow rate
FLWOUT = 0.0
IF (CHK.GT.0.0) THEN
FLWOUT = XINOUT*AREAN*SQRT(CHK)
ENDIF
*
* volume and mass
VTRANS(NSEG) = DLTH*FLWOUT/RHO
DMASS (NSEG) = RHO*VTRANS(NSEG)
*
* store face pressure
FPRESS(NSEG) = PFACE
100 CONTINUE
RETURN
END
EXPOR2 809
User-defined Porosity Mode for Multi-material Euler
The EXPOR2 user subroutine defines a general porosity model for coupling surfaces in combination with
the Multi-material Euler solver.
Calling Sequence
CALL EXPOR2 (CEXPOR,LENNAM,TIME,
+ NMENTR,IEUL,IFACE,
+ PELEM,QELEM,UXELEM,UYELEM,UZELEM,
+ RHOEL,SIEEL,UXSEG,UYSEG,UZSEG,
+ PFACE,UXFACE,UYFACE,UZFACE,RHOFAC,
+ SIEFAC,AREA,SX,SY,SZ,
+ COEFFV,CMATNO)
Input
CEXPOR Character array
Name of the porosity definition
Length: NMENTR
LENNAM Integer variable
Length of the CEXPOR name variable
NMENTR Integer variable
Number of segments in the current batch
IEUL Integer array
User Euler element number connected to the segment
Length: NMENTR
IFACE Integer array
Internal face number connected to the segment
Length: NMENTR
PELEM,RHOEL,SIEEL Real arrays
Pressure, density and specific internal energy in the element
connected to the segment
Length: NMENTR
810 EXPOR2
User-defined Porosity Mode for Multi-material Euler
Input
UXELEM,UYELEM,UZELEM Real arrays
X-, Y- and Z-velocity components in the element connected to the
segment
Length: NMENTR
UXSEG, UYSEG, UZSEG Real arrays
X-, Y- and Z-velocity components of the segment
Length: NMENTR
AREA, SX, SY, SZ Real arrays
Total segment area and the X-, Y- and Z-components of the segment
normal
Length: NMENTR
QELEM Real array
Artificial viscosity of the element connected to a segment
Length: NMENTR
Output
CMATNO Character array
Name of material for inflow through the segment face. Outflow of
material occurs on basis of the material fractions present in the
adjacent Euler element. For outflow, CMATNO is ignored.
Length: NMENTR
PFACE,RHOFAC,SIEFAC Real arrays
Pressure, density and specific internal energy at the segment face.
These are the boundary conditions that will be imposed on the
Euler element.
Length: NMENTR
XFACE, YFACE, ZFACE Real arrays
Velocity components at the segment face. These are the
boundary conditions.
Length: NMENTR
COEFFV Real array
Porosity coefficient of the segment
Length: NMENTR
EXPOR2 811
User-defined Porosity Mode for Multi-material Euler
Remarks
1. The EXPOR2 user subroutine must be included if a POREX entry is used in combination with the
multi-material solver.
2. The POREX entry can only be used in combination with a coupling and porosity definition
(COUPLE and COUPOR).
3. The user-defined porosity can only be used with the single mat hydrodynamic Euler solver, the
Roe solver and the multi-material Euler solver.
4. The user-defined subroutine must be compiled with a Fortran 90 compiler for compatibility.
There is no guarantee that a Fortran 77-compiled object will link properly with the Fortran 90
compiled library objects provided on the Dytran distribution.
5. The user subroutine loops over surface segments. Each segment is connected to only one Euler
element and only one surface element. The arrays IEUL and IFACE can be used to refer to these
elements or faces as a function of the segment number. Note that each Euler element and each
face can refer to multiple face segments.
6. The porosity is computed according to the user-defined model. The output must consist of the
pressure, specific internal energy and the velocity components at the face.
7. The area coefficient COEFFV represents the open fraction of the surface area. The coefficient
must be in the range [0.0, 1.0], where a value of 1.0 means entirely open to flow and 0.0 means
entirely closed to flow. The coefficient is subsequently used for the impulse calculation on the
surface.
8. The segment face values for the velocity components, the pressure and the specific internal energy
are by default set to the centroidal values of the Euler element the segment is connected to.
9. The precision of the computations should be appropriate for the computer being used. You can
use the include file, spdbl, to automatically define the proper accuracy.
10. The EXPOR2 user subroutine is part of a “vectorized” computation process and may be called
several times within a time step.
Example
In the example that follows, the subroutine contains a simple inflow boundary.
SUBROUTINE EXPOR2
+ (CEXPOR,LENNAM,TIME,
+ NMENTR,IEUL,IFACE,
+ PELEM,QELEM,UXELEM,UYELEM,UZELEM,
+ RHOEL,SIEEL,UXSEG,UYSEG,UZSEG,
+ PFACE,UXFACE,UYFACE,UZFACE,RHOFAC,
+ SIEFAC,AREA,SX ,SY,SZ,
+ COEFFV,CMATNO)
*
#include "spdbl"
*
* input arguments
CHARACTER*(LENNAM) CEXPOR(*)
812 EXPOR2
User-defined Porosity Mode for Multi-material Euler
DIMENSION IEUL(*),IFACE(*)
DIMENSION PELEM(*),QELEM(*),UXELEM(*),UYELEM(*),
+ UZELEM(*), RHOEL(*),SIEEL(*)
DIMENSION AREA(*),SX(*),SY(*),SZ(*)
*
* output arguments
DIMENSION PFACE(*),UXFACE(*),UYFACE(*),UZFACE(*),RHOFAC(*),
+ SIEFAC(*)
DIMENSION COEFFV(*)
CHARACTER*8 CMATNO(*)
*
#include "constants"
*
DO 100 NSEG=1,NMENTR
IF (CEXPOR(NSEG) (1:LENNAM).EQ.'INFLOW') THEN
UXFACE(NSEG) = 0D0
UYFACE(NSEG) = 200D0
UZFACE(NSEG) = 0D0
RHOFAC(NSEG) = 1100D0
SIEFAC(NSEG) = 0D0
COEFFV(NSEG) = 1.0D0
*
CMATNO(NSEG) = '4'
ENDIF
*
100 CONTINUE
RETURN
END
EXSHR 813
User-specified Shear Behavior
The EXSHR user subroutine defines the shear modulus, SHEAR, for Lagrangian solid elements or
Eulerian elements with shear strength, for all elements in the string (ISTART ... IEND).
Calling Sequence
CALL EXSHR (MATNAM, LENNAM, TIME, NCYCLE, DLTH,
+ EXX, EYY, EZZ, EXY, EYZ, EZX,
+ PRES, EDIS, SIE, RHO, FBURN, ZMASS,
+ SHEAR, ISTART, IEND)
Input
MATNAM Character string
Name of the material
LENNAM Integer variable
Length of MATNAM
TIME Real variable
Time at the current time step
NCYCLE Integer variable
Cycle number of the current time step
DLTH Real variable
Time step increment at the current time step
EXX,..,EZX(*) Real arrays
Strain components in element
PRES(*) Real array
Pressure in the element
EDIS(*) Real array
Distortional energy of the element
SIE(*) Real array
Specific internal energy of the element
RHO(*) Real array
Density of the element
FBURN(*) Real array
Burn fraction of the element
814 EXSHR
User-specified Shear Behavior
Input
ZMASS(*) Real array
Mass of the element
EFFSTS(*) Real array
Old effective stress of the element
ISTART Integer
First element in string
IEND Integer
Last element in string
Output
SHEAR (*) Real array
Shear modulus of the element
Remarks
1. The subroutine must be included if there are any SHREX entries in the input.
2. The FBURN array is only used for Eulerian material with strength.
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
Example
In this example, the shear modulus will be computed as a function of the shear strain. The routine returns
the shear modulus SHEAR to the code.
SUBROUTINE EXSHR
+ (MATNAM, LENNAM, TIME, NCYCLE, DLTH,
+ EXX, EYY, EZZ, EXY, EYZ, EZX,
+ PRES, EDIS, SIE, RHO, FBURN, ZMASS,
+SHEAR, ISTART, IEND)
*
INCLUDE DOUBLE PRECISION (A-H,O-Z)
*
DIMENSION SHEAR(*)
DIMENSION EDIS(*),ZMASS(*),SIE(*),RHO(*),FBURN(*),PRES(*)
IMENSION EXX(*),EYY(*),EZZ(*),EXY(*),EYZ(*),EZX(*)
*
CHARACTER*80 MATNAM
*
*
* Example of shear modulus as a function of shear strain.
*
DO 100 NZ = ISTART, IEND
*
* define the shear modulus
EXSHR 815
User-specified Shear Behavior
Calling Sequence
CALL EXSPR (N, M, IX, IC, PROP, HISV, FORCEO, C, DI,
+ V, UREL, DUREL, VREL, XMASS, FORCE, STIFF)
Input
N Integer variable
Element number
M Integer variable
Property number
IX(2) Integer array
Connectivity
IX(1) = grid point at end 1.
IX(2) = grid point at end 2.
IC(2) Integer array
Unused
PROP(7) Real array
Properties as input on the PSPREX entry
HISV(6) Real array
History variables for the element. This array can be used by the user to store
variables from one time step to the next.
FORCEO Real variable
Force in the element at the previous time step
C(3,2) Real array
Deformed coordinates in the basic coordinate system
C(1:3,1) = x-, y-, z-coordinates at end 1.
C(1:3,2) = x-, y-, z-coordinates at end 2.
DI (6,2) Real array
Incremental displacements in the basic coordinate system:
DI(1:3,1) = x, y, z, translational displacements of end 1
DI(4:6,1) = x, y, z, rotational displacements of end 1
EXSPR 817
User-defined CSPR Spring Element
Input
DI(1:3,2) = x, y, z, translational displacements of end 2
DI(4:6,2) = x, y, z, rotational displacements of end 2
These are incremental displacements; i.e., the displacements for this time
step only.
V(6,2) Real array
Velocities in the basic coordinate system:
V(4:6,1) = x, y, z, rotational velocities of end 1
V(4:6,1) = x, y, z, rotational velocities of end 1
V(1:3,2) = x, y, z, translational velocities of end 2
V(4:6,2) = x, y, z, rotational velocities of end 2
UREL Real variable
Relative displacement of the element; i.e., the displacement of end 2 in the spring
direction minus the displacement of end 1.
DUREL Real variable
Relative incremental displacement of the element.
VREL Real variable
Relative velocity of the end points of the element in the direction of the element
XMASS(2) Real array
Mass of the grid points at ends 1 and 2
Output
FORCE Real variable
Force in the element
STIFF Real variable
Current stiffness of the element
Remarks
1. This subroutine must be included if the PSPREX entry is specified in the Bulk Data Section.
2. The velocities (V) and accelerations (A) of the end points can be updated by the user subroutine
when required.
3. The stiffness is used by Dytran to estimate the time step. A nonzero value must be returned.
4. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
818 EXSPR
User-defined CSPR Spring Element
Example
This example defines the stiffness and the corresponding force for a spring element.
SUBROUTINE EXSPR
+ (N,M,IX,IC,PROP,HISV,FORCEO,C,DI,V,UREL,DUREL,
+ VREL,XMASS,FORCE,STIFF)
*
single or double defined below
IMPLICIT DOUBLE PRECISION (A-H,O-Z)
*
* declare argument as arrays and data-type here....
DIMENSION IX(2),IC(2),PROP(7),HISV(6),C(3,2),
+ DI(6,2),V(6,2),XMASS(2)
*
* define the stiffness and the corresponding force
RMASS = 1./(XMASS(1) + XMASS(2))
STIFF = RMASS * (XMASS(1)*1.E3 + XMASS(2)*2.E3)
FORCE = STIFF * DUREL
*
RETURN
END
EXTLU 819
User-defined Logical Unit
The EXTLU user subroutine declares Fortran logical unit (LU) numbers for usage by other
user subroutines.
Calling Sequence
CALL EXTLU (LUUSR, LUMAX)
Input
LUMAX Integer
Maximum LU number allowed
Output
LUUSR Integer array
To store declared LU number
Remarks
1. LUMAX is set by Dytran. This value can be used to check whether the user-defined LU number
does not exceed the maximum allowable LU number. LUMAX should not be changed in the
user subroutine.
2. Declared Fortran LU numbers are reserved within Dytran and are used for files you need in other
user subroutines.
3. It is advised to define a common block in the EXTLU subroutine where the user-defined LU
numbers are kept. This common block can be included in any other user subroutine that utilizes
external user-defined files. For example:
COMMON /MSCD_MYLU/ LU01, LU02, LU03, LU04, LU05
Example
LU01 = 80
LU05 = 81
LUUSR(LU01) = LU01
LUUSR(LU05) = LU05
*
* The above statements reserve LU01 and LU05 as user exclusive
LU’s
*
RETURN
END
EXTVEL 821
User-defined Grid Point Constraint
User Subroutines
Constrains the velocity of Lagrangian grid points.
Calling Sequence
CALL EXTVEL (NAME, LENNAM, NGP, XPOS, YPOS, ZPOS,
+ XVEL, YVEL, ZVEL, XAVEL, YAVEL, ZAVEL,PMASS)
Input
NAME Character string
Velocity boundary name
LENNAM Integer variable
Number of characters in NAME
NGP Integer variable
Grid point number
XPOS Real variable
Old x-coordinate of point
YPOS Real variable
Old y-coordinate of point
ZPOS Real variable
Old z-coordinate of point
XVEL Real variable
Tentative x-translational velocity of the point
YVEL Real variable
Tentative y-translational velocity of the point
ZVEL Real variable
Tentative z-translational velocity of the point
XAVEL Real variable
Tentative x-angular velocity of the point
YAVEL Real variable
Tentative y-angular velocity of the point
ZAVEL Real variable
Tentative z-angular velocity of the point
822 EXTVEL
User-defined Grid Point Constraint
Output
XVEL Real variable
Constrained x-translational velocity of the point
YVEL Real variable
Constrained y-translational velocity of the point
ZVEL Real variable
Constrained z-translational velocity of the point
XAVEL Real variable
Constrained x-angular velocity of the point
YAVEL Real variable
Constrained y-angular velocity of the point
ZAVEL Real variable
Constrained z-angular velocity of the point
PMASS Real variable
Grid point mass
Remarks
1. This subroutine must be included if there are any FORCEEX entries in the input file.
2. The subroutine returns the constrained velocities of each grid point.
3. EXTVEL is called once for every grid point referenced on FORCEEX entries.
4. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
Example
This example constrains the x-velocity of grid points with an x coordinate that is positive.
SUBROUTINE EXTVEL
+ (NAME, LENNAM, NGP, XPOS, YPOS, ZPOS, XVEL, YVEL, ZVEL, XAVEL,
+ YAVEL, ZAVEL)
*
IMPLICIT DOUBLE PRECISION (A-H, O-Z)
CHARACTER*(*) NAME
*
* This routine puts the x-velocity to zero when the x-position
of the point is positive.
*
IF (XPOS.GT.0) XVEL = 0.
*
RETURN
END
EXVISC 823
User-defined CVISC Damper Element
Calling Sequence
CALL EXVISC (N, M, IX, IC, PROP, HISV, FORCEO, C, DI,
+ V, UREL, DUREL, VREL, XMASS, FORCE)
Input
N Integer variable
Element number
M Integer variable
Property number
IX(2) Integer array
Connectivity
IX(1) = grid point at end 1.
IX(2) = grid point at end 2.
IC(2) Integer array
Unused
PROP(7) Real array.
Properties as input on the PVISCEX entry
HISV(6) Real array
History variables for the element. This array can be used by the user to store
variables from one time step to the next.
FORCEO Real variable
Force in the element at the previous time step
C(3,2) Real array
Deformed coordinates in the basic coordinate system
C(1:3,1) x, y, z, coordinates at end 1
C(1:3,2) x, y, z, coordinates at end 2
DI(6,2) Real array
Incremental displacements in the basic coordinate system:
DI(1:3,1) x, y, z, translational displacements of end 1
DI(4:6,1) x, y, z, rotational displacements of end 1
824 EXVISC
User-defined CVISC Damper Element
Input
DI(1:3,2) x, y, z, translational displacements of end 2
DI(4:6,2) x, y, z, rotational displacements of end 2
These are incremental displacements; i.e., the displacements for this time
step only.
V(6,2) Real array
Velocities in the basic coordinate system:
V(1:3,1) x, y, z, translational velocities of end 1
V(4:6,1) x, y, z, rotational velocities of end 1
V(1:3,2) x, y, z, translational velocities of end 2
V(4:6,2) x, y, z, rotational velocities of end 2
UREL Real variable
Relative displacement of the element; i.e., the displacement of end 2 in the
damper direction minus the displacement of end 1
DUREL Real variable
Relative incremental displacement of the element
VREL Real variable
Relative velocity of the end points of the element in the direction of the element
XMASS(2) Real array
Mass of the grid points at ends 1 and 2
Output
FORCE Real variable
Force in the element
Remarks
1. This subroutine must be included if the PVISCEX entry is specified in the Bulk Data Section.
2. The velocities (V) and accelerations (A) of the end points can be updated using the user subroutine
if required.
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
EXVISC 825
User-defined CVISC Damper Element
Example
This example defines the damping force for a danger element.
SUBROUTINE EXVISC
+(N,M,IX,IC,PROP,HISV,FORCEO,C,DI,V,UREL,DUREL,
+ VREL,XMASS,FORCE)
*
* single or double defined below
IMPLICIT DOUBLE PRECISION (A-H,O-Z)
*
* declare argument as arrays and data-type here....
DIMENSION IX(2),IC(2),PROP(7),HISV(6),C(3,2),
+ DI(6,2),V(6,2),XMASS(2)
*
* define the force on the damper element
VELX = V(1,1) - V(1,2)
VELY = V(2,1) - V(2,2)
VELZ = V(3,1) - V(3,2)
*
FORCE = 1.E-3 * SQRT(VELX*VELX + VELY*VELY + VELZ*VELZ)
*
RETURN
END
826 EXYLD
User-defined Yield Behavior
The EXYLD user subroutine defines the yield stress, YLDSQ, for Lagrangian solid elements or Eulerian
elements with shear strength, for all elements in the string (ISTART ... IEND).
Calling Sequence
CALL EXYLD (MATNAM, LENNAM, TIME, NCYCLE, DLTH, IZONE,
+ DEZX, TDET, YLDSQ, ISTART, IEND)
+ SXYT, SYZT, SXZT, DEXX, DEYY, DEZZ, DEXY, DEYZ,
+ SYYO, SZZO, SXYO, SYZO, SXZO, SXXT, SYYT, SZZT,
+ EFFSTS, TWOJ2, EFFSR, USRVR1, USRVR2, RELV, SXXO,
+ PRES, EDIS, SIE, RHO, FBURN, EFFPLS, ZMASS,
Input
MATNAM Character string
Name of the material
LENNAM Integer variable
Length of MATNAM
TIME Real variable
Time at the current time step
NCYCLE Integer variable
Cycle number of the current time step
DLTH Real variable
Time step increment at the current time step
IZONE(*) Integer array
Element number
PRES(*) Real array
Pressure in the element
EDIS(*) Real array
Distortional energy of the element
SIE(*) Real array
Specific internal energy of the element
RHO(*) Real array
Density of the element
EXYLD 827
User-defined Yield Behavior
Input
FBURN(*) Real array
Burn fraction of the element
EFFPLS(*) Real array
Effective plastic strain of the element
ZMASS(*) Real array
Mass of the element
EFFSTS(*) Real array
Old effective stress of the element
TWOJ2(*) Real array
Trial second invariant at current time of the element
EFFSR(*) Real array
Effective strain rate of the element
USRVR1(*) Real array
User variable 1 of the element
USRVR2(*) Real array
User variable 2 of the element
RELV(*) Real array
Relative volume of the element
SXXO(*)...SXZO(*) Real arrays
Old deviatoric stresses of the element
SXXT(*)...SXZT(*) Real arrays
Trial deviatoric stresses at current time of the element
DEXX(*)...DEZX(*) Real arrays
Strain rate components of the element
TDET(*) Real array
Detonation time of the element
ISTART Integer
First element in string
IEND Integer
Last element in string
Output
YLDSQ(*) Real array
Yield stress of the element
828 EXYLD
User-defined Yield Behavior
Remarks
1. The subroutine must be included if there are any YLDEX entries in the input.
2. The FBURN array is only used for Eulerian material with strength. The IZONE array and the
USRVR1-2 arrays can only be used for Lagrangian material.
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
Example
In this example, the yield stress is computed as a function of the effective strain rate and the pressure.
The routine returns the yield stress YLDSQ to the code. The USRVR1 and USRVR2 arrays are used to
store the yield stress and the effective strain rate in memory so that they can be requested as output.
SUBROUTINE EXYLD
+ (MATNAM, LENNAM, TIME, NCYCLE, DLTH, IZONE, PRES, EDIS, SIE,
+ RHO, FBURN, EFFPLS, ZMASS, EFFSTS, TWOJ2, EFFSR, USRVR1,
+ USRVR2, RELV, SXXO, SYYO, SZZO, SXYO, SYZO, SXZO, SXXT,
+ SYYT, SZZT, SXYT, SYZT, SXZT, DEXX, DEYY, DEZZ, DEXY,
+ DEYZ, DEZX, TDET, YLDSQ, ISTART, IEND)
C
IMPLICIT DOUBLE PRECISION (A-H, O-Z)
C
DIMENSION IZONE(*)
DIMENSION YLDSQ(*)
DIMENSION EDIS(*),ZMASS(*),EFFSTS(*),TDET(*)
DIMENSION SIE(*),RHO(*),FBURN(*),EFFPLS(*),EFFSR(*)
DIMENSION TWOJ2(*),PRES(*),RELV(*)
DIMENSION USRVR1(*), USRVR2(*)
DIMENSION SXXO(*),SYYO(*),SZZO(*),SXYO(*),SYZO(*),SXZO(*)
DIMENSION SXXT(*),SYYT(*),SZZT(*),SXYT(*),SYZT(*),SXZT(*)
DIMENSION DEXX(*),DEYY(*),DEZZ(*),DEXY(*),DEYZ(*),DEZX(*)
C
CHARACTER*80 MATNAM
C
C
C Example of yield stress as a function of
C effective strain rate and pressure.
C
DO 100 NZ = ISTART, IEND
C
C define the yield stress.
YLDSQ(NZ) = EFFSR(NZ)*SQRT(ABS(PRES(NZ)))
C
C store the yield stress and effective strain
C rate in the user vars, so that they can be
C requested as output.
USRVR1(NZ) = YLDSQ(NZ)
USRVR2(NZ) = EFFSR(NZ)
100 CONTINUE
*
RETURN
END
EXYLD1 829
User-specified Yield Behavior
The EXYLD1 user subroutine defines the yield stress, YLDSQ, for Eulerian elements with shear strength,
for all elements in the string (ISTART ... IEND). The yield stress can depend on a damage variable
and the SOFTE and VOLPLS variables. These last two variables can be set in, for example, an FAILEX2
routine or in an EXEOS1 routine.
Calling Sequence
CALL EXYLD1 (MATNAM, LENNAM, TIME, NCYCLE, DLTH, IZONE,
+ DEZX, TDET, YLDSQ, DAM, SOFTE,VOLPLS,ISTART, IEND)
+ SXYT, SYZT, SXZT, DEXX, DEYY, DEZZ, DEXY, DEYZ,
+ SYYO, SZZO, SXYO, SYZO, SXZO, SXXT, SYYT, SZZT,
+ EFFSTS, TWOJ2, EFFSR, USRVR1, USRVR2, RELV, SXXO,
+ PRES, EDIS, SIE, RHO, FBURN, EFFPLS, ZMASS,
Input
MATNAM Character string
Name of the material
LENNAM Integer variable
Length of MATNAM
TIME Real variable
Time at the current time step
NCYCLE Integer variable
Cycle number of the current time step
DLTH Real variable
Time step increment at the current time step
IZONE(*) Integer array
Element number
PRES(*) Real array
Pressure in the element
EDIS(*) Real array
Distortional energy of the element
SIE(*) Real array
Specific internal energy of the element
830 EXYLD1
User-specified Yield Behavior
Input
RHO(*) Real array
Density of the element
FBURN(*) Real array
Burn fraction of the element
EFFPLS(*) Real array
Effective plastic strain of the element
ZMASS(*) Real array
Mass of the element
EFFSTS(*) Real array
Old effective stress of the element
TWOJ2(*) Real array
Trial second invariant at current time of the element
EFFSR(*) Real array
Effective strain rate of the element
USRVR1(*) Real array
User variable 1 of the element
USRVR2(*) Real array
User variable 2 of the element
Relative volume of the element
RELV(*) Real array
SXXO(*)...SXZO(*) Real arrays
Old deviatoric stresses of the element
SXXT(*)...SXZT(*) Real arrays
Trial deviatoric stresses at current time of the element
DEXX(*)...DEZX(*) Real arrays
Strain rate components of the element
TDET(*) Real array
Detonation time of the element
ISTART Integer
First element in string
IEND Integer
Last element in string
EXYLD1 831
User-specified Yield Behavior
Input
DAM(*) Real array
Damage
SOFTE(*), VLPL(*) Arrays that allow the user to store an additional variable. Contents are
transported and clumped. This array can also be accessed within EXFAIL2.
Output
YLDSQ(*) Real array
Yield stress of the element
Remarks
1. The subroutine must be included if there are any YLDEX entries in the input.
2. The FBURN array is only used for Eulerian material with strength. The IZONE array and the
USRVR1-2 arrays can only be used for Lagrangian material.
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
Example
In this example, the yield stress will be given by the Johnson-Cook yield model. The yield stress will be
reduced using the damage variable. This reduction is equivalent to continuous failure.
SUBROUTINE EXYLD1
+ (MATNAM,LENNAM,TIME,NCYCLE,DLTH,
+ IZONE,PRES,EDIS,
+ SIE,RHO,FBURN,EFFPLS,ZMASS,EFFSTS,TWOJ2,
+ EFFSR,USRVR1,USRVR2,RELV,
+ SXXO,SYYO,SZZO,SXYO,SYZO,SXZO,
+ SXXT,SYYT,SZZT,SXYT,SYZT,SXZT,
+ DEXX,DEYY,DEZZ,DEXY,DEYZ,DEZX,
+ TDET,YLDSQ,DAM,SOFTE,VOLPLS,ISTART,IEND)
$cmsc/dytran ompstk
*
#include "spdbl"
*
*---------------------------------------------------------
* input:
* matnam - name on exyld entry
* lennam - length of name
* time - time
* ncycle - cycle
* dlth - time step
* izone - (lagrange) element number
* pres - old element pressure
* edis - old element distortional energy
* sie - old element specific internal energy
* rho - element density
* fburn - (euler) burn fraction of element
832 EXYLD1
User-specified Yield Behavior
YLDA =
YLDB =
YLDC =
YLDN =
YLDM =
SPHEAT =
TROOM =
TMELT =
EFSTN0 =
*
DO 50 NZ=ISTART,IEND
TEMP = SIE(NZ)/SPHEAT
TEMP = (TEMP-TROOM)/(TMELT-TROOM)
TEMP =MAX(SMALL,TEMP)
TEMP =MIN(ONE,TEMP)
EFFSTN = SQRT(3./2.*TWOJ2(NZ))/(3.*SHEAR*DLTH)
EFFSTN = EFFSTN/EFSTN0
EFFSTN =MAX(ONE,EFFSTN)
EFFPLS(NZ) = MAX(ZERO,EFFPLS(NZ))
TMP1 = YLDA+YLDB*EFFPLS(NZ)**YLDN
TMP2 = ONE+YLDC*LOG(EFFSTN)
TMP3 = ONE-TEMP**YLDM
YLDSQ(NZ) = TMP1*TMP2*TMP3
YLDSQ(NZ) = (ONE-DAM(NZ))*YLDSQ(NZ)
50 CONTINUE
*
*
#include "call_byebye"
RETURN
END
834 GEXOUT
User-defined Grid Point Output
Calling Sequence
CALL GEXOUT (NAME, LENNAM, NGP, CGP, NGTYPE, LIGRD, LXGRD)
Input
NAME Character string
Output name specified on the GPEXOUT entry.
LENNAM Integer variable
Length of NAME
NGP(*) Integer array
Grid-point number
CGP(*) Character *8 array
Unused
NGTYPE Integer variable
Type of element to which the grid point is attached:
2 One-dimensional element
3 Triangular shell
4 Quadrilateral shell
5 Triangular membrane
6 Dummy triangle
7 Dummy quadrilateral
8 Lagrangian solid
9 Eulerian solid (hydrodynamic)
10 Eulerian solid (with strength)
11 Eulerian solid (multimaterial)
LIGRD(*) Integer array
Base address of grid point in the main integer storage array ILGDAT
LXGRD(*) Integer array
Base address of grid point in the main real storage array XLGDAT
GEXOUT 835
User-defined Grid Point Output
Remarks
1. This subroutine must be included if there are any GPEXOUT Case Control commands.
2. The subroutine can be used to calculate results based on the data available in Dytran.
3. The precision of the calculations should be appropriate for the computer being used. See the
Dytran Installation and Operations Guide.
4. This subroutine is vectorized. All the input data is stored in arrays, which must be dimensioned.
The start and end of the arrays is given by the variables LST and LFIN in the common block
/MSCD_LOCLOP/. All of the entries in the arrays between LST and LFIN must be output. See
the following example.
5. Access to grid-point variables is possible by including calls to the subroutines listed in User
Subroutines using the variable names from Outputting Results.
Example
This example outputs the total force on a grid point to the primary output (unit 6).
SUBROUTINE GEXOUT
+ (NAME, LENNAM, NGP, CGP, NGTYPE, LIGRD, LXGRD)
*
IMPLICIT DOUBLE PRECISION (A-H, O-Z)
*
DIMENSION NGP (*), LIGRD(*), LXGRD(*)
CHARACTER *(*) NAME
CHARACTER*8 CGP(*)
*
COMMON/MSCD_LOCLOP/LST, LFIN
COMMON/MSCD_XLGMEM/XLGDAT(1)
*
IF (NGTYPE.NE.8) GOTO 9900
*
* The total force on each Lagrangian node is printed out.
*
DO 100 NG = LST, LFIN
FTOT = XLGDAT(LXGRD(NG) +7)**2+
+ XLGDAT(LXGRD(NG)+8)**2+
+ XLGDAT(LXGRD(NG)+9)**2
FTOT = SQRT (FTOT)
WRITE (6, 101) NGP (NG), FTOT
101 FORMAT (1X, ’Force on node’, I5, ‘is‘, E13.5)
100 CONTINUE
*
9900 RETURN
END
836 GEXOUT
User-defined Grid Point Output
Chapter 8: Diagnostic Messages
Dytran Reference Manual
8 Diagnostic Messages
838 Dytran Reference Manual
Whenever Dytran encounters invalid or inconsistent data in the input file or a problem is encountered
during the analysis, a diagnostic message is printed.
Diagnostic messages produced during the initialization and solution are written to the
<jobname>_ERROR_SUMMARY-MSG file. These messages normally indicate incorrect or inconsistent
data and problems encountered during the solution.
Each diagnostic message is produced a maximum of five times to prevent large quantities of output from
being produced.
The diagnostic message is a set of short codes that indicate the severity of the message, its number, and
the subroutine that generated it. One or more lines of text follows, indicating what the problem is.
The coded line has the basic form:
%x-<diagnostic number>-<subroutine name>
where x indicates the severity:
• I Information
• W Warning
• E Error
• F Fatal
• C Catastrophic
Information messages do not indicate a problem, and the analysis should continue successfully.
Warnings are not fatal, and the analysis will continue. However, warnings are an indication that
something about analysis is not normal. You should review all warnings carefully and make sure you
know what is causing the message.
%W-P3007905-P3XXTXX_CYCLE_ZERO
Authorization files will expire this month
Error messages indicate that there is almost certainly something wrong with your analysis. You should
review your input and modify it appropriately. Errors in the solution cause termination at the end of the
current time step. If you specified output at the end of the analysis, then the output is produced before the
analysis terminates.
%E-CN000602-SYS_CHECK_RST_INPUT_FILE
Restart input file must have extension .RST
Fatal messages have the same effect as error messages but indicate a more serious problem.
%F-2039502-P2XXTXIX_PACKET_EDIT
Materials cannot be put on archive files, only on time history files.
Catastrophic errors are issued only when the program would otherwise crash. They may occur, for
example, when the analysis would result in a division by zero.
%C-P2057301-C2_STORE_IZONER_FOR_CFACE
Face number -4 is illegal
Chapter 8: Diagnostic Messages 839
The severity code letter is followed by the unique diagnostic number. There is a unique number for each
diagnostic message and it can be used to reference the message. The subroutine name indicates which
routine produced the diagnostic message. Note that the routine names in Dytran consist of up to 31
characters.
Internal program errors have the message (PROGRAM ERROR) at the end of the first line of the diagnostic
message, e.g.,
%E-CN000502-SYS_CHECK_RST_INPUT_FILE (PROGRAM ERROR)
RESTART INPUT FILE HAS WRONG EXTENSION
You should never get program errors. If you do, check if there are other diagnostic messages indicating
other problems. If not, please note the diagnostic number and contact your local MSC representative.
Redefinition of severity and number of prints of diagnostic messages can be performed by using
PARM,ERRUSR. This parameter has to be used carefully.
840 Dytran Reference Manual
Appendix A References
Dytran Reference Manual
A References
842 Dytran Reference Manual