Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

D1.1 Migrate Method to use processed arrays directly #111

Open
4 tasks
cmutel opened this issue Sep 3, 2022 · 0 comments
Open
4 tasks

D1.1 Migrate Method to use processed arrays directly #111

cmutel opened this issue Sep 3, 2022 · 0 comments

Comments

@cmutel
Copy link
Member

cmutel commented Sep 3, 2022

We don't need to, or even necessarily want to, store all CFs in the database. Instead, taking inspiration from the read-only proxies in the IO table backend, we can interact directly with the processed arrays of characterization factors. This has several advantages:

  • Very fast import of methods when setting up projects
  • Very fast import of methods provided in the lciafmt specification
  • Don't need to figure out how to store more complicated CFs with uncertainty of scenarios in SQLite

Tasks:

  • Update bw2io.convert_lcia_methods_data to product a lciafmt dataframe
  • Design the extra metadata fields for storing LCIA data (e.g. Context separator character, how bibliographic data is stored)
  • SQLite row schema for methods. Optional inclusion of dataframe in database.
  • New bw2io importer for lciafmt methods
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant