-
Notifications
You must be signed in to change notification settings - Fork 48
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
0f12cb0
commit a5c68d5
Showing
8 changed files
with
29 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,7 +24,7 @@ Workflow | |
As illustrated in the workflow diagram above, *premise* follows an Extract, Transform, Load (ETL_) process: | ||
|
||
Extract the ecoinvent database from a Brightway_ project or from ecospold2_ files. | ||
Expand the database by adding additional inventories related to future production pathways for certain commodities, such as electricity, steel, cement, etc. | ||
Expand the database by adding additional inventories for future production pathways for certain commodities, such as electricity, steel, cement, etc. | ||
Modify the ecoinvent database, focusing primarily on process efficiency improvements and market adjustments. | ||
Load the updated database back into a Brightway project or export it as a set of CSV files, such as Simapro CSV files. | ||
|
||
|
@@ -79,8 +79,9 @@ Additionally, we provided a summary of the main characteristics of each scenario | |
|
||
.. _CarbonBrief: https://www.carbonbrief.org/explainer-how-shared-socioeconomic-pathways-explore-future-climate-change | ||
|
||
You can however use any other scenario files generated by REMIND or IMAGE. If you wish to use an IAM file | ||
which has not been generated by either of these two models, you should refer to the **Mapping** section. | ||
You can however use any other scenario files generated by REMIND or IMAGE. | ||
If you wish to use an IAM file which has not been generated by either of these | ||
two models, you should refer to the **Mapping** section. | ||
|
||
.. _maintainers: mailto:[email protected] | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters