-
Notifications
You must be signed in to change notification settings - Fork 9
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
Calculate impacts for all stands within Project Areas #2063
Merged
Conversation
This file contains 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
Contributor
roquebetioljr
commented
Jan 6, 2025
•
edited
Loading
edited
- Calculate impacts for all stands within Project Areas, even when no action was applied to stands.
- Filtering stands with applied actions to calculate the Project Area Treatment Result in order to keep current implementation.
- Calculate baseline metrics for Flame Length and Rate of Spread metrics instead of calculating its impacts.
- Some refactoring on repetitive queries to retrieve Stands.
george-silva
approved these changes
Jan 6, 2025
roquebetioljr
force-pushed
the
plan-1906
branch
from
January 7, 2025 14:06
093826d
to
d555db3
Compare
roquebetioljr
changed the title
[WIP] Calculate impacts for all stands within Project Areas
Calculate impacts for all stands within Project Areas
Jan 7, 2025
roquebetioljr
commented
Jan 7, 2025
@@ -402,107 +398,6 @@ def test_calculate_delta(self): | |||
) | |||
|
|||
|
|||
class AsyncGetOrCalculatePersistImpactsTestCase(TransactionTestCase): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just moved to test_tasks.py
file as the tested method is under the task file.
george-silva
reviewed
Jan 7, 2025
george-silva
reviewed
Jan 7, 2025
george-silva
reviewed
Jan 7, 2025
george-silva
reviewed
Jan 7, 2025
roquebetioljr
force-pushed
the
plan-1906
branch
from
January 7, 2025 19:30
d61113b
to
be78e9e
Compare
george-silva
approved these changes
Jan 7, 2025
roquebetioljr
force-pushed
the
plan-1906
branch
from
January 8, 2025 13:53
4530d70
to
4812dad
Compare
george-silva
approved these changes
Jan 8, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Let's test and see if this impacts other stuff.
- Filtering stands with applied actions to calculate the Project Area Treatment Result
Test-case update due to behavior change
…d Rate of Spread variables
Get stands from scenario refactored
roquebetioljr
force-pushed
the
plan-1906
branch
from
January 8, 2025 17:20
7539db2
to
e2c6123
Compare
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.