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

Expression data input units #10

Closed
dBenedek opened this issue Feb 17, 2022 · 1 comment
Closed

Expression data input units #10

dBenedek opened this issue Feb 17, 2022 · 1 comment

Comments

@dBenedek
Copy link

Hello,

What is the ideal input expression unit?
TPM or some other normalized counts?

Best,
Benedek Danko

@KaiAragaki
Copy link
Owner

KaiAragaki commented Feb 25, 2022

Good question.

This method that the ESTIMATE team implemented is very similar to the ssGSEA method. As noted here,

You can find a brief description on how this ssGSEA implementation works in the details of ?estimate_score:

Enrichment scores for each sample are calculated using an implementation of single sample Gene Set Enrichment Analysis (ssGSEA). Briefly, expression is ranked on a per-sample basis, and the density and distribution of gene signature 'hits' is determined. An enrichment of hits at the top of the expression ranking confers a positive score, while an enrichment of hits at the bottom of the expression ranking confers a negative score.

So it seems to me like any kind of 'scaling' normalization like library size correction or log-transformation won't have an effect on score. However, TPM likely will (and it may be wise to normalize as such, as noted here:

ssGSEA is performed based on a ranked gene list (within sample comparisons) therefore it makes sense to use something that accounts for gene length bias in this case such as TPM or FPKM instead of normalized counts.

Hope this helps!

@KaiAragaki KaiAragaki pinned this issue Mar 11, 2022
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