-
Notifications
You must be signed in to change notification settings - Fork 176
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
Add soil color data and change the way to read in Noah-MP parameter table #1697
Add soil color data and change the way to read in Noah-MP parameter table #1697
Conversation
Since this PR does not include the NoahMP table stuff yet, I propose we make this PR just for the soil color data so we can push it through quickly, and then have a separate PR for the NoahMP table. (Single subject PRs are greatly preferred anyway.) |
@HelinWei-NOAA this has been sitting idle for two weeks. Is there more to add for the soil color data, or can we reduce the scope of this PR to get just that part in and use a separate PR for the Noah-MP parameter table? |
@WalterKolczynski-NOAA I am working to get this into ufs repository first then I can start to work on global workflow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shellcheck found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.
@WalterKolczynski-NOAA As you suggested I will split this PR to two. This one is just for soil color and the other one will be the NoahMP table. Can I open this PR for review? |
@HelinWei-NOAA Please fix the conflicts you now have with develop first, then open it up for review. |
sync with the develop
@WalterKolczynski-NOAA I just synced my branch to the develop. What conflicts do you refer to? failing shellnorms/lint-shell check? |
Merging in develop fixed the conflicts. The shellcheck issues do need to be addressed though. |
This PR is undoing a lot of the changes in |
@WalterKolczynski-NOAA Thanks for pointing this out. I solved this issue but the commit seems too messy. Do you want me to start over with the develop branch? My modification is very minor.
|
It's fine as-is. We squash PRs into develop, so the history of the branch doesn't matter as long as the changes themselves are clean (which they appear to be now). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noting that this change won't be backward compatible due to the change in forecast_postdet.sh
Otherwise changes look good to me.
This was due to a change by me to remove |
Add mask resolution to sfc fix file names
@WalterKolczynski-NOAA Merged and ran a successful prototype test. |
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Thanks for the work @HelinWei-NOAA and team.
Description
A new soil color dataset is introduced to Noah MP to reflect the right soil albedo to reduce the large warm bias found in the Sahel desert. The more-recent and higher resolution BNU soil texture data will be used to replace the old data.
Noah MP parameter table is part of the source code in the current version. The UFS model has to be recompiled whenever there is any parameter change in the table. Therefore we propose to change this structure and the table will become one of the input file to the model.
Closes #1614
Closes #1617
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Checklist