Fix DC junctions in simplify_network

[bobbyxng]

Closes open-energy-transition#275
@brynpickering @euronion
Same bug present in PyPSA-Eur upstream

Changes proposed in this Pull Request

• Fixes overly aggressive DC link simplification in simplify_network (literal edge case example for new UK/Shetland HVDC and multi-terminal setup)
• Updates supernodes so only true chain nodes (degree 2, also applied to DC) are collapsed. Preserves DC junction buses/multi-terminals (degree 3+) to avoid dropping branches in topologies like Shetland to onshore branching links.

Original base network topology

Before fix
remove_stubs: true

remove_stubs: false

After fix
remove_stubs: true

remove_stubs: false

Checklist

Required:

• Changes are tested locally and behave as expected.
• Code and workflow changes are documented.
• A release note entry is added to doc/release_notes.rst.

[bobbyxng]

Clustered example 50 nodes with fix

[bobbyxng]

I had to add a new key, named it allow_ac_dc_mix for now to make this decision transparent/user configurable. Specifically, now that more DC buses "survive", it can happen that AC and DC buses in the same region (depending on clustering mode) are to be clustered. The question is, do you keep them separate (maintaining individual bus carriers) or allow DC buses to be clustered with AC buses (in this case all bus carriers become AC).

• "Visually" this looks the same, however, the underlying subnetworks and topology, number of lines and links change.
• For example, using config/test/config.clusters.yaml (administrative clustering)
  • allow_ac_dc_mix: false → 54 buses, 10 subnetworks (AC and DC kept separate)
  • allow_ac_dc_mix: true → 52 buses, 8 subnetworks (mixed clusters coerced to AC)

Open question, what to set as default. I believe the closest to replicate old behaviour is to allow mixing of AC and DC, but the technically more correct way would be to set allow_ac_dc_mix: false, as you also could have congestion between the AC and DC buses. Any thoughts? @fneum @brynpickering, maybe @martacki (given your clustering expertise :))

[brynpickering]

there shouldn't be a need to set a default here any more since our config validation means there is always a value for this config item in any snakemake run. Adding a default here means you have to maintain the default in two places (the validation config and in this script)

Suggested change

	allow_ac_dc_mix = params.cluster_network.get("allow_ac_dc_mix", False)
	allow_ac_dc_mix = params.cluster_network["allow_ac_dc_mix"]

[brynpickering]

Extend docstring to describe params and return

[brynpickering]

any possibility that a bus could have :: in it that you didn't put there?

[fneum]

I would suggest allow_ac_dc_mix: false as default, since mixing could be heavy simplification of network topology. Don't mind the extra buses.

Not sure the name is expressive enough though. Just looking at the name, one could assume separate synchronous zones (like Balearic Islands, DK etc.) can be clustered / simplified.