Fire Behaviour Calculator (old) error messages (WF1 errors, gaps in data)
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**As a** *FBAN* **I want** *to know why errors occur* **So That** *I can workaround gaps in data with confidence and/or action the gap if relevant (e.g. contact someone about Wx problems, or communicate with a Forecaster)*
**Additional Context**
- getting lots of SME and testing feedback about a broad theme of error prevention and UI feedback - this ticket pertains specifically to ERROR statuses thrown by WF1 API
- Example: SME points out that Quick Deploy Wx stations such as Shackan QD (EK) and Tremont QD (BB) don't work - it's because they aren't forecasted for. Would be great to communicate where the error is (WFWX - no forecast) - it's actionable (talk to Forecaster) and FireBAT isn't perceived as broken.
- Proposed solution: Icons with tooltip (hover for context)
- To do: map out the common errors and the corresponding feedback that is most feasible and valuable to end users
- "How can the error messages be more actionable and clear"
-- noticing on some FBAs, when weather stations are throwing errors they use a double asterisk and note that a technician has been informed of the Wx issue
**Acceptance Criteria**
- [ ] Given I have selected a Wx, When there is no forecast data, Then the error message states there is "no forecast data available"
- [ ] Given I have selected a Wx with a incomplete forecast, When it calculates, Then there will be an error message in the status column
- [ ] Given I have selected a Wx with a incomplete forecast, When it calculates, Then there will be an icon next to the error label which on hover has a tool tip that cannot retrieve data from the API **(the text needs work)**
Contributor guide
Research direction
Start by tracing the WF1 API error statuses for no or incomplete Wx forecast data and the status-column UI described in the issue. Catalogue the messages and tooltip text needed for each case; done means the acceptance criteria are met and users can understand the error and its next action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python, react
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100