-
Notifications
You must be signed in to change notification settings - Fork 312
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
Fix subset_data error "no attribute 'evenly_split_cropland'" #2253
Conversation
This also caps the numba environment to avoid a numba/numpy compatability issue that is currently unaddressed by numba
…ather than using nco.
FATES API update to facilitate fates refactor This updates a number of FATES type names and module use statements which correspond with a refactoring effort that moves FATES patches and cohorts into their own respective modules. With the FATES update is a minor science update, so there are changes to answers for FATES. This also incorporates a minor update to a more recent version of the ccs config external.
b4b changes to Python scripts, history lists, tech note, and clm_time_manager.
… with user_init_interp=.false.
Thank you for this explanation, @ekluzek. Makes sense. |
I did 3 git reverts to remove #2080 from this group merge. All three touch python codes only. |
To address the above izumi test-failure...
Similar solution for the 3 missing dev158 derecho tests, which are new in dev 158 (DONE).
From branch that will be dev159:
Update the group permissions for dev159 baseline directories DONE If all goes smoothly with these, then talk to @ekluzek about another PR that may join the merge. @ekluzek will look into the other two failing tests. May need to open issue and deal with later. In that case add EXPECTED FAILURE. Then I will finish the merge. |
In looking at the DAE test, it passed for me and doesn't show the same error you see. And I looked at your case and see what the failure looks like. I'll try running with vanilla ctsm5.1.dev158 and see if that's an issue. |
The issue with SMS_D.f10_f10_mg37.I2000Clm51BgcCrop.derecho_nvhpc.clm-crop, is just that the entry in Expected fails lists it incorrectly as failing in RUN when it should be SHAREDLIB_BUILD. |
The DAE test passes for me also in vanilla ctsm5.1.dev158. PASS DAE_C2_D_Lh12.f10_f10_mg37.I2000Clm50BgcCrop.derecho_intel.clm-DA_multidrv CREATE_NEWCASE @slevis-lmwg maybe also try it in vanilla ctsm5.1.dev158 and see if it was just a glitch for you that it failed? There might be environment issue as well, but I don't know what it would be... |
Ok, submitted: |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Resubmitted DAE_C2_D_Lh12.f10_f10_mg37.I2000Clm50BgcCrop.derecho_intel.clm-DA_multidrv this morning. I submitted DAE_C2_D_Lh12.f10_f10_mg37.I2000Clm50BgcCrop.derecho_intel.clm-DA_multidrv @ekluzek this PR is now ready for the merge. Do you prefer that I wait for that additional PR that you said may fit well with this PR? Will that require a new round of testing? |
@slevis-lmwg I'm having trouble getting a set of externals that work together and fix the mpi-serial intel-DEBUG issue. There is a simple change that fixes the FUNIT issue. But go ahead and make the tag as is, and we'll get that fix in later. It would've needed you to redo the testing (since enough externals had to be updated) anyway, which isn't a good way to go anyway. |
Description of changes
This command returned the error:
./subset_data point --lat 38.9375 --lon 253.0625 --site Gothic --create-surface --create-user-mods --create-datm --outdir /glade/scratch/slevis/nldas/gothic --datm-syr 2000 --datm-eyr 2014 --dompft 1
Adding the following lines to subset_data.py fixes the error:
@ekluzek you plan to open an issue for resolving pylint suggestions that have appeared in recent tags and have been ignored. I could resolve these in this PR if you agree.
Update: #2253 consists of two commits (9e0f81c d895c6e), and I may have confused things by merging several other branches to this PR's branch as part of a larger BFB merge. Details below.
Specific notes
Contributors other than yourself, if any:
@wwieder encountered the error
Several additional contributors as part of the larger BFB merge.
CTSM Issues Fixed (include github issue #):
No issue opened
Are answers expected to change (and if so in what way)?
No
Any User Interface Changes (namelist or namelist defaults changes)?
No
Testing performed, if any:
Python testing missed this and was passing and continues to pass