Repository navigation
Archive a forecast round ahead of the next release - #238
Open
vahid-ahmadi wants to merge 1 commit into
Open
vahid-ahmadi wants to merge 1 commit into
vahid-ahmadi wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
forecasts/nowcast-round
branch
from
November 12, 2026 05:13
bcf528f to
1dc2592
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated round from
forecasts/nowcast.py, generated byforecast_ukon the hosted MCP server ahead of an announced ONSrelease.
Merging this makes a public, permanent claim. Rounds are
append-only — CI fails any PR that edits or deletes one — so a
round that is wrong cannot be corrected, only superseded, and it
stays in the denominator of every accuracy statistic.
Check before merging:
data_edgeis the data the model was actuallyallowed to see, and the outturn it will be scored against has
not been published yet
provenance.warningsis empty andprovenance.essiscomfortably above 100 — the script refuses on the warnings it
knows about, but read them anyway
forecasts/rounds/is an addition onlyThe regenerated scorecard and fan charts are on this branch, so
the provenance gate passes on merge.