You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently show total contributions (process contributions tab) and a Sankey (Sankey tab) in the results. What could have added value is to also include a system that shows us the impacts of a first level (all technosphere flows going in to the reference/functional flow) like in the example image below:
One major feature of the below image is the display of all used impact categories at once, allowing a quick overview of where each '1st level` contribution is contributing most to.
We could also consider a more 'advanced' version of the above where we could 'dig deeper' into processes, for example showing a sunburst or treemap figure. Perhaps where users can select certain flows to see their lower level impacts, either per level (1st/2nd etc) or per process (only dig into 1 process). These 2 figures lose 1 major benefit of the top figure though; we cannot use them for a total overview of all impact categories in 1 overview.
Technical considerations:
What we're effectively looking for is Structural Path Analysis/Power Series Expansion, commonly used in EEIOA. AFAIK, we don't have this in BW2.
We could go 1 of 2 ways:
We can use the current multiLCAs from BW to calculate a bunch of processes
We can use the Sankey system, and use it's graph traversal
Both solutions are not ideal to expand to lower levels, but should both work well for only the 1st level. For only the 1st level, I'm guessing a multiLCA is faster for a few flows but many impact categories, but the graph traversal would be faster with many flows but slower with many impact categories, though this is just a guess.
The text was updated successfully, but these errors were encountered:
If I can add on this idea, a low-hanging fruit would be to have the data behind the Sankey made available to users so that they can make their own graphics in Excel or whatnot, grouping whichever processes together as they please.
If I'm not mistaken everything is already made available in brightway with the GraphTraversal method:
Just need to change the format to something more easily usable by users.
Thanks for the input! Indeed, a text/table format would be nice, though it also has some inherent challenges such as the inability to show loops, like with the contribution tree in openLCA.
Using the Sankey system in BW also has some limitations, see last paragraph of my OP for that, though I also haven't come up with a good solution yet.
We currently show total contributions (process contributions tab) and a Sankey (Sankey tab) in the results. What could have added value is to also include a system that shows us the impacts of a first level (all technosphere flows going in to the reference/functional flow) like in the example image below:

One major feature of the below image is the display of all used impact categories at once, allowing a quick overview of where each '1st level` contribution is contributing most to.
We could also consider a more 'advanced' version of the above where we could 'dig deeper' into processes, for example showing a sunburst or treemap figure. Perhaps where users can select certain flows to see their lower level impacts, either per level (1st/2nd etc) or per process (only dig into 1 process). These 2 figures lose 1 major benefit of the top figure though; we cannot use them for a total overview of all impact categories in 1 overview.
Technical considerations:
What we're effectively looking for is Structural Path Analysis/Power Series Expansion, commonly used in EEIOA. AFAIK, we don't have this in BW2.
We could go 1 of 2 ways:
Both solutions are not ideal to expand to lower levels, but should both work well for only the 1st level. For only the 1st level, I'm guessing a multiLCA is faster for a few flows but many impact categories, but the graph traversal would be faster with many flows but slower with many impact categories, though this is just a guess.
The text was updated successfully, but these errors were encountered: