Skip to content
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

tumor purity estimate is NA #66

Closed
trptyrphe11 opened this issue Dec 7, 2017 · 22 comments
Closed

tumor purity estimate is NA #66

trptyrphe11 opened this issue Dec 7, 2017 · 22 comments

Comments

@trptyrphe11
Copy link

Hi,

I have successfully run FACETS on several samples. However for my latest sample, I got tumor purity estimate is NA.

[1] "tumor purity estimated:NA"
[1] "tumor ploidy estimated:2"

I inspected that I have enough het loc, so don't know what's the reason. Thanks.

sum(oo$jointseg$het): 28816
nrow(oo$jointseg): 283433

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

Purity is NA because there is no copy number change in the sample. Have you looked at the plot?

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

NO. It can be anything from 0 to 100%. If the "tumor" didn't have any tumor cells at all then there will be no copy number change and the purity is zero. On the other hand if the tumor is driven purely by mutation or epigenetics then there won't be any copy number change and the purity can be any number.

@trptyrphe11
Copy link
Author

trptyrphe11 commented Dec 7, 2017

Yes there is no copy number change. But I have also seen cases with purity estimate when ploidy = 2.018...
Anyway, does that mean I will not get tumor purity estimate when ploidy = 2 using FACETS? Thanks.

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

Ploidy is just the average copy number. If there is a 1 copy loss spanning 50 megabases in one chromosome and an offsetting 1 copy gain of 50 megabases in a different chromosome then ploidy will be 2 and purity will be estimable. That is not the case when there is no change.

@trptyrphe11
Copy link
Author

Thanks for the explanation. So when there's not copy number changes, can FACETS using other metrics (BAF, etc) to estimate purity?

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

FACETS only deals with het SNPs present in the normal. So BAF won't help. If there are mutations you can use that to estimate purity.

@trptyrphe11
Copy link
Author

Sorry can you elaborate on "If there are mutations you can use that to estimate purity."? And do you mean using FACETS or develop my own way? Thanks.

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

Generate a MAF file using a mutation pipeline (say mutect). Then the mutant allele frequency of calls with high confidence will be an estimate of 0.5*purity since most mutations happen in only one chromosome and no copy number change means copy number is 2 everywhere. More reliable if the depth at the mutant location is high.

@trptyrphe11
Copy link
Author

But if the mutation is subclonal, how can that be used to accurately estimate the purity?

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

Then purity cannot be estimated with available data.

@trptyrphe11
Copy link
Author

Makes sense. Thanks. BTW, just want to confirm I provided the right vcf file in the first snp-pileup step: I use the vcf file generated from the tumor sample only (initially I tried to use somatic.vcf but with very few het loci FACETS couldn't proceed correctly):
snp-pileup tumor_dna.vcf normal.sorted.bam tumor.sorted.bam

Does the approach look correct to you? Thanks.

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

That is the wrong vcf to use. You need a vcf from dbsnp or 1000 genome. FACETS needs the locations of known polymorphic loci in the population.

@trptyrphe11
Copy link
Author

So you mean the vcf only serves to define known polymorphic loci in a population instead of the patient specific polymorphic loci (aka, for different tumor/normal paired sequencing, I can reuse this ONE vcf for snp-pileup)? If so, can you provide a link for such vcf? Thanks.

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

The dbSnp files are here ftp://ftp.ncbi.nlm.nih.gov/snp/organisms/human_9606/VCF/

@trptyrphe11
Copy link
Author

That's very helpful, and I guess I should use common_all (MAF >= 0.01) version for FACETS?

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

Yes.

@trptyrphe11
Copy link
Author

Thanks. Now thinking back, I am wondering why FACETS needs a population-based polymorphic site file instead of the patient's own germline polymorphic file (aka a vcf called from normal.bam)? Would the latter be more accurate?

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

This question is beyond the scope of this forum in which issues regarding the software are discussed not the methodology.

@veseshan veseshan closed this as completed Dec 7, 2017
@trptyrphe11
Copy link
Author

Thanks. I downloaded the common_all vcf from the ftp portal, however by loose counting the unique positions in the file, there's 37M lines instead of ~1.9M that's mentioned in the tutorial or paper. Anything I missed here?

@veseshan
Copy link
Collaborator

veseshan commented Dec 7, 2017

1.9 million are ones that fall within WES targets. The VCF file has lot more. Phase 3 release of 1000 genomes for instance has ~80 million.

@trptyrphe11
Copy link
Author

That makes more sense now. Thank you for your quick reply, Dr!

@lidd77
Copy link

lidd77 commented Jun 25, 2019

Hi,

I have successfully run FACETS on several samples. However for my latest sample, I got tumor purity estimate is NA.

[1] "tumor purity estimated:NA"
[1] "tumor ploidy estimated:2"

I inspected that I have enough het loc, so don't know what's the reason. Thanks.

sum(oo$jointseg$het): 28816
nrow(oo$jointseg): 283433

@trptyrphe11
Could you share your FACES command lines ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants