Closed LeoVincenzi closed 12 months ago
hi, are you using the pal2nal script outside of phame or is this happening within a phame run?
Hi @mshakya. I was using pal2nal.pl itself, outside of the phem pipeline.
Hi @LeoVincenzi and @mshakya,
I have exactly the same error. In my case, first, I used translatorX to to get the aminoacid and nucleotide alignment from the same nt sequences, so how can be posible to have so many inconsistencies like this?
"#--- ERROR: inconsistency between the following pep and nuc seqs ---#".
Thanks in advance for any help or suggestion.
Hi, we dont maintain a separate version of pal2nal and i dont think that tool has been supported for a long time. So, i am not exactly sure how can this be resolved. We had been thinking of replacing pal2nal with something else, but havent had a time to find the right tool. I am going to close the issue for now as it falls outside of phame, but will keep in mind for next iteration of phame.
In my case, it is because my protein sequence used for MSA contains an in-frame stop which will be resolved as a gap in the MSA output, which will be then ignored by pal2nal analysis and finally cause the inconsistency between lengths of protein sequence and coding sequence. I replaced the inframe stop (*) to 'X' and succed, hope it helps!
Dear developers, I am writing you about an error obtained converting a .aln file of a multiple protein alignment (4 species) to the correspondent nucleotide sequence. The error is the following:
It seems no conversion happened. I do not completely understand the problem and how to solve it. I have seen it is a common error on web, but I haven't found any clear solution about it. Thank in advance for your help. Leo