Requirements
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Tranquilo
- Stack tecnológico
- python
- Área
- build-system, data-engineering
Línea de trabajo
No files, tests, or entry points are named. Start by reviewing the requirements in this issue alongside the repository structure and existing workflow description. The issue is complete only when the inputs, outputs, methodology, validation approach, and configuration options have been turned into an agreed, implementable architecture.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hello!
I'm adding an issue to summarize the ideas on the architecture to facilitate coordination.
This issue is meant to collect feedback on the (a) inputs, (b) outputs, (c) methodology and (d) configuration options.
Feel free to comment and integrate relevant points into this message: the list can ideally be updated to track all relevant ideas that appear.
Motivation: validated grid data for power-system models using open data
Inputs
- Open Street Map data [main requirement for minimum viable product]
- the architecture shall support additional custom data with standard data format
Outputs
- Substations
- Lines
- Cables
- Converters/Transformers
- Their graph representation (basically substation ids for lines/cables)
- Electrical parameters as appropriate (Line types / impedance values)
- Rated power capacity
- Optionally visual representations of the resulting network
- While we start with HV lines, we can consider a modular architecture to support LV/MV in the future
Methodology
We agree on the conceptual steps of the model
- download data
- cleaning/harmonizing the raw data
- building the graph-representation of the network
- validation of the result: estimating error-metrics against known datasets and track changes in results over time.
pypsa-earth-status (name could be revised) can support on the validation
Options
- Regional scope: it shall be global as well as regional
- Line Types shall optionally change by region
- The cleaning steps must contain multiple heuristics, that can be optionally used for cleaning
- The building step shall require heuristics on how to merge the entries (e.g. using substation geometries, spatial tolerance, relations, etc)
Looking forward to hear your opinion!
I give permission to all maintainers to edit this message to track all relevant information that may follow in the discussion.
- Lenguaje dominante
- Python
- Estrellas
- 6
- Forks
- 1
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Issues similares
-
agent-ready documentation needs-triage
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
-
documentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
-
Add https://search.jeremyh.xyz/ Abiertoinstance instance add
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
searxng/searx-instances#939 · 1 comentario ·
-
area-deployment area-integrations triage:bot-seen
Dificultad 2/5 Medio día Aptitud para principiantes 86/100