-
Notifications
You must be signed in to change notification settings - Fork 21
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
Error when sequence ID is too long #53
Comments
Traceback (most recent call last): |
I have also encountered this issue, but I have hundreds of gbk files to process, so is there any way to batch shorten the IDs in the files |
I met the same issue. Any clues on this? |
Can you point me to a file where this issue occurs so that I can fix it? |
Hi, I also had this issue. I initially tried to add the whitespace manually but that didn't work. My genbank files were annotated in PROKKA. Re-annotating using the --compliant flag for PROKKA fixed the issue for me as it parses the locus line in a different way. |
@linsalrob @qianxin-kxy @jcmckerral thank you and the easy way would be to do this before running:
|
@ShanlinKe @TSZUoE see my response in this thread above. if you have the C++ code, pointer declaration snippet, paste here, will do the convertible for the same
Thank you |
There is a small issue where one of the biopython functions has a character length limit on sequence IDs, a more informative error message might be useful. A fasta ID
results in a genbank file which will give a PhiSpy traceback/error
Changing the ID to
resolves the problem.
The text was updated successfully, but these errors were encountered: