Allow Grids/Scenarios to be created over smaller-than-interconnection areas
@rouille ci sta già lavorando.
Dal 3/2/2022.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
🚀
- Is your feature request essential for your project?
Describe the workflow you want to enable
I wish I could run simulations over geographical regions smaller than an interconnect. For example: running just California without the rest of the Western interconnection, or New York without the reset of the Eastern interconnection.
Describe your proposed implementation
The simplest possible implementation would be to remove all buses, branches, and generators outside of a given subset of zones that we want to consider. From the modeling perspective, this implicitly assumes that there is no import or export of power along these lines. We could instantiate this using something like: Grid("Western", zones={"Northern California", "Southern California", ...}).
In reality, power will flow into and out of a given area, but these imports/exports could be considered 'fixed', and could be modeled using constant or time-varying profiles of injections/withdrawals. For example, something like:
from powersimdata import Scenario
scenario = Scenario()
scenario.set_grid("usa_tamu", "Western")
scenario.set_zones(zones={"Northern California", "Southern California", ...})
scenario.set_import_profiles(df_indexed_by_timestamp_and_columns_are_branch_or_bus_ids)
The Scenario would then add pseudo-generators of type import_export which have fixed profiles just like hydro generators.
Additional context
I think this sort of functionality would be useful for state- or ISO/RTO-level analyses, where it's assumed that external conditions are relatively unchanging. This sort of analysis wouldn't capture how changes in powerflow within the study region could impact wheeling of power through other regions, but could allow faster iteration within a region of interest, followed by validation/tuning of the whole interconnection as a final step.
- Lingua principale
- Python
- Stelle
- 63
- Fork
- 48
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Breakthrough-Energy/PowerSimData
-
Update demand flexibility documentationForse di nuovo libera @jenhagg l’ha presa 1415 giorni fa e non c’è nessuna pull request aperta. Apertadocumentation
Breakthrough-Energy/PowerSimData#706 · 4 assegnatari ·
-
Allow demand flexibility to be enabled without flexibility profilesForse di nuovo libera @jenhagg l’ha presa 1415 giorni fa e non c’è nessuna pull request aperta. Aperta
Breakthrough-Energy/PowerSimData#705 · 1 commento · 4 assegnatari ·
-
Create a dedicated object that compares two gridsForse di nuovo libera @jenhagg l’ha presa 1479 giorni fa e non c’è nessuna pull request aperta. Apertafeature request
Breakthrough-Energy/PowerSimData#688 · 4 assegnatari ·
-
Fetch usa_tamu data from zenodoForse di nuovo libera @jenhagg l’ha presa 1479 giorni fa e non c’è nessuna pull request aperta. Apertafeature request
Breakthrough-Energy/PowerSimData#687 · 4 assegnatari ·
-
Make ramp rate input flexible to other gridsForse di nuovo libera @jenhagg l’ha presa 1490 giorni fa e non c’è nessuna pull request aperta. Apertabug
Breakthrough-Energy/PowerSimData#680 · 9 commenti · 5 assegnatari ·
Tutte le issue di Breakthrough-Energy/PowerSimData
Issue simili
-
Path subtraction removes repeated suffix characters instead of one suffixForse già presa @Gwerdonatus l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
joke2k/django-environ#671 ·
-
good first issue help wanted windows
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
-
test_pgbouncer deploys the server under test from Charmhub instead of the local build (track/1.31)Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
canonical/temporal-k8s-operator#195 · 1 commento ·
I maintainer di solito rispondono entro 4 giorni
-
`burr` fails to start when the Python path has a space in itForse già presa @enekoreto l’ha presa oggi. Apertastatus/needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 5 giorni
-
device support request
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
zigpy/zha-device-handlers#5461 ·
I maintainer di solito rispondono entro 4 giorni