-
Notifications
You must be signed in to change notification settings - Fork 45
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
Running error with Singularity image #422
Comments
We should probably update the README and/or the input datasets. Currently, A lazy way to fix the error and keep the VCF in output is to just hack sequence names in zcat DRB1-3123.fa.gz | sed 's/:/#1#/g' > DRB1-3123.pansn.fa and run |
Thanks for the fast response! I tried both ways, which gave me same error: I also tried the solutions in #291 and #404, all ended up with showing same error info. As the suggestions from these two notes, I tried below commands: I am running on HPC, so I don't have docker access to run pggb with docker commands. Thanks, |
Many thanks! |
Hello, thanks for the great work!
I am trying to run PGGB with Singularity image, and I strictly followed the example commands line as below:
Pull the docker file:
git clone --recursive https://github.com/pangenome/pggb.git
clone the repo and cd:
git clone --recursive https://github.com/pangenome/pggb.git
cd pggb
run pggb:
singularity run -B ${PWD}/data:/data ../pggb_latest.sif pggb -i /data/HLA/DRB1-3123.fa.gz -p 70 -s 3000 -n 10 -t 16 -V 'gi|568815561' -o /data/out
which gives me:
[pggb] warning: there are sequence names (like 'gi|568815592:32578768-32589835') that do not match the Pangenome Sequence Naming (PanSN).
[pggb] ERROR: -V/--vcf-spec cannot be used if the Pangenome Sequence Naming (PanSN) is not respected.
I did checked the solution in issue#388, I am little confused, do I have to installed all other components individually (wfmash, seqwish...) and pull the docker image at the same time? is there anything I did wrong?
FYI, I did:
./pggb --version
pggb v0.7.2-0-g0e9c9e1
Thanks for the help!
-S.
The text was updated successfully, but these errors were encountered: