Skip to content

Updated section Configuring MOM6 diagnostics in Run OM3 docs #1201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
heidinett wants to merge 2 commits into
base: development
Choose a base branch
from
Draft

Updated section Configuring MOM6 diagnostics in Run OM3 docs #1201

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5753d9f
Updated section Configuring MOM6 diagnostics in Run OM3 docs
heidinett May 12, 2026
c57e30c
Additional updates to the Run OM3 text
heidinett May 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/models/run_a_model/run_access-om3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -338,9 +338,9 @@ refer to [how to configure your experiment with payu](https://payu.readthedocs.i

### Configuring MOM6 diagnostics

MOM6 diagnostic output is configured using the `diag_table` file. However, users should not edit the `diag_table` file directly. Instead, a tool is provided to generate the `diag_table` from an easily editable YAML file. This tool ensures that the `diag_table` requests MOM6 output that is formatted consistently and is suitable for postprocessing (e.g., inclusion in Intake-ESM catalogs).
MOM6 diagnostic output is configured using the `diag_table` file. However, users should not edit the `diag_table` file directly. Instead, a [`make_diag_table` tool](https://github.com/COSIMA/make_diag_table) is provided to generate the `diag_table` from an easily editable `diag_table_source.yaml` file. This tool ensures that the `diag_table` requests MOM6 output that is formatted consistently and is suitable for postprocessing (e.g., inclusion in Intake-ESM catalogs).

Preset `diag_table` files, along with the YAML configuration files used to generate them, can be found in the `diagnostic_profiles` subdirectory of the _control_ directory. To create and use a custom `diag_table`, follow the instructions in `diagnostic_profiles/README.md`.
The default `diag_table` file, along with the `diag_table_source.yaml` configuration file used to generate it, can be found in the _control_ directory. To create and use a custom `diag_table`, follow the instructions in the [`make_diag_table/README.md`](https://github.com/COSIMA/make_diag_table#make_diag_table).

!!! warning
MOM6 provides the ability to vertically remap diagnostics onto user-defined vertical coordinates, including density coordinates (check [MOM6 vertically remapped diagnostics documentation](https://mom6.readthedocs.io/en/main/api/generated/pages/Diagnostics.html#vertically-remapped-diagnostics) for more information). Remapping to density coordinates can add substantially to the runtime of the model. The default `diag_table` used by {{ model }} includes diagnostics remapped to density coordinates. These should be removed for performance reasons if they are not needed.
Expand Down
Loading