To unsubscribe from this group and stop receiving emails from it, send an email to ucsc-cancer-genomics-browser+unsub...@googlegroups.com.
Hi Chris,All of those will allow full compatibility between TCGA and GTEx.
---------- Forwarded message ----------
From: Christian Mazzeo <christi...@icloud.com>
Date: Tue, May 22, 2018 at 9:50 PM
Subject: [ucsc-cancer-genomics-browser] TCGA TARGET GTEx dataset
To: UCSC Xena and Cancer Genomics Browser <ucsc-cancer-ge...@googlegroups.com>Hi!My doubt is witch of gene expression RNAseq dataset i have to use for full compatibility between TCGA and GTex to make a differential expression analysis?RSEM norm_count , RSEM expected_count o RSEM expected_count (DESeq2 standarized)?Thanks in advance!Chris
--
You received this message because you are subscribed to the Google Groups "UCSC Xena and Cancer Genomics Browser" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ucsc-cancer-genomics-browser+unsubs...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Adnan,
and I can’t find the call to DeSeq2 that would produce the Deseq2-standardized/normalized TCGA/GTEx/TARGET data posted here
This is a good point — this was added about a year after the initial recompute by request and I didn’t think to send along the commands to the Xena team. The deseq2 normalized counts were obtained using a method recommended by the author. I wrote a wrapper function to create the counts here.
This is less important, but likewise I’m not able to see where the upper-quartile normalization takes place for Hugo “normalized” counts. It looks like you’re rescaling by setting the upper-quartile of non-zero values to 1000, as in GDAC, then taking the log, but it’s not quite exact. It would be useful to see the exact methods.
The script to normalize the counts is actually embedded inside a Docker container which is why you don’t see it in the source code, but you can see its contents here. I ported it over from the original TCGA RNA-seq workflow but ended up removing it from the toil-rnaseq workflow after I realized they were running it on every RSEM output (like TPM, which doesn’t really make sense). Currently the workflow just includes the raw RSEM output with no normalization.
Let me know if you have any further questions and apologies for making you dig around so much.
Cheers,
John
To view this discussion on the web visit https://groups.google.com/d/msgid/ucsc-cancer-genomics-browser/30695b7a-9104-4da9-a0a1-065a8f453ed9n%40googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ucsc-cancer-genomics-browser/b6dbf3aa-5178-4800-ad99-85bb30a595bdn%40googlegroups.com.