Don't zero out patch%fuel%frac_burnt()
before we use it
#1302
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.
Fixes #1301 by checking inside the
TransLitterNewPatch
for the type of disturbance instead of zero-ing outside of the subroutine.Description:
Removed the lines in
spawn_patches
that zero-d thefrac_burnt
array too soon.Added checks in
TransLitterNewPatch
to check for fire disturbance and a fire on the patch:If no fire, new local variable
frac_burnt
set to 0.0, otherwise usepatch%fuel%frac_burnt
Collaborators:
@glemieux
Expectation of Answer Changes:
Yes - should change answers because before we weren't burning any fuel
Checklist
Contributor
Integrator
Test Results:
CTSM (or) E3SM (specify which) test hash-tag:
ctsm5.3.012
CTSM (or) E3SM (specify which) baseline hash-tag:
ctsm5.3.012
FATES baseline hash-tag:
sci.1.80.4_api.37.0.0
Test Output:
Running tests now