Exclude sample groups from quantification when MapAlignerIdentification doesn't finds shared feature maps - #474
Merged
jonasscheid merged 2 commits intoSep 11, 2026
Conversation
|
jonasscheid
marked this pull request as draft
September 8, 2026 12:13
jonasscheid
force-pushed
the
fix/mapaligner-zero-landmarks
branch
2 times, most recently
from
September 9, 2026 11:41
167f807 to
93947bb
Compare
❌ nf-test failed with latest Nextflow versionNote Tests with Nextflow's latest version failed but it will not cause a CI workflow failure.
See the full run for details. |
jonasscheid
commented
Sep 9, 2026
…pAlignerIdentification finds no shared RT landmarks
jonasscheid
force-pushed
the
fix/mapaligner-zero-landmarks
branch
2 times, most recently
from
September 9, 2026 12:49
93947bb to
091c4ce
Compare
jonasscheid
marked this pull request as ready for review
September 9, 2026 20:27
…peptide identifications on FAIMS data
steffenlem
approved these changes
Sep 11, 2026
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
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.
MapAlignerIdentificationaborts (exit 8,no data points for 'linear' model) when one LC-MS run of a sample+condition shares no FDR-filtered peptide IDs with its replicates within--max_rt_alignment_shift, so no RT anchor pairs exist for the linear fit. Seen in PRIDE reprocessing (RCC replicate with 3 PSMs; PXD037270 QE vs QE2 runs beyond the shift window). The tool has no option to skip such runs.flowchart TD R1[Replicate 1<br/>2063 shared peptides] --> A R2[Replicate 2<br/>1872 shared peptides] --> A R3[Replicate 3<br/>2038 shared peptides] --> A R4[Replicate 4<br/>3 PSMs, 0 shared peptides] --> A A[RT alignment, MapAlignerIdentification<br/>no RT anchors for replicate 4, exit 8] A -- dev --> X[Pipeline aborts] A -- this PR --> S[Sample excluded from LFQ<br/>peptide IDs exported, warning logged] style R4 fill:#fde2dc,stroke:#c2410c,color:#7c2d12 style X fill:#fde2dc,stroke:#c2410c,color:#7c2d12 style S fill:#d5f0ec,stroke:#0f766e,color:#134e4aerrorStrategyforOPENMS_MAPALIGNERIDENTIFICATION;MAP_ALIGNMENTdetects groups without trafoXMLs (join(remainder: true)+branch), warns once per sample, and the main workflow exports them identification-only like empty-FDR samplesfaims:merge_featuresinFeatureFinderIdentification: OpenMS 3.5.0 drops all peptide IDs from features on FAIMS data (upstream issue to follow)PR checklist
nf-core pipelines lint).nf-test test --profile +docker).CHANGELOG.mdis updated.