You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment technology-data does not contain any costs for HVDC underground. The default assumption seems to be that cables are either submarine or overhead. For example in add_electricity:
Think about harmonizing cost data for Offwind-connection/HVDC
Think about using the same default assumption for non-submarine DC lines (either overhead, or underground, consistently for Offwind-DC and Other-DC)
I made this observation, because in PyPSA-Ariadne we use NEP costs data, and the NEP does not contain any submarine costs, only underground costs. Our immediate fix will be to use the same costs for HVDC underground/ HVDC submarine/ Offwind-connection underground/offwind connection submarine.
The text was updated successfully, but these errors were encountered:
At the moment technology-data does not contain any costs for
HVDC underground
. The default assumption seems to be that cables are either submarine or overhead. For example in add_electricity:pypsa-eur/scripts/add_electricity.py
Lines 374 to 385 in 4c1ec35
On the other hand, the default assumption for Offwind DC connections is, that cables are either submarine or underground.
pypsa-eur/scripts/prepare_sector_network.py
Lines 471 to 481 in 4c1ec35
Relatedely the
HVDC submarine
cost is at around 1000€, while offwind-connection-submarine is around 2000€. Why is this discrepancy there?So here are a few things we could do:
HVDC underground
costs to technology-data. (And perhaps vice versaoffwind-X-connection-overhead
).I made this observation, because in PyPSA-Ariadne we use NEP costs data, and the NEP does not contain any submarine costs, only underground costs. Our immediate fix will be to use the same costs for HVDC underground/ HVDC submarine/ Offwind-connection underground/offwind connection submarine.
The text was updated successfully, but these errors were encountered: