Revision of the carbon capture rate
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 615
- Forks
- 459
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 6
Description
Describe the feature you'd like to see
The cc_fraction option in the config is (currently) only applied to SMR CC, other capture rates are retrieved from technology data which are based on https://www.sciencedirect.com/science/article/abs/pii/S0961953415000070?via%3Dihub. Interestingly, we also have a SMR CC in the technology data repo but don't use it. In "further description" (https://github.com/PyPSA/technology-data/blob/master/outputs/costs_2030.csv#L319) and capture rates between 54%-90% are mentioned.
Ideas for implementation/revision:
- Retrieve the SMR CC carbon capture from technology data instead of the config (or is it intended to have a parameter sweep on that, which is obviously easier when kept in the config)
- Revise the capture rate (54%-90%?), also interesting: https://ieaghg.org/exco_docs/2017-02.pdf and this article stating that
existing production plants for blue hydrogen only achieve separation rates of around 56% on average and could therefore ‘only’ reduce GHG emissions by around half compared to gray hydrogen.
I am happy to submit a PR for 1. and if an updated capture rate makes sense also for 2.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with config/config.default.yaml at the referenced cc_fraction setting and compare it with the SMR CC entry in technology-data/outputs/costs_2030.csv. Review the cited sources and determine whether capture rates should come from technology data, remain configurable for parameter sweeps, or be revised; done requires an agreed choice and corresponding updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100