Skip to content

Conversation

@mvdebolskiy
Copy link

@mvdebolskiy mvdebolskiy commented Dec 11, 2025

Testing:

  • prealpha_noresm all PASS (new baseline noresm_develop/noresm3_0_beta09)
  • aux_cam_noresm
    • several expected BASELINE and NLCOMP failures
    • several unexpected SUBMIT failures due to unavailability of input data from new NCAR server. To be fixed in beta09a
  • aux_clm_noresm all PASS (new baseline ctsm_develop/ctsm5.4.002_noresm_v1)
  • aux_blom_noresm all PASS (new baseline blom_develop/noresm3_0_beta09)

@TomasTorsvik
Copy link
Contributor

TomasTorsvik commented Dec 11, 2025

@mvdebolskiy - We have one more BLOM update, which is also non-answer changing. Could we also include that one?

tomast@login-3.betzy:.../tomast/noresm/nor3_b08-v1.12.23 
$ ./cs.status.20251211_195911_hy1j9n -s
20251211_195911_hy1j9n: 3 tests
  PASS ERS_Ld3.T62_tn21.NOINY.betzy_intel
  NLFAIL SMS_D_Ld1.T62_tn14.NOIIAJRAOC1850.betzy_intel
  NLFAIL SMS_D_Ld1.T62_tn14.NOINYOC.betzy_intel

@TomasTorsvik
Copy link
Contributor

@mvdebolskiy - Let me know if you want me to run the aux_blom_noresm test for this PR.

@mvdebolskiy
Copy link
Author

I am running all the tests right now.

@TomasTorsvik
Copy link
Contributor

OK, the v1.12.23 BLOM tag can also wait until the next noresm3_0_beta10 update, if you are already running the tests.

@gold2718
Copy link

If the update is to CTSM 5.4, why is the tag name still 5.3?

@mvdebolskiy
Copy link
Author

@mvdebolskiy - We have one more BLOM update, which is also non-answer changing. Could we also include that one?

tomast@login-3.betzy:.../tomast/noresm/nor3_b08-v1.12.23 
$ ./cs.status.20251211_195911_hy1j9n -s
20251211_195911_hy1j9n: 3 tests
  PASS ERS_Ld3.T62_tn21.NOINY.betzy_intel
  NLFAIL SMS_D_Ld1.T62_tn14.NOIIAJRAOC1850.betzy_intel
  NLFAIL SMS_D_Ld1.T62_tn14.NOINYOC.betzy_intel

Yes, I can include it. I have to rerun prealpha anyway.

@mvdebolskiy
Copy link
Author

If the update is to CTSM 5.4, why is the tag name still 5.3?

No, I haven't merged the ctsm PR yet, was generating baselines. will be done in couple of hours. Should I run aux_cam too?

@gold2718
Copy link

No, I haven't merged the ctsm PR yet, was generating baselines. will be done in couple of hours. Should I run aux_cam too?

Are you worried about CAM functioning with this PR? If so, running some tests would be great. Often (e.g., for a BLOM update), I just make new aux_cam_noresm baselines after the tag is made.

@TomasTorsvik
Copy link
Contributor

Since testing has been carried out with BLOM v1.12.22, I suggest to stick to this version for noresm3_0_beta09 and leave the update to v1.12.23 for later.

@mvertens
Copy link

@TomasTorsvik @gold2718 - note that cice in this PR is noresm_cice6_6_0_20250522_v1 not noresm_cice6_6_0_20250522_v3. I changed this in the documentation. Not noresm_cice6_6_0_20250522_v3 as was originally here. However, this is not in the PR that @mvdebolskiy has. I have done all my testing with noresm_cice6_6_0_20250522_v1. What should we do?

@mvdebolskiy
Copy link
Author

@mvertens I can fix this. Did the module get fixed?

@mvdebolskiy
Copy link
Author

@mvertens the name in the header is wrong. The cice checkout is correct. It's the latest cice from beta08.

@mvertens
Copy link

mvertens commented Dec 16, 2025

@mvdebolskiy - when I look at the .gitmodules file from the head of your PR I see the following:

submodule "cice6"]
path = components/cice
url = https://github.com/NorESMhub/NorESM_CICE.git
fxtag = noresm_cice6_6_1_20251129_v1
fxrequired = ToplevelRequired
fxDONOTUSEurl = https://github.com/NorESMhub/NorESM_CICE.git

This would point to the same cice as in beta08. But I thought we wanted the changes from v1->v3 for cice. We could certainly just put this into noresm3_0_beta10 since the testing is almost complete.

@TomasTorsvik
Copy link
Contributor

I have created new baselines for aux_blom_noresm.

RUNDIR: /cluster/work/users/tomast/noresm/nor3_b09-rc1
BASELINE: /cluster/shared/noresm/noresm_baselines/blom_develop/noresm3_0_beta09

All tests PASS except the 4 expected FAIL tests:

$ ./cs.status.20251216_191202_b9tfxn -s
20251216_191202_b9tfxn: 22 tests
  PASS ERI_C2.TL319_tn14.NOIIAJRAOC.betzy_intel
  FAIL ERP_Ld3_P256.T62_tn14.NOINYOC.betzy_gnu
  FAIL ERP_Ld3_P256.T62_tn14.NOINYOC.betzy_intel
  PASS ERR_Ld3.TL319_tn14.NOIIAJRAOC.betzy_gnu
  PASS ERS_Ld3.T62_tn14.N2NOINYOC.betzy_intel
  PASS ERS_Ld3.T62_tn14.NOINYOC.betzy_intel
  FAIL ERS_Ld3.T62_tn14_wtn14nw.NOINY_WW3.betzy_gnu.blom-wavice
  PASS ERS_Ld3.T62_tn14_wtn14nw.NOINY_WW3.betzy_intel.blom-wavice
  PASS ERS_Ld3.T62_tn21.NOINY.betzy_intel
  PASS ERS_Ld3.TL319_tn05.NOIIAJRA.betzy_intel
  PASS ERS_Ld5.T62_tn14.NOINY.betzy_intel.blom-woa_nuopc
  PASS SMS_D_Ld1.T62_tn14.NOIIA.betzy_intel
  PASS SMS_D_Ld1.T62_tn14.NOIIAJRAOC1850.betzy_intel
  PASS SMS_D_Ld1.T62_tn14.NOIIAJRAOC20TR.betzy_intel
  PASS SMS_D_Ld1.T62_tn14.NOIIAOC.betzy_intel
  PASS SMS_D_Ld1.T62_tn14.NOINYOC.betzy_gnu
  PASS SMS_D_Ld1.T62_tn14.NOINYOC.betzy_intel
  FAIL SMS_D_Ld1.T62_tn14_wtn14nw.NOINYOC_WW3.betzy_gnu.blom-wavice
  PASS SMS_D_Ld1.T62_tn14_wtn14nw.NOINYOC_WW3.betzy_intel.blom-wavice
  PASS SMS_D_Ld1.TL319_tn14.NOIIAJRARYF6162OC.betzy_intel
  PASS SMS_D_Ld1.TL319_tn14.NOIIAJRARYF8485OC.betzy_gnu
  PASS SMS_D_Ld1.TL319_tn14.NOIIAJRARYF8485OC.betzy_intel

@TomasTorsvik TomasTorsvik added this to the noresm3_0_beta09 milestone Dec 16, 2025
@TomasTorsvik TomasTorsvik linked an issue Dec 16, 2025 that may be closed by this pull request
12 tasks
@mvdebolskiy
Copy link
Author

@mvertens _v3 has date 250522, it's older than latest cice.

@github-project-automation github-project-automation bot moved this from Todo to In Progress in NorESM Development Dec 16, 2025
@mvertens
Copy link

@mvdebolskiy - thanks. The name in the PR summary was incorrect. As you point out - the tag we want is noresm_cice6_6_1_20251129_v1 - which is what your .gitmodules has. Sorry for my confusion.

@gold2718
Copy link

gold2718 commented Dec 16, 2025

I am getting missing inputdata files for some tests.
One example is lnd/clm2/surfdata_esmf/ctsm5.4.0/landuse.timeseries_ne30np4.pg3_hist_1850-2023_78pfts_c251022.nc
Where is this file, check_input_data cannot find it?

@gold2718
Copy link

Answer, it is on the new NCAR server which is not yet configured into our ccs_config_noresm/config_inputdata.xml

https://osdf-data.gdex.ucar.edu/ncar/gdex/d651077/cesmdata/inputdata/lnd/clm2/surfdata_esmf/ctsm5.4.0/landuse.timeseries_ne30np4.pg3_hist_1850-2023_78pfts_c251022.nc

@TomasTorsvik
Copy link
Contributor

TomasTorsvik commented Dec 16, 2025

@gold2718 , @mvdebolskiy , @mvertens
I "jumped the gun" and fired of a test run with CLM cold start: NorESMhub/noresm3_dev_simulations#298
At least, this seems to start up and run without issues.

@gold2718 gold2718 merged commit 7a28488 into NorESMhub:noresm_develop Dec 17, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in NorESM Development Dec 17, 2025
@gold2718 gold2718 deleted the pr-noresm3_0_beta09 branch December 17, 2025 14:13
@gold2718
Copy link

Tagged as noresm3_0_beta09

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

noresm3_0_beta09

4 participants