Skip to content
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

Bring in hillslope hydrology #222

Closed
2 tasks
billsacks opened this issue Jan 25, 2018 · 3 comments
Closed
2 tasks

Bring in hillslope hydrology #222

billsacks opened this issue Jan 25, 2018 · 3 comments
Labels
enhancement new capability or improved behavior of existing capability science Enhancement to or bug impacting science

Comments

@billsacks
Copy link
Member

billsacks commented Jan 25, 2018

Notes on bringing the hillslope_hydrology branch to master.

Items to do:

@billsacks billsacks added the enhancement new capability or improved behavior of existing capability label Jan 25, 2018
@billsacks
Copy link
Member Author

Reconcile changes in SoilHydrologyMod:

On the unified_land_model branch, I'm incorporating most of the hillslope_hydrology changes in SoilHydrologyMod, including the main changes in LateralFlowHillslope. So for the most part, we can keep the version of SoilHydrologyMod from the unified_land_model branch, but see below for exceptions.

As of 9c3d3ce on the hillslope_hydrology branch, I have incorporated all changes except:

  • I am NOT setting qdischarge (qdischarge(c) = qflx_latflow_out_vol(c))

  • I have NOT incorporated this change in SurfaceRunoff:

!scs: only allow non-zero saturated areas in lowest hillslope column
      do fc = 1, num_hillslope
         c = filter_hillslopec(fc)
         if (col%cold(c) /= ispval) fsat(c) = 0._r8
      enddo

@billsacks
Copy link
Member Author

Review changes to make sure nothing was inadvertently deleted:

In looking at some diffs on the hillslope branch, I noticed that it reverts some changes that were made on the CLM trunk, mistakenly. This problem is in the svn branch, and then has been carried over to the git branch, too.

The one issue I noticed is in clm_varctl.F90, where the hillslope_hydrology branch brings some variables back into clm_varctl.F90 that were deleted in the trunk: repartition_rain_snow and glcmec_downscale_longwave. I haven't looked to see if there are other problems, too.

From doing some analysis of the history, my best guess is that this problem arose due to plugging in SourceMods that were based on one CLM version into a branch that started from a different CLM version: The hillslope_hydrology branch started from clm4_5_14_r223, whereas the above variables were removed in r221.

A careful review should be done of all diffs in the hillslope_hydrology branch before it is brought to master.

@billsacks billsacks added type: science enhancement and removed enhancement new capability or improved behavior of existing capability labels Jan 25, 2018
@billsacks billsacks added tag: en - major new science enhancement new capability or improved behavior of existing capability and removed type: enhance - science labels May 24, 2019
@billsacks
Copy link
Member Author

I don't think the comments in this issue are relevant any more, so I'm closing the issue to avoid confusion. See #1715 .

samsrabin pushed a commit to samsrabin/CTSM that referenced this issue May 3, 2024
Fix iradsw logic for CPLHIST mode
samsrabin pushed a commit to samsrabin/CTSM that referenced this issue May 3, 2024
Update stream definitions for new coupler history file format

### Description of changes

Modify stream_definition_datm.xml to generate a streams file (datm.streams.xml) with the new coupler history file format.

### Specific notes

Changes to accommodate new coupler history file names.
Change offset for solar stream from 2700 to -900 to accommodate changes due to time stamps.
These changes work in conjunction with CDEPS PR ESCOMP#224 and CDEPS PR ESCOMP#222 .
Note that I did not change the file names for ndep, or remove that stream. See ESCOMP/CDEPS#230

Contributors other than yourself, if any: @billsacks 

CDEPS Issues Fixed (include github issue #):  N/A

Are there dependencies on other component PRs (if so list):  No

Are changes expected to change answers (bfb, different to roundoff, more substantial):  Yes, in coupler history mode.

Any User Interface Changes (namelist or namelist defaults changes): No

Testing performed (e.g. aux_cdeps, CESM prealpha, etc):  I have conducted a pair of cases, an F-case to generate coupler history files, and an I-case to read those files, using the new file name convention, and compared the forcing output variables from clm history files between the two cases.  @billsacks and I reviewed these differences and found them to be acceptable.

@billsacks ran SMS_D_Ld1.ne30pg3_t061.I1850Clm50BgcSpinup.cheyenne_intel.clm-cplhist in the context of ESCOMP#1999

Hashes used for testing:  N/A
@samsrabin samsrabin added the science Enhancement to or bug impacting science label Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability science Enhancement to or bug impacting science
Projects
None yet
Development

No branches or pull requests

2 participants