Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add 'massflows per tech' to massflow_stats #40

Open
spuhlerd opened this issue Nov 18, 2020 · 4 comments
Open

add 'massflows per tech' to massflow_stats #40

spuhlerd opened this issue Nov 18, 2020 · 4 comments
Labels
documentation Improvements or additions to documentation

Comments

@spuhlerd
Copy link
Collaborator

add everything to massflow_stats (but do not export to df)

For each tech give info on
transferred per output/recovered
three losses
mean, sd, quantiles?

Maybe later if needed for UX: make function to represent flows within a system (to make sankey diagram)

@scheidan scheidan changed the title add to massflow_stats massflows per tech add 'massflows per tech' to massflow_stats Nov 23, 2020
@spuhlerd
Copy link
Collaborator Author

spuhlerd commented Feb 3, 2021

The risk is to make system properties too heavy. Two options:

    1. calculate mass flows live using the transfer coefficinets saved per tech. For this, we would need a function that calls Santiago and returns the massflows per tech. E.g. massflows_per_tech(tech, inflows) - the problem is, that this means we would need to save for each system the massflows in Santiago for inflow=1 and then scale, because the inflow of the tech depends on its position within a system and calculating massflows "live" in the frontend is not possible
    1. Save the massflow_per_tech and system as separate object e.g. system_massflow[1].properties["nametech"] etc... Based on this e.g. for the uddt contained in system xlz-uuu we could get the massflows by system_massflow["ylz-uuu"].properties["uddt"]["phosphorus"]

You to decide!

@scheidan
Copy link
Member

scheidan commented Feb 4, 2021

610f615 adds an option techflows to massflow_summary!, see readme. If this is true the individual massflows through every tech are stored iunder properties["massflows"]["tech_flows"].

The default is techflows=false, because if set to true, the exported JSON files are almost 2.5 times larger.

@scheidan scheidan closed this as completed Feb 4, 2021
@scheidan
Copy link
Member

scheidan commented Feb 9, 2021

The comment above links to the wrong commit. This is the right one:
e628419

@spuhlerd spuhlerd reopened this Mar 3, 2021
@spuhlerd
Copy link
Collaborator Author

spuhlerd commented Mar 3, 2021

This needs to be tested and added to bestpractice runfile and WIKI

@spuhlerd spuhlerd added to be discussed documentation Improvements or additions to documentation and removed to be discussed labels Mar 3, 2021
@scheidan scheidan removed the priority1 label Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants