Add validation of segments when writing a `MultiRecord`
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
The issue names no file or test; start by tracing the MultiRecord writing workflow and locating the existing _check_segment_cohesion validation. Use #555 and the current validation as context, then confirm which additional segment checks are in scope and what completion criteria should be applied.
Written by the indexing model from the issue text.
Description
As mentioned in #555, when writing multisegment records we should validate the segments. A good initial step would be to simply add the already developed _check_segment_cohesion validation to the workflow.
There are likely a number of other validations that should be performed. For example, we may want to confirm that samps_per_frame is set for segments with expanded signals and that their length is as expected.
Please add any additional suggestions for validating the segments below.
- Dominant language
- Jupyter Notebook
- Stars
- 853
- Forks
- 322
- 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 MIT-LCP/wfdb-python
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MIT-LCP/wfdb-python#568 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
MIT-LCP/wfdb-python#554 ·
-
WFDB path ignored Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MIT-LCP/wfdb-python#545 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
MIT-LCP/wfdb-python#540 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MIT-LCP/wfdb-python#538 · 2 comments ·
All issues in MIT-LCP/wfdb-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
robjhyndman/forecast#1220 ·
-
Add: New Channel Openchannels:add check:passed
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
good first issue help wanted NLnet
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
collective/icalendar#1819 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
confluentinc/dbt-confluent#160 ·
-
inceleme-kuyrugu
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Greater-Turkiye/platform#107 ·