OHDSI / OHDSI/StudyAgent

Support multiple cohort-method comparisons instead of only the first one

Open
#43 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
12
Forks
8
Avg merge
2m
Merged PRs (30d)
12

Description

Title
Support multi-comparison cohort-method generation from cm_comparisons.json

Body

Problem

The cohort-method generator currently materializes only the first comparison in cm_comparisons.json.

Current behavior

Even when multiple valid comparisons are present, only the first is propagated into the generated cohort-method artifacts and script.

Risk

  • silent under-generation of intended analyses
  • confusing mismatch between comparison-selection artifacts and final execution script
  • users may assume all selected comparisons are included when only one is executed

Requested change

Update the cohort-method shell and generator to support multiple comparisons end-to-end.

Acceptance criteria

  • all selected comparisons in cm_comparisons.json are considered during generation
  • generated output can represent multiple cohort-method analyses
  • script generation remains compatible with supported HADES versions
  • output/state clearly identifies which comparisons were included
  • regression tests cover one-comparison and multi-comparison cases

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the cohort-method shell and generator that consume cm_comparisons.json, then trace how selected comparisons reach generated artifacts and the execution script. Compare one-comparison and multi-comparison behavior, and use regression tests to verify all selected comparisons are represented, supported HADES script generation remains compatible, and output/state identifies included comparisons.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, shell
Domain
data, testing, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.