Open GeorgeBGM opened 1 year ago
It looks to me like those are warnings, not errors, so they shouldn't have caused VG to crash. However, the fact that your GFA has duplicate paths is a cause for concern. You might want to look into the pipeline that's creating the GFA to figure out why it's adding multiple paths with the same name.
You're running out of memory. You're best to use the xg and gbz released alongside that gfa file in order to use vg.
If you really want to convert that graph into a .vg
file (for editing?) then you can try
vg convert -f hprc-v1.0-mc-grch38.gfa > hprc-v1.0-mc-grch38.vg
Or if that takes too much memory (but this will drop haplotypes)
vg convert -f hprc-v1.0-mc-grch38.gfa -H > hprc-v1.0-mc-grch38.vg
vg view --vg
converts the graph to vg Protobuf, which is deprecated, and should be avoided. We should deprecate this option.
Thanks for your reply.
Yes, I need to use vg tools to further complete the downstream analysis (vg mpmap;vg augment;vg deconstruct) and the gfa file cannot be imported directly. I am curious how much memory will be consumed to complete the process and if 1T of memory is enough to complete the gfa into a .vg file in the HPRC project.
At 2023-06-08 04:04:17, "Glenn Hickey" @.***> wrote:
You're running out of memory. You're best to use the xg and gbz released alongside that gfa file in order to use vg.
If you really want to convert that graph into a .vg file (for editing?) then you can try
vg convert -f hprc-v1.0-mc-grch38.gfa > hprc-v1.0-mc-grch38.vg
Or if that takes too much memory (but this will drop haplotypes)
vg convert -f hprc-v1.0-mc-grch38.gfa -H > hprc-v1.0-mc-grch38.vg
vg view --vg converts the graph to vg Protobuf, which is deprecated, and should be avoided. We should deprecate this option.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
By the way, is it possible to use multiple CPUs in collaboration or through GPUs to complete the process.
At 2023-06-08 10:22:06, "杜多" @.***> wrote:
Thanks for your reply.
Yes, I need to use vg tools to further complete the downstream analysis (vg mpmap;vg augment;vg deconstruct) and the gfa file cannot be imported directly. I am curious how much memory will be consumed to complete the process and if 1T of memory is enough to complete the gfa into a .vg file in the HPRC project.
At 2023-06-08 04:04:17, "Glenn Hickey" @.***> wrote:
You're running out of memory. You're best to use the xg and gbz released alongside that gfa file in order to use vg.
If you really want to convert that graph into a .vg file (for editing?) then you can try
vg convert -f hprc-v1.0-mc-grch38.gfa > hprc-v1.0-mc-grch38.vg
Or if that takes too much memory (but this will drop haplotypes)
vg convert -f hprc-v1.0-mc-grch38.gfa -H > hprc-v1.0-mc-grch38.vg
vg view --vg converts the graph to vg Protobuf, which is deprecated, and should be avoided. We should deprecate this option.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Hi, I'm using version v1.48.0 of vg and I noticed that the -f parameter refers to output as GFA format, so I'm a bit confused about that command (vg convert -f hprc-v1.0-mc-grch38.gfa > hprc-v1.0-mc-grch38.vg). I used 1T of CPU memory to convert the GFA file into a vg format that VG can recognize, but it still got a similar error. I'm curious if I can split the GFA based on chromosomes first, then finish the GFA file and VG file conversion by chromosomes, and then eventually merge them together.So how to split the GFA file by chromosomes?Are other suggestions on this issue?Thanks!
I think it should be -g
instead of -f
1. What were you trying to do?
2. What did you want to happen?
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:5. What data and command can the vg dev team use to make the problem happen?
6. What does running
vg version
say?