EAMxx: multi-instance and nbfb testing

[mahf708]

Adding support for multi-instance capability in EAMxx (a one-liner in mct coupling layer) and adding a customized/specialized MVK tests for climate/nbfb reproducibility in EAMxx. More details to come.

[BFB]

[github-actions]

PR Preview Action v1.6.0
🚀 View preview at https://E3SM-Project.github.io/E3SM/pr-preview/pr-6984/
Built to branch gh-pages at 2025-02-07 21:25 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[mahf708]

To trigger:

./cime/scripts/create_test MVKxx_Ly1.ne4pg2_ne4pg2.F2010-SCREAMv1.chrysalis_gnu.eamxx-mvkpert --generate --baseline-root=/lcrc/group/e3sm/ac.ngmahfouz/baselines -b new -o --wait

./cime/scripts/create_test MVKxx_Ly1.ne4pg2_ne4pg2.F2010-SCREAMv1.chrysalis_gnu.eamxx-mvkpert --compare --baseline-root=/lcrc/group/e3sm/ac.ngmahfouz/baselines -b new -o --wait

I aim to integrate this next week. It seems to be working fine. We [EAMxx Eval team] will validate it so that we can potentially adopt as the official nbfb/climate reproducibility test

---

I will use this comment to make keep a record of some notes:

• We really need to address EAMxx: settle on IO naming scheme #6822 in the near future because we do a lot of cute dance around it; one of my motivations in documenting that issue and pushing for it is because I want us to peacefully go in and out for the ancient CIME/EAM/etc. infrastructure without having to walk on eggshells and do all sorts of customizations to get stuff going. One day when another revolution happens in the coupler and/or CIME, we can think about reinventing stuff, but for now, I think we should just use it and spare our cycles for other things we care about ...

[rljacob]

This adds eamxx/cime_config/SystemTests to the CIME software?

[mahf708]

I don't know exactly, but this enables us to define new tests, namely MVKxx

[mahf708]

btw, after talking to @mkstratos; I think we will move most of these overrides here to EVV module. Either before or after integrating this PR.