Closed cademirch closed 3 years ago
Is it possible to share the data you were using when you ran into this bug?
Is it possible to share the data you were using when you ran into this bug?
I made a small version of my data to share, but could not recreate the error with this data.
I am running the command on my full dataset again to see if I can recreate the error and will report back. Regardless, I can share the full VCF (33gigs) and reference if you'd like.
Also, for the unsupported allele warning, is there any way to include those variants in construction?
@jeizenga Autoindex failed again with the same error on my full dataset. I can share it with you, could you give me your email? I'll email you a link to where the data is hosted.
Sure. You can reach me at joeizeng@gmail.com.
@cademirch This should be fixed now in the main branch. Let me know if you have any more issues with it.
1. What were you trying to do? Use autoindex to produce indexes for mapping.
2. What did you want to happen? Produce indexes for mapping.
3. What actually happened? Many warnings about unsupported allele "*", then error regarding no phasings - though the VCF does contain phasing info. Stderr from autoindex:
4. If you got a line like
Stack trace path: /somewhere/on/your/computer/stacktrace.txt
, please copy-paste the contents of that file here:5. What data and command can the vg dev team use to make the problem happen? The VCF is rather large, I can supply a small version.
vg autoindex -w map -r ref.fa -v vars.vcf.gz -T ./tmp -M 120000
6. What does running
vg version
say?