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 option for HTSeq-count #190

Closed
olgabot opened this issue Apr 2, 2019 · 3 comments
Closed

Add option for HTSeq-count #190

olgabot opened this issue Apr 2, 2019 · 3 comments

Comments

@olgabot
Copy link
Contributor

olgabot commented Apr 2, 2019

Hello!
We use HTSeq-count for quantifying gene expression, as featureCounts' combined exon model has been shown to not be very good (ref: https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0141910). Is anyone else interested in this feature?

I noticed the feature to run Salmon/Kallisto (#171), which would be welcomed as well!

Warmest,
Olga

@ewels
Copy link
Member

ewels commented Apr 3, 2019

Also related: #70 (add RSEM).

Could definitely add the two new tools and have an option to choose which one is used.. 👍

@ewels
Copy link
Member

ewels commented Apr 3, 2019

Note that we used to use HTSeq in our previous pipeline way back when. We switched to using featureCounts because it was significantly faster and less computationally intensive. I'm not sure if this is still the case though.

@olgabot
Copy link
Contributor Author

olgabot commented May 28, 2019

I think the reason for HTSeq was that the meta-exon model of featurecounts was inaccurate compared to the summation of transcripts model by HTSeq (citation: https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0141910)

I've implemented HTSeq-count here and could add it to nf-core/rnaseq as well.

@olgabot olgabot closed this as completed Jun 3, 2019
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