-
Notifications
You must be signed in to change notification settings - Fork 37
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
Provide a list of TitanCall abbreviations in an easily-accessible form #8
Comments
Hi Luca, Sorry for the inconvenience. I was an oversight on my part not to have put this directly into the R documentation.
I typically use the Best, |
What are all the possible values for Also I've observed states > 20. I figured perhaps the table continues in a linear fashion, since there are 2 rows for CN=1, 3 for CN=2, 4 for CN=3, 5 for CN=4, 6 for CN=5. However, I've observed state 21 and 23 for CN=8? I've copied Supp Table 14 below:
Here are the (distinct) titan states from two of my TITAN seg output files, which seem to match each other, but not Supplementary Table 14?
EDIT: looking at the code here it looks like this has to do with whether the parameter |
Working back from the code I reconstructed the following version of supplementary table 14 for when It may be useful to add this to the wiki somewhere, where it is easily visible.
|
This is also not documented anywhere I believe, but males seem to get the |
Thanks @fpbarthel As I probably mentioned in this issue, earlier, the table of states went down with the original website. TitanCNA is usually run with The chromosome X correction is a new addition and like many other things, I haven't had time to provide documentation. The idea with using NEUT by default for chrX is that it is neutral relative to the matched normal. Yes, there is only 1 copy originally, and any copy number changes in the signal should be scaled by half compared to autosomes (which originated with 2 copies). It's a subtle detail but I had to deal with this when analyzing prostate cancer data, so I thought I'd include it into the TitanCNA post-processing. I just hope that it makes sense. Again for the actual formulation where this idea of using a baseline of 1 copy for chrX in males will lead to a scaling of 1/2, see the writeup here: |
Thank you for the clarification! |
In ploidy 3 or more cases, I am seeing GAIN or ASCNA calls (not exceeding corrected copy of 4) in regions where canonical tumor suppressor like CDKN2A, PTEN are located. While other cases have expected HOMD and DLOH calls for these genes, I believe there is a possibility for GAIN/ASCNA regions to have an actual state of a deletion of one or more allele following whole genome duplication event. Comments? I did enrichment analysis to test whether CDKN2A GAIN calls are in ploidy2 vs ploidy3 cases vs CDKN2A HOMD/DLOH calls (equally present in ploidy2 vs 3 cases). While is 18/19 GAIN calls (CN < 4) are in ploidy3 cases, I think I am missing something here because the way TITANCNA selects optimal solution, if a case had majority of GAIN (2+1) calls, it should fall under ploidy3 solution, and perhaps I need a different way to test significance, if any. |
Hi @sbamin If regions are first deleted and then genome doubled, then (hopefully) the prediction is copy neutral LOH (NLOH) or amplified LOH (ALOH). The tumor ploidy parameter represents, in practice, the average tumor copy number across the genome. So your interpretation is correct. I am less clear what your question is. Do you have examples of plots that can help to illustrate it? Thanks, |
Thanks Gavin, Indeed and early CDKN2A loss have LOH or NLOH for most cases. So, TitanCNA is calling it correctly. For CDKN2A calls with GAIN/ASCNA state, I am labelling them as late events if I've reasonable confidence for WGD based on TitanCNA major:minor CN of >5:<1, ploidy of >4, and segmental logR copy number of > 2 on at least 50% of of at least half of canonical chromosomes (last one is based on https://www.biorxiv.org/content/10.1101/415133v2). Ad-hoc rules for now and open for comments. Samir |
As the subject says, having to hunt a supplementary table in a manuscript to see what an abbreviation indicates is awkward (and, IIRC, there is no "supplementary table 2" in the TitanCNA paper).
Ideally this should be in the README.md or in the repo (or in the help files).
The text was updated successfully, but these errors were encountered: