New feature option: Post fire albedo decay#37
Merged
Merged
Conversation
This value is now automatically set based on the current run date in AWSM. It's a leftover cleanup from reworking the AWSM CLI interface.
Change the names to configure dates to `decay_start` and `decay_end` to be consistent with the main parameter name `decay_method`.
Adding a new albedo decay method for post fire scenarios
jomey
added
enhancement
Should not have been in here to begin with.
arobledano
approved these changes
May 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is the research done by @caldwellng and adds support for an configurable post fire albedo decay.
Change here reflect the
.inichange where the parameter in the albedo section was renamed to be more generic. See iSnobal/smrf#27