我在调试解码系统时发现一处浮点数比较不严谨的代码，可能导致歧义。调试界面截图如下：
When I was debugging the decoding system, I found a code with less rigorous floating-point numbers, which may cause ambiguity. The screenshot of the debugging interface is as follows:

此处循环前保留的最佳匹配度是 0.219780与当前计算的匹配度0.219780是完全一样的，但代码比较中使用了< ，并且通过了比较，导致bestMatch从1变成了2
The best matching degree retained before the loop here is 0.219780 and the current calculated matching degree 0.219780 is exactly the same, but the code comparison uses <and passes the comparison, resulting in the bestMatch changing from 1 to 2

如果此处相等的匹配度总是能通过，应该将 < 号修正为 <=，否则，应该使用指定精确度的比较
If the equal matching degree here always passes, the <sign should be corrected to <=, otherwise, the comparison with the specified accuracy should be used

重现代码如下:
The code to reproduce the bug is as follows:

Test code:

    Result result = null;
    Map<DecodeHintType,Object> hints = new EnumMap<>(DecodeHintType.class);

    hints.put(DecodeHintType.TRY_HARDER, Boolean.TRUE);

    int[] bits = {0, 0, 0, 0, 0, 0, 0, 0, -33570816, 118, 0, 0, 946064924, -2026257522, 955253639, 124828, 0, 0, 0, 0};
    BitArray row = new BitArray(bits, 640);
    result = new UPCEReader().decodeRow(128, row, hints); //  here throws ChecksumException

此段代码在解码时得到的临时结果是 05221169 （如果浮点数比较指定了精度，得到的结果是 05111169 ，并且不会抛出 ChecksumException）
The temporary result of this code during decoding is 05221169 (if the precision is specified for the comparison of floating-point numbers, the result is 05111169 and ChecksumException will not be thrown)

在测试项目中新增一个测试方法，将以上代码复制过去，以Debug模式运行，运行前在 UPCEANReader.decodeDigit 的相关位置打好断点
Add a test method to the test project, copy the above code, run it in Debug mode, and set a breakpoint at the relevant position of UPCEANReader.decodeDigit before running