Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixes ntrimmer bug basepair output growing in size #234

Merged
merged 5 commits into from
Oct 12, 2020
Merged

Conversation

joe-angell
Copy link
Collaborator

Problem was empty reads were causing ntrimmer to set rcut 1 on empty sequence making Read::getLengthTrue return 0-1 or max size_t.

@joe-angell
Copy link
Collaborator Author

This still doesn't address the issue of how the empty reads are getting output.

// number of bp that are trimmed off left side
size_t getLTrim() const { return cut_L; }
// number of bp that are trimmed off right side
size_t getRTrim() const { return (length - cut_R); }
size_t getRTrim() const { return cut_R <= cut_L ? (length - cut_L)+1 : length - cut_R; }
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if getRTrim is the number of bp trimmed off the right side, I don't think this should be altered.

@joe-angell
Copy link
Collaborator Author

@msettles I recommend we merge this before making the change preventing trimming of all bases.

@joe-angell joe-angell merged commit 438994d into master Oct 12, 2020
@joe-angell joe-angell deleted the trim-bug branch October 12, 2020 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants