Milestones
List view
## Purpose Enhancements and coordinated redesigns scheduled beyond the initial paper submission. They should not delay evidence and documentation for the existing software. Revisit an issue if implementation review uncovers a correctness problem in a feature claimed by the paper. ## Suggested sequence Add declarative configuration (#79) and framework adapters (#80) according to demonstrated consumer needs; neither is necessary for the protocol-based public benchmark. ## Issue triage | Issue | Reason | Previous topic milestone | | --- | --- | --- | | [#79](https://github.com/jcm-sci/trade-study/issues/79) | Declarative study files are a convenience layer; the Python API already supports the proposed study. | — | | [#80](https://github.com/jcm-sci/trade-study/issues/80) | New framework-specific adapters can follow demonstrated consumer demand; the simulator protocol suffices for the generic benchmark. | — | Use focused PRs of no more than approximately 1,000 changed code lines, with commits around 200–300 lines where the change naturally allows it. Run the applicable local CI before pushing/opening a PR. Planning basis: [JOSS review checklist](https://joss.readthedocs.io/en/latest/review_checklist.html) and [submission criteria](https://joss.readthedocs.io/en/latest/submitting.html). No due date is implied; first confirm eligibility and the realistic submission schedule. Existing topic milestones remain available for their historical context.
No due date•0/2 issues closed## Purpose Required repository work before submitting the planned software paper: correctness and closure audits, verified functional/performance claims, reproducible research materials, and discoverable documentation/contribution guidance. This milestone does not replace separate verification of public-development eligibility, research use, paper authorship, or the complete submission checklist. ## Suggested sequence 1. Fix the stale-annotation overwrite bug (#171) in a small standalone PR. 2. Define and implement the artifact contract (#172), splitting schema/validation from safe publication. 3. Publish the staged/replicated-study evidence (#173), with exported results using the qualified artifact contract. ## Issue triage | Issue | Reason | Previous topic milestone | | --- | --- | --- | | [#171](https://github.com/jcm-sci/trade-study/issues/171) | Fix the confirmed stale-annotation overwrite bug first, independently of artifact redesign. | — | | [#172](https://github.com/jcm-sci/trade-study/issues/172) | Define and qualify a consistent, versioned research artifact with explicit replayability and legacy-read behavior. | — | | [#173](https://github.com/jcm-sci/trade-study/issues/173) | Produce budget-matched staged/replicated-study evidence, uncertainty-aware validation, and fair optimizer comparisons. | — | Use focused PRs of no more than approximately 1,000 changed code lines, with commits around 200–300 lines where the change naturally allows it. Run the applicable local CI before pushing/opening a PR. Planning basis: [JOSS review checklist](https://joss.readthedocs.io/en/latest/review_checklist.html) and [submission criteria](https://joss.readthedocs.io/en/latest/submitting.html). No due date is implied; first confirm eligibility and the realistic submission schedule. Existing topic milestones remain available for their historical context.
No due date•2/3 issues closedDocumentation, CI publish workflow, PyPI release. Stable public API.
No due date•5/5 issues closedWire VBPCApy convergence sweep as first consumer. Validate against existing stability_analysis.py results.
No due date•3/3 issues closedMulti-phase Study with hierarchical filtering. io.py for save/load. Full integration tests.
No due date•5/5 issues closedBayesian stacking (arviz) and score-based stacking (scipy). Grid runner with joblib parallelism.
No due date•10/10 issues closedpareto.py (non-dominated sorting, hypervolume, IGD+) and design.py (LHS, full factorial, Morris screen) with tests.
No due date•9/9 issues closedModelWorld, Scorer, Observable protocols fully typed. scoring.py wired to scoringrules with full test coverage.
No due date•13/13 issues closed