Dev merge eclm with FruitTree and WinterCrops all at once#95
Draft
AGonzalezNicolas wants to merge 2197 commits into
Draft
Dev merge eclm with FruitTree and WinterCrops all at once#95AGonzalezNicolas wants to merge 2197 commits into
AGonzalezNicolas wants to merge 2197 commits into
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PULL REQUEST info
This pull request wants to include the following developments:
Into the last eclm-commit a72229c of repo HPSCTerrSys/eCLM/ by merging branch-eclm of repo HPSCTerrSys/clm5_0. Below there is a detailed explanation how branch-eclm of repo HPSCTerrSys/clm5_0 is produced.
Before accepting this pull request, the following needs to be checked:
Next steps should include to run these 3 cases in CI.
This should conclude issues: #94, #93, #45
This only can be done with scientific support from IBG-3 (e.g., @tboas, @Toeroeoe).
STEPS FOLLOWED TO MERGE FT and WC into clm5.0:
Start two new dev-branches with the most updated clm5.0 version at that moment (commit e7285f6caeec6f0b35b25a6d49cb59f41d1a0c3e) in our HPSCTerrSys/clm5 repo
Merge WC (
tags/reelase_08_2020) development with one of the new dev-branches -->release-clm5.0_WinterCropsREADMEfile.Merge FT with the other new dev-branch -->
release-clm5.0_FruitTreeREADMEfile.Replace variable names on FT branch -->
release-clm5.0_FruitTree_namesVarrelease-clm5.0_WinterCropswas different fromrelease-clm5.0_FruitTree.release-clm5.0_WinterCropsused variables ascovercrop_1andcovercrop_2.release-clm5.0_FruitTree:These variable replacements are found in this other branch release-clm5.0_FruitTree_namesVar.
release-clm5.0_FTWCI used
Visual studio codeto manually solve conflicts one by one (no agents, no AI involved).The branch with both merged developments is clm5_FTWC.
Case files here
Case files here
Once the merge is considered successful (after validation against the reference cases), I proceeded to change structure of clm5 to eclm while preserving the commit history of clm5.
STEPS FOLLOWED from clm5-structure to eclm-structure
release-clm5.0_FTWC--> eclm_base_00bootstrap_v2_FTWC_00--> very similar to what @kvrigor had applied to fork eclmAnd solve conflicts on
Viscual Code Studiomanually.