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

toil-vg call throws XGFormatError: Unimplemented XG format version: 0 #759

Open
alancleary opened this issue Aug 27, 2019 · 4 comments
Open

Comments

@alancleary
Copy link

I have a graph that was built with Seqwish and augmented with reads mapped with GraphAligner. I used vg version 1.16.0 to build an xg for the augmented graph

vg index -x graph.aug.xg graph.aug.vg

I then used toil-vg with Singularity (which used vg version 1.11.0) to call variants

toil-vg call \
        --config config_wg.yaml \
        --realTimeLogging --logInfo --realTimeStderr \
        --workDir /workdir \
        /jobstore \
        graph.aug.xg \
        sample \
        /outstore \
        --gams reads.gam \
        --chroms 1

This resulted in an XGFormatError

Unimplemented XG format version: 0

Is this because I'm using a different version of vg than toil-vg, or could it be something else? Just looking for guidance on debugging really. Unfortunately, I can't share my data, but let me know if there's anything else I can tell you that would help. Much thanks!

@adamnovak
Copy link
Member

adamnovak commented Aug 27, 2019 via email

@alancleary
Copy link
Author

Thanks for the quick reply, @adamnovak.

I installed toil-vg via pip. Looking at the package on PyPi, it apparently hasn't been updated since Nov 3, 2018. I was using the whole genome config file that toil-vg can generate which I now see is hard-coded to vg version 1.11.0 in this older version.

I'll just pull the master branch (which I see is hard-coded to use vg version 1.16.0) and build it locally.

Cheers!

@adamnovak
Copy link
Member

@glennhickey We probably should do a new release. You have some changes to make for the new vg call; should we make a PyPI release after that?

@glennhickey
Copy link
Collaborator

glennhickey commented Aug 28, 2019 via email

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