Skip to content

Remove get_latest_forecasts call from Data Platform functions #210

@devsjc

Description

@devsjc

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions