GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

OSMOSIS update

Context

The version of the OSMOSIS turbulent closure scheme available in NEMO requires updates to remain aligned with the ongoing development of this scheme.

Proposal

The purpose of this issue is to provide an overview of actions related to the long-term development of the OSMOSIS parameterisation:

OSMOSIS updates for NEMO version 4.2 in branch 281-update-osmosis-branch;
re-enabling of the OSMOSIS implementation in branch_5.0, in preparation for the release of NEMO version 5.0, and in NEMO main by making it compatible with nn_hls = 2;
porting of OSMOSIS updates made in branch 281-update-osmosis-branch both into NEMO branch_5.0, in preparation for the release of NEMO version 5.0, and into NEMO main.

Edited Jul 11, 2024 by Simon Mueller

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information