rl-institut / rl-institut/simbev
Allow to use database instead of CSVs
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 13
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
simBEV produces several CSVs for each EV. For large numbers of EVs, e.g. 14 million as in the NEP 2021, scenario 2035 C, this amounts up to ~350 GB of data (looped timeseries make up most of the data).
It would speed up the processing if we had a postgres database (or HDF file(s)) to store all that stuff. I recommend sqlalchemy ORM.
Contributor guide
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
No files, tests, or entry points are named. Begin by locating where simBEV produces the per-EV CSVs, then compare the proposed PostgreSQL/SQLAlchemy and HDF approaches; done means storing the same data without the current CSV volume and preserving the required processing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, python, sqlalchemy
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100