-
Notifications
You must be signed in to change notification settings - Fork 10
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
Should PAR locus on the Y chromosome be removed in RSEM pipeline? #172
Comments
The 50 genes from PAR locus are here, from your gene table
|
My suggestion: These genes should be paired with their homogenous genes on chrX. Then expression value of these genes should be added to their homogenous genes, and then remove these genes on chrY from meta table of gene expression. |
Dear @wangshun1121 ,
Thank you immensely for this write-up and corresponding table. Due to demands that the workflow produce deterministic expression results that match the values on Xena, I have to freeze the default workflow inputs, but I've wanted to start hosting new sets of inputs as new Gencode annotations get released and the issues you've brought up are important points to consider. I'll keep this issue open until I've properly addressed it. Please let me know if you have any other suggestions or improvements I can make, they're greatly appreciated. |
Hello Dr Vivian:
I developed a raw pipeline following your instruction. I checked the RSEM gene expression results on Xena:
https://xenabrowser.net/datapages/?dataset=tcga_RSEM_gene_fpkm&host=https%3A%2F%2Ftoil.xenahubs.net&removeHub=https%3A%2F%2Fxena.treehouse.gi.ucsc.edu%3A443
You have 50 more gene IDs than mine. Then I checked gene IDs between yours and mine, and found that all these 50 gene IDs are begin with ENSGR. What's more, these genes are all from PAR locus on the Y chromosome.
Your results indicate that you didn't remove these PAR locus in RSEM pipeline as you did in Kallisto. In my opinion, these genes from PAR locus should also be removed in RSEM pipelines.
The text was updated successfully, but these errors were encountered: