/STATE/INIMAP2D/Keyword3

Engine Keyword A state file is written with mapping data as functions (/FUNCT) or generated into a binary file.

Format

/STATE/INIMAP2D/Keyword3

Definition

Field Contents SI Unit Example
Keyword3
VP
Velocity-Pressure state file is written with mapping data as functions (/FUNCT), used as an include file in a second simulation with Starter /INIMAP2D.
VE
Velocity-Energy state file is written with mapping data as functions (/FUNCT), used as an include file in a second simulation with Starter /INIMAP2D.
FILE
Mapping data is generated into a binary file, used as initial conditions in a second simulation with Starter /INIMAP2D/FILE.

Comments

  1. Compatible with QUADS or TRIAS in 2D and BRICKS in 3D.
  2. Frequency output and related part can be defined with Engine keyword /STATE/DT.
  3. For each submaterial, state functions are generated in a file with incremental name starting from ROOT_INIMAP1D_0001.sta.
    • (y,z)↦α(y,z) for volume fraction
    • (y,z)↦ρ(y,z) for mass density
    • (y,z)↦E(y,z) for energy density
    • (y,z)↦F(y,z) for burn fraction
    • (y,z)↦v(y,z) for velocity function

    This generated file needs to be included in the following Starter run: #include ROOT_INIMAP1D_0001.sta

    For Keyword3= FILE, file is compressed using gzip format. Frequency output is defined with /STATE/DT. First file is named ROOT_2D_0001.inimap.gz.

  4. Generated data can be used subsequently in a target model using /INIMAP2D/VP, /INIMAP2D/VE or /INIMAP2D/FILE. In the target model, a frame will have to be defined and must be consistent with mapping data, as described below:


    Figure 1.
    2D Original Model 3D Target Model
    O N1
    Y N1N2
    Z N1N3