Circularity Futures: Glass Case Study

First release of SCORPIO/Circularity Futures version of the code, packaged with data files to execute the glass case study.

What's Changed

• Adds bugfix #198 to circularity futures dev branch by @rjhanes in #200
• Updates Circularity Futures dev branch with recent bug fixes in master by @rjhanes in #205
• Adding some of the cost methods - all based on the fine grinding cost… by @jwalzberg in #207
• Updates liaison w circularity futures recent coding by @rjhanes in #210
• Issue 212: Converts facility id values to string and adds letter to enforce by @rjhanes in #214
• Updates circfutures/liaison working branch with facility id conversion to strings by @rjhanes in #215
• updates path_split feature branch with recent updates from liaison dev branch by @rjhanes in #218
• Updates issue branch for #208 with recent commits by @rjhanes in #224
• Issue 208: converts path_split functionality to only move lost mass to landfill by @rjhanes in #227
• Issue 231 by @rjhanes in #236
• Dev circfuture liaison transport by @jwalzberg in #237
• Issue 234 by @rjhanes in #238
• #233 changes route_id processing for split path facilities to return … by @rjhanes in #239
• Fixing celavi-data issue #83 by @jwalzberg in #243
• updates feature branch 240 with bug fix in dev branch by @rjhanes in #250
• updates feature branch 241 with bug fix in dev branch by @rjhanes in #251
• Issue 241: implement un-scaling when component_scaledown is used by @rjhanes in #256
• Fixes issue 249 and shorten code by @jwalzberg in #258
• Issue 259: speed up CostGraph by applying vectorization and dropping duplicates from the routes_computed file by @rjhanes in #260
• #261 filters upstream nodes and replaces the edgebased distance with … by @rjhanes in #262
• Revert "#261 filters upstream nodes and replaces the edgebased distance with …" by @rjhanes in #263
• Issue 261 by @rjhanes in #264
• Update to feature branch by @rjhanes in #268
• Update to feature branch II by @rjhanes in #269
• Issue 266: refactor supply chain structure input datasets and various speed ups by @rjhanes in #267
• updates feature branch with new color scheme for diagnostic plots by @rjhanes in #272
• #247 adds inc/decrement for all facilities in between glass manuf and… by @rjhanes in #276
• Issue 240: Implement additional logic for accurate component accounting in closed loop pathways by @rjhanes in #275
• Issue 286: Resolves occasional facility material flow duplication by @rjhanes in #287
• Dev circfutures liaison by @rjhanes in #289
• Issue 281: Docstring and comment updates only; no code functionality changes by @rjhanes in #288
• Resolving issue of negative component counts ( window glass recovery ) for Scenario 410 by @tapajyoti-ghosh in #291
• Updates feature branch with recent PR to dev branch by @rjhanes in #292
• Update feature branch for issue 284 by @rjhanes in #294
• Side bug fix: Corrects use of in_use_facility_lifespan parameter during CostGraph instantiation (Issue 296) by @rjhanes in #297
• Updating feature branch remove-route-ids by @rjhanes in #305
• Update fix-route-ids feature branch by @rjhanes in #306
• Storing lca_db shortcut in memory. by @tapajyoti-ghosh in #310
• Forward merge issue 309 to feature branch fix-route-id by @tapajyoti-ghosh in #311
• Forward merge issue 309 to remove-route-ids by @tapajyoti-ghosh in #312
• Merges fix for #315 into feature branch fix-route-ids by @rjhanes in #316
• Option 1 to resolve issues 300, 301: Remove route_id tracking altogether by @rjhanes in #303
• Revert "Option 1 to resolve issues 300, 301: Remove route_id tracking altogether" by @rjhanes in #318
• Merges additional fix for #314 into fix-route-ids feature branch by @rjhanes in #319
• [merge first] Option 2 to resolve issues 300, 301: Fix route_id records and transportation tracking logic by @rjhanes in #304
• [merge second] Issue 284 and 307: expands pathway_crit_history results file with additional location and facility details by @rjhanes in #313
• [merge last] Cleaning up the PyLCIA LiAISON code ( Several changes are included ) Issue 282 by @tapajyoti-ghosh in #293
• Resolving issues with LCA calculation: See details by @tapajyoti-ghosh in #327
• Issues 325, 321, 322, 323, and 324 by @rjhanes in #328
• corrections to des and des_interface for LCA by @tapajyoti-ghosh in #329
• Updates branch for issue 320 with fixes implemented for issue 326 by @rjhanes in #331
• Merges fixes for issues 320 and 326 for combined test by @rjhanes in #333
• Resolves issue 326 by @rjhanes in #332
• Updates fix branch for issue 320 on top of 326 with fix for 326 by @rjhanes in #336
• updates combined issue fix branch with individual issue fix by @rjhanes in #337
• Resolves issue 320 on top of issue 326 fixes by @rjhanes in #335

Full Changelog: v1.3.4...circfut-v1.0

Data Files

celavi-data-circfutures (1).zip

v1.3.4: Improve error handling

See issue #202 for changes made in this release.

No input data were changed for this release.

There are two input datasets downloadable for use with CELAVI. Both datasets contain all the required data files as well as READMEs and YAML files for CELAVI execution.

This is the national (U.S.) scale datasets for the wind blade case study used in our previous publications:
CELAVI_WindBladesDatasets_National.zip

This is an artificially small dataset for the same case study, to be used only for debugging, troubleshooting, testing, and generally getting to know CELAVI:
CELAVI_DebuggingDatasets.zip

Release v1.3.3: Bug fix

See issue #198 for explanation

No input data were changed for this release.

There are two input datasets downloadable for use with CELAVI. Both datasets contain all the required data files as well as READMEs and YAML files for CELAVI execution.

This is the national (U.S.) scale datasets for the wind blade case study used in our previous publications:
CELAVI_WindBladesDatasets_National.zip

This is an artificially small dataset for the same case study, to be used only for debugging, troubleshooting, testing, and generally getting to know CELAVI:
CELAVI_DebuggingDatasets.zip

Release 1.3.2: Bug fixes

See Issue #195 for full details

No input data were changed for this release.

There are two input datasets downloadable for use with CELAVI. Both datasets contain all the required data files as well as READMEs and YAML files for CELAVI execution.

This is the national (U.S.) scale datasets for the wind blade case study used in our previous publications:
CELAVI_WindBladesDatasets_National.zip

This is an artificially small dataset for the same case study, to be used only for debugging, troubleshooting, testing, and generally getting to know CELAVI:
CELAVI_DebuggingDatasets.zip

Release 1.3.1

This is the final release of the Circular Economy Lifecycle Assessment and VIsualization (CELAVI) codebase.

From release 1.3.0, there have been only non-functionality-related changes that include updates to the README, the code version and description in setup.py, and the removal of an old dependency.

There are two input datasets downloadable for use with CELAVI. Both datasets contain all the required data files as well as READMEs and YAML files for CELAVI execution.

This is the national (U.S.) scale datasets for the wind blade case study used in our previous publications:
CELAVI_WindBladesDatasets_National.zip

This is an artificially small dataset for the same case study, to be used only for debugging, troubleshooting, testing, and generally getting to know CELAVI:
CELAVI_DebuggingDatasets.zip

Release 1.3.0

This release implements:

• Uncertainty analysis capabilities, primarily in cost methods and a few other key parameters
• pyLCIA 2.0 upgrade for faster and more stable (non-optimization) impact calculations
• Generation of a summary file with key cumulative or end-of-run output values, for use in uncertainty visualizations

Release 1.2.0

Release 1.2.0 adds support for uncertainty calculations.

It also contains a major rewrite and cleanup of main.py by refactoring functionality into scenario.py

Bug fix release: v1.1.1

Resolves issue #138 and PR #139

Release 1.1.0

The goal for this release is fully generalized, well documented prototype code. Issues belonging to this milestone should focus on making the code more data-driven, including using input parameters from the config file, and on expanding and clarifying the docstrings throughout the codebase.

Release 1.0.0

This is the first stable release of CELAVI.