fix BECCS capacities in 2020 to zero #1883
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this PR
Currently, all operating CCS projects are set as bounds for 2020 and REMIND decides freely about which capture technologies to use. globally, the split is about 50:50 for BECCS and fossil CCS, leading to 20Mt BECCS in 2020 and 27 Mt in 2025.
However, in 2020 there were 3 BECCS plants in the USA (ethanol+CC, which we don't model), which total a maximum of 1 Mt captured, and one in Japan (bioigccc with 0.18 Mt).
We thus set vm_cap for all BECCS technologies to 0 in 2020.
For policy runs, this does not make a difference. However, in NPis the head-start for BECCS makes a big difference.
Type of change
(Make sure to delete from the Type-of-change list the items not relevant to your PR)
Checklist:
FAIL 0
in the output ofmake test
)Further information (optional):
See this development issue for effects on NPi