-
Notifications
You must be signed in to change notification settings - Fork 194
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
Error in 'vg autoindex' a GFA file derived from PGGB #3712
Comments
Some big chromosomes work well with 'vg autoindex', but small chromosomes did not work properly, occurring issues above. |
Can you provide the command line call that you ran into this error on? |
Thanks for your reply. Here you go:
vg autoindex --workflow giraffe \
-g $gfa_chr37 -t 23 \
--target-mem 90G
…On Thu, Aug 4, 2022 at 4:16 PM Jordan Eizenga ***@***.***> wrote:
Can you provide the command line call that you ran into this error on?
—
Reply to this email directly, view it on GitHub
<#3712 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQTTOOCEDJMTOBEKTAT5BYTVXQQJFANCNFSM55TXCDCQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
By the way, here is the GFA file I used, which is 52MB, a small chromosome.
Please let me know if the GFA file is wrong or not properly produced.
Thank you!
Bohao Fang
VGP#prim#SUPER_37.pan.fa.gz.3051141.04f1c29.ecb...
<https://drive.google.com/file/d/1nLpGPHSlZs4h1hmfuJHcI3hOyIFIDvXY/view?usp=drive_web>
…On Thu, Aug 4, 2022 at 4:59 PM Bohao Fang ***@***.***> wrote:
Thanks for your reply. Here you go:
vg autoindex --workflow giraffe \
-g $gfa_chr37 -t 23 \
--target-mem 90G
On Thu, Aug 4, 2022 at 4:16 PM Jordan Eizenga ***@***.***>
wrote:
> Can you provide the command line call that you ran into this error on?
>
> —
> Reply to this email directly, view it on GitHub
> <#3712 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AQTTOOCEDJMTOBEKTAT5BYTVXQQJFANCNFSM55TXCDCQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
@adamnovak This looks to me like it's running into a problem in the named-node stuff you implemented. Could you take a look? |
I came across this issue when using panSN-spec named input like
but there is a I couldn't find clear documentation on the pathsense API, but from Best, |
Found the [path metadata model[(https://github.com/vgteam/vg/wiki/Path-Metadata-Model) (I knew I had stumbled on it before), so will try with this a bit further |
Unfortunately I can't get @fangbohao's file; it looks like it's a Google Drive upload shared with a specific list of people that I'm not on. But it does seem like a path like By my reading of the panSN spec that I had when I wrote the path name parsing, that isn't valid panSN because the haplotype piece Whether that's true or not, we should produce a more useful error when we can't parse the path name. |
FWIW, the spec does indeed say here that haplotype ID is a number. |
OK, @fangbohao shared the file with me, and I tested my fix, and I now have vg interpreting it like this:
It's not parsing it as the file writer intended, I don't think, but it is parsing it to something we can represent. For the file to really work properly (and not result in a possibly unmanageable number of named paths), |
1. What were you trying to do?
I am trying to index a GFA graph file (a chromosome) derived from PGGB.
2. What did you want to happen?
index done.
3. What actually happened?
error message appears as above.
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?The text was updated successfully, but these errors were encountered: