Skip to content

Gradual implementation of HIGHTUNE functionality into MONC #26

Description

@sjboeing

Leif and I had a brief chat about this earlier today. One option would be to start implementing small parts of the functionality required in a clean module. @leifdenby and @cemac-ccs , you would then be able to restructure this so that the MONC forma.

In particular, this could include functionality to help:

  • Read the HIGHTUNE-formatted netCDF files, both the logical flags and the input fields (not sure whether to keep the full input fields in memory).**
  • Perform height (and time, for time-varying fields) interpolation of these fields to the MONC grid.** (Implementing space and time interpolation for HIGHTUNE-based forcing #27)
  • Initialise the fields in MONC.
  • Apply relevant tendencies corresponding to the different processes.**
    ** Inspired by Todd's earlier work

Other functionality we will want to implement later:

  • Ensure there are no entries in the case MONC configuration file (mcf) that should be set via NetCDF (these entries will be in the global mcf, but should be ignored there). Ensure the termination time is smaller than the HIGHTUNE file end time (make a subroutine that simply performs checks).
  • Use the HIGHTUNE NetCDF flags to enable/disable components. This may also need checks on compatibility with the mcf.
  • Use the HIGHTUNE files to set other parameters: surface properties, time-dependent coriolis parameter, surface pressure.
  • Getting the relevant inputs for SOCRATES from HIGHTUNE (lat, lon, time of day). We can use the prescribed radiative tendencies from ERA5 for early testing if needed.

An overview of the parameters that could come from either the mcf or the HIGHTUNE NetCDF is here (from page 7).
https://docs.google.com/document/d/1mz2Ajo4ABdMQBHEYTKmNgBUV4Y9iZjCCLdlbtu1aYgU/edit?usp=sharing

What do you think, @leifdenby and @cemac-ccs?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions