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

About the workflow of "Create PanGenie-ready VCF from Minigraph-Cactus VCF" #2

Open
JhinAir opened this issue Dec 2, 2024 · 2 comments

Comments

@JhinAir
Copy link

JhinAir commented Dec 2, 2024

Dear Dr. Ebler,

when I ran the pipeline using the human hprc-v1.1 MC_graph VCF (hprc-v1.1-mc-chm13.vcfbub.a100k.wave.vcf.gz) and GFA (hprc-v1.1-mc-chm13.gfa), I encountered an exception during the 'annotate_vcf' step, with the error message: "assert nr_alleles > 1". I have attached both the log file, error file and config file for your reference.
Do you have any insights on what might be causing this error? Thank you very much.

Best regards,
Jing Liu
issue.zip

@eblerjana
Copy link
Owner

Hi,

This pipeline only works for VCFs representing graph bubbles as produced by Minigraph-Cactus using the --vcf option. The VCF you are using was decomposed already using an alternative decomposition approach based on vcfwave (which is not compatible with PanGenie). If you want to use the HPRC data, follow the following steps:

  1. Get the raw Minigraph-Cactus HPRC VCF: https://s3-us-west-2.amazonaws.com/human-pangenomics/pangenomes/freeze/freeze1/minigraph-cactus/hprc-v1.1-mc-chm13/hprc-v1.1-mc-chm13.raw.vcf.gz
  2. Run vcfbub to remove non-top level bubbles: vcfbub -l 0 -r 100000 --input hprc-v1.1-mc-chm13.raw.vcf.gz | bgzip > mc.vcf.gz && tabix -p vcf mc.vcf.gz
  3. Use the resulting VCF (mc.vcf.gz) as input to this pipeline.

Note that for newer versions of Minigraph-Cactus, the vcf produced with --vcf is already processed with vcfbub. These VCF can thus be directly used with this pipeline (no need to run the command shown in step 2). VCFs produced with MC's --vcfwave option (as the one you have) are not compatible.

@JhinAir
Copy link
Author

JhinAir commented Dec 4, 2024

I see. I will retry. Thank you very much for your detailed help!

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