You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/users/parameter-reference.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ A handful of 1D arrays are present in the constants file. Note that the constant
20
20
*`soil_l`: Soil layers, length must equal `n_soil_layers` in the model config file.
21
21
*`sed_l`: Sediment layers, length must equal `n_sediment_layers` in the model config file.
22
22
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.
24
24
25
25
The **Specified in** column indicates which file the model parameter should be included in:
26
26
* {bdg-primary}`data.nc` The spatio(temporal) NetCDF file input directly to the model.
0 commit comments