I'm working on AMIP simulation performance, and I just made a change to CloudMicrophysics but want to test against the latest ClimaAtmos on main inside the Coupler's AMIP environment. However, the AMIP environment has a version of ClimaParams that's missing a parameter, so ClimaAtmos fails.
If AMIP is one of the most important things (worth checking this assumption), how does one propagate changes into it effectively? Do releases need to happen? The coarse nightly AMIP installs some packages from main, but not CloudMicrophysics. Should we drop the Coupler manifests to unlock the environments while lots of development is happening?
I'm working on AMIP simulation performance, and I just made a change to CloudMicrophysics but want to test against the latest ClimaAtmos on
maininside the Coupler's AMIP environment. However, the AMIP environment has a version of ClimaParams that's missing a parameter, so ClimaAtmos fails.If AMIP is one of the most important things (worth checking this assumption), how does one propagate changes into it effectively? Do releases need to happen? The coarse nightly AMIP installs some packages from
main, but not CloudMicrophysics. Should we drop the Coupler manifests to unlock the environments while lots of development is happening?