Fix BAM grouping failure due to lane field in metadata#70
Open
RaqManzano wants to merge 3 commits intodevfrom
Open
Fix BAM grouping failure due to lane field in metadata#70RaqManzano wants to merge 3 commits intodevfrom
RaqManzano wants to merge 3 commits intodevfrom
Conversation
Member
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.5.1. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
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.
Problem:
DNA BAMs were not progressing past the groupTuple() operation, causing the pipeline to hang indefinitely. The issue affected DNA samples with multiple lanes (L001, L002, L003). The issue was as follows:
groupTuple()operator groups items by the entire metadata map, not just some fieldslanefield was still present in the metadata when creating thegroupKey.Solution:
Remove the
lanefield from metadata in the appropriate local subworkflow (BAM_ALIGN) before creating thegroupKey, ensuring all BAMs from the same sample group together correctly regardless of lane.