Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review forecast proposal / snapshot endpoint documentation for clarity and correctness #82

Closed
Tracked by #73
caindy opened this issue Mar 19, 2024 · 1 comment · Fixed by #83
Closed
Tracked by #73
Assignees

Comments

@caindy
Copy link
Contributor

caindy commented Mar 19, 2024

No description provided.

@catkins-miso
Copy link
Contributor

catkins-miso commented Mar 20, 2024

In a discussion with a vendor yesterday and responding to a TO in a separate email, this scenario came up:

Scenario: Temporary AAR exception clashes with telemetered

Given Ratings Provider has previously submitted a Temporary AAR Exception for a particular segment
When the Ratings Provider successfully submits a Ratings Forecast for the current Forecast Window for that segment
And the forecasted value clashes (higher or lower) with the exception value
Then the TROLIE proposal uses the Ratings Forecast value not the Exception value
And the response indicates the Temporary AAR exception clashed

Do you think we should nail down this scenario before completing the milestone?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants