Little ETM input conversion module #82
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Btw we created this branch a while ago, and there's a lot of commits I dont recognise. If you want me to rebase onto main let me know, tomorrow I might have a spare 20 mins for it. Otherwise one of you could fix it, as you know more about what happened in the other part of the model. |
*Configuration: o.a. default energy assets Run: o.a. gridConnection calculateEnergyBalance(), connectionOwner updateFinances(). *Dummy-parameter voor forceren uncached cloud-runs met dezelfde instellingen *Pythonscripts: modelkeuze wordt nu in experiment gemaakt; caching kan omzeild worden met boolean.
*Dummy parameter toegevoegd waarmee d.m.v. een random-getal uncached API-runs kunnen worden geforceerd zonder modelinstellingen aan te passen. -Mogelijke bug: bij het 1000-agents experiment loopt de cloud vast, maar het offline model werkt gewoon..
*parallelStream.forEach() in f_addDefaultEnergyAssets ongedaan gemaakt; geeft onvoorspelbaar gedrag en is niet sneller (op mijn laptop iig) *parallellisatie in hoofd tijdstap-event alleen op de populatie gridConnections (for now...) Dat is verreweg de zwaarste stap. *Parameter toegevoegd p_paralellize waarmee parallelisatie aan en uit gezet kan worden, toegevoegd aan cloud-model inputs *Parameter p_importLocalJsonConfigs toegevoegd aan cloud-model inputs, zodat die in de cloud altijd op False geforceerd kan worden (tenzij je dat niet wil natuurlijk) *Python class Experiment uitgebreid met parallelize parameter
noracato
force-pushed
the
feature-BuildingsFromETM
branch
from
e712f3c to
9396ce4
Compare
Scenario: bedrijventerrein in Groningen. Geeft een lege dataset terug..
Queries toegevoegd voor curves en totale opgestelde vermogen van de zon-productie-posten (households, buildings, energy power solar plant).
…mand households The hourly electricity demand households is still WIP. We would like to divide the curves with the yearly electricity demand of households, so this has to be added.
Hourly curves in MW per hour Yearly demands in PJ
noracato
force-pushed
the
feature-BuildingsFromETM
branch
from
9396ce4 to
35e1f2c
Compare
|
This banch has been rebased on |
noracato
added a commit
to Zenmo/HOLON-ETM
that referenced
this pull request
Oct 17, 2022
|
Moved in Zenmo/HOLON-ETM@77d1970 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here's the first version of the configurable ETM input conversion module. We can use it for the passive connection to start with, but we can also bend it a bit to be included in the active connection - as an imported module in the Django backend (? I'm not too familiar with Django to know if that's really possible, but I guess so..).
It features:
✨ Retrieving all possible curves from the ETM ✨
✨ Retrieving any gquery ✨
✨ Retrieving any node property ✨
✨ And you can mix them and create conversions! ✨
Right now only a 'divide by' conversion is supported, where you can divide an ETM output curve by the value of a node property or query. All customisable in the config file.
Check out the README for more info on how to use it.
This is a first version, so there's room for improvement:
I hope you can have fun with this and try to make some connections to the ETM when I'm on holidays. Looking forward to bugfixing and feature requests when I'm back 😉
Including @marliekeverweij