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
I am creating external scenarios and ran into the following problem:
In my LCI, I have an activity with the name Advanced Dry Recovery (ADR) and an activity with the name ADR. These activities have variables attached in my configuration, where I refer to these names to match them.
I found that the ADR activity matched without issue, but the Advanced Dry Recovery (ADR) would not. After inspection, it turns out that the second process is written to Brightway as advanced Dry Recovery (ADR) (note the lower case first letter). After changing my LCI and config file to advanced Dry Recovery (ADR), Premise matched the correct variable without issue.
Somehow Premise is lower-casing the first letter (but only in some cases??), which cause Premise to fail to link.
The text was updated successfully, but these errors were encountered:
There's a function that indeed lower-caps names and reference products of datasets and exchanges, except if it starts with an acronym. This is to align more with the ecoinvent naming convention.
I am creating external scenarios and ran into the following problem:
In my LCI, I have an activity with the name
Advanced Dry Recovery (ADR)
and an activity with the nameADR
. These activities have variables attached in my configuration, where I refer to these names to match them.I found that the
ADR
activity matched without issue, but theAdvanced Dry Recovery (ADR)
would not. After inspection, it turns out that the second process is written to Brightway asadvanced Dry Recovery (ADR)
(note the lower case first letter). After changing my LCI and config file toadvanced Dry Recovery (ADR)
, Premise matched the correct variable without issue.Somehow Premise is lower-casing the first letter (but only in some cases??), which cause Premise to fail to link.
The text was updated successfully, but these errors were encountered: