Repository navigation
update recursive-refac with sector_mapping (includes up-to-date develop branch) - #330
Conversation
… kaleido to write static images if kaleido installed
update v1.3-release with develop
… rows caused by dropping metasources/attributionsources cols
Data vis
# Conflicts: # requirements.txt # setup.py
V1.3 release
…ions for location/activity Budugs
… weighted average, or adding new data
…s do not fully match original method
Update GHGI method to v2.0
…w included in FBS yaml
…w included in FBS yaml
…e "allocation" to "attribution"
Update saving of file and metadata
matthewlchambers
left a comment
There was a problem hiding this comment.
I think this should all be basically fine, noting that I haven't tested all the additions to flowby.py. Also, in the recursive branch I don't think flowbysector.py is getting used much if at all, so I hope that the changes to flowbysector.py are accomplishing their intended goal.
@matthewlchambers I updated sector_mapping with the most recent changes to develop/master branches, so the changes in flowbysector.py are not applicable to the recursive code. Thanks for the review - I will go ahead and merge |
relevant to recursive-refac:
-- return_primary_activity_column()
-- estimate_suppressed_sectors_equal_attribution()
relevant updates from master: