Skip to content

Identifying the determining product (from non square SUTs) #12

@agneta20

Description

@agneta20

We were facing a challenge in detecting the determining product flow as theoretically these could be picked up from diagnol of the Supply tables. However, given that Exiobase is non- square i.e. 200 pdts x 164 activities, it is not that trivial to identify the determining flow directly.

Hence we have the following solution:

  • We use a separate basic correspondence vector of determining products and the activities that helps us translate the information correctly into RDF

  • Another method could be to square the Supply and Use tables before converting them to RDF. This was already done in the Mojo repository . Here the product flows are aggregated and the exclusive by-products are placed in a global market. This is useful to build the computational structure (A/Z matrix) but aggregating product flows also leads to loss of information.

Would like feedback

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions