[go: nahoru, domu]
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.

Sign up for GitHub

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

Jump to bottom

dealing with UMIs containing N #36

Closed
rmvpaeme opened this issue Oct 12, 2020 · 2 comments
Closed

dealing with UMIs containing N #36

rmvpaeme opened this issue Oct 12, 2020 · 2 comments
Assignees
@baraaorabi

Comments

@rmvpaeme
Copy link

After running calib, about 30% of my reads contain an UMI with at least one 'N'. How do you suggest that we deal with these? Currently, we are filtering out all these reads.

Thanks.
@rmvpaeme
Copy link
Author

in addition, could it be possible to add an option that outputs the base with the highest quality for bases that don't have a 50%+1 majority vote?

@baraaorabi baraaorabi self-assigned this Oct 16, 2020
@baraaorabi
Copy link
Collaborator

I think you should examine the .msa files generated by the consensus step. Do they make sense to you? If a lot of read clusters have bad consensus (thus generating a lot of N's), it might be worth changing the clustering parameters.

Also, if you want to have your own consensus building rules (e.g. using qualities or keeping non-majority plurality bases), you can use the .msa file. Each cluster has its full multiple sequence alignment printed out and you should be able to process in your own custom way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@baraaorabi baraaorabi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@baraaorabi @rmvpaeme