Closed MarionPerrier closed 4 months ago
As is, vg autoindex
expects at least one of the GTFs to be provided as a "reference GTF" (-x) rather than a "haplotype GTF" (-H). It wouldn't be too hard to relax this restriction, but designating one as a reference might be enough to unblock you on the insufficient input error.
On the "Could not open GFA" error, that typically occurs when there's a typo in the file path, a missing file, or a permissions issue for the file. It looks to me like this error was thrown the first time vg
tried to access any file. Perhaps your docker has some issues with its file mounts?
Oh ok! Makes sense 😅. It works very smoothly now. Thank you!
1. What were you trying to do? I was trying to use
vg autoindex
to index my pangenome graph for mpmap and rpvg. I have build the pangenome using PGGB on the pangenome pipeline of nf-core.2. What did you want to happen? A full completion of the program
3. What actually happened?
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:NA
5. What data and command can the vg dev team use to make the problem happen? Here is my command:
6. What does running
vg version
say?I am running vg on a HPC (slurm) directly in command line from a node. VG has been installed with conda. When I use the docker image, the error message is always the same:
error:[IndexRegistry] Could not open GFA file ../nf_pangenome_results/results4/smoothxg/final_v1.1.gfa