Closed glennhickey closed 6 years ago
Hey Glenn,
I could reproduce your problem with the latest version of graphtyper
and vt
. Not sure if the latest vt
version has a new bug or if the latest Graphtyper version is not fully comply-ing with the VCF standard... I will investigate further and let you know.
Hannes
Hey again,
BCFTools does not complain when parsing the failed VCF and an older version of vt also parses the file without any problems, so I am guessing this is a recently introduced issue in vt. For me I was able get it to work using vt git hash version 6686b5c
(full hash: 6686b5c44515743a764568c7c3a29bdf3f5af3fd
). Can you try to git checkout that vt version, re-build it, and then try again running the graphtyper-pipeline tests?
All the best, Hannes
Thanks Hannes! Using that vt got make test working. I think you definitely want to update README.md to reflect this dependency.
Great! Yes, I will happily note this in the README and let the vt guys know about this. Thank you for discovering and reporting this issue!
All the best, Hannes
I get the following when running
make test
(and the same errors when trying to run my own data)As far as I can tell, these errors are coming from vt (see below):
I have the latest graphtyper, graphtyper-pipelines and vt from their respective github masters. graphtyper itself seems to be built correctly and I can run it directly to, say, construct a graph. Are there any version constraints of tools I should be aware of? Do you have an idea what might be behind this error?