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

Make handling of CONVENTIONAL variables consistent #488

Open
denised opened this issue Oct 11, 2021 · 1 comment
Open

Make handling of CONVENTIONAL variables consistent #488

denised opened this issue Oct 11, 2021 · 1 comment
Labels

Comments

@denised
Copy link
Member

denised commented Oct 11, 2021

When multiple solutions have the same CONVENTIONAL alternative, they should use the same values for CONVENTIONAL variables. E.g. all the Energy solutions should use the same values for things like emissions-for-conventional-alternatives.
In the current practice, this is handled as a separate, manual step early in the integration process.

Moving forward, in the python system where it is easier to share things, solutions should be able to declare what their conventional technology is, and that should cause all the conventional values to be loaded from that shared data set.

@denised
Copy link
Member Author

denised commented Oct 15, 2021

Note: this is already done for the energy solutions: they share conventional VMAs located in the data/energy/vma_data directory. Its nice how the change in vma directory representation makes this much more transparent when looking at the code.

@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
Projects
None yet
Development

No branches or pull requests

1 participant