Skip to content

Estimate properly the size of ocean 3D variables #2

@jesusff

Description

@jesusff

The ocean component has quite a few 3D variables which are provided in a single file. This differs from the atmosphere, where a set of pressure levels have been selected and variables are defined as 2D variables per level (e.g. ta850). Programmatically, the simplest way to know if a variable is 3D is by checking the dimensions in the main data request file or in the CMOR tables themselves. The dimension olevel indicates the vertical ocean dimension:

https://github.com/WCRP-CORDEX/cordex-cmip6-cmor-tables/blob/508ca0ee5df5c27663622371bbf34f0ba916970b/Tables/CORDEX-CMIP6_mon.json#L3226-L3236

This, however, does not provide the size of this dimension, which is model-dependent. For the estimate (#1), we could use an average value across models, which will be better than the current assumption of a 2D field. For Med-CORDEX, a finer estimate could be achieved by retrieving the vertical levels from the model documentation, e.g.:
https://github.com/Med-CORDEX/model-documentation/blob/2cc1366eadce926f8397a874ba35abee8e9df52e/_models/CNRM-RCSM6B.md?plain=1#L254
but I'm not sure that the levels requested in the ocean data request (depth levels in meters) are the native levels in the ocean models or these need to be interpolated (to a predefined set of depth levels?). @sam-somot?

The same problem affects soil variables (sdepth dimension), which is relevant for WCRP-CORDEX/simulation-status#40

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions