openclimatefix / openclimatefix/data-platform
Quarantine Forecast
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 1
- Avg merge
- 44m
- Merged PRs (30d)
- 2
Description
Verification
- I have searched the existing issues to ensure this feature has not already been requested.
Provide a detailed description of the proposed feature.
Sometimes we make bad forecast that we dont want to server to the users, but we dont want to delete them either. It would be nice if tech-on-call person could easily quarantine a forecast if it was very bad
What is the motivation for the feature?
NL produced some very bad forecasts
Outline a potential approach or solution (optional).
- add quarantine flag (debug false) to the forecast table
- adapt read function to by default get forecasts that are not quarantined, but have option to get all forecasts
- add tool in analysis dashboard to easily quarantine a forecast (and see which ones have been quarantined)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the forecast table and its read function, then inspect the analysis dashboard entry point. Define how quarantine affects default reads and how callers can request all forecasts. Done means forecasts can be quarantined and reviewed in the dashboard without being deleted, while normal reads exclude them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- analytics, backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100