Conversation
FabianHofmann
left a comment
There was a problem hiding this comment.
this looks nice @p-glaum, what is the status? can I support with something?
status hasn't changed so far 😅 . It was just an initial draft that the code is not lost/forgotten. I think it still needs some cleaning and updating because not all graphs look nice at the moment. I collected some TODOs above. |
Validator ReportI am the Validator. Download all artifacts here. General Files comparison
NRMSE: Normalized (combined-min-max) Root Mean Square Error Model Metrics Comparing |
improve plotting script adjust plotting parameters in plotting yaml
|
I fixed some bugs and made it compatible with the newest master version. For me, it is working and almost all plots look nice. Maybe we can fine tune the config a bit further. This PR is currently not interfering with default snakemake workflow, as you need to call the plot function separately with |
|
I will have a quick pass over this once @bobbyxng has given his feedback he announced bilaterally. Don't forget to reference the rules in the documentation and add a release note :) |
There was a problem hiding this comment.
In my tests, the plots of all carriers ran through @fneum, so the implementation generally looks good to me, only two smaller remarks:
- All plotting-related configs will be moved from config.default.yaml to plotting.default.yaml, as @p-glaum suggested. I support the idea.
vmin,vmax, see comment here: #1285 (comment)
…sv table which was previously not shown
added release note and documentation. There are just two minor open TODOs but you can already take look if you want. |
|
Just scrolling through old PRs. Any status update here? |
|
I think the idea is to get PyPSA/PyPSA#1156 in first and then use these functions directly. |
…otting configuration
|
This is amazing! Sorry for not pulling it in earlier @p-glaum! The maps have a legend sizing problem, which is however a more general problem that needs to be tackled in PyPSA: PyPSA/PyPSA#1031 I have made a few changes:
|
|
@bobbyxng had a look at my changes and had no further comments. There is some follow-on work to improve the default scaling, but since this is very scenario dependent it is difficult to give all-encompassing settings here. I think this can be merged now. |



Closes # (if applicable).
Changes proposed in this Pull Request
This PR is still a draft and needs improvement. Only uses statistics functions to create network plots by including scripts from @bobbyxng, @FabianHofmann and me.
Feel free to make improvements/changes to make it even more modular.
Checklist
envs/environment.yaml.config/config.default.yaml.doc/configtables/*.csv.doc/data_sources.rst.doc/release_notes.rstis added.TODOS
[ ] improve scaling parameters[ ] try to calculate flow width from branch width. not sure if this is possible and how exactly flow and branch_width are related. But would be nice to only havebranch_factor