-
Notifications
You must be signed in to change notification settings - Fork 14
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
Z-score normalization to normal samples #53
Comments
Good question. When I look at the sample type in the pancancer TCGA studies, I see only the following: |
Hi @antass sorry for the delayed response! In case you're still interested:
The profile shows tumor sample z-scores calculated with reference to expression in normal samples.
Normal sample data is available for 16 TCGA Pancancer studies. You can find more details in cBioPortal/datahub#1241
This indicates over expression of cholangio tumors compared to cholangio normals from the same study. |
@pieterlukasse currently only the tumor sample profile with z-scores calculated relative to expression in normal samples is loaded into the portal. We have two additional profiles:
These profiles are not yet loaded into the portal, but you can access this data in the pan_can_atlas studies under the We will update the README to include details about this profile. |
I'm exploring the TCGA Pan-Cancer dataset which includes 32 studies. What samples are used as background when I select expression with normalization to normal samples?
Are there adjacent normal samples available in all of the 32 studies? I'm struggling to find any detailed info on that. In one webinar, the z-score calculation with normals as reference is mentioned, but only in the MSK Prostate study.
Specifically, for my gene of interest, when I look at the Cancer Types Summary tab, the graph shows significant over expression in cholangiocarcinoma (94% of tumor samples have high mRNA status (z-score > 2)). Does this mean over expression of cholangio tumors as compared to
Thank you very much for your help!
The text was updated successfully, but these errors were encountered: