Docs Needed: Calibration section to tech note
- Dominant language
- Fortran
- Stars
- 352
- Forks
- 361
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 7
Description
(Please see our [contribution guidelines for documentation](https://escomp.github.io/CTSM/users_guide/working-with-documentation/docs-intro.html#contribution-guidelines).)
### What sort(s) of documentation issue is this?
- [X] Something is missing.
- [ ] Something is (or might be) incorrect or outdated.
- [ ] Something is confusing.
- [ ] Something is broken.
### What part(s) of the documentation does this concern?
- [X] [Technical Note](https://escomp.github.io/CTSM/tech_note/index.html) (science and design of the model)
- [ ] [User's Guide](https://escomp.github.io/CTSM/users_guide/index.html) (using the model and related tools)
- [ ] Somewhere else (e.g., README file, tool help text, or code comment): _Please specify_
- [ ] I don't know
### Describe the issue
I will add a section to the tech note that describes the calibration at a high level. This way, everywhere in the tech note where parameter values are stated, other people can reference/link to this section. @adrifoster For example:
In the LUNA module, Jmaxb0 and Jmaxb1 parameters were set based on Ali et al., (), but were subject to calibration (see section *.*.**).
### Additional context (optional)
@samsrabin is planning to magically automatically update parameter values in the documentation from the paramfile so this language will help to avoid additional verbiage changes as parameter values are updated (see #3923).
Contributor guide
Assessment
This issue has not been assessed yet.