Is your feature request related to a problem?
Certain amplicons may be larger than the combined read length, resulting in a situation where merging fails for all or some of the reads.
Describe the solution you'd like
We already have the option to deal with non-overlapping reads (--non_overlapping). What we lack is a way to alert users that they should use this option.
A minimal solution would include:
- Count the merged reads
- count the un-merged reads
- Define a threshold past which we trigger an allert (> 10% unmerged?)
There is no built-in way to do this at the moment, and we have two completely separate processing chains to consider (dada2 + vsearch), which will require separate solutions.
Description
No response
Additional context
No response
Is your feature request related to a problem?
Certain amplicons may be larger than the combined read length, resulting in a situation where merging fails for all or some of the reads.
Describe the solution you'd like
We already have the option to deal with non-overlapping reads (--non_overlapping). What we lack is a way to alert users that they should use this option.
A minimal solution would include:
There is no built-in way to do this at the moment, and we have two completely separate processing chains to consider (dada2 + vsearch), which will require separate solutions.
Description
No response
Additional context
No response