Closed mvdebolskiy closed 10 months ago
@mvdebolskiy - I think making a 2.0.7 tag for CIME sounds like a good idea. We should then make a new noresm 2.0.7. tag that pulls in this CIME tag. @TomasTorsvik @gold2718 - do you agree.
I guess this is the problem if we abandon a continuation of 2.0.x release line. Should we just make a tag and NorESM tag, but do not define it as a release?
@oyvindseland - that's exactly what I am suggesting. That way we can use a tag in the tutorial that will have updated settings on betzy / fram and I think that will be really useful.
@mvertens , @mvdebolskiy , @gold2718
I tried the release-noresm2.0.7
tag, but I get an error when I run the script run_example1.sh
run_example1.sh.txt
The script works with release-noresm2.0.6
, except I need to edit env_batch.xml
, line 37, to change the sbatch
argument from -p
(partition) to -q
(qos), which is not optimal. However, with noresm2.0.7 it seems to fail at _setup_mach_pes
. Any ideas how to fix this?
$ ./run_example1.sh
=== Creating the case ===
Compset longname is 1850_CAM60%NORESM%FRC2_CLM50%BGC-CROP_CICE%NORESM-CMIP6_BLOM%ECO_MOSART_SGLC_SWAV_BGC%BDRDDMS
Compset specification file is /cluster/projects/nn9039k/people/tomast/NorESM/cime/../cime_config/config_compsets.xml
Compset forcing is 1850
ATM component is CAM cam6 physics:
LND component is clm5.0:BGC (vert. resol. CN and methane) with prognostic crop:
ICE component is Sea ICE (cice) model version 5 :with NORESM modifications appropriate for CMIP6 experiments
OCN component is BLOM default:BLOM/Ecosystem:
ROF component is MOSART: MOdel for Scale Adaptive River Transport
GLC component is Stub glacier (land ice) component
WAV component is Stub wave component
ESP component is
Pes specification file is /cluster/projects/nn9039k/people/tomast/NorESM/cime/../cime_config/config_pes.xml
Compset specific settings: name is RUN_STARTDATE and value is 0001-01-01
Could not find machine match for 'login-2.betzy.sigma2.no' or 'login-2.betzy.sigma2.no'
Machine is betzy
Traceback (most recent call last):
File "/cluster/projects/nn9039k/people/tomast/NorESM//cime/scripts/create_newcase", line 210, in <module>
_main_func(__doc__)
File "/cluster/projects/nn9039k/people/tomast/NorESM//cime/scripts/create_newcase", line 198, in _main_func
case.create(casename, srcroot, compset, grid, user_mods_dir=user_mods_dir,
File "/cluster/projects/nn9039k/people/tomast/NorESM/cime/scripts/Tools/../../scripts/lib/CIME/case/case.py", line 1445, in create
self.configure(compset_name, grid_name, machine_name=machine_name,
File "/cluster/projects/nn9039k/people/tomast/NorESM/cime/scripts/Tools/../../scripts/lib/CIME/case/case.py", line 853, in configure
self._setup_mach_pes(pecount, multi_driver, ninst, machine_name, mpilib)
File "/cluster/projects/nn9039k/people/tomast/NorESM/cime/scripts/Tools/../../scripts/lib/CIME/case/case.py", line 660, in _setup_mach_pes
gfile = GenericXML(infile=self._pesfile)
File "/cluster/projects/nn9039k/people/tomast/NorESM/cime/scripts/Tools/../../scripts/lib/CIME/XML/generic_xml.py", line 57, in __init__
self.read(infile, schema)
File "/cluster/projects/nn9039k/people/tomast/NorESM/cime/scripts/Tools/../../scripts/lib/CIME/XML/generic_xml.py", line 87, in read
self.read_fd(fd)
File "/cluster/projects/nn9039k/people/tomast/NorESM/cime/scripts/Tools/../../scripts/lib/CIME/XML/generic_xml.py", line 112, in read_fd
self.tree = ET.parse(fd)
File "/cluster/software/Python/3.9.5-GCCcore-10.3.0/lib/python3.9/xml/etree/ElementTree.py", line 1229, in parse
tree.parse(source, parser)
File "/cluster/software/Python/3.9.5-GCCcore-10.3.0/lib/python3.9/xml/etree/ElementTree.py", line 580, in parse
self._root = parser._parse_whole(source)
xml.etree.ElementTree.ParseError: mismatched tag: line 2095, column 2
@TomasTorsvik - I have put in a bug fix in PR #473 and verified that your command now works. I've documented the command I used in the PR. Sorry about this. I suggest overwrite release_noresm2.0.7 - unless @gold2718 and you disagree.
@mvertens - Thanks! I agree with the suggestion to overwrite and re-use the release-noresm2.0.7
tag.
@mvertens - Thanks! I agree with the suggestion to overwrite and re-use the
release-noresm2.0.7
tag.
I have removed the tag from GitHub, however, anyone who has pulled tags from NorESMhub/NorESM while it was there have a "sticky" situation. They have to remove the tag locally (git tag -d release-noresm2.0.7
), then fetch tags again. git fetch
will not overwrite a tag.
@gold2718 - Thanks for reminder to delete old tag! :+1:
Resolved in https://github.com/NorESMhub/NorESM/pull/473
@gold2718 Can you please document this release: https://noresm-docs.readthedocs.io/en/noresm2/access/releases_noresm20.html
@gold2718 Can you please document this release: https://noresm-docs.readthedocs.io/en/noresm2/access/releases_noresm20.html
or @mvertens ? :-)
@gold2718 Can you please document this release: https://noresm-docs.readthedocs.io/en/noresm2/access/releases_noresm20.html
I think this should be an issue in the NorESM-docs repo.
Resolved by #473
Can make a tag with the updated cime in the external? Cime also needs a tag for that. This branch's head should be checked out. This tag should be checkout for the NorESM workshop so devel queue and fram works. @TomasTorsvik @gold2718