Morecast 2: Data Source Error Message
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 70
Description
**As a** Weather Forecaster
**I need** To know when the data source for a weather model is unavailable
**So That** I can easily distinguish between data errors caused by Morecast vs. errors from 3rd-party data sources
**Acceptance Criteria**
- [ ] Given I have logged in to Morecast 2, When one of the weather model data sources is down, Then an error message or notification is visible in Morecast 2 so that I know which weather models have not been updated on schedule, and that consequently the weather data displayed may be "stale" even if it is the most recently available model data
- [ ] Given (Context), When (action carried out), Then (expected outcome)
**Additional Context**
- Uptime.com
- FOR TEAM DISCUSSION: we're still using legacy code from Morecast 1 for Morecast 2.0, where WeatherStationModelPredictions are only generated from a model run when the cronjob successfully downloads ALL data from a model run. If a data source only has partial data available (i.e., only some of the expected time intervals are available) for an individual model run, our jobs won't even attempt to create station predictions from a weather model until all data is available. In the context of GFS/NOAA data, it currently seems that data is missing quite often and we don't know if it ever gets updated, so it's possible that we may rarely be able to create WeatherStationModelPredictions unless we change our logic for when these predictions are generated.
**Definition of Done**
https://github.com/bcgov/wps/wiki/Definition-of-Done
Contributor guide
Research direction
Start by tracing the Morecast 2 weather-model data jobs and the WeatherStationModelPredictions flow described in the issue, including how cronjob downloads handle partial data. Then identify where a visible error message or notification belongs and how model freshness can be determined. Done means users can see which model sources failed or were not updated and understand that displayed data may be stale.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100