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

Scenarios should declare whether they are Baseline, Conservative, etc. #451

Open
denised opened this issue Sep 16, 2021 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@denised
Copy link
Member

denised commented Sep 16, 2021

There is no requirement that a scenario be in any specific camp, but most of them are. Adding explicit metadata would make it easier for any user interface to help users select appropriately, And if we start to have functionality that operates on a sector or global level, it would make it easy for scenarios to use the correct global assumptions.

@denised
Copy link
Member Author

denised commented Oct 3, 2021

Also, I had added module fields PDS1, PDS2 and PDS3 to all scenarios, but I realize now that this is misleading --- these labels refer to global scenarios, and the behavior of individual solutions may be different in each. So, really, those fields should also be renamed to align.

Note: there are two very similar naming conventions that are easily confused:
Conservative/Ambitious/100%Res
Plausible/Drawdown/Optimum

The first officially refers to categorizations of sources, but tends to bleed over into the naming of scenarios.
The second is synonymous with PDS1/2/3. So I think we should use the Conservative/Ambitious labels, but I'd like to find another name for 100% because of the difficulty of using it as an identifier. "Max" seems like it might be a good choice, or maybe Ultimate.

@denised denised added the enhancement New feature or request label Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant