You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently MERGE_CFF is not kicking off for certain samples even though upstream processes STARFUSION_TO_CFF, ARRIBA_TO_CFF and FUSIONCATCHER_TO_CFF have completed for a given sample. The issue seems to be occurring here:
with the mix operators working correctly but the groupTuple operation is not emitting the expected result each time. confusingly, resumed runs will have different samples running MERGE_CFF and other samples that never launch the task.
after some troubleshooting i found that the error originates from inconsistent values in the meta map, specifically read_group and fastq_pair_id. since the meta map is used as the key in the groupTuple operation, it needs to be consistent across each sample. The value is inconsistent because it is how it is grouped in another subworkflow:
meta = meta + [read_group:read_group.join(','), fastq_pair_id:fastq_pair_id.join(',')]
[meta, reads.flatten()]
}
here read_group and fastq_pair_id in the meta map is replaced after grouping with a string that concatenates the read group and fastq pair ids strings. they are sometimes not concatenated in the same order. sort() is expected to fix the problem.
Command used and terminal output
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered:
Description of the bug
currently
MERGE_CFF
is not kicking off for certain samples even though upstream processesSTARFUSION_TO_CFF
,ARRIBA_TO_CFF
andFUSIONCATCHER_TO_CFF
have completed for a given sample. The issue seems to be occurring here:forte/subworkflows/local/fusion.nf
Lines 101 to 111 in d38564e
with the
mix
operators working correctly but the groupTuple operation is not emitting the expected result each time. confusingly, resumed runs will have different samples runningMERGE_CFF
and other samples that never launch the task.after some troubleshooting i found that the error originates from inconsistent values in the meta map, specifically
read_group
andfastq_pair_id
. since the meta map is used as the key in the groupTuple operation, it needs to be consistent across each sample. The value is inconsistent because it is how it is grouped in another subworkflow:forte/subworkflows/local/group_reads.nf
Lines 8 to 19 in 0b3d927
here
read_group
andfastq_pair_id
in the meta map is replaced after grouping with a string that concatenates the read group and fastq pair ids strings. they are sometimes not concatenated in the same order.sort()
is expected to fix the problem.Command used and terminal output
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: