Update tables for upcoming `release-MC_25km_jra_iaf-1.0`

[chrisb13]

As discussed, would be useful to update the tables to reflect the latest release-MC_25km_jra_iaf-1.0 release (once parameters are frozen)

See discussion:

• Hovmoller (depth-time) of horizontally averaged temperature drift ACCESS-Community-Hub/access-om3-paper-1#8 (comment)

[chrisb13]

Also discussed at standup this morning: ACCESS-NRI/access-om3-configs#904 (comment)

[aekiss]

Is this what you had in mind @chrisb13 ? https://github.com/COSIMA/access-om3-doc/blob/da4c1f974a2a17fd5efd9f08a9e9430a171f1836/tables/MOM_input/GFDL-OM5_ACCESS-OM3_25km_nml_diff.md

[chrisb13]

Thanks @aekiss.

I've put some new comments at the top of the 25km "stub" page (we're no longer using stubs but hopefully you get the idea) -- see PR and rendered version here. I'd like to put a link like this into it. What do you think is appropriate text such that maintenance burden is reduced? If I'm following what you've done the right two columns are the current tip of the dev branches? Which is a problem I guess when they are updated.

I reckon @anton-seaice might have some clever ideas here?

Feel free to just commit onto: ACCESS-NRI/access-om3-configs#912 if you've got an idea that you think can work.

[anton-seaice]

We could generate this table at midnight everyday and add to the config docs, or something similar, if we think it's useful enough (its a non trivial amount of work).

I would probably disentangle this from completing the iaf_1.0 release, and just make it an action for someone

[chrisb13]

Yeah I've been thinking that too. Was planning on opening a separate issue as Josh has some relevant work. I think I remember @aekiss advocating for this in the past (couldn't readily find the comments though)?

[chrisb13]

In the interim

Feel free to just commit onto: ACCESS-NRI/access-om3-configs#912 if you've got an idea that you think can work.

@aekiss feel free to action if you've got an idea.

Otherwise, feel free to close this issue.

[aekiss]

I'm unsure what is being requested here.

You can add more savetables calls in https://github.com/COSIMA/access-om3-doc/blob/main/make_tables.py to generate both tables and diff tables of any set of configs you like, for both MOM and CICE parameters. But the diff tables of 25km releases won't be very interesting as nearly everything is the same.

So

• which repos/branches
• which parameter files should be tabulated (MOM or CICE or both)?
• how many columns (configs) per table (noting that typically more columns = more diffs)

see examples in https://github.com/COSIMA/access-om3-doc/tree/main/tables

[aekiss]

from ACCESS-Community-Hub/access-om3-paper-1#8 (comment)

Tables haven't been done for the last IAF run, but I agree they should be done for the new IAF release.

I didn't mean this should necessarily be part of the IAF release (integrated into the docs), just that I should update the tables in https://github.com/COSIMA/access-om3-doc after the release