Medical-Event-Data-Standard / Medical-Event-Data-Standard/MEDS-DEV
We need formal guidance on how to run experiments leveraging local, private only datasets through the whole scope of MEDS-DEV
Open
Nobody has claimed this yet.
Blocking External Use
Datasets
documentation
enhancement
priority:critical
Usability/Interface
- Dominant language
- Python
- Stars
- 43
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
This entails:
- Adding documentation on how to run with local datasets (likely mediated through an environment variable or something)
- https://github.com/Medical-Event-Data-Standard/MEDS-DEV/issues/57
Contributor guide
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 reading issue #57 and tracing how experiments currently receive datasets across MEDS-DEV. Document the complete workflow for running experiments with local, private-only datasets, including the configuration or environment-variable approach; the work is done when the guidance covers the full scope of MEDS-DEV.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100