-
Notifications
You must be signed in to change notification settings - Fork 307
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
ne30np4 1850 case fails because the fsurdat file is incorrect. #1036
Comments
I noticed a similar issue with a file that doesn't exist (from running the -test mode in build-namelist_test.pl) lnd/clm2/surfdata_map/landuse.timeseries_48x96_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c170824.nc. |
ekluzek
added
the
branch tag: release
Changes go on release branch as well as master
label
Feb 3, 2022
This is a problem on release-clm5.0 branch as well. |
ekluzek
added a commit
to jedwards4b/ctsm
that referenced
this issue
Feb 4, 2022
ekluzek
removed
the
branch tag: release
Changes go on release branch as well as master
label
May 11, 2023
This was handled on CTSM dev, but not on the clm5.0-release branch, but we aren't updating that branch at this point, so I'm closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Brief summary of bug
Chris Fischer found that ERP_D_Ld5.ne30_g16.I1850Clm50BgcCrop.cheyenne_intel.clm-default tests fail. It looks like the fsurdat file is incorrect when this is setup. This is in cesm2_2_alpha06a testing. So the problem likely came in on ctsm1.0.dev098.
General bug information
CTSM version you are using: ctsm1.0.dev100
Does this bug cause significantly incorrect results in the model's science? No
Configurations affected: ne30_g16.I1850Clm50BgcCrop
Details of bug
fsurdat points to the landuse timeseries file...
fsurdat = '/glade/p/cesmdata/cseg/inputdata/lnd/clm2/surfdata_map/landuse.timeseries_ne30np4_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c170824.nc'
Important output or errors that show the problem
Shows error in reading the surfdat file...
The text was updated successfully, but these errors were encountered: