-
Notifications
You must be signed in to change notification settings - Fork 20
Sequence contains no elements? #97
Comments
your error is likely different than in issue #86. The first error you are seeing I think is because of mismatched chromosome names in the small variant vcf and the reference genome fasta? The second error you are seeing is likely a problem with the data, either noisiness in the read coverage resulting in no usable segments. Essentially Canvas cannot fit a purity/ploidy model. What is the coverage of the WGS sample? Which sequencer was used? We recommend at least 40x coverage for T/N WGS |
Hi Eric! Thank you for the response. We are using the "b37" -version of hg19 (https://wiki.dnanexus.com/scientific-notes/human-genome)
But it's still throwing the "Sequence contains no elements" error. I also tried trimming down the --sample-b-allele-vcf file to contain just 10 or so SNVs but same error. Is there something hardcoded that looks for "chr" in the chromosome names? Our WGS samples are 60x tumour 30x normal. I think the machine used for this is HiSeq X-Ten. Not exactly sure but its one of the Hi-Seq machines. Do you mean that the coverage for tumour should be 40x or above or both the tumour and normal? Thanks again! |
The file you are passing for --sample-b-allele-vcf is named LCH16_normal_SVs.vcf. Are these structural variants? They need to be SNVs in the normal sample from a small variant caller, preferably strelka. We recommend 40x normal and 80x tumor, but the analysis should still work with 30x normal /60x tumor. |
Thanks for the rapid response! Yes, initially that vcf also contained indels and SVs along with SNVs, but we removed all non-SNV variants from this file and Canvas crashed with the same "Sequence contains no elements" message. We are using the Sentieon DNAscope software to call the variants, which is outputting VCFv4.2. I have so far not been able to get Somatic-WGS running with any vcf file. Germline-WGS, I have gotten to work using the dbsnp vcf- Below are some of my results:
My only remaining idea is that my vcf is incorrectly formatted for Canvas somehow, as the dbsnp vcf either results in other error or works. Is there some limit on the number of fields allowed in the input vcf? Could trying some vcf version downgrade tool (4.2 -> 4.0) work? In case none of that would work, my backup would be to use dbsnp for all samples. In that case, I'm curious as to why the Germline WGS works fine with a 30x normal bam but Somatic fails to fit a purity/ploidy model using the 60x and 90x tumor bam? I have also tried Running v1.11.0 on the same bam and vcf which
Using dbsnp as the vcf did produce good output, however. How big are the improvements of going to a newer version like 1.38.0.1554 versus 1.11.0? I have also noted that you've updated Canvas to version 1.39.0.1598. Could upgrading to this version possibly ameliorate the issue? The notes merely mention an issue with multiple samples. Any ideas would be helpful. Thanks! |
Can you show me the stack trace for this scenario: Tried Germline-WGS with --sample-b-allele-vcf=sentieon normal SNV-only vcf. Sequence contains no elements. I want to compare it to the Somatic-WGS case. The problem with the Somatic-WGS case is definitely a problem with the SNVs. I don't think vcf spec 4.2 vs 4.1 would cause a problem. 1.38.0.1554 is substantially different than 1.11.0 and should give superior performance. 1.39.0.1598 won't give any different for single sample analysis compared to 1.38.0.1554. If you could share an example SNV entry in the vcf that could also help troubleshoot. |
Thanks again for the quick response. I reran the following command:
Which resulted in the following stacktrace:
I will also attach a truncated version of the normal vcf I used: LCH16_normal_SNVonly_truncated.zip Thanks again Eric! |
Germline-WGS is deprecated. Can you try running SmallPedigree-WGS? It supports single sample analysis. |
I think the problem might be the FILTER column. It is "." and we are using only PASS variants. Try changing them to PASS. |
Hi Eric! I modified the vcf to use only PASS in the FILTER- column. After initially having some issues with dependencies for bedGraphToBigWig (libpng12.so.0), I got this command to run through:
I also got the command for Somatic-WGS to work:
So it seems like the FILTER column was the issue. I did consider this when I looked at the help output saying "vcf containing SNV b-allele sites in the sample (only sites with PASS in the filter column will be used) (either this option or option population-b-allele-vcf is required)". I disregarded it though, since dbsnp and my vcf both had "." and crashed with different error outputs. Thanks a lot for the help Eric, very nice to have it working again! |
Interesting, I did not realize bedGraphToBigWig required libpng12. That should probably be statically linked! |
I too had libpng12 missing error. We have an updated version, libpng16. I ended up replacing canvas bedGraphToBigWig with an updated binary from Kent utilities, mkdir -p /os7apps/kent
rsync -azvP rsync://hgdownload.soe.ucsc.edu/genome/admin/exe/linux.x86_64/ /os7apps/kent/ |
Hi!
Running rhel7, we are having issues getting Canvas Somatic-WGS for version 1.38.0.1554 working with our whole genome samples:
The error I’m getting is:
This error seems to happen when I am using vcf-files versioned 4.2 or 4.1 for the --sample-b-allele-vcf input. When using the old dbsnp_common_all_20160601.vcf (vcf v4.0) it instead crashed with the following error:
Which I found this person also had an issue with this: #86
Although he was running on PC and using TN-enrichment instead of Somatic-WGS
Do you suggest we stick with the old canvas version 1.11.0 & mono when running canvas on Red Hat instead of trying to get the newer versions using dotnet core running or is there some fix i could try for the new version?
Thankful for any assistance!
The text was updated successfully, but these errors were encountered: