-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fixed conversion of minimal CAPAC to RUNOFF (catchment.F90) #991
Fixed conversion of minimal CAPAC to RUNOFF (catchment.F90) #991
Conversation
Bug fix: Previously, minimal CAPAC values were converted into runoff by adding them directly into total RUNOFF, but not into one of its components (RUNSRF or BFLOW), which violated the definition of total RUNOFF (=RUNSRF + BFLOW). This fix adds the minimal CAPAC into RUNSRF and thus preserves the equation of total RUNOFF.
Bug fix (CatchCN): Previously, minimal CAPAC values were converted into runoff by adding them directly into total RUNOFF, but not into one of its components (RUNSRF or BFLOW), which violated the definition of total RUNOFF (=RUNSRF + BFLOW). This fix adds the minimal CAPAC into RUNSRF and thus preserves the equation of total RUNOFF.
Testing summary: Difference is always only in variable 1. AMIP run or diff view for few differences: 2. Replay run 3. Replay No-Inc run 4. MOM6 Coupled run
5. GEOSldas regression tests All tests |
@sdrabenh: This PR is ready for merging. I apologize for what looks like confusing labels. Would it make sense to introduce one or two more labels: |
Addresses #990
Bug fix: Previously, minimal CAPAC values were converted into runoff by adding them directly into total RUNOFF, but not into one of its components (RUNSRF or BFLOW), which violated the definition of total RUNOFF (=RUNSRF + BFLOW). This fix adds the minimal CAPAC into RUNSRF and thus preserves the equation of total RUNOFF.
Changes should be 0-diff for restarts in AGCM and LDAS, and differences should only be seen in the RUNSRF and possibly RUNOFF diagnostics. The current implementation of the bug fix prioritizes efficiency and logic but may result in (minimal) changes in the total RUNOFF diagnostic, which may in turn result in non-0-diff changes in the coupled model (AOGCM). If needed, we could change the implementation of the bug fix to also make it 0-diff for coupled model restarts.
@biljanaorescanin: When you get a chance, please test this PR for the GCM (incl. the coupled model) and the LDAS.
cc: @rdkoster