Change approach for allowing `seg_name` and `seg_len` to be lists
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 853
- Forks
- 322
- PR merge metrics
- No merged PRs in 30d
Description
In https://github.com/MIT-LCP/wfdb-python/pull/514 an update was made to allow seg_name and seg_len to be lists. This is needed for writing a MultiSegmentRecord.
@bemoody , suggested an alternate approach:
But I think what we really want is, rather than changing the types in SEGMENT_SPECS, we want to add "seg_name" and "seg_len" to LIST_FIELDS (wfdb/io/record.py, line 1675.)
This issue is being opened to track implementing this alternate approach.
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
Start by inspecting LIST_FIELDS in wfdb/io/record.py around line 1675, along with the current SEGMENT_SPECS handling. The change is complete when seg_name and seg_len are handled through LIST_FIELDS and writing a MultiSegmentRecord continues to support them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100