Use giraffe in vg
I am trying to run "vg autoindex --workflow giraffe" and get the reply: "giraffe indexing not yet implemented" Why?
giraffe
vg
• 2,296 views
•
link
updated
by
Jordan M Eizenga •
•
written
by
Michal •
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
What does vg autoindex mpmap do?
written by Ziyue •I tried to run vg autoindex --workflow mpmap using GRCh38, GENCODE 47, with hprc decomposed VCF. I renamed the names of chr in VCF to …
-
Query Regarding Missing Sample Paths in Graph-Based Pangenome Construction
written by s_135 •I constructed a graph-based pangenome using a reference FASTA file and a VCF file containing 150 individuals. I used the vg autoindex command with the …
-
How to parallelize running vg autoindex to create graph references from VCFs with vg?
written by Ricky •Hi, I'm running `vg autoindex --workflow giraffe` to try to create a graph reference using a VCF of variants I have that I later want …
-
Distance index computation during `vg --autoindex` takes too long with one GFA file but not with th…
written by Harsh •I have two GFA files representing the same dataset. I am trying to map reads to these two files using Giraffe. One of them is …
-
using vg on DNA-nexus platform
written by Michal •I have data stored on the DNA-Nexus cloud service and I would like to utilize the vg tool, particularly the giraffe alignment tool, with this …
-
vg: Mapping fewer reads to a genome graph than a linear reference
written by John Lloyd •I am seeing a 5-10% reduction in reads mapped to a genome graph compared to a linear reference of the same genome sequence. I have …
-
vg tools is running, but memory consumption is not happened and log files are not updated
written by dragon940401 •Hi there, I use vg tools for giraffe mapping. I started vg tools 2022.01.13 and now(2022.01.17). vg makes log files : chunked fasta, chunked vcf …
-
vg tools, I ran vg autoindex -w giraffe and use splited vcf file (multi vcf file) then index regist…
written by dragon940401 •Hi! First, Thanks to your help! I ran vg tools for mapping vcf that was splited I choose mapping algorithm giraffe First, I ran vg …
-
Creating a variation graph for Giraffe alignment from assemblies
written by Michael •I have a collection of ~100 4.5 megabase haploid assemblies that I would like to map to using giraffe. However, I am not completely clear …
-
How to run vg giraffe for sv genotyping?
written by brentpI have seen this: https://github.com/vgteam/vg/wiki/Automatic-indexing-for-read-mapping-and-downstream-inference This thread: https://github.com/vgteam/vg/issues/3316 seems to be the most comprehensive trail of documentation on how to run, but that seems impossibly …
What version of vg are you using? They have that exact line in their documentation so I think it might be an older version you are using. Also I just noticed that your tags has a typo (vg. insteead of just vg), could you (or a person with the right permissions) change it so that it might catch the eye of the devs? :)
my version is: vg version v1.30.0 "Carentino" Is it an old one? (I downloaded it last week...) How can I upadate my version?
Yeah, that's over 2 years old. The current version can be downloaded from the GitHub page: https://github.com/vgteam/vg/releases
I downloaded the new version (vg-v1.49.0) and I can see the folder in my directory but the vg command still work with the old version (when I ask the version I get 1.3.00.0 and when I try to use giraffe I get the response that giraffe is not yet implemented). How can I activate the new version?
My guess is that this is an issue with your Unix path. You can try
which vgto check the location of thevgbinary that's being picked up. I'd recommend deleting the old version.You can also check the commands from this issue for comparison in addition to biofalconch's suggestion: vg tools, I ran vg autoindex -w giraffe and use splited vcf file (multi vcf file) then index registry error is happened
Updating the VG version should resolve this. Giraffe autoindexing has been implemented since February of 2021.