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

Bad sequence encodings in SEVAHub #1480

Open
jakebeal opened this issue Nov 5, 2021 · 1 comment
Open

Bad sequence encodings in SEVAHub #1480

jakebeal opened this issue Nov 5, 2021 · 1 comment

Comments

@jakebeal
Copy link

jakebeal commented Nov 5, 2021

I ran into validation errors that trace back to some bad sequence encodings in SEVAhub.
This doesn't seem like the right place to report them, but there is no other contact information listed.

The specific cases that I ran into are on

http://sevahub.es/public/Canonical/seq_seqKm 
http://sevahub.es/public/Canonical/seq_seqpRO1600_ColE1 

both of which have the obviously incorrect encoding: http://seva.cnb.csic.eshttp//seva.cnb.csic.es/

Other sequences, such as http://sevahub.es/public/Canonical/seq_seqSanDI have the correct encoding value.
The sequences with issues, however, were chosen essentially at random in a test involving SEVAhub, so there are likely many others with the same issue there.

@jakebeal
Copy link
Author

jakebeal commented Nov 5, 2021

A little more information: it looks like this affects nearly every top-level SEVA plasmid, because it affects the antibiotic resistance genes and ORIs.

jakebeal added a commit to iGEM-Engineering/iGEM-distribution that referenced this issue Nov 5, 2021
…ieces to let it pass validation

Also change SEVA examples in import, due to SEVAhub validation failures (SynBioHub/synbiohub#1480)
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

1 participant