-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NorESM2.0.6 release #385
Comments
I have created a milestone for BLOM/iHAMOCC-1.3.0 for 23 November. |
I think this is only needed for components that will have an updated CMIP6-compatible version. If there are no changes (or only answer-changing code changes) we can use the component tag from noresm2.0.5. |
Hi @matsbn @TomasTorsvik @JorgSchwinger I have tested the noresm2 branch (in preparation of the noresm2.0.6 release). For BLOM I used the branch release-1.3, but I obtain a problem during compilation with BLOM : blom/hamocc/read_netcdf_var.F90(103): error #6404: This name does not have a type, and must have an explicit type. [II] When I tried for BLOM the v1.1.0 tag, I found back identical results to CMIP6 results for a N1850_f19_tn14 simulation. Any idea what might cause this? Regards, Dirk |
Dear Dirk, it looks as if it could be related to the usage of |
Hi, I wanted to test We might need |
Dear Dirk, just to give you a brief update: we've identified the potential issues and are about to fix it. If it goes as expected, a fixed version should be available soon. |
Hi @JensBDebernard (and @matsbn) after discussion with Mats, we wonder whether it would be a good idea to try to reduce the number of output files from the CICE model for the noresm2.0.6 release. In the current version, the daily output of CICE ends up in individual daily files, which creates a considerable number of files. So could all the daily output be put in one file per year already during model execution? So the concrete questions are: Is this a good idea or are there too many drawbacks (e.g., restarting in the middle of the year might create problems)? Could we manage this for the noresm2.0.6 (we can extend the deadline if needed)? Who could do this (is it difficult to do)? Best regards, |
Hi @DirkOlivie |
Hi @DirkOlivie , @JensBDebernard , @YanchunHe , I just wonder if a change like this could have implications for the CMORization routine, i.e. if our current setup expect CICE output in individual daily files? If so, it may be better to change the CICE output in the next (non-CMIP6 conformant) release instead.
|
Hi @TomasTorsvik @matsbn , I have now tested again the noresm2-branch after the bugfix for pnetcdf in BLOM. I now however have problems (both on fram and betzy) in the compilation of BLOM, related to the CVMix code, I think. Is that code supposed to be downloaded automatically? Or does it live somewhere? I have the impression that I need files like, cvmix_convection.F90, cvmix_ddiff.F90, cvmix_kinds_and_types.F90, ... but they do not seem to be present when the model wants to build. During the build I get error messages like : The code I use can be found on : Hilsen, Dirk |
Hi @DirkOlivie , I just jump in since I just saw it. Under the BLOM entry in the NorESM
which should then allow to checkout the right CVMIX automatically via |
Hi @DirkOlivie This means that NorESM Externals need to be changed, with an additional
|
Thanks Jöran, didn't see you already replied, I should practice to type faster ;) |
Probably we should also include this as a point in the changelog file. |
I have two remaining issues with the documentation page on the releases (doc/access/releases_noresm20.rst), which has now an updated version in the noresm2 branch on NorESMhub. (1) the page on read-the-docs (even when I choose the noresm2 version) is still the old one (it still starts with noresm2.0.5, although I added noresm2.0.6). So maybe I did something wrong, or is the update not taken into account automatically. (2) I would like to add the tag number of the new release version on that documentation, but I think that it is impossible : I cannot have my commit number before I do my latest commit ... (In earlier versions I added the commit number after the actual release). Best regards, |
Hi @DirkOlivie , @adagj
However, it seems that the formatting problems that we had earlier (issue #388) has returned for the noresm2 documentation. I will go through the build log and check for errors.
Best wishes, |
I updated the |
The I'm closing this issue since the release is now out. |
Hi @kjetilaas @monsieuralok @oyvindseland @tto061 @matsbn @MichaelSchulzMETNO @TomasTorsvik @adagj @JorgSchwinger @tjiputra @JensBDebernard,
we plan to have a new release of NorESM2 (noresm2.0.6) by 30 November 2022 (this is still aimed to be a release that can reproduce the CMIP6 results of NorESM2).
There is a milestone shortly describing it : https://github.com/NorESMhub/NorESM/milestone/2
where one can find a short overview of the planned updates. Feel free to edit it, if relevant information is missing.
To allow for testing, it would be good that individual components are updated by 23 November 2022.
To facilitate the process, it is maybe a good practice that these individual components get their own milestone (with due date 23 November 2022). I hope that the individual component maintainers could make those milestones.
Best regards,
Dirk
The text was updated successfully, but these errors were encountered: