当前位置：文档库 › ls-dyna_database

ls-dyna_database

LS-DYNA? Database Binary Output Files

Revised October 2012

LIVERMORE SOFTWARE TECHNOLOGY CORPORATION

LS-DYNA DATABASE

Support Address

Livermore Software Technology Corporation

7374 Las Positas Road

Livermore, California 94551

Tel: 925 449 2500

Fax: 925 449 2507

Email: support@https://www.wendangku.net/doc/a75518525.html,

LS-DYNA, LS-OPT and LS-PREPOST are registered trademarks of Livermore Software Technology Corporation.

LS-DYNA DATABASE

TABLE OF CONTENTS INTRODUCTION (1)

STATE DATABASE (d3plot and d3part) (2)

CONTROL DATA (3)

MATERIAL TYPE DATA (7)

FLUID MATERIAL ID DATA (8)

SMOOTH PARTICLE HYDRODYNAMICS ELEMENT DATA FLAGS (9)

PARTICLE DATA (NPEFG > 0) (10)

GEOMETRY DATA (11)

USER MATERIAL, NODE, AND ELEMENT IDENTIFICATION NUMBERS (12)

EXTRA 2 NODE CONNECTIVITY ARRAY FOR 10 NODE TETRAHEDRON

ELEMENTS (ONLY IF NEL8 < 0) (13)

SMOOTH PARTICLE HYDRODYNAMICS NODE AND MATERIAL LIST (13)

RIGID ROAD SURFACE DATA (14)

HEADER, PART & CONTACT INTERFACE TITLES (15)

DESCRIPTION OF BINARY FILE TYPES (16)

EXTRA DATA TYPES (OUTPUT FOR MULTI-SOLVER ANALYSIS) (17)

STATE DATA (24)

ELEMENT DELETION OPTION (31)

SMOOTH PARTICLE HYDRODYNNAMICS NODE/ELEMENT STATE DATA (32)

PARTICLE STATE DATA (NPEFG > 0) (33)

ROAD SURFACE MOTION (33)

EXTRA DATA (MULTI-SOLVER ANALYSIS) (34)

END OF FILE MARKER (38)

TIME HISTORY DATABASE (d3thdt) (39)

CONTROL DATA (39)

SMOOTH PARTICLE HYDRODYNAMICS ELEMENT DATA FLAGS (42)

GEOMETRY DATA (43)

USER MATERIAL, NODE, AND ELEMENT IDENTIFICATION NUMBERS (44)

TIME HISTORY DATA (46)

INTERFACE FORCE DATABASE (56)

CONTROL DATA (56)

GEOMETRY DATA (58)

USER MATERIAL, NODE, AND ELEMENT IDENTIFICATION NUMBERS (59)

STATE DATA (61)

FSIFOR FILE OUTPUT: (62)

LS-DYNA DATABASE

BLSTFOR FILE (NV2D=16 OR 7) OUTPUT: (62)

CRACK FILE (d3crck) (64)

DYNAIN BINARY FILE FORMAT (dynain.bin) (68)

EXTRA DATA TYPE DEFINITIONS (NCFDV1 = 67108864) (69)

LS-DYNA DATABASE

INTRODUCTION

Three databases are discussed, these are:

1.State Database (G=ptf, default name d3plot and d3part)

2. Time History Database (F=thf, default name d3thdt)

3. Interface Force Database (S=iff, no default name, typically: intfor)

The purpose of this information is to give guidance on how to access and read the various databases.

The databases are written as word addressable fixed length binary files. The actual length depends on the amount of data saved, but will always be a multiple of 512 words (4 or 8 bytes each). Since it is likely that the database cannot be contained in a single file of length, FEMLEN, the data will spread over several files known as a family of files. Having a set of files enables them to be handled more easily than a single very large file. The root name for a family is the name of the first file member. Successive member names are compiled by appending a two or three digit number to the root name starting with 01, 02, through to 99, then 100 and ending with 999. Root names are limited to 75 characters. The original reason for a family of files was because the hard disks used for dyna3d runs could not cope with a single contiguous files large enough to contain all the data output. Subsequently, it has been found that splitting the output into separate files allows some unwanted data to be discarded and aids the copying, saving and movement of the data. Very large files can be impossible to transfer reliably over networks. Total output data can amount to several gigabytes or more depending on the model size.

For ls-dyna runs with mesh adaptivity, the root name has a two letter appendage for each adapted mesh. Starting from ‘aa’ through ‘az’, then ‘ba’ through ‘bz’ and continuing up to ‘zz’, this gives a maximum of 676 possible adaptions. For example if the root name is ‘d3plot’ the subsequent files related to the original mesh are ‘d3plot01’, d3plot02, …, after adaption the new mesh and undeformed geometry is put in ‘d3plotaa’ and the subsequent files for the new mesh are: ‘d3plotaa01’, d3plotaa02, … The next adapted mesh will be in file ‘d3plotab’ and so on.

A set of files at a particular adaption can be read separately by giving the root name with appendage, as the base file name.

For example command: ‘lsprepost d3plot’ will read in all the file with root name ‘d3plot’ While: ‘lsprepost d3plotab’ will read in only files have ‘d3plotab’ in the name.

LSPREPOST will read the binary databases separately or combined.

Eg: lsprepost d3plot, lsprepost d3thdt, lsprepost iffname, lsprepost d3plot h=d3thdt f=iffname

LS-DYNA DATABASE

The file length used is set in the ls-dyna run as the default size of 7x512x512 words. The size can be changed on the command line with the ‘x=factor’ parameter giving a size of: factor x512x512 words.

If the initial data or state data is larger than the given file length, the data will automatically split across files. This condition is not desirable because it is not clear whether any non root file can be discarded without destroying the continuity of the data. Ls-dyna checks before writing to a file, to ensure that there is room left in the file to contain the data at a particular state time. If not, it closes the current family member and starts writing the state data in the next file member. The files are written with a block size of 512 words, and if the data does not complete the last block it is padded out. This means that files cannot be concatenated and read together. The word size is 4 bytes for the single precision version of ls-dyna and 8 bytes for the double precision version, unless 32bit ieee format is defined, see *DATABASE_FORMAT, IBINARY.

FILE GENERAL STRUCTURE

The root file starts with a control words section, followed by node coordinates, then element connectivity for solids, thick shells, beams, and shells. Next are lists to reference the sequential internal numbering to the users number. State data is output next always starting with the time word. Data is of fixed length through the file members except where the mesh is adapted. The length of each area can be calculated from the information in the control words. The first file at adaption is like the root file in structure, so the new control words are used to recalculate the size of the subsequent data. The root file contains the initial data and also state data if there is room to write it. Further state data is written to the family members and each file will start with the time word provided data from the previous state did not overflow onto the file.

If the disk address, DA, of the data being written exceeds the maximum file length, then data is written into file number int(DA/FAMLEN) at location DA-FAMLEN*int(DA/FAMLEN). If the state length is greater than the remaining length, the disk address is increased to start the writing at the beginning of the next file.

STATE DATABASE (d3plot and d3part)

There are three sections in this database. The first contains 64 words of control information plus extensions. The second contains geometric information including the nodal coordinates and element connectivities and user numbering lists. The third section contains the

LS-DYNA DATABASE

results of the analysis at sequential output intervals. The output at a given time, called a state, contains a time word, global variables such as total energies and momenta for the whole model and each material (part), node data consisting of displacements, velocities, accelerations, and optionally temperatures, and finally element data that can include stresses and strains at integration points, and element deletion flags. The control data provides information about what is in the file and is used to calculate the various data length.

There are two other state database files, namely: d3drfl and d3part, these are similar to d3plot but contain less data. The dynamic relaxation file, d3drfl, provides the state at the end of the DR process, while d3part is state output for a reduced number of parts in the model.

CONTROL DATA

DISK

VALUE #WORDS ADDRESS DESCRIPTION

Title 10 0 Model identification

Run time 1 10 time in seconds since 00:00:00 UTC, January 1, 1970 INUM (File type) 1 11 d3plot=1

1=d3plot, 2=d3drlf, 3=d3thdt, 4=intfor, 5=d3part

6=blstfor, 7=d3cpm, 8=d3ale, 11=d3eigv,

12=d3mode, 13=d3iter, 21=d3ssd, 22=d3spcm,

23=d3psd, 24=d3rms, 25=d3ftg, 26=d3acs If > 1000, File type=INUM-1000

all external(users) numbers (Node, Element, Material and Rigid Surface Nodes) will be

written in I8 format.

Length of arbitrary numbering array = NARBS * 8 bytes for single precision files.

Source version 1 12 ls-dyna version *1000000 + svn number

Release number 1 13 Release number in character*4 form

50 for R5.0

511c for R5.1.1c

Version 1 14 Code version, floating number, eg 960.0 it is used to

distinguish the floating point format, like cray, ieee,

and dpieee

NDIM 1 15 Number of dimensions (2 or 3). If 5 or 7 then an array

of material types is read (MATTYP=1), element

connectivities are unpacked and NDIM=3. If 4 then

element connectivies are unpacked in the DYNA3D

LS-DYNA DATABASE

database and NDIM is reset to 3. If >5 then state data

contains movement of rigid road surface.

NUMNP 1 16 Number of nodal points

ICODE 1 17 Flag to identify finite element code=2: old DYNA3D,

code=6: NIKE3D, LS-DYNA/3D, LS-NIKE3D

database

NGLBV 1 18 Number of global variable to be read with each state

NUMRW=number of rigid walls.

NUMRBS=number of rigid body sets.

= 6 + 6 * (NUMMAT8 + NUMMAT2 + NUMMAT4

+ NUMATT+NUMRBS) + NUMRW * N

N = 1 for DYNA3D and LS-DYNA3D

N = 4 for LS-DYNA >= version 971 IT 1 19 Flag for temperatures

= 0, none,

= 1, read in a temperature for each node

= 2, read temperature for each node and heat flux

for each node.

= 3, read thermal shell middle temperature,

thermal shell inner temperature,

thermal shell outer temperature, and heat flux

for each node. Solid node temperatures are

repeated

+=10, read mass scaling value for each node IU 1 20 Flag for current geometry (=1 or 0)

IV 1 21 Flag for velocities (=1 or 0)

IA 1 22 Flag for accelerations (=1 or 0)

NEL8 1 23 Number of 8 node solid elements

If NEL8 < 0, 2 extra nodes are output for ten node

solids. Array is 2 * abs(NEL8), and is read after the

arbitrary numbering arrays.

NUMMAT8 1 24 Number of materials used by the

8 node solids

BLANK 1 25 Insert zero

BLANK 1 26 Insert zero

NV3D 1 27 Number of values in database for each solid element.

=7+NEIPH

If NV3D is 8 * (7+NEIPH), each solid element has

values at each Gauss point.

NEL2 1 28 Number of 2 node one-dimensional elements

NUMMAT2 1 29 Number of materials used by the 2 node 1D elements

LS-DYNA DATABASE NV1D 1 30 Number of values in database for each 1D element

= 6 + BEAMIP * 5

NEL4 1 31 Number of four node two-dimensional elements NUMMAT4 1 32 Number of materials used by the 4 node 2D elements NV2D 1 33 Number of values in database for each 2D element

Are: MAXINT*(6*IOSHL(1)+IOSHL(2)+NEIPS)+8

*IOSHL(3)+4*IOSHL(4)+12*ISTRN

NEIPH 1 34 Number of additional values per solid element to be

written in the type 6 database,NV3D=7+NEIPH,

Actual number of history variables=NEIPH-6*ISTRN NEIPS 1 35 Number of additional values per integration point to be

written into the type 6 database for shell elements. MAXINT 1 36 Number of integration points dumped for each shell.

The magnitude of MAXINT must be greater than or

equal to 3.

if MAXINT>=0, then

MDLOPT=0

MAXINT=MAXINT

elseif MAXINT<0, then

MDLOPT=1

MAXINT=abs(MAXINT)

elseif MAXINT<10,000, then

MDLOPT=2

MAXINT=abs(MAXINT)-10,000

endif

MDLOPT controls the element deletion table (see

below). The increase in state lengths allows deletion

by nodes or elements.

EDLOPT 1 37 Element deletion flag (not standard)

=xxx1 Solids deleted

=xx1x Beams deleted

=x1xx Shells deleted

=1xxx Thick Shells deleted

(Not used in LS-DYNA)

NMSPH 1 37 Number of SPH Nodes

NGPSPH 1 38 Number of SPH materials

NARBS 1 39 Additional storage required for arbitrary node and

element numbering in type 6 database

=0 Sequential numbering

=(10+NUMNP+ NEL8+NEL2+NEL4+NELT).

LS-DYNA DATABASE

NELT 1 40 Number of 8 node thick shell elements.

MAXINT*(6*IOSHL(1)+IOSHL(2)+NEIPS)+

12*ISTRN

NUMMATT 1 41 Number of materials used for the 8 node thick shell

element.

NV3DT 1 42 Number of values in database for each thick shell

IOSHL(1) 1 43 6 stress components flag, if 1000 =1 else =0

IOSHL(2) 1 44 Plastic strain flag, if 1000 =1 else =0

IOSHL(3) 1 45 Shell force resultants flag, if 1000 =1 else =0

IOSHL(4) 1 46 Shell thickness, energy+2 others, if 1000 =1 else =0 IALEMAT 1 47 Size of array containing solid element parts numbers

used as ALE material

NCFDV1 1 48 Bit flags for CFD nodal values. If = 67108864, then state

contains CFD extra data – see below (ls980 version) NCFDV2 1 49 Further bit flags for CFD nodal values. If extra data, then

value equals number of data domains (ls980 version) NADAPT 1 50 Number of adapted element to parent pairs (not

implemented)

NMMAT 1 51 Total number of materials – not set in LS-DYNA/3D NUMFLUID 1 52 Total number of ALE fluid groups. Fluid density and

volume fractions output as history variables, and a flag

for the dominant group. If negative multi-material

species mass for each group is also output. Order is: rho,

vf1, … vfn, dvf flag, m1, … mn. Density is at position 8

after the location for plastic strain. Any element material

history variables are written before the Ale variables, and

the six element strains components after these if

ISTRN=1.

INN 1 53 Invariant node numbering fore shell and solid elements

See INN in card *CONTROL_ACCURACY NPEFG 1 54 Number of particle method data sets.

NVEFG 1 55 Not used.

IDTDT 1 56 Rate of change of temperature per node flag.

LS-DYNA DATABASE

An array of dT/dt values of length NUMNP. Array is

written after node temperature arrays.

NWORD 1 57 Additional number of control words.

WORDS 6 58-63 Used by D3THDT and INTFOR

The value of ISTRN must be computed, it is not output in the control data

ISTRN can only be computed as follows and if NV2D > 0.

If NV2D-MAXINT*(6*IOSHL(1)+IOSHL(2)+NEIPS)+8*IOSHL(3)+4*IOSHL(4) > 1

Then ISTRN = 1, else ISTRN = 0

If ISTRN=1, and NEIPH>=6, last the 6 additional values are the six strain components.

Or NELT > 0

If NV3DT-MAXINT*(6*IOSHL(1)+IOSHL(2)+NEIPS) > 1

Then ISTRN = 1, else ISTRN = 0

MATERIAL TYPE DATA

The material section contains the material type numbers. This section is skipped if MATTYP is zero.

This data is required because those shell elements that are in a rigid body have no element data output in the state data section. The normal length of the shell element state data is:

NEL4 * NV2D, when the MATTYP flag is set the length is: (NEL4 – NUMRBE) * NV2D. When reading the shell element data, the material number must be check against IRBRTYP list to find the element’s material type. If the type = 20, then all the values for the element to zero. This option is set in *DATABASE_EXTENT_BINARY, with DCOMP=2

VALUE LENGTH DESCRIPTION

NUMRBE 1 Number of rigid body shell elements.

NUMMAT 1 Number of materials in the database.

IRBTYP NUMMAT Material type numbers

LS-DYNA DATABASE

FLUID MATERIAL ID DATA

The fluid material section contains the material numbers for solid elements that are used to define an Euler grid or Arbitrary Lagrangian Euler mesh. This section is skipped if IALEMAT is zero.

VALUE LENGTH DESCRIPTION

FLUIDID IALEMAT Fluid material number used in solid element mesh

LS-DYNA DATABASE

SMOOTH PARTICLE HYDRODYNAMICS ELEMENT DATA FLAGS

This section is only output if NMSPH > 0. The section is a list of flags to indicate what SPH data is output for each SPH node/element. The first number is the length in words for this array, currently = 11.

SPH elements are centered at nodes, and cover a spherical volume defined by the radius of influence. They do not have a connection with other SPH elements. They should be displayed as a dot or a spherical surface, with radius scaling to reduce the size and enable each element to be distinguishable.

As follows:

isphfg(1) = 11 - length of sph flags array

isphfg(2) = 1 - radius of influence

isphfg(3) = 1 - pressure in particle

isphfg(4) = 6 - 6 true stress components

isphfg(5) = 1 - plastic strain, > 0.0 if effective stress exceeds yield strength

isphfg(6) = 1 - density of particle material

isphfg(7) = 1 - internal energy (strain)

isphfg(8) = 1 - number of neighbors affecting particle

isphfg(9) = 6 - 6 true strain components

isphfg(10)=1 - mass of element (>= ls971)

isphfg(11)=1 - max number of sph history variables.

If any value of isphfg(2) through isphfg(11) = 0, then the particular data item is not output for the particle. To calculated the size of data add the isphfg values from isphfg(2) through

isphfg(11) plus one. One value is always output which is the material number as a floating point number for each particle.

If this value is negative then the particle has been deleted from the model.

Note: it is possible a SPH element could be deleted, or be non active in the initial states, and become active in later states.

Full output for each particle is:

mat#, radius, pressure, {sx, sy, sz, sxy, syz, sxz} ps, rho, ie, nn, {ex, ey, ez, exy, eyz, exz}, mass, hv1 … hvn.

NUM_SPH_VARS = 1 + sum of isphfg(i), i=2 to isphfg(1)

Hence, total size is 20 + the total number of history variables.

When a particle is deleted from the model, data is still output for it because the length of data must always be the same for each state.

LS-DYNA DATABASE

PARTICLE DATA (NPEFG > 0)

Control block

If NPEFG > 0 airbag particles are output

The first three digits of NPEFG are the number of airbags in the database = NPARTGAS NPARTGAS = NPRFG % 1000

SUBVER = NPEFG / 1000

In the extended control block:

The first four words in the block are:

1. NGEOM number of geometry variables

2. NVAR number of state variables

3. NPART number of particles

4. NSTGEOM number of state geometry variables

If SUBVER == 4

5. NCHAMBER number of chambers

NLIST = NGEOM + NVAR + NSTGEOM

NLIST words of output for variables listed to define the type of each variable, =1 for integer and 2= for floating point

2 * NLIST words of variable names (8 bytes per name or 16 for double precision output).

LS-DYNA DATABASE

GEOMETRY DATA

The geometry section contains the nodal coordinates and the element connectivities. The ordering of the nodal points is the same as the ordering of the nodal data in the state data that follows. If NDIM=3 the connectivities are assumed to be packed with 3 integers per word, if NDIM>3, then connectivities are not pack, (the default for LS-DYNA, LS-DYNA3D and LS-NIKE3D. The order of the elements are 3, 2, and 1 dimensional elements if the database is ICODE=2 or 6.

VALUE LENGTH DESCRIPTION

X(3,1) NDIM*NUMNP Array of nodal coordinates X1,Y1,Z1,

X2,Y2,Z2, X3,Y3,Z3, ... ,Xn,Yn,Zn IX8(9,1) 9*NEL8 Connectivity and material number for

each 8 node solid element.

If NEL8 < 0 2*abs(NEL8) Extra nodes for ten node solids.

IXT(9,1) 9*NELT Connectivity and material number for each 8

node thick shell element.

IX2(6,1) 6*NEL2 Connectivity, orientation node, two null

entries, and the material number for each

2 node beam element.

For some beam types the last two number contain

the beam type and length to width ratio * 100

and length to height ratio * 100

type = ix2(5,*) & 0x3F

width = 0.01 * length / (ix2(5,*)>>6

height = 0.01 * length / ix2(6,*)

Third node (orientation) may be > 1e9

Contain flag 1e9 to indicate a spot weld.

IX4(5,1) 5*NEL4 Connectivity and material number for

each 4 node shell element

Note the node numbers are the LS-DYNA internal numbers for nodes, these will be the same as the user’s numbers if NARBS = 0, otherwise, the arbitrary number lists are used to find the user’s numbers, similarly, for element numbers and material numbers.

LS-DYNA DATABASE

USER MATERIAL, NODE, AND ELEMENT IDENTIFICATION NUMBERS Skip this section if NARBS (disk address 39) is zero. The user node and element numbers must be in ascending order. It assumed that if this option is used all node and element data anywhere in the databases is in ascending order in relation to the user numbering. The total length of the data in this data is equal to:

NARBS=10+NUMNP+NEL8+NEL2+NEL4+NELT,

if sequential numbering is used for the materials/parts. For arbitrary material numbering (NSORT < 0), the total length is increased by

6+NUMMAT8+NUMMAT4+NUMMAT2+NUMMATT. Material numbers are not in ascending order.

VALUE LENGTH DESCRIPTION

NSORT 1 Pointer to arbitrary node numbers in

LS-DYNA source code. If < 0, it flags that

arbitrary material identification numbers are

also used.

NSRH 1 Pointer to arbitrary solid element numbers in

LS-DYNA source code:

=NSORT+NUMNP

NSRB 1 Pointer to arbitrary beam element numbers in

LS-DYNA source code:

=NSRH+NEL8

NSRS 1 Pointer to arbitrary shell element numbers in

LS-DYNA source code:

=NSRB+NEL2

NSRT 1 Pointer to arbitrary thick shell element

numbers in LS-DYNA source code:

=NSRS+NEL4

NSORTD 1 Number of nodal points

NSRHD 1 Number of 8 node solid elements

NSRBD 1 Number of 2 node beam elements

NSRSD 1 Number of 4 node shell elements

NSRTD 1 Number of 8 node thick shell elements

NSRMA 1 Pointer to an array in the LS-DYNA source code

that list the material ID’s in ascending order.

NSRMU 1 Pointer to an array in the LS-DYNA source code

that gives the material ID’s in the actual order that

they are defined in the user input.

LS-DYNA DATABASE VALUE LENGTH DESCRIPTION

NSRMP 1 Pointer to an array in the LS-DYNA source code

that gives the location of a member in the array

originating at NSRMU for each member in the array

starting at NSRMA.

NSRTM 1 Total number of materials

NUMRBS 1 Total number of nodal rigid body constraint sets NMMAT 1 Total number of materials

NUSERN NSORTD Array of user defined node numbers

NUSERH NSORTH Array of user defined solid element numbers

NUSERB NSORTB Array of user defined beam element numbers

NUSERS NSORTS Array of user defined shell element numbers

NUSERT NSORTT Array of user defined thick shell numbers

NORDER NMMAT Ordered array of user defined material ID’s

NSRMU NMMAT Unordered array of user material ID’s

NSRMP NMMAT Cross reference array

EXTRA 2 NODE CONNECTIVITY ARRAY FOR 10 NODE TETRAHEDRON ELEMENTS (only if NEL8 < 0)

List of extra nodes for each 10 node tetrahedron element, 2 * abs(NEL8). Any 8 node solids have these two nodes set to zero.

ADAPTED ELEMENT PARENT LIST (not implemented)

List of element id pairs for H-type shell element adaptivity.

Length of data is 2 * NADAPT, pairs are element number and element parent number SMOOTH PARTICLE HYDRODYNAMICS NODE AND MATERIAL LIST

If NMSPH > 0 List of sph node and its material number

Length of data 2 * NUMSPH

PARTICLE GEOMETRY DATA (NPEFG > 0)

LS-DYNA DATABASE

NPARTGAS blocks of NGEOM data to describe the geometry for each airbag:

1. first particle ID for the airbag

2. number of particles in the airbag

3. ID for the airbag

4. number of gas mixtures in the airbag

If NGEOM == 5

5. number of chambers

RIGID ROAD SURFACE DATA

If NDIM > 5

NNODE Number of nodes in road surface

NSEG Total number of 4 noded road surface segments

NSURF Number of road surfaces

MOTION Flag to indicate motion data is output for each state

NODEID NNODE list of IDs

SURFNODE XYZ Coordinate for each node

Lists of 4 noded segments for each surface

SURFID Surface ID Number

SURFNSEG Number of segments in surface

SURFSEGS SURFNSEG of 4 node ids for each segment

Length of data = 4 + NNODE + 3 * NNODE + NSURF * (2 + 4 * SURFNSEG)

LS-DYNA DATABASE HEADER, PART & CONTACT INTERFACE TITLES

At the end of the first binary files, eg d3plot, the part and model titles are appended.

If the model input includes *DATABASE_BINARY_D3PROP, all the d3prop part data is included.

At the end of the first interface force file, titles and contact id are appended.

This extra data is written at the end of the following files:

d3plot, d3part and intfor files, and the header and part titles are written directly after the

EOF (= -999999.0) marker.

Header output

------------------------------------

NTYPE 1 entity type = 90000

HEAD 18 Header title (72 characters)

For the interface force file (intfor), header and contact titles are written at the end of first file after the EOF (= -999999.0) marker

Part title output

Value Length Description

-------------------------------

NTYPE 1 entity type = 90001

NUMPROP 1 number of parts

For NUMPROP parts:

IDP 1 part id

PTITLE 18 Part title (72 characters)

For the interface force file (intfor), header and contact titles are written at the end of first file after the EOF (= -999999.0) marker.

Contact title output

------------------------------------

NTYPE 1 entity type = 90002

NUMCON 1 number of contacts

For NUMCON contacts:

IDC 1 contact id

CTITLE 18 Contact title (72 characters)

Header output

------------------------------------

NTYPE 1 entity type = 90000

HEAD 18 Header title (72 characters)

The d3prop data is written to the d3plot file only if it is requested.

LS-DYNA DATABASE

D3PROP output

Values Length Description

-------------------------------

NTYPE 1 entity type = 900100

NLINE 1 number of keyword lines

For NLINE keyword lines:

KEYWORD 20 keyword line (80 characters)

DESCRIPTION OF BINARY FILE TYPES

Control word 11

File type:

1=d3plot plot file of model and state data

2=d3drlf plot file of model and state data from a dynamic relaxation analysis 3=d3thdt time history plot file for a set of nodes and elements

4=intfor plot file of contact interfaces

5=d3part plot file of model and state data for a set of parts

6=blstfor plot file for a blast wave analysis

7=d3cpm

8=d3ale plot file for ale fluid-structure interface

or fsifor

11=d3eigv plot file for an eigen value analysis

12=d3mode

13=d3iter

21=d3ssd plot file for steady state dynamic response.

22=d3spcm plot file for response spectrum analysis.

23=d3psd plot file for power spectral density of response, in random vibration. 24=d3rms plot file for root mean square of response, in random vibration.

25=d3ftg plot file for random fatigue analysis.

26=d3acs plot file for frequency domain acoustic FEM analysis