Update BLOM tag to v1.7.0 #627
Conversation
TomasTorsvik
requested review from
gold2718,
matsbn,
monsieuralok,
JorgSchwinger,
mvdebolskiy and
jmaerz
TomasTorsvik
added
the
Next release
There was a problem hiding this comment.
Generally approved. Question though, how this should be handled in the light of #623 - and whether tag 1.7 should rather enter NorESM2.3 then (while it is then questionable, why we didn't wait until the stuff is in, which is now marked as entering tag1.8... - see NorESMhub/BLOM#462)
|
@jmaerz - I see that the v1.7 tag becomes a bit of a lose end if it is not used in NorESM2.5. It should be possible to run with NorESM2.3, I will test this. Potentially, it could be used in a NorESM2.3.1 tag, if the model output does not change substantially with the changes going from v1.6 to v1.7. |
|
Hi @TomasTorsvik , I feel that it would be good to decide on the role of NorESM2.5 (technical versus scientific useful release - thus far my impression was that 2.5 is a rather technical release for the INES interim, where answer changes aren't so much of an issue). If it turns out that current tag 1.7 shouldn't enter 2.5, we can either withdraw the tag or perceive it as an interim version - heading to tag 1.8 for NorESM2.3 - then everything beyond is going to be NorESM3. But this is just my suggestion with a limited overall overview. |
|
@jmaerz - I think NorESM2.5 will be a technical release, it will not be tuned in any way. I would rather keep v1.7 as an intermediate tag since there have been quite a number of commits since v1.6.1. Maybe we will only have a few additional commits before we make v1.8, but that should not be a big problem. |
|
Was this tested? I don't see new baselines? |
|
I was running the "allactive" test, but didn't make new baselines. I get a FAIL on ERR_Ld3.ne30pg3_tn14.N1850.betzy_intel.allactive-defaultio. |
This tag version is intended for
noresm2_5_alpha09, and potentially the NorESM2.5 release.