HFI Calculator: Show only forecasted dailies

[conbrad]

As a HFI User I want to generate HFI calc results based on forecasts only So That I don't have to race to download a PDF before actuals come in

TODO: should this be a toggle or just the default data?

Additional Context

• Feedback from DK and SI in NWFC
• WF1 API supports this with query param query=recordType.id=="FORECAST"

Acceptance Criteria

• [ ] Given (Context), When (action carried out), Then (expected outcome)
• [ ] Given (Context), When (action carried out), Then (expected outcome)

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]

I want to caution us on jumping on feedback from a couple users in one FC during spint review for a product that impacts a ton of folks. Squeaky wheels / loudest voices / what else do we know about this topic? (e.g. UXR, business context). Note of caution: NWFC process tends to be divergent from the other FCs and the official SOP/Gs (standard operating procedures and guidelines) at times. This ties into one of the business goals for this product - streamlining some of this divergence/inconsistency.

That said, asking good Qs above - UXR has uncovered that other folks rely on the actual data so that they can monitor the reality vs projection as the day goes on - adjust, learn, incorporate any trends into tomorrow. Ideally we can show them side by side for comparison and context. It's weird how we hide forecast data across BCWS applications.

[conbrad]

Thanks @tessmgood , surprised to hear others want actuals vs forecasts. Ultimately I'd like to implement something on the frontend to show a diff between forecasts and actuals so the comparison can be inlined: https://elastic.github.io/eui/#/utilities/text-diff

[tessmgood]

Not actuals vs./instead of forecasts, they make their decisions in the morning with forecasted data, but when the actuals roll in around 1pm they re-assess and watch for big discrepancies, surprises, or trends they didn't expect and roll this into communication and decision making.

The actuals are important context. Ideally we show both forecast and actual data, rather than replace. I'm not sure if the diff is enough context - there is a ton of value in knowing if the RH is 20 or 60 (those are very different scenarios and impacts on fire behaviour), not just if the RH was higher/lower by x percent.

[conbrad]

Sounds like there could be a potential for a bigger feature then. Some UI that conveys the difference between forecasted and actuals. We kind of had this visually represented with Morecast. I'd like to create a simple API that returns the actuals and forecasts together for each daily/hourly, that assumes nothing more. That way we could experiment with different workflows and UI to surface that to the user based on how they work.

[tessmgood]

How would users use the difference value? I feel like I'm missing that part.

I like your suggestion of a toggle above. Don't want to lose the forecasted values, but at some point reality (actuals) becomes more important than the projections - weather can often be wrong! If forecasted values said prep was a 2 but the actuals roll in and bump it to a 4 that is critical info.

[conbrad]

How would users use the difference value? I feel like I'm missing that part.

No idea, but we'd have both the forecast and the actual that could be displayed in different ways. Personally I like a bar chart showing differences but the API doesn't care it just gives us both values, giving us a quick structure to prototype different frontend solutions.