Closed noracato closed 5 months ago
but the scenario is young enough to be ok
Wat do you mean by this? Is this related to the '1 month old migration criterium'?
Keep compatible => Simple
True
orFalse
Good idea!
Compatibility => Interpreting the current state:
Fully compatible
Within this deploy
Possibly outdated
This seems fine, as long as there is good documentation what each state means. On their own I don't have a feeling for what these states mean.
This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.
This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.
You can view the current scenario in the engine to check the compatibility settings quickly, see the screenshot here below.
However there are two issues with the current display:
This issue proposes solutions for both these problems.
1. Changing the tags
The current way of displaying compatibility: Current model version only
keep_compatible
is set to false, but the scenario is young enough to be ok Outdated - not guaranteedkeep_compatible
is set to false, and the scenario is (most probably) too old to join migrations Keep compatiblekeep_compatible
is set to true, the scenario is being migratedWe would like to split this up into two labels:
True
orFalse
Fully compatible
Within this deploy
Possibly outdated
2. Update the link
The new link to the docs is https://docs.energytransitionmodel.com/api/scenarios#forward-compatibility