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

Add Warning for poly(A) libraries #781

Closed
ojziff opened this issue Mar 8, 2022 · 3 comments
Closed

Add Warning for poly(A) libraries #781

ojziff opened this issue Mar 8, 2022 · 3 comments
Milestone

Comments

@ojziff
Copy link

ojziff commented Mar 8, 2022

Description of feature

Hi there,

Many RNAseq accessions do not make explicit whether the RNA prep was total or polyA. I think TrimGalore and cutadapt require -a "A{10}" to trim poly-A tails. My concern is the implications on expression and splicing analyses of not removing polyA tails in oligo(dt) selected libraries?

Like RSeQC infer_experiment.py is used to generate a warning for strandedness fail, I wondered if a similar warning could be created with Qualimap:Genomic Origin or RSeqQC read distribution when intronic reads are < 10% indicative of polyA selection? And suggest to re-run the pipeline with -a "A{10}" ?

Many thanks,
Oliver

@drpatelh drpatelh modified the milestones: 3.7, 3.8 Apr 26, 2022
@drpatelh drpatelh modified the milestones: 3.9, 3.10 Sep 25, 2022
@drpatelh drpatelh modified the milestones: 3.10, 3.11 Dec 16, 2022
@drpatelh drpatelh modified the milestones: 3.12, 3.11 Mar 21, 2023
@drpatelh
Copy link
Member

Hi @ojziff would there be any harm in always trimming poly(A) tails? Just added fastp support in #970 where you can use --trimmer fastp --extra_fastp_args '--trim_poly_x' which should trim the polyA tails by default along with any adapter sequences.

@ojziff
Copy link
Author

ojziff commented Mar 22, 2023

Thanks @drpatelh. I can't envisage any harm from trimming polyA tails together with the adapter as default.

@drpatelh
Copy link
Member

Sweet! Will close this then!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants