Skip to content

Current year is not suitable for some model forecasting. #369

@LukeParky

Description

@LukeParky

Using 2026 as a Projected Year input breaks the pipeline. Make a code change that means we don't have to revisit this each year

Metadata

Metadata

Assignees

Labels

back-endRelated to the processing or server of the digital twinfront-endRelated to the visualisation of the digital twin

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions