-
Notifications
You must be signed in to change notification settings - Fork 9
refactoring river-routing #1143
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
base: develop
Are you sure you want to change the base?
Conversation
…t in GEOSgcm_GridComp/GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/GEOSland_GridComp/GEOSroute_GridComp
…ent (GEOS_RouteGridComp.F90)
@zyj8881357 and @gmao-rreichle , I have made some changes:
4)Also all the outputs ( including check balance) and restarts will be replaced by the simple codes like this |
To make further changes, we should start with make_bcs to produce necessary files |
…outing_GEOSroute_on_yujin
…/wjiang/river_bcs
create bcs for river-routing
…m:GEOS-ESM/GEOSgcm_GridComp into feature/wjiang/Routing_GEOSroute_on_yujin
@zyj8881357 , I think this PR is ready for the test and comparison. To run this branch, you will need the develop branch of GEOSldas and feature/wjiang/pfaf_index of MAPL. Also please take a look at my run example in /discover/nobackup/wjiang/LDAS_exp/model/Routing |
@YujiN, I am trying to bring back some codes in develop branch. The develop branch is not working as it is but I believe it would be more efficient. The runoff and the other variables are distributed as needed, which is way more efficient than allgatherV.