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_stubs: false not supported #843

Closed
2 tasks done
koen-vg opened this issue Jan 3, 2024 · 3 comments
Closed
2 tasks done

remove_stubs: false not supported #843

koen-vg opened this issue Jan 3, 2024 · 3 comments
Labels

Comments

@koen-vg
Copy link
Contributor

koen-vg commented Jan 3, 2024

Checklist

  • I am using the current master branch or the latest release. Please indicate.
  • I am running on an up-to-date pypsa-eur environment. Update via conda env update -f envs/environment.yaml.

Describe the Bug

It must have a been a while ago that the clustering["simplify_network"]["remove_stubs"] configuration option actually worked. Right now, when set to false, the workflow actually crashes because the connection_costs output of the simplify_network rule is never produced. (This output is written by the _adjust_capital_costs_using_connection_costs function, which, slightly indirectly, is only run when the remove_stubs option is enabled.)

Moreover, when I was playing around with the option, I found several problems later in the workflow too for sector-coupled networks, apparently mostly related to DC offshore wind buses that are stubs and usually merged with onshore AC buses, but lead to problems when remove_stubs: false. This is the case only for certain countries (Germany, Sweden, possibly more).

One option would be to remove the choice altogether and just remove the configuration option.

On the other hand, not removing stubs actually helps quite a bit with the spatial representation of Northern Norway, which is the reason for me to look into the option in the first place. Right now I sort of hacked together a solution where stubs are removed everywhere but in Norway, and this basically works for me.

I'm not exactly sure what the best solution for the project overall is. If nobody else is interested in having networks with stubs, it's probably best to just remove the configuration option. If it's a clear ambition that stubs should be supported, however, the lack of functionality should at least be mentioned in the documentation.

@koen-vg koen-vg added the bug label Jan 3, 2024
@koen-vg
Copy link
Contributor Author

koen-vg commented Jan 3, 2024

Just to illustrate what I mean, here the topology of a network I'm currently working with. When stubs are removed, every node north of Lofoten (i.e. all the upper "tree-like" network extensions) are merged into more southern nodes, unfortunately removing any kind of spatial resolution in the representation of wind capacity factors, etc.
bilde

@koen-vg
Copy link
Contributor Author

koen-vg commented Jan 23, 2024

If any of the above ideas or something else is preferred, I'd be happy to draft and submit a pull request.

@fneum
Copy link
Member

fneum commented Apr 18, 2024

closed by #1031? reopen if that's not the case

@fneum fneum closed this as completed Apr 18, 2024
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

2 participants