AB would not properly take the correct version user selected and would instead use an older version and apply patches to the newest version
bw2io has patches, but does apparently not properly update the naming of an unknown amount of flows between unknown versions. The flow from which we found the problem is berillium, which is now called beryllium II in biosphere 3.9. The patches do not update these flownames properly when used. There is an unknown amount of flows that will have similar problems.
It is likely all installs of ecoinvent 3.9 since AB version 2.9.3 have this problem. I don't know why these versions will have installed, as AB usually notifies the user that ecoinvent could not be installed if biosphere flows are unmatched.
Checklist
[x] Keep pull requests small so they can be easily reviewed.
[x] Categorize the PR by setting a good title and adding one of the labels:
bug, feature, ui, change, documentation, breaking, ci
as they show up in the changelog.
coverage: 50.681% (-0.007%) from 50.688%
when pulling e289fad05c5bdb6615f118827a74c2865ebda389 on marc-vdm:biosphere_install_fix
into 0955df9ad3644251c9511f73a3998cdefc99df74 on LCA-ActivityBrowser:master.
Beryllium issue we were notified of over email
There are multiple problems:
berillium
, which is now calledberyllium II
in biosphere 3.9. The patches do not update these flownames properly when used. There is an unknown amount of flows that will have similar problems.It is likely all installs of ecoinvent 3.9 since AB version 2.9.3 have this problem. I don't know why these versions will have installed, as AB usually notifies the user that ecoinvent could not be installed if biosphere flows are unmatched.
Checklist
bug
,feature
,ui
,change
,documentation
,breaking
,ci
as they show up in the changelog.