Forcing ACCESS-OM2 using ESM1.5 data

Hi Ellie,

I am looking to run ACCESS-OM2 at 1deg resolution using surface forcings from ESM1.5 future projection runs (SSP585)

Interesting to hear your plans. Following @Flick.Chun post, this sort of thing falls under a science application so is out of scope for ACCESS-NRI support. For additional background, I suggest having a look at Ryan’s tutorial and we wondered if @dkhutch @wghuneke might have done related things? Having said this, we’ve had a little a chat (@AndyHoggANU @anton @Aidan @spencerwong) around a suggested workflow:

  • Suggest using bulk formula not a flux forcing for ACCESS-OM2 forcing (avoids tricky sea ice issues for example).
  • Obtain or re-run ESM1.5 with the variables and temporal resolution required to match ACCESS-OM2’s bulk formula inputs. This post can likely help. It’s very likely that outputs from existing runs won’t be appropriate for this but @spencerwong thought (without checking) it was possible. Take care to match the height and other constraints (MOM5 unlike NEMO can’t adjust on the fly). To reduce the forcing size, you may also want to consider reducing the frequency of temporal output, at least for some variables but you’ll have to check the model can support interpolation in that regard (NEMO can).
  • A remaining issue is the different grids/resolution. ACCESS OM2 can re-grid on the fly but you need an appropriate weights file (calculated offline once), you may be able to find one in the CM2 configuration but this presumes that they use the same grid so one needs to check that first or re-create the file (see Changing the OASIS remapping files here, i.e., To remake the mapping files using the new land-sea masks use the script make_remap_weights.py in the access-om2/tools/ directory of the main access-om2 repository. ).

Looking forward:

Chris.

1 Like