Hello, This commit (in the blast_tests branch)
http://github.com/mkszuba/pygr/commit/85cb23f37403013d948d36fe721200c46a264eaa introduces a new, more relaxed check of BLASTP results, used instead of check_results() in test_blastp() and test_multiblast(). The check consists of the following parts: - compare the number of tuples in real and expected output, with some latitude (+-2 entries for blastp, +-10 for multiblast); - scan all fields in real output for syntactic correctness: fields 0 and 1 must be strings matching a certain regular expression (three capital letters optionally followed by another capital letter or a digit, an underscore, two to five capital letters), field 2 must be a number from the range 0. < x <= 1.; - require strict agreement between the two data sets only for entries with identity ratio above 50 %. With such changes in place, blast_test.py no longer fails. However, note that this work is not complete - relaxed checks must also be implemented in test_blastx() and test_tblastn(). I'll take care of that tomorrow. By the way, Chris - haven't you said once the TBLASTN test could be re-written so that it has exactly the same form as the BLASTX one? Please let me know what you think. -- MS --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
