Skip to content

Conversation

@mnlevy1981
Copy link
Collaborator

Description of changes:

Use a newer version of MARBL; take advantage of some performance improvements.
The big change is that MARBL will only compute diagnostic values for fields the driver has requested, rather than computing values that the driver then ignores.

Testing:

Test case/suite: will run aux_pop_MARBL when done with the MARBL changes
Test status: this should be bit-for-bit

User interface (namelist or namelist defaults) changes? N/A

Cleaned up how the GCM interacts with some diagnostic attributes
The first time ecosys_driver_set_compute_now() is called, it loops through all
of the MARBL diagnostics and sets compute_now = set_in_tavg_contents() for that
diagnostic.

Note that we use set_in_tavg_contents() instead of accumulate_now() because we
need to set compute_now flags before the time manager is set up, and
accumulate_now() returns False for all diagnostics at that stage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant