mimic3wdb-matched has malformed record
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 3.4k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- Put an X between the brackets on this line if you have done all of the following:
- Checked the online documentation: https://mimic.mit.edu/
- Checked that your issue isn't already addressed: https://github.com/MIT-LCP/mimic-code/issues?utf8=%E2%9C%93&q=
Description
Description of the issue, including:
- what you have tried
I opened an issue and was told to open an issue with this project. - references to similar issues
https://github.com/MIT-LCP/wfdb-python/issues/430#issuecomment-1307619102 - queries demonstrating your question (if applicable)
import wfdb
line = 'p08/p086831/p086831-2130-12-29-18-28n'
line_parts = line.strip().split('/')
record = wfdb.rdrecord(line_parts[2], pn_dir=f'mimic3wdb-matched/{line_parts[0]}/{line_parts[1]}')
The above will throw an error due to an error in the database.
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 with the Python reproduction in the issue and inspect the referenced record path in mimic3wdb-matched. Compare the malformed record with the expected database format and check the linked wfdb-python discussion for context. Done means the supplied rdrecord call no longer fails because of this database record.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100