Ben Young (ERG)
Ben Young (ERG)
see https://github.com/USEPA/flowsa/commit/e7d35a149cf327a6eb3ecd43b9c06edc69c8326d
> We might want to make it optional in the result calculation and not the default unless we're sure it won't interfere with pkg functions operating on the result objects...
ok are you still working on this now or should I take over?
The following can solve this: ``` source_names: FBA_1: source_name: FBA year: 2018 activity_sets: ... FBA_2: source_name: FBA year: 2019 # These datasets last appear in 2019 activity_sets: ... ``` With...
I've clarified the descriptions for this and `aggregateResultMatrixbyRow()` in a61fc47. One is designed to aggregate a result matrix (`G` or `H`) while the other is to aggregate a sector by...
Initial scripts provided in https://github.com/USEPA/USEEIO_team/commit/b0832995c74f363d893cb765c429deb61d09d022 and https://github.com/USEPA/USEEIO_team/commit/a27178d4fad6f0789da295e86d0f66f57d08da23
Nope, I didn't do much with the trading
and $y_m$ to $m$?
Update results matrices to use `G` and `H` for flows and impacts respectively (replacing `LCA` and `LCIA`) where superscript `l` is final and `r` is direct https://github.com/USEPA/useeior/blob/master/format_specs/Calculation.md
For regional LCIA, the location objects must match those used by the LCIA methods. Meaning, unless LCIA methods are updated to include location objects aligned with electricity regions (BA, NERC,...