Question: What exactly is the denominator when normalizing expression for sequencing depth?
1
colin.kern920 wrote:

I have a question about the calculation of RPKM/FPKM and TPM in regards to how they are normalized for sequencing depth. I can think of at least 3 numbers that could be use as the denominator when doing this normalization: the total number of raw reads, the total number of raw reads that successfully aligned to the genome, or the total number of alignments that are counted by one or more transcripts.

Looking at this blog post, it describes the RPKM normalization for depth step as:

Count up the total reads in a sample and divide that number by 1,000,000 – this is our “per million” scaling factor.

This implies that the total number of raw reads is used, regardless of alignment rate or alignments that were not counted by any gene.

But then the TPM normalization step is:

Count up all the RPK values in a sample and divide this number by 1,000,000. This is your “per million” scaling factor.

Since the RPK values are calculated in the previous step and are normalizing for transcript length, then this implies that TPM only considers reads that aligned to a transcript when normalizing for depth.

My main question is whether this difference truly exists in the calculation of these two metrics by common bioinformatics software, or does it depend on the software? For example StringTie will report both FPKM and TPM in its output. Does anyone know if it calculates these metrics with this difference in how unaligned reads and "stray" alignments are included in the normalization?

rna-seq • 2.7k views
modified 2.8 years ago by Devon Ryan96k • written 2.8 years ago by colin.kern920
0
Devon Ryan96k wrote:

Normally the number of aligned reads are used for this, but as you've noticed this needn't always be the case and every tool can do whatever it wants. For what it's worth, many tools that measure RPKM/FPKM don't know how many total reads you started out with, because you're just giving them a BAM file.

Like other tools, StringTie doesn't necessarily know about your unmapped reads (they're probably not in the BAM file you give it), so it can't then use them in its calculation.

As an aside, I would argue that using unmapped reads in the calculation is incorrect. It's not uncommon to have fairly different alignment rates for different samples and this would result in the RPKM/FPKM values to be drastically different as a result.

As an aside, don't use RPKM/FPKM for anything important, they're incredibly unrobust.
{"ft_lang_label":"__label__en","ft_lang_prob":0.94129723,"math_prob":0.88484526,"size":1486,"snap":"2020-34-2020-40","text_gpt3_token_len":310,"char_repetition_ratio":0.13697706,"word_repetition_ratio":0.027777778,"special_character_ratio":0.2025572,"punctuation_ratio":0.08127209,"nsfw_num_words":0,"has_unicode_error":false,"math_prob_llama3":0.95883465,"pos_list":[0],"im_url_duplicate_count":[null],"WARC_HEADER":"{\"WARC-Type\":\"response\",\"WARC-Date\":\"2020-08-05T13:58:08Z\",\"WARC-Record-ID\":\"<urn:uuid:259cdf6d-48c4-4f22-a8d7-03ef6843d0dc>\",\"Content-Length\":\"28554\",\"Content-Type\":\"application/http; msgtype=response\",\"WARC-Warcinfo-ID\":\"<urn:uuid:49c8abcd-931c-4ae7-98eb-6d7e2cdf69f3>\",\"WARC-Concurrent-To\":\"<urn:uuid:fc9ebfe9-59dc-4633-8940-0e9c5b105ba5>\",\"WARC-IP-Address\":\"69.164.220.180\",\"WARC-Target-URI\":\"https://www.biostars.org/p/278329/\",\"WARC-Payload-Digest\":\"sha1:FZEBXHQGQERAKSB4H43ZYMMJDWEQ2VZS\",\"WARC-Block-Digest\":\"sha1:B5DRFLWRDDK3JSIGCEU2S7KEWLKVM5ZL\",\"WARC-Identified-Payload-Type\":\"text/html\",\"warc_filename\":\"/cc_download/warc_2020/CC-MAIN-2020-34/CC-MAIN-2020-34_segments_1596439735958.84_warc_CC-MAIN-20200805124104-20200805154104-00480.warc.gz\"}"}