You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment BLOM/iHAMOCC supports both NUOPC and MCT. Maintaining both options is creating an extra burden for model development, and it is a question how long we should maintain support for MCT.
MCT is the default coupler for model versions that use the CMIP6 model framework and components, i.e. up to and including NorESM2.3. Hence if a BLOM/iHAMOCC release is intended to run in NorESM2.3, it should include support for MCT.
We are now preparing a new tag v1.7.0 and release branch release-1.7 for use with NorESM2.3. If there are further developments that would be useful in v1.7.0, please list them in issue #340 . If you have other development steps in mind, that will not go into v1.7.0, but for which MCT support will still be useful, please edit this item and add to the list below.
...
The text was updated successfully, but these errors were encountered:
At the moment BLOM/iHAMOCC supports both NUOPC and MCT. Maintaining both options is creating an extra burden for model development, and it is a question how long we should maintain support for MCT.
MCT is the default coupler for model versions that use the CMIP6 model framework and components, i.e. up to and including NorESM2.3. Hence if a BLOM/iHAMOCC release is intended to run in NorESM2.3, it should include support for MCT.
We are now preparing a new tag
v1.7.0
and release branchrelease-1.7
for use with NorESM2.3. If there are further developments that would be useful inv1.7.0
, please list them in issue #340 . If you have other development steps in mind, that will not go intov1.7.0
, but for which MCT support will still be useful, please edit this item and add to the list below.The text was updated successfully, but these errors were encountered: