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

HFI Calculator: Convert Fire Starts cell to a drop down in Planning Area row #1551

Closed
3 of 12 tasks
Tracked by #1542
tessmgood opened this issue Nov 18, 2021 · 2 comments
Closed
3 of 12 tasks
Tracked by #1542
Assignees
Labels
Ready User Story or Task Ready to be pulled into sprint User Requested User Story User story

Comments

@tessmgood
Copy link

tessmgood commented Nov 18, 2021

As a R/ZWCO I want to adjust the number of predicted fire starts using historical fire starts for that day plus current local risk (e.g. long weekends, festivals, weather events) So That I can calculate an accurate Prep Level

Additional Context

  • until we get further down the road with FOP prediction, we need a way to adjust Fire Starts, given that starts are a key part of the Prep equation (Mean Intensity Group x Fire Starts = Prep Level)
    • users should always like to be able to adjust the Fire Starts value, even with a perfect predictive FOP model there are still human variables to account for, for example a big music festival on the weekend (higher risk of human starts)
  • DECISION - USE SAME STARTS (KFC) FOR ALL FCs: HFI Calculator: Math differs between KFC and other FCs #1627 KFC uses a different range of Fire Starts to calculate their Prep Levels - as we bring in the other 5 Fire Centres, do we load a different range for them (the current 'official' range) or do they adjust to KFC range? (this creates operations work for them, impacting their prep sheets, policies/procedures)
  • figma

Acceptance Criteria

  • Given I am using the HFI Calculator, When I am using the weekly or daily views, Then the Fire Starts cells in a planning area row are a dropdown with ranges
  • The Fire Start ranges for Kamloops all Fire Centres are 0-1, 1-2, 2-3, 3-6, 6+
  • Given I select a Fire Start range, the Prep Level is (re)calculated accordingly (Mean Intensity Group x Fire Starts = Prep Level)
  • The Fire Start value will be a default value of 0-1 to start, understanding that a blank loading state is likely a better approach, for a future ticket? (Figma for what empty and partial states would look like)
  • The selected Fire Start value and resulting Prep Level are reflected in the copy-to-clipboard workflow
  • TBD Given a Prep Level is recalculating, the relevant planning area row uses a shimmer effect when loading (same as Fire Behaviour Calculator) - if fast, this is unnecessary

Definition of Done

  • Ready to Demo in Sprint Review
  • Does what I have made have appropriate test coverage?
  • Documentation and/or scientific documentation exists and can be found
  • Peer Reviewed by 2 people on the team
  • Manual testing of all PRs in Dev and Prod
  • Merged
@tessmgood tessmgood added User Requested User Story User story 4Refinement this ticket is ready for refinement with the team labels Nov 18, 2021
@andrea-williams
Copy link
Collaborator

I think another item for acceptance criteria in this ticket (or maaayyybe it's a separate ticket?) is adjusting the Copy-to-Clipboard-as-CSV functionality to also reflect the Fire Starts value. Right now it's hard-coded to '0-1' in the clipboard logic too

@conbrad
Copy link
Collaborator

conbrad commented Nov 23, 2021

Does this require the permissions infrastructure we discussed in daily?

@tessmgood tessmgood added Ready User Story or Task Ready to be pulled into sprint and removed 4Refinement this ticket is ready for refinement with the team labels Jan 5, 2022
@conbrad conbrad self-assigned this Jan 25, 2022
@conbrad conbrad closed this as completed Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ready User Story or Task Ready to be pulled into sprint User Requested User Story User story
Projects
None yet
Development

No branches or pull requests

3 participants