Add ERA5-forced ACCESS-OM2 runs

[dougiesquire]

Adds the runs described in this ACCESS-Hive Forum post to the catalog: https://forum.access-hive.org.au/t/era-5-forced-access-om2-simulations/1103

Closes #127

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (f83a7bb) 97.20% compared to head (f0f857b) 97.20%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #130   +/-   ##
=======================================
  Coverage   97.20%   97.20%           
=======================================
  Files           9        9           
  Lines         573      573           
=======================================
  Hits          557      557           
  Misses         16       16           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dougiesquire]

Some additional fields need to be added to the metadata.yaml files for these runs. I've created new versions of these files with the additional fields here: /scratch/ik11/ds0092. @rmholmes would you mind taking a look at these and copying them to the corresponding run directories if you're happy with them?

If you think it's worthwhile, it could be helpful to add some additional info to the descriptions fields to clarify:

• 1deg_jra55_iaf_era5comparison: how is this different than the 1deg_jra55_iaf_omip2_cycle* runs?
• 1deg_jra55v14_ryf: how is this different than the 1deg_jra55_ryf9091_gadi run? Just the JRA55 version?
• 025deg_jra55_iaf_era5comparison: how is this different than the 025deg_jra55_iaf_omip2_cycle* runs?
• 025deg_jra55_ryf_era5comparison: how is this different than the 025deg_jra55_ryf9091_gadi run? Just the JRA55 version?

[dougiesquire]

@anton-seaice would you mind casting your eyes on this?

[anton-seaice]

I think this (from the description) is not accurate for the ERA runs

1 degree ACCESS-OM2 global model configuration under '
                    'the RYF9091 Repeat\n'
                    'Year Forcing strategy outlined by Stewart et al. '
                    '(2020), \n'
                    'https://doi.org/10.1016/j.ocemod.2019.101557.

The document in the DOI is about JRA55

[dougiesquire]

I think this (from the description) is not accurate for the ERA runs

1 degree ACCESS-OM2 global model configuration under '
                    'the RYF9091 Repeat\n'
                    'Year Forcing strategy outlined by Stewart et al. '
                    '(2020), \n'
                    'https://doi.org/10.1016/j.ocemod.2019.101557.

The document in the DOI is about JRA55

Hopefully @rmholmes can comment/improve

[rmholmes]

Sorry for the slowness on this.

Thanks @dougiesquire for providing the updated meta data. I've added a few updates on top of yours (including comments on how the JRA-55 runs differ from the standard control runs listed at https://forum.access-hive.org.au/t/access-om2-control-experiments/258) and copied them to the appropriate directories in ik11. If you want to see what I changed, see the last two commits at https://github.com/rmholmes/era5_metas/commits/main. I think they should be all good now.

[dougiesquire]

Great - thanks heaps @rmholmes!

[anton-seaice]

Based on the updated metadata.yaml files for the 8 relevant runs being updated and moved in ik11, I managed to build datastores (using bin/build_all.sh) for new added model runs.

Log files attached

v127_OM2_ERA5.tar.gz
conda_env.yaml.txt
build_all.sh_as.o99597320.txt