searchp returns pident 0.0 in results
Hello,
I ran across a potential bug where pident was reporting 0.00 for some results.
The test I ran was a sample against a protein database with the full UniRef100 data (flags: -e 100 -n 10 --output-columns "std qlen slen").
I have a Gist with the full input/output showing these results.
tl;dr-- Shows 6 results with 0.00 pident all the same subject accession and data.
CP006794.1|part222 UniRef100_A0A0L9U2H8 30.94 223 139 5 2938 2300 66 283 2e-12 84.7 5001 8269
CP006794.1|part222 UniRef100_A0A0L9U2H8 36.23 138 77 3 2710 2300 68 195 2e-07 68.6 5001 8269
CP006794.1|part222 UniRef100_A0A0L9U2H8 54.55 55 25 0 2464 2300 93 147 4e-07 67.4 5001 8269
CP006794.1|part222 UniRef100_A0A0L9U2H8 67.44 43 14 0 2428 2300 380 422 2e-05 61.6 5001 8269
CP006794.1|part222 UniRef100_A0A1Q9C9Y4 0.00 43 43 0 2300 2428 148 190 31 41.2 5001 836
CP006794.1|part222 UniRef100_A0A1Q9C9Y4 0.00 43 43 0 2300 2428 187 229 31 41.2 5001 836
CP006794.1|part222 UniRef100_A0A1Q9C9Y4 0.00 43 43 0 2300 2428 226 268 31 41.2 5001 836
CP006794.1|part222 UniRef100_A0A1Q9C9Y4 0.00 43 43 0 2300 2428 265 307 31 41.2 5001 836
CP006794.1|part222 UniRef100_A0A1Q9C9Y4 0.00 43 43 0 2300 2428 304 346 31 41.2 5001 836
CP006794.1|part222 UniRef100_A0A1Q9C9Y4 0.00 43 43 0 2300 2428 343 385 31 41.2 5001 836
Cheers~
Hi @bfowle,
Thanks for reporting this. Did this happen with lambda2 or lambda3? I will have a look at it then.
Sara
This was with lambda2.
Thanks~
@bfowle Can you reproduce this with lambda3?
Please open if you can reproduce with the lambda3 branch