Skip to content

Commit d9dfaa9

Browse files
committed
Doc corrections
1 parent baf8569 commit d9dfaa9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/users/parameter-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ A handful of 1D arrays are present in the constants file. Note that the constant
2020
* `soil_l`: Soil layers, length must equal `n_soil_layers` in the model config file.
2121
* `sed_l`: Sediment layers, length must equal `n_sediment_layers` in the model config file.
2222

23-
The **Units** columns gives the internal model units, and therefore those required by the NetCDF and constants namelist. "dt" is the length of the model timestep, for example, is the model has a timestep of one day, then "kg/timestep" means "kg/day". The NanoFASE data module is capable of converting units of spatial data (not constants), and therefore any reasonable units can be used for the data input to this - as long as these units are specified in the config file.
23+
The **Units** columns gives the internal model units, and therefore those required by the NetCDF and constants namelist. "dt" is the length of the model timestep. For example, if the model has a timestep of one day, then "kg/dt" means "kg/day". The NanoFASE data module is capable of converting units of spatial data (not constants), and therefore any reasonable units can be used for the data input to this - as long as these units are specified in the config file.
2424

2525
The **Specified in** column indicates which file the model parameter should be included in:
2626
* {bdg-primary}`data.nc` The spatio(temporal) NetCDF file input directly to the model.

0 commit comments

Comments
 (0)