Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Identifying the determining product (from non square SUTs)

Open
  • Is something wrong?
#12 3 comments 0 reactions 2 assignees View on GitHub

@boweidema is already working on this.

Since Jul 3, 2020.

Assessment

This issue has not been assessed yet.

Description

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

Dominant language
Python
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BONSAMURAIS/EXIOBASE-conversion-software

All issues in BONSAMURAIS/EXIOBASE-conversion-software

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.