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.
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.
A little more information: it looks like this affects nearly every top-level SEVA plasmid, because it affects the antibiotic resistance genes and ORIs.
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
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.