Preprocessing script (fixing inconsistent DEA entries)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- data-engineering
Research direction
Start with compile_cost_assumption.py and inspect how DEA inputs are currently parsed, especially the Hydrogen to Jet Fuel data. Define a consistent preprocessed input format and move the technology-specific handling there; done means the compilation script is less bloated and can consume the normalized data consistently.
Written by the indexing model from the issue text.
Description
I'm becoming a bit frustrated by the inconsistent data format of the DEA input data.
E.g.: Column orders and names being inconsistent, most unchanging values are filled across all years while sometimes they are not. The inconsistencies for "Hydrogen to Jet Fuel" are e.g. at an extend were I simply started extracting the numbers by hand rather than automatically =/
The inconsistencies also make the compile_cost_assumption.py script more and more bloated and unreadable.
Suggestion:
Have a pre-processing script which is responsible for creating a consistent input data format and move all "if this tech than special treatment" cases there.
- 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
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·