Open mnlevy1981 opened 2 years ago
@klindsay28 suggests starting out by only including these variables when running aux_mom
, and then we can add them in additional situations in the future as needed.
@alperaltuntas can you tell me how to do this? I'm happy to put together a PR with these changes.
To turn on a field list for test runs only, you can do something like:
fields:
$TEST == True :
- module: "ocean_model"
packing: 2
lists: [ *foo, *bar ]
else:
- module: "ocean_model"
packing: 2
lists: [ *foo ]
In above case, the foo
list will be included at all times and the bar
list will be included in test runs only, including but not limited to aux_mom test suite instances.
Am I answering the right question?
I put the following into my sandbox (and ran
yaml_to_json
to generate changes indiag_table.yaml
):KPP_QminusSW
andKPP_netSalt
are the surface fluxes that are redistributed by the nonlocal term in KPPKPP_NLT_dTdt
andKPP_NLT_dSdT
are the tendency terms due to the non-local transportKPP_NLT_temp_budget
andKPP_NLT_saln_budget
are the unitless shape functions computed by KPPI'm not sure if these should only be included in testing, or if they would be useful in all runs. My use-case has been entirely on the testing side, though some of the testing includes one-off cases that I compare by hand so I didn't try to limit it to just tests.
https://github.com/NCAR/MOM6/pull/202 introduces round-off level changes to
KPP_NLT_temp_budget
andKPP_NLT_saln_budget
, so it was useful for me to include them in the test suite. Also, I think all of these diagnostics include various dimensional-scaling terms so we want them included in the scaling test outputs.After the NCAR/MOM6 PR is merged, there will also be some KPP variables in the optional tracer modules (specifically CFCs and pseudosalt). It's not clear to me how to add those variables, either. Maybe something like