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

Remove {ll} wildcard? #1354

Open
koen-vg opened this issue Oct 9, 2024 · 0 comments
Open

Remove {ll} wildcard? #1354

koen-vg opened this issue Oct 9, 2024 · 0 comments

Comments

@koen-vg
Copy link
Contributor

koen-vg commented Oct 9, 2024

It looks to me like the {ll} wildcard remains mainly as a historical artefact -- I'm guessing this goes back to "The role of spatial scale in joint optimisations of generation and transmission for European highly renewable scenarios". However, today I don't really see any particular reason why transmission expansion limits should get their own wildcard? To me it would make perfect sense to make this a configuration option instead, and add a flag to the {opt}/{sector_opts} wildcards instead.

It's not really consequential, and the main drawback would be a disruptive change for users, having to deal with a new file-name structure.

If it's worth considering breaking backwards-compatibility on the file-name like this, there are some other things to consider:

  • Remove prenetworks and postnetwork directory  #708
  • A little bit more radical, but I would love to merge the {opts}/{sector_opts} wildcards, eliminating confusion for new users and making it impossible to falsely put options in both of them. Instead, whether a network is electricity-only or sector-coupled should, in my opinion, be a configuration option.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant