Add support for reading and writing WFDB files in cloud containers
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 853
- Forks
- 322
- PR merge metrics
- No merged PRs in 30d
Description
Functions like rdrecord expect a direct path to a file be passed. Cloud services typically use URIs to point to files stored in cloud containers. When working in the cloud, simply passing the URI to functions like rdrecord will not work. A filesystem interface is required to handle backend requirements (like authentication and protocols).
Packages such as pandas and dask use fsspec. This filesystem interface allows using the same functions to read files from local, remote, or embeeded file systems.
We should consider integrating fsspec or something similar into the WFDB software.
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 tracing how rdrecord and related functions currently handle file paths. Review fsspec as the proposed filesystem interface and determine the scope of support for reading and writing WFDB files through cloud-container URIs. Done means the supported cloud filesystem use cases are defined and implemented with appropriate coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100