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

Read length distributon after processing #35

Open
coolmak32 opened this issue Mar 9, 2018 · 7 comments
Open

Read length distributon after processing #35

coolmak32 opened this issue Mar 9, 2018 · 7 comments

Comments

@coolmak32
Copy link

Hello, I have using afterqc with default settings to remove adapter sequences from RNA Seq read files. My original files have all the reads of uniform length. After processing with afterqc the sequence lengths are not uniform. Therefore, I have two questions 1) Can I somehow make all the reads of uniform length? 2) What implications are we talking if the length in not uniform down the analysis (Original read length for all reads was 151 bases, after afterqc read length is between 35-142).

@sfchen
Copy link
Member

sfchen commented Mar 9, 2018

I suggest you to use our new tool fastp (https://github.com/OpenGene/fastp) to address this issue. With fastp, you can control the output with much more configurable options.

And fastp is much much faster than AfterQC (10X)

@coolmak32
Copy link
Author

coolmak32 commented Mar 9, 2018 via email

@sfchen
Copy link
Member

sfchen commented Mar 9, 2018

AfterQC performs automatic adapter trimming, and this is why it causes non-uniform read length.

@sfchen
Copy link
Member

sfchen commented Mar 9, 2018

Adapters should be trimmed before downstream analysis. So AfterQC does it automatically.

Would you like an option to disable adapter trimming?

@coolmak32
Copy link
Author

coolmak32 commented Mar 9, 2018 via email

@sfchen
Copy link
Member

sfchen commented Mar 9, 2018

No, don't worry, non-uniform length distribution is never a problem.

@coolmak32
Copy link
Author

coolmak32 commented Mar 9, 2018 via email

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

No branches or pull requests

2 participants