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

ScalingSize field in Technodata.csv isn't/shouldn't be required #494

Open
tsmbland opened this issue Sep 27, 2024 · 0 comments
Open

ScalingSize field in Technodata.csv isn't/shouldn't be required #494

tsmbland opened this issue Sep 27, 2024 · 0 comments

Comments

@tsmbland
Copy link
Collaborator

The purpose of this parameter is to provide a reference capacity at which the capital_costs objective can compare capital costs of different technologies.

But why is it using a reference capacity, when it can just work out how much capacity is required to meet demand and use that capacity to compare capital costs? Surely that would be more informative?

Several other objectives (LCOE, EAC etc.) calculate capital costs as part of their overall calculation, and they all use this approach rather than using the reference capacity.

Maybe someone can shed light on this, but otherwise I suggest we delete this parameter and update the capital_costs objective in line with the other objectives.

@github-project-automation github-project-automation bot moved this to 📋 Backlog in MUSE Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant