openclimatefix / openclimatefix/quartz-api
Remove get_latest_forecasts call from Data Platform functions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 32
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 13
Description
For getting forecasts with the data platform backend, the default is to pull the forecasts from the forecaster that most recently ran. However, now we are updating the versions of the forecasters less regularly, we should remove dependency on this. Ideally, the forecaster name and version desired for the location type/region etc should be mapped or hardcoded in the routers.
That way, this part could be removed, and the forecaster_name and forecaster_version parameters could be made non-optional.
https://github.com/openclimatefix/quartz-api/blob/main/src/quartz_api/internal/backends/dataplatform/client.py#L102-L119
this will speed up queries.
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 in src/quartz_api/internal/backends/dataplatform/client.py at lines 102-119, then trace the routers that request forecasts for each location type or region. Identify where forecaster_name and forecaster_version are currently optional or resolved through get_latest_forecasts. Done means the routers select the desired forecaster details, the parameters are required, and the get_latest_forecasts dependency is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100