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

Indicator: Activitiy is an input exchange to another activity count. #9

Open
cafriedb opened this issue Sep 4, 2024 · 1 comment
Open

Comments

@cafriedb
Copy link
Collaborator

cafriedb commented Sep 4, 2024

Adding information on how many times an activity functions as an input exchange to another activitiy is very run time intensive. Creating the for loop is quickly done. However, to reduce run time it would probably make sense to get the counts for a sector seperately from generating the lca tables and adding them subeseuqntly to the lca tables. My approach was to add these statistics post lca table generation which conqsequently would run the loop multiple times (for each table) for one activtiy. I was also considering to add this part of code to the bw2analyzer function compare_activities_by_grouped_leaves but this would likely entail multiple runs for one activity.

Approach to consider: Include loop in activity dictionary generated by sector_filter.process_yaml_files.

@cafriedb
Copy link
Collaborator Author

cafriedb commented Sep 5, 2024

Added a function that creates a dictionary for each activitiy in sector_filter.py. --> def activities_are_exchanges_stats(activity_dict, database_name)

Next step, add the data to generated tables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant