xyyyyyn.hea files missing in mimic3wdb-matched DB
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
Not a big issue, but a nuisance, if what I am guessing is right. Also this is an issue regarding data hosting, not about any code.
While trying to read the 'numerics' data from the 'mimic3wdb-matched' using rdsamp() , I ran into the
'Could not find record: ...'
error. I realized that this is because the corresponding header files are not present. For example for the numerics file
$base/p04/p040033/3606239n.dat
There is no matching
$base/p04/p040033/3606239n.hea
Documentation says the file names of 'mimic3wdb' and 'mimic3wdb-matched' are the same, so I downloaded the needed header files from 'mimic3wdb', and copied over to the corresponding 'mimic3wdb-matched' directory. After that rdsamp() seems to work.
Description of the issue, including:
- what you have tried
- references to similar issues
- queries demonstrating your question (if applicable)
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
Compare the listed numerics path in mimic3wdb-matched with the corresponding directory in mimic3wdb, focusing on the missing 3606239n.hea file. Check the online MIMIC documentation and use the reported rdsamp() failure to verify the mismatch. Done means the matched database contains the required header files, or the documentation clearly explains why they are absent.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100