-
Notifications
You must be signed in to change notification settings - Fork 23
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
MAFFT error when running ppanggolin MSA #210
Comments
Hi, Thank you for your issue, there is definitely an error reporting from ppanggolin on that specific case that we can improve. To find out what is happening, ideally I'd run this command again and check the content of "/tmp/tmp8ye30tt_/BLONNJ_19495.fasta", and rerun mafft on it outside of PPanGGOLiN, but I don't remember if it's easy to keep the tmp files as I have not used "msa" in a while now. I assume there is something odd with this family, BLONNJ_19495. Is there something different or strange about it ?
Adelme |
Hi, so I ended up removing the genome that had 'BLONNJ_19495' and tried running it again. Unfortunately I overwrote the old results, but got the exact same error, this time for a different ID, 'ELALCC_40030'. So I'll answer your questions based on this last run, since it should point to the same issue. I can't access ELALCC_40030.fasta directly since it ran in a tmp directory under a docker container, but I can give you the gff3 file it came from (It's in contig 76, see below).
|
Alright I see, thank you. Maybe the fact that it's the only non-fragment member of the family is linked to the problem? |
Hi, I did not manage to reproduce this problem using our testing dataset, nor with a real dataset I was working on, nor using the genome you uploaded. Would it be possible for you to share a (possibly small-ish) "pangenome.h5" file that resulted in a problem like this? Adelme |
Just in case, if you have no means of sharing your pangenome.h5 file, if you share with us your email address someone from the ppanggolin dev team can provide you with a link where you can upload the file. |
Sorry for such a late reply, but here is the pangenome.h5 file that is failing in the way I described above. Unfortunately it's not that small (~3GB). I'll see if I can create a smaller one that returns this same error. |
Hi After some testing I managed something that looks like your error... accidently. For me, it was actually unrelated to ppanggolin directly but linked to a lack of permission to the TMPDIR of the system in which you are executing PPanGGOLIN. When mafft tries to access it, it fails and this makes it crash. The error given for me was the same as this one: https://forum.qiime2.org/t/plugin-error-from-phylogeny/19519 This was however impossible to guess with the way ppanggolin prints out the mafft stderr. The PR linked to this issue improves this. Adelme |
I see! Thank you so much for your patience. I managed to fix the issue on my side as well after changing the TMPDIR singularity was using. |
Hi, after running and creating the pangenome file with this command, for about ~1600 GFFs:
I started running the MSA command:
But I'm always getting this MAFFT error:
I couldn't figure out why as I can't access the mafft error directly so I'm kind of out of ideas at the moment. I had managed to run both of these commands previously on a smaller subset of this dataset (~200 gffs). I'm using the PPanGGOLIN docker image from biocontainers, in case that's relevant.
Thanks!
The text was updated successfully, but these errors were encountered: