Skip to content

intention of NO_READS_READLEN #74

@blex-max

Description

@blex-max

_get_reads_length returns nothing when the constant NO_READS_READLEN is not exceeded in the final if condition, propagating an undefined variable down the chain until the program crashes. We've got users trying to run the tool on long read data with low depth - which I appreciate the tool wasn't designed for. The most obvious way to fix this problem would be to lower the value of NO_READS_READLEN, currently at 50,000. And notably judging by the commit history this did used to be lower - originally the return conditional checked against a hardcoded value of 1000. However, maybe this is a very bad fix, and I don't want to go changing things without understanding the intention of these checks. @davidrajones git reckons these bits of the codebase were written/modified by you. I know it was quite a while ago, but do you have insight into this? Many thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions