Improvements for correct_peaks
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Jupyter Notebook
- Stars
- 853
- Forks
- 322
- PR merge metrics
- No merged PRs in 30d
Description
- Correct peaks to the same side of the signal if it is possible:
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
The issue names the correct_peaks entry point and includes an image illustrating the desired correction, but it does not identify a file or test. Start by locating correct_peaks and understanding how it determines peak sides; done means peaks are corrected to the same side when possible and the behavior matches the provided image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100