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
Exogenous transition path for shipping, Steel, and Aluminum production #136
Conversation
update from master upstream
The share of shipping demand that is transformed is defined now for different years to be used with the myopic code. The carbon emission from the remaining share is treated as a negative load on the atmospheric carbon dioxide bus, just like aviation and land transport emissions.
…ances. When plotting the balance for H2, the rename dictionary merges all the demands containing H2. This commit disables such merging and keeps different colours for H2 in shipping and H2 in industry. This is useful when one wants to look at the H2 balance and have an overview of where the H2 is consumed in the model.
Previously, the transformation of the Steel and Aluminum production was assumed to occur overnight. This commit enables the definition of a transformation path via the config.yaml file. This requires adding the {planning_horizon} to the input and output file name of the following rules: build_industrial_production_per_country_tomorrow build_industrial_production_per_node build_industry_energy_demand_per_node prepare_sector_network
I just realized that I missed adding the oil consumed in shipping as a load to the EU oil bus. |
That is really cool! I guess n the Snakefile there is the wildcard |
That was my mistake when I merged the master. |
Great, flexibly switching between exogenous transition paths and fixed choices for parameters is very nicely implemented and we can surely use this as role model for other parameters, too. |
Transformation of shipping demand, as well as production of Steel and Aluminum, is currently assumed to occur overnight.
(i.e. is only represented by one value in the config.yaml file). This PR enables the use of exogenously defined transition paths for these transformations.