Repository navigation
Correct Limma 0.1.1 run-summary provenance - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Corrects the adapter-owned run-summary provenance that remained stale after canonical OMIX Limma Analysis
0.1.1was synchronized.Closes #4.
Changes
code/main.Rnow records canonical module0.1.1, interface1, and source commitdb70975167807d10634d5af33fc49828e32be633.tests/test-pseudobulk-handoff.Rasserts those exact values for both ordinary and numeric-group handoffs.CHANGELOG.mdrecords the provenance correction.Validation
git diff --checkbash tests/run-tests.shAll local adapter checks passed.
Platform evidence
Code Ocean run
1212150already proved that the synchronized scientific function completes the exact Harmony1-0analysis withauto -> ebayes, but exposed the stale provenance text. After this PR merges, rerun the same capsule parameters and verify the corrected summary.No release is authorized.