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
When one wants to retain the computational structure of the SUT to be used as a model, e.g. for LCA analyses, MARIO now implicitly allows only the industry-based technology assumption.
However, it is becoming increasingly necessary to be able to adopt the product-based technology assumption while retaining the SUT framework.
This requires adding an attribute when initialising a SUT table in MARIO. By default this will be compiled technology_assumption = 'industry-based'. This will result in the calc_all algorithm behaving exactly the same as it currently does.
If instead technology_assumption ="product-based" it will be necessary to fill in the endogenous coefficient matrix (to date, z) so that the make side is consistent with the equations for this assumption.
When one wants to retain the computational structure of the SUT to be used as a model, e.g. for LCA analyses, MARIO now implicitly allows only the industry-based technology assumption.
However, it is becoming increasingly necessary to be able to adopt the product-based technology assumption while retaining the SUT framework.
This requires adding an attribute when initialising a SUT table in MARIO. By default this will be compiled technology_assumption = 'industry-based'. This will result in the calc_all algorithm behaving exactly the same as it currently does.
If instead technology_assumption ="product-based" it will be necessary to fill in the endogenous coefficient matrix (to date, z) so that the make side is consistent with the equations for this assumption.
Attached is a conceptual Excel file to make the reasoning explicit, with nomenclature consistent with what is already present and potentially implementable in MARIO for completeness.
https://enextgen22.sharepoint.com/:x:/s/eNextGen/EUmvIiplgdFLkrD8B6I1SSMBD5KPsN-W9QfY07ZuU0fOWQ?e=4xLl9t
The text was updated successfully, but these errors were encountered: