Closed stevekm closed 3 years ago
@stevekm How would IGV know what reference you intended to use? Secondly, the wrong reference should not give you those messages. Actually maybe the first one, the other 2 are not actual errors.
I am not sure but it would be helpful to know when creating the report that my input is going to break IGV. Especially since broken IGV in the web browser does not produce a readily visible error message like the command line would, I never would have know what was going on if I did not know to check the browser console. Maybe its outside the scope of igv-reports
I'll close this since it sounds like something outside the scope of igv-reports
I'm reopening to see if I can reproduce that first error. There is no way to know what reference genome you intend, but you shouldn't get an error. I suspect the igv.js version embedded here is out of date.
I'm closing this, I can't reproduce the error using your command line with an hg19 fasta, specifically I tried
create_report examples/variants/variants.vcf.gz https://s3.amazonaws.com/igv.broadinstitute.org/genomes/seq/hg19/hg19.fasta --ideogram examples/variants/cytoBandIdeo.txt --flanking 1000 --info-columns GENE TISSUE TUMOR COSMIC_ID GENE SOMATIC --tracks examples/variants/variants.vcf.gz examples/variants/recalibrated.bam examples/variants/refGene.sort.bed.gz --output igvjs_viewer.hg19.html
Its possible this was due to out-of-date code in the previous pypi release.
Just spent a lot of time trying to debug why the output html reports were not working, getting errors like this in the Firefox web console;
with the variant table showing but the IGV browser not showing up
Turns out its because I was using hg19 instead of hg38;
Would have been really nice to have gotten an error about this from
create_report
instead of having to debug it inside the web browser after loading the HTML report output. Is that possible?