Bring-in regional line types
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
- Issue-Typ
- Feature
- Klarheit
- Muss geklärt werden
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- python
- Bereich
- data-engineering
Rechercherichtung
Start by reviewing PyPSA-Earth PR 1933, data/custom_line_types.csv, the USA configuration example, and scripts/non_workflow/build_us_line_types.py. Compare those artifacts with grid-builder's current workflow and determine how regional line types should be represented and selected. Done means regional reference data and configuration are integrated with validation for the supported cases.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Problem
Regional-specific linetypes are essential to ensure accurate representation of the line parameters. In particular, it has been demonstrated previously that default PyPSA linetypes lead to significant errors for the transmission capacity.
Solution
The approach has been elaborated basing of experience of regional case studies for Bolivia, Colombia, USA, Zambia and Japan. A solution has been implemented into PyPSA-Earth in https://github.com/pypsa-meets-earth/pypsa-earth/pull/1933 and includes the following steps.
Search for reference data
Physical parameters of conductors are normally defined by the national standards and parameters of the transmission development project and can be restored by using published data. That implies answering to the following questions.
- Which line types and line parameters present in the power system? That includes both physical parameters of conductors, as well as major operational parameters. The latter include voltages, polarity and frequency.
- What is the correspondence between the voltage levels and line types used? Ideally, voltage must be mapped into line types in an unambiguous way, while there may be also the need to accommodate some diversity across the line types
- What are physical parameters of each line type?
Generation of standardised reference dataset
The outputs of the analytical steps are translated into the following artifacts:
- parameters of the line types
- a regional-specific set of configuration features
For the now, we are using PyPSA conventions which are shared with pandapower (see custom_line_types.csv for an example).
The configuration features are region-specific, and include currently the voltage and line type id (a USA example)
Proof-of-concept
Zambia
An example of such a restoration procedure is given in this issue https://github.com/open-energy-transition/pypsa-zambia/issues/400, including dealing with data gaps and unambiguities.
The main challenges in this case are:
- the need to collate and analyse multiple reference sources
- rapid changes which are to be expected in the national power system during the next years
USA
A concept of automated procedure on the linetype extraction is available in build_us_line_types script of PyPSA-Earth. The script is parsing a synthetic network into the standardised inputs. The major challenge has been to manage richness of the reference data. That has implied format transformation, clean-up and verification. The line types in this case have been restored from physical parameters of the conductors.
- Vorherrschende Sprache
- Python
- Sterne
- 7
- Forks
- 2
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Kein Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus PyPSA/grid-builder
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 35/100
PyPSA/grid-builder#11 ·
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 30/100
PyPSA/grid-builder#10 · 2 Kommentare · 1 Reaktion ·
-
Fail to import module via github urlEvtl. vergeben @jnnr hat das vor 30 Tagen übernommen. Offenbug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 65/100
PyPSA/grid-builder#9 · 1 Reaktion ·
-
needs discussion
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 20/100
PyPSA/grid-builder#6 · 2 Kommentare ·
-
RequirementsOffen
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 25/100
PyPSA/grid-builder#2 ·
Alle Issues in PyPSA/grid-builder
Ähnliche Issues
-
area: providers/aws priority: p2 size: S type: bug type: testing
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
finos/open-resource-broker#851 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 88/100
sandialabs/atlas-ui-3#1196 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
ShaftHQ/SHAFT_ENGINE#7902 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Bug]: GraphML export writes invalid XML when a value contains a control character (e.g. form feed)Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
topoteretes/cognee#6646 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 75/100
DOI-USGS/pywatershed#428 ·