-
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
Normal_contamination_estimate #64
Comments
Hi @udp3f Are you able to show a plot of one of the chromosomes so that we can see what might be happening. Thanks, |
Hi Gavin, Above is a chr10 plot for ploidy=2, cluster 1 for which normal contamination was 0.99 -Uma |
Hi @udp3f The quality of the data seems really good and might not be the problem. Do you see this type of result for the rest of the chromosomes? If so, then perhaps the normal contamination estimate of 0.99 is actually reasonable? -Gavin |
Hi @udp3f What are the estimates for the run with initializations of ploidy=2 and number of clusters of 1 (cluster01)? This might be an issue with the optimal solution selection. -Gavin |
It is 0.99 for ploidy=2, cluster01 (for fixed cluster size =1) & |
Something funny is going on. It must be a bug. Would it be possible for you to share the Thanks, |
I mailed you the RData. |
I am facing a similar issue, were there any insights from this example? I have 3 cases where titan selects a very low purity solution. However, VAFs suggest a higher purity. |
This one has a KRAS mutation with AF=0.3 Estimated purity from titan in this case, is 2.5%, however, by including CNV+SSM in phylowgs the purity comes out to be 70%.
|
Hi,
I am running the snakemake pipeline for TitanCNA for tumor/normals, where my maxploidy is set for 2 (that is what we believe of our sample) and I am doing different cluster initializations. I am a bit perplexed with the normal_contamination estimate I get for ploidy2 state where the params file outputs 0.99 as the normal contamination for any fixed cluster solution, which means 0.01 is the tumor purity. The same sample when run with a max ploidy of 3 gives 0.23 as the normal contamination for cluster 1, which seems pretty close to what we expect to see. I am not sure what this difference means. If I stick to ploidy state 2 which we believe our sample is, for different cluster solutions, my tumor purity is only 1% which we can not go with. Could you please explain what this might mean.
The text was updated successfully, but these errors were encountered: