Skip to content

Use only patch subsequence of ONT read in consensus #68

@skoren

Description

@skoren

Right now, we do not split reads so the full ONT reads are included even if the patch is much shorter. This can lead to issues when the patch is near the ends of tigs. The long ONT reads will extend past the last HiFi read and generate low-quality ONT-only cns. It is also likely redundant (overlapping) with other tigs in the output that do have the HiFi reads. To address this, make consensus support subsequence coordinates for reads and only use the minimum needed ONT sequence (+ surrounding sequence to place it).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestwontfixThis will not be worked on

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions