Skip to content
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

PGGB singularity vg deconstruct not recognizing sample prefix #399

Open
SimonaSecomandi opened this issue Jun 7, 2024 · 1 comment
Open

Comments

@SimonaSecomandi
Copy link

SimonaSecomandi commented Jun 7, 2024

Hi all,

I am trying to call variants using the pggb singularity pipeline starting from multiple haplotype-resolved genomes. I used PanSN-spec naming and it all worked well until I had to chose the reference for graph decomposition.

My path names are similar to these:

ind1#1#chr1
ind1#2#chr1
ind2#1#chr1
ind2#2#chr1
...
ind10#1#chr1
ind10#2#chr1

I would like to deconstruct the graph using ind1#1 as a reference, since it's the most complete genome and I used it for linear short-read mapping.

However, when choosing a reference in pggb singularity (pggb 87510bc):

  • if I specify -V 'ind1#', -V 'ind1#1' or -V 'ind1#1#' the prefix is not recognized
  • if I specify -V 'ind1', vg deconstruct works but calls the variants against both haplotypes of ind1 and ind10 because they both start with 1

The command used in the pggb runs is:
vg deconstruct -P ind1#2# -H # -e -a -t 32 chr1.smooth.final.gfa
and this is an example error:

[vg::deconstruct] making VCF with reference=ind1#1# and delim=# xxxxxxxxxxxxx ind1#1# ------------ 0
Error [vg deconstruct]: No specified reference path or prefix found in graph

I can successfully run vg deconstruct using ind1#1 as a ref if I do it after pggb graph construction, removing -H #:
vg deconstruct -P ind1#1 -e -a -t 32 ch1.smooth.final.gfa.

Do you have any recommendation on how to specify the haplotype/sample I want to call the variants against to directly in pggb?

Many thanks!

Simona

@AndreaGuarracino
Copy link
Member

@SimonaSecomandi would you please try again with the newest image? I've updated several components, including the latest vg 1.59.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants