You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When estimating ANI from Jaccard (only for scaled jaccard searches via sourmash search), we can run into cases where the error around the Jaccard estimate itself is too high for the Jaccard --> ANI conversion to be trustworthy.
We currently notify with a warning and store ani_untrustworthy in SearchResult.
WARNING: Error on Jaccard distance point estimate is too high (0.0010).
We could:
add ani_untrustworthy column to Jaccard search output (though it is irrelevant for any other search/ANI)
zero out the ANI estimate (""/None probably better than 0, as 0 is a valid ANI result)
The text was updated successfully, but these errors were encountered:
When estimating ANI from Jaccard (only for
scaled
jaccard searches viasourmash search
), we can run into cases where the error around the Jaccard estimate itself is too high for the Jaccard --> ANI conversion to be trustworthy.We currently notify with a warning and store
ani_untrustworthy
inSearchResult
.We could:
ani_untrustworthy
column toJaccard
search output (though it is irrelevant for any other search/ANI)""
/None
probably better than 0, as 0 is a valid ANI result)The text was updated successfully, but these errors were encountered: