ImperialCollegeLondon / ImperialCollegeLondon/PyProBE
Automate data labelling
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 56
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
This issue aims to reduce the dependence on `Step` for splitting up cycler data. Potential solutions to this include, but are not limited to:
- Simple segmentation with tools like `aeon` or `ruptures`
- `README` informed segmentation, using the pybamm experiment descriptions for validation of the identified segments
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
Start by reviewing how Step currently splits cycler data and the README-informed segmentation approach described in this issue. Compare simple segmentation with aeon or ruptures against PyBaMM experiment descriptions for validation. Done means reducing dependence on Step with an agreed automated labelling approach, but the issue does not identify files or tests.
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