Tungsten PFC Model - JSON Input Files¶
App overview (binaries, run line): ../README.md. How JSON maps to the simulator: ../../../docs/app_pipeline.md.
This directory contains JSON input files for the Tungsten PFC model. These files follow the same structure as the TOML files in the inputs_toml directory, with the following sections:
Structure¶
Each JSON file follows this structure:
{
"model": {
"name": "tungsten",
"params": {
// Model parameters
}
},
"domain": {
// Domain configuration
},
"timestepping": {
// Time stepping parameters
},
"fields": [
// Field definitions
],
"initial_conditions": [
// Initial condition definitions
],
"boundary_conditions": [
// Boundary condition definitions
]
}
Available Input Files¶
tungsten_fixed_bc.json- Fixed boundary conditions with seed gridtungsten_moving_bc.json- Moving boundary conditions with seed gridtungsten_moving_bc_options.json- Moving boundary, narrow front (width3,alpha10) advancing in larger steps thantungsten_moving_bc.jsontungsten_performance.json- Performance testing configurationtungsten_restart.json- Restart from checkpointtungsten_single_seed.json- Single seed initial conditiontungsten_resolved_bcc.json- One BCC cell at the qualified spacing, 2/3 mask on. Numerical resolution, not a material calibration. ctest runs this file.
Model Parameters¶
The model parameters are identical to those in the TOML files. See the TOML files for detailed descriptions of each parameter.
Domain Configuration¶
size: grid points per axislower,upper: limits of the box. Spacing is(upper - lower) / size; a symmetric box puts the single seed at(0, 0, 0)in its middle
Time Stepping¶
t0: Initial timet1: Final timedt: Time step sizesaveat: Save interval
Field Definitions¶
Each field definition has:
name: Field namedata: Output file path pattern
Initial Conditions¶
Supported initial condition types:
constant: Fill entire field with constant valuesingle_seed: Create a single crystal seedseed_grid: Create a grid of crystal seedsrandom_seeds: Create random crystal seedsfrom_file: Load field from file
Boundary Conditions¶
Supported boundary condition types:
fixed: Maintain field values at boundariesmoving: Allow boundaries to move over time. The shipped cases pin"mode": "cutoff"(the historical column maximum above0.1) so their trajectories are unchanged; omitmodefor the defaultamplitudetracker, seeapps/tungsten/README.md.