Skip to content

Support ERA5 forcing #242

@aekiss

Description

@aekiss

This issue is a continuation of an email discussion on making configurations that support ERA5 forcing, e.g. to assess the impact of the forcing dataset on the sea ice simulation.

ERA5 is available on NCI at /g/data/rt52: https://opus.nci.org.au/display/ERA5/ERA5+Community+Home
[edit: use /g/data/ik11/inputs/ERA5 instead]

  • the hourly single-level data is probably what we want. This appears to be from the "reanalysis" or "HRES" dataset (as opposed to the lower-resolution "ensemble" or "EDA" dataset).
  • It's 1-hourly 0.25° data (higher resolution than JRA55-do, which is 3-hourly 0.5625°), though this has been interpolated from the reanalysis grid, which is 0.28125° (31km) for HRES.
  • It's currently only from 1979 onwards but data from 1950 will be available soon (cf. 1958 for JRA55-do).
  • JRA55-do has a lot of adjustments relative to JRA55 to reduce drift. ERA5 doesn't have these, so we'd expect greater drift in long climate simulations. But it may be superior to JRA55-do for shorter timescales.
  • for more detail see the ECMWF ERA5 documentation and download page

Replacing JRA55-do with ERA5 would require

  • new grid remapping weights files (see here)
  • making sure that we have physically equivalent fields (height and variable)
  • discussion on whether ERA5 fields should be used for initial conditions, e.g. for SST or sea ice concentration (SIC)

and changes to

  • config.yaml
  • atmosphere/forcing.json
  • namcouple

and possibly more, e.g.

  • coming up with liquid runoff data (unless we'd be happy with JRA55-do for that)
  • parameter changes for bulk formulas or whatnot.

Our configurations currently support only JRA55-do forcing: https://github.com/COSIMA/access-om2/tree/master/control
but we have some old, unsupported CORE configs here that may be useful as a reference for the changes required
https://github.com/COSIMA/1deg_core_nyf
https://github.com/COSIMA/025deg_core2_nyf
https://github.com/COSIMA/025deg_core_nyf

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions