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

Some .gbf files don't import well into the genome browser #13

Open
nactopus opened this issue Jul 1, 2024 · 2 comments
Open

Some .gbf files don't import well into the genome browser #13

nactopus opened this issue Jul 1, 2024 · 2 comments

Comments

@nactopus
Copy link

nactopus commented Jul 1, 2024

This is because, on the first line of the gbf file, sometimes there is no space between the "chunk" number and the length of the sequence, altering the real sequence length:

E.g:

LOCUS my_meta_ct3_21@Chunk_1410396 bp DNA linear 01-JAN-2019

(The real length of the sequence is 410,396 bp, and it belongs to "Chunk 1").

Loving this program so far, btw!!

@mtisza1
Copy link
Owner

mtisza1 commented Jul 2, 2024

I appreciate the kind words.

I'm now seeing this problem with the .gbf files with long locus names. Thanks for pointing it out.

The quickest fix on your end is to use a short run name (the -r flag). 10 characters or less should work.

I will fix this issue and make a new release in the next 2 weeks.

In the mean time, can you please tell me which genome browser you're using that is having issue with this bug? I can open these "run-on" locus name .gbf files in SnapGene Viewer without apparent issue.

@nactopus
Copy link
Author

nactopus commented Jul 2, 2024

Thank you! I'm using Geneious Prime 2024.0.5. Apparently, it needs the stated length of the sequence to match the actual sequence length. I'll let you know if I run into any other issue.

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