Unresolved diag table generation and handling

ESCOMP / MOM_interface

CESM interface to MOM Ocean Model

5 stars 18 forks source link

Unresolved diag table generation and handling #156

Closed alperaltuntas closed 7 months ago

alperaltuntas commented 8 months ago

The buildnml script now generates a "diag_table.unresolved" file alongside the usual "diag_table" in the Buildconf/momconf directory. In this unresolved version, the case name is represented as ${CASE}, enabling easy sharing of a diag table across multiple cases in a portable manner. This unresolved diag table can be placed in SourceMods/src.mom and modified if needed. If a diag_table.uresolved file is found in SourceMods/src.mom, the buildnml script creates a new "diag_table" file in the RUNDIR directory based on the unresolved one, replacing ${CASE} with the actual case name. If both diag_table and diag_table.unresolved files are encountered in the SourceMods directory, an error will be triggered to instruct the user to use only one of them.
black reformatting of buildnml

see the following commit only for unresolved diag_table changes: 009b3cf0064f78f2e8e4bc7fdeae51937f07a7ad

testing: aux_mom.derecho (ongoing)

klindsay28 commented 8 months ago

If a resolved diag_table is in SourceMods/src.mom, do you also want to remove diag_table.unresolved from CaseDocs, if present? It looks like you're currently only doing this removal in Buildconf/momconf.

alperaltuntas commented 8 months ago

If a resolved diag_table is in SourceMods/src.mom, do you also want to remove diag_table.unresolved from CaseDocs, if present? It looks like you're currently only doing this removal in Buildconf/momconf.

That's because I am currently only writing unresolved diag_table in Buildconf/momconf. I am still uncertain about the specific purposes of the Buildconf vs CaseDocs directories, but it seems like Buildconf is a better place for intermediate files like unresolved diag_table (judging by the fact that input_data_list file only appears in Buildconf)