H2 storage and compressors: Costs and efficiencies
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- data
Research direction
Start by comparing the DEA Excel entries “151a Hydrogen Storage - Tanks” and “151c Hydrogen Storage - Caverns” with the DEA PDF guidance on compressor energy and storage efficiency. Review the repository’s hydrogen storage data assumptions, then resolve and document one consistent treatment of compressor costs, FOM, and efficiency for both storage types.
Written by the indexing model from the issue text.
Description
The DEA technology data on H2 storage technologies (Technology Data Catalogue for Energy Storage) contains assumptions for H2 tanks (compressed, <= 200bar) and H2 underground (cavern, compressed <= 200bar). The data reported on these two storage types is not consistent:
a.) data for "hydrogen storage tank" (DEA excel: "151a Hydrogen Storage - Tanks") reports cost and efficiency for the full system, including piping and compressors.
b.) data for "hydrogen underground storage" (DEA excel: "151c Hydrogen Storage - Caverns") only covers the costs and efficiencies of the cavern storage.
The text (DEA pdf) is more clear on this: The storage efficiency of both storage types is similar (>99%), efficiency losses are due to the energy demand of the compressors (4 kWh_el/kg_H2 for compression to 200bar), which is taken 1:1 from the hydrogen LHV of 33 1/3 kWh_LHV/kg_H2 .
For a.) Investment costs for the system without compressors are reported, but FOM is only reported for the full system. Also no cost assumptions for compressors (per MW, only per MWh of storage system capacity) are reported.
Two options:
- separate compressor costs from storage costs
- include compressor costs and efficiency in the H2 underground storage
- Dominant language
- Python
- Stars
- 130
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
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.
More from PyPSA/technology-data
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
PyPSA/technology-data#271 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
PyPSA/technology-data#284 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
PyPSA/technology-data#283 ·
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 38/100
PyPSA/technology-data#282 · 4 comments ·
-
bug
Difficulty 5/5 Over a week Newbie friendliness 25/100
PyPSA/technology-data#281 ·
All issues in PyPSA/technology-data
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/skills#1811 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
speaches-ai/speaches#678 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
datalayer/mcp-compose#42 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
UKGovernmentBEIS/inspect_evals#2523 ·