-
Notifications
You must be signed in to change notification settings - Fork 1
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
wrong boxb found with newest code #21
Comments
@phycologia ; what does boxb end with in these cases? |
TGCTG! @callmcgovern |
Can you paste what it's supposed to be? @phycologia |
I think I'm making progress on this one. It was actually BIG. It uncovered that it could be a problem in the future with other sequences. I have a working prototype of yet another algorithm but I think it's more robust now. |
@phycologia @callmcgovern I think this is fixed. I ran a test and it found the one @phycologia wanted above alongside another possible one. I set the BoxB length limit to 60 bases or you'd get a bunch more. I don't think they are ever that long, but keep an eye out. |
was not found in genbank btw. The other two worked. |
@nlabrad ah my bad I was with fam for the weekend so I didn't your first comment til now! It sounds like you got it figured out, but just in case: |
seems to be working for the first two, but for the last one I get
|
huh, I'm not sure! |
previous version(s?) of the code identified boxb correctly, but now identifies incorrect sequences as boxb; all begin with "TAGCA"
accession numbers for sequences with this issue (all in order Nostocales):
KF417427.1
MK953008.1
MN15981.1
The text was updated successfully, but these errors were encountered: