Created
April 7, 2016 15:25
-
-
Save willgdjones/8a3b2ac59a645d4c033a4f0abb22728a to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
./vg construct -r /lustre/scratch113/projects/graphs/yeast/data/SGD_2010.fasta \ | |
-v /lustre/scratch113/projects/graphs/yeast/data/SGRP2-cerevisiae-freebayes-snps-Q30-GQ30.vcf.gz \ | |
-m 1000 -a > output/yeastgraph.vg\ | |
./vg mod -pl 16 -e 3 output/yeastgraph.vg \ | |
| ./vg mod -S -l 32 - \ | |
| ./vg kmers -gB -k 16 -F -H 1000000000 -T 1000000001 - \ | |
> output/yeastgraph.graph / |
There is a hack here that works. Strip the paths.
vg-81b5a2cb mod -D yeast1.vg | vg-81b5a2cb mod -pl 16 -e 3 - >yeast1.modl16e3.vg
This completes pretty quickly. I'm going to try the last parts of the process and see how it goes.
Something is very wrong with the path manipulation. @adamnovak has reported it I think, but I'm not finding the documentation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This gets stuck in a weird place. In rebuild_mapping_aux.
To reproduce (assume we've built our graph into yeast1.vg):
Let it run for a while (10 minutes), now control+c and
bt
(backtrace) should show us what's happening:So one solution may be to remove the paths from the graph before pruning. They are irrelevant for this process.
But this should not be happening, anyway. So thanks @willgdjones for the catch.