Repository navigation
[Deployment]: create Code Ocean adapter and capsule for Limma Analysis #69
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or request
Description
Goal
Create the first Code Ocean deployment adapter and Standard Capsule for canonical modules/OMIX-Limma-Analysis (currently module 0.1.0, interface 1). This is the downstream statistical-analysis capsule for declared continuous feature-by-sample matrices, including Seurat Pseudobulk donor means and GSVA enrichment scores.
Ownership
- Helix: canonical limma model and pseudobulk handoff review
- Compass: GSVA enrichment-score handoff review
- Harbor: initial adapter repository, App Panel, workflow discovery, and Code Ocean capsule
- Forge: pinned
r-statisticsruntime provenance - Beacon: contract, source, parameter, handoff, and release-evidence parity
Required workflow inputs
- One continuous feature-by-sample matrix.
- Matching sample metadata.
- Optional
Pseudobulk_Manifest.dcfwhen supplied by OMIX Seurat Pseudobulk.
The adapter should accept one unambiguous combined upstream result bundle and optional explicit file overrides. It must reject raw counts and direct users to OMIX DEG Analysis.
Required modes
- Harmony donor means:
input_kind=log2_expression, manifest-drivenvariance_model=ebayes. - SCTransform donor means:
input_kind=log2_expression, manifest-drivenvariance_model=ebayes_trend. - GSVA output:
input_kind=enrichment_score, with explicit contrasts and the appropriate declared variance model. - General declared continuous scores, without claiming support for untransformed proportions.
All public and advanced canonical parameters must be exposed, including ordered contrasts, covariates, optional donor blocking, input kind, variance model, and feature summarization. Platform output paths remain hidden.
Dependencies
- The Seurat Pseudobulk adapter issue provides end-to-end Harmony/SCT workflow fixtures and manifests.
- The GSVA adapter issue provides a representative enrichment-score workflow fixture.
- Canonical Limma Analysis must complete representative-data validation and any resulting compatible corrections before adapter release.
Acceptance evidence
- Adapter repository created from the standard template and registered in canonical module metadata after its URL exists.
- Canonical source export, commit, and hashes agree.
- CLI, schema, App Panel, source-parity, input-discovery, and failure-path tests pass.
- Representative Code Ocean runs validate Harmony, SCT, and GSVA score handoffs.
- Output tables, aligned metadata, run summary, design, contrast order, variance model, and donor-blocking provenance are inspected.
- Runtime image tag/digest and Code Ocean environment identity are recorded.
- Helix, Compass, Forge, and Beacon reviews pass. Release remains a separate explicit approval step.
Out of scope
- Raw-count normalization or voom; those remain in OMIX DEG Analysis.
- Re-running pseudobulk aggregation or GSVA inside this capsule.
- Changing the preserved Limma template behavior without a separate canonical scientific review.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
Activity
maggiecam commentedon Oct 4, 2026
Limma deployment release update:
bd58480771e48d714eb6d55227921609e4dfa580v0.1.01134919ghcr.io/nidap-community/omix-r-statistics@sha256:1325722877fec5167d171aa766ddf7bbfd056e4999bf40fd8c1eabee495da667The SCT pseudobulk handoff is released and recorded. This issue remains open because its acceptance criteria also require recorded Harmony and GSVA platform-handoff runs. Those missing evidence classes are not inferred from the successful SCT run.
maggiecam commentedon Oct 4, 2026
Traceability correction required for the Limma adapter tag:
v0.1.0resolves to post-release evidence mergebd58480771e48d714eb6d55227921609e4dfa580.734f8f4299cf4b28224ab238b0341ed62d2d93fd.The existing tag will not be moved or deleted. The Code Ocean release evidence remains valid, but tag-to-candidate provenance must be marked partial until the owner approves a corrective immutable version/tag and source-record update. No corrective tag has been created.
maggiecam commentedon Oct 6, 2026
Code Ocean validation is now complete for the Limma deployment adapter across all three intended continuous-matrix handoffs:
The single metadata-only post-release evidence PR is NIDAP-Community/OMIX-Limma-Analysis#8. It proposes, but does not create, annotated adapter tag v0.1.2 targeting validated adapter commit ed6d3cb058c9618dd18f14d9eaad4192e178bac7. No scientific code or deployment behavior changes in that PR.