-
Notifications
You must be signed in to change notification settings - Fork 10
Issues
is:issue state:open
is:issue state:open
Issue creation is restricted in this repository
Search results
Expose ACES task criteria + dataset predicates to model
supervisedcommandsenhancementNew feature or requestNew feature or requestModelsAssociated with the curated set of models available in MEDS-DEVAssociated with the curated set of models available in MEDS-DEVStatus: Open.#314 In Medical-Event-Data-Standard/MEDS-DEV;Separate autoregressive generation from downstream inference for AR zero-shot models
enhancementNew feature or requestNew feature or requestModelsAssociated with the curated set of models available in MEDS-DEVAssociated with the curated set of models available in MEDS-DEVStatus: Open.#304 In Medical-Event-Data-Standard/MEDS-DEV;Add larger MEDS-Tab variants alongside meds_tab/tiny
enhancementNew feature or requestNew feature or requestMEDS-TabRelating to the MEDS-Tab/ derived modelsRelating to the MEDS-Tab/ derived modelsModelsAssociated with the curated set of models available in MEDS-DEVAssociated with the curated set of models available in MEDS-DEVStatus: Open.#303 In Medical-Event-Data-Standard/MEDS-DEV;Add MEDS-EIC-AR as a registered model
enhancementNew feature or requestNew feature or requestModelsAssociated with the curated set of models available in MEDS-DEVAssociated with the curated set of models available in MEDS-DEVStatus: Open.#302 In Medical-Event-Data-Standard/MEDS-DEV;Add meds-dev-submit-result CLI: client-side submission via gh
enhancementNew feature or requestNew feature or requestpriority:mediumMedium priority; should be triaged for inclusion in near-term releases.Medium priority; should be triaged for inclusion in near-term releases.Usability/InterfaceAssociated with usability by non-expert usersAssociated with usability by non-expert usersWebsite / BrandingFor website/branding/tutorial content issues (beyond pure technical documentation)For website/branding/tutorial content issues (beyond pure technical documentation)Status: Open.#297 In Medical-Event-Data-Standard/MEDS-DEV;Make result-submission form fields meaningful (dropdowns + registry-driven regen)
priority:mediumMedium priority; should be triaged for inclusion in near-term releases.Medium priority; should be triaged for inclusion in near-term releases.Website / BrandingFor website/branding/tutorial content issues (beyond pure technical documentation)For website/branding/tutorial content issues (beyond pure technical documentation)Status: Open.#296 In Medical-Event-Data-Standard/MEDS-DEV;act-based workflow smoke tests + sandbox infrastructure
priority:mediumMedium priority; should be triaged for inclusion in near-term releases.Medium priority; should be triaged for inclusion in near-term releases.TestingAssociated with testing &/or CI practices to ensure validityAssociated with testing &/or CI practices to ensure validityWebsite / BrandingFor website/branding/tutorial content issues (beyond pure technical documentation)For website/branding/tutorial content issues (beyond pure technical documentation)Status: Open.#293 In Medical-Event-Data-Standard/MEDS-DEV;Add concrete schemas for result blobs and entity manifests
priority:mediumMedium priority; should be triaged for inclusion in near-term releases.Medium priority; should be triaged for inclusion in near-term releases.Results storage and trackingAssociated with the stored model/experimental results & their validityAssociated with the stored model/experimental results & their validityWebsite / BrandingFor website/branding/tutorial content issues (beyond pure technical documentation)For website/branding/tutorial content issues (beyond pure technical documentation)Status: Open.#290 In Medical-Event-Data-Standard/MEDS-DEV;Unify entity-walking code paths; make entity collation version-aware
priority:mediumMedium priority; should be triaged for inclusion in near-term releases.Medium priority; should be triaged for inclusion in near-term releases.Results InterpretationAssociated with the impact, ease, and validity of interpreting resultsAssociated with the impact, ease, and validity of interpreting resultsWebsite / BrandingFor website/branding/tutorial content issues (beyond pure technical documentation)For website/branding/tutorial content issues (beyond pure technical documentation)Status: Open.#289 In Medical-Event-Data-Standard/MEDS-DEV;Document the website integration / results pipeline
documentationImprovements or additions to documentationImprovements or additions to documentationpriority:mediumMedium priority; should be triaged for inclusion in near-term releases.Medium priority; should be triaged for inclusion in near-term releases.Website / BrandingFor website/branding/tutorial content issues (beyond pure technical documentation)For website/branding/tutorial content issues (beyond pure technical documentation)Status: Open.#282 In Medical-Event-Data-Standard/MEDS-DEV;Add workflow to auto-regenerate _web entity manifests on source changes
priority:highHigh priority; should be included in subsequent release candidate.High priority; should be included in subsequent release candidate.TestingAssociated with testing &/or CI practices to ensure validityAssociated with testing &/or CI practices to ensure validityWebsite / BrandingFor website/branding/tutorial content issues (beyond pure technical documentation)For website/branding/tutorial content issues (beyond pure technical documentation)Status: Open.#281 In Medical-Event-Data-Standard/MEDS-DEV;Promote web tooling (collate_entities, aggregate_results) into the package
priority:highHigh priority; should be included in subsequent release candidate.High priority; should be included in subsequent release candidate.Website / BrandingFor website/branding/tutorial content issues (beyond pure technical documentation)For website/branding/tutorial content issues (beyond pure technical documentation)Status: Open.#280 In Medical-Event-Data-Standard/MEDS-DEV;