Only allocate MARBL coupled fields if MARBL is in use#345
Conversation
|
Should the following block also be MOM6/config_src/drivers/nuopc_cap/mom_cap.F90 Lines 598 to 619 in 623e49d |
|
I ran tests with and without MARBL, and everything ran fine. The non-MARBL run reported the baseline comparison differences, because there are 19 fields that are no longer included in coupler history: The variables that were not removed are bit-for-bit, as expected (and the run with MARBL is bit-for-bit identical as well) |
That's a good question. Let's leave this block as-is for now, but I can create an issue on the NCAR fork to investigate. I don't think CESM does anything with multiple ice categories unless MARBL tracers are turned on, though. |
mnlevy1981
left a comment
There was a problem hiding this comment.
Test results are in my previous comment. I have two small suggestions for code changes, so I'll mark this as "Request changes" just to make sure they get seen. If it makes more sense to leave the cesm_coupled .and. use_MARBL, then I'll change my review to Approve.
Thanks so much for putting this together!
This PR prevents allocation and advertisement of MARBL coupled fields when MARBL is not in use.
See mom-ocean#1653 (comment) for motivation.