Medical-Event-Data-Standard / Medical-Event-Data-Standard/MEDS-DEV
[Proposal] We should codify a schema or standard (or a path forwards as more experiments are developed in this vein) to separate some sentinel experimental properties for visualization (e.g., dataset size).
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Current proposal: (model_name, model_version, model_hash (?), dataset_name, dataset_version, dataset_hash (?), task_name, MEDS-DEV_version, uploaded_timestamp, result_json_blob)
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
The issue proposes a schema or standard for separating experimental properties used in visualization, including model, dataset, task, version, timestamp, and result fields. Start by reviewing the existing MEDS-DEV benchmark conventions and experiments, then determine the path forward for codifying these fields. Done would require an agreed schema or standard, but the issue does not identify files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100