Skip to content

Releases: polca/premise

Ecoinvent 3.10 + fixes

06 Jun 15:51
Compare
Choose a tag to compare
  • Adds ecoinvent 3.10 support
  • Adds inventories for ammonia production
  • Fixes scaling of PV systems (mounting panels were nto scaled down)
  • Adjusts electricity mix for aluminium production (previously unchanged, now aligned on regional electricity mixes)
  • Fixes water balance for H2 from coal gasification
  • H2 from SMR now uses national gas markets instead of regional one

v.2.1.0

16 May 01:16
Compare
Choose a tag to compare
Version bump

Fix issue when converting cubic meters of water to kilograms

14 May 15:36
Compare
Choose a tag to compare

Before, cubic meters fo water were divided by 1000 to obtain kilograms, which was wrong.
Only concerns Simapro exports.

Change database export name

14 May 06:28
Compare
Choose a tag to compare
v.2.1.0.dev7

Change database export name

Fix validation issues

10 May 11:21
Compare
Choose a tag to compare
v.2.1.0.dev6

Black reformating

Fix issue with accessing log file and prevent same function being applied twice

06 May 10:12
Compare
Choose a tag to compare
v.2.1.0.dev5

Merge remote-tracking branch 'origin/master'

v.2.1.0.dev4

03 May 07:14
Compare
Choose a tag to compare

Adds pickling of databases to avoid RAM maxing out

v.2.1.0.dev3

01 May 13:26
Compare
Choose a tag to compare
Black reformating

v.2.1.0.dev1

15 Apr 17:19
Compare
Choose a tag to compare

Full Changelog: v.2.1.0.dev0...v.2.1.0.dev1

Fixes some export issues mostly.

More flexible listing of external scenarios

08 Apr 14:24
Compare
Choose a tag to compare

THe use of external scenarios is no longer determined by the IAM scenario.

Hence, this now works:

fp = "/Users/romain/GitHub/RTE_scenarios/datapackage.json"
rte = Package(fp)

scenarios = [
{"model": "image", "pathway":"SSP2-Base", "year": 2020, "external scenarios": [{"scenario": "Reference - M0", "data": rte}]},
{"model": "image", "pathway":"SSP2-Base", "year": 2050, "external scenarios": [{"scenario": "Reference - M0", "data": rte}]},
{"model": "image", "pathway":"SSP2-RCP26", "year": 2050, "external scenarios": [{"scenario": "Reference - M0", "data": rte}]},
{"model": "image", "pathway":"SSP2-RCP26", "year": 2050, "external scenarios": [{"scenario": "Reference - N03", "data": rte}]},
{"model": "image", "pathway":"SSP2-RCP26", "year": 2050, "external scenarios": [{"scenario": "Extensive reindustrialization - M23", "data": rte}]},
{"model": "image", "pathway":"SSP2-RCP19", "year": 2050, "external scenarios": [{"scenario": "Extensive reindustrialization - M23", "data": rte}]},
{"model": "remind", "pathway":"SSP2-PkBudg1150", "year": 2050, "external scenarios": [{"scenario": "Sobriety - M23", "data": rte}]},
#{"model": "remind", "pathway":"SSP2-Base", "year": 2025},
]

ndb = NewDatabase(
scenarios = scenarios,
source_db="ecoinvent 3.9.1 cutoff",
source_version="3.9.1",
key='xxxx',
use_multiprocessing=True
)

External scenarios to use are passed directly in the list of scenarios. Also, any external scenario cna be used with any IAM scenario. Finally, we pass a list, meaning that several external scenarios can be considered per scenario.