INITIAL_DAMAGE_MAP
Initial conditions
Beta command
This command is in the beta stage and the format may change over time.
"Optional title"
coid
entype, enid, mapid, csysid, $t_{map}$, i${}_x$, i${}_y$, i${}_z$, $sf$
$x_0$, $y_0$, $z_0$, $x_1$, $y_1$, $z_1$, no_erode
Parameter definition
Description
This command is used in combination with OUTPUT_DAMAGE_MAP. The command takes the damage field that has been stored in the ASCII file damage_map1.k from the previous simulation and projects it on the new model. The file needs to be included to the model and correct map ID must be assigned.
Typical use is in multi-step blast and fragment loading simulations. The fragment loading requires a fine mesh and is of short duration. On the contrary a blast loading simulation requires longer simulation time but the mesh can be relatively coarse. Thus, a combined fragment and blast loading simulation would be computationally expensive (many elements and small time steps are required). However, if separated, a significant speed up can be achived by mapping the result from a local fragment impact simulation to a global blast loading model.
Damage values $-1$ represent empty space. Elements in empty space can either be eroded no_erode=0 or kept untouched no_erode=1.
Example
Blast loaded concrete slab with initial damage from fragment impacts
A global model of a blast loaded concrete slab. The local fragment impact simulation (step 1) can be found under examples in OUTPUT_DAMAGE_MAP. The damage is mapped to the global model and repeated at 20 random locations.
Fragment loaded concrete slab with time offset and impulses
In this example, $t_{map}$ is being used to set a time offset at which the damage will be inflicted to the model. Also impulses are applied with parameter i${}_x$, i${}_y$ and i${}_z$.
