[
https://issues.apache.org/jira/browse/LUCENE-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315871#comment-15315871
]
Karl Wright commented on LUCENE-7316:
-------------------------------------
[~mikemccand]: The bounds for the shape is the following:
bounds=XYZBounds: [xmin=-0.71289725396678 xmax=1.0011188549924792
ymin=-0.9656813334373919 ymax=1.0000001299807888E-9 zmin=-0.9977622930221052
zmax=0.9806582427397669]
Doc 21's point values:
{code}
[junit4] 1> doc=21 is contained by shape but is outside the returned
XYZBounds
[junit4] 1> unquantized=[lat=-0.41518838180529244,
lon=3.141592653589793([X=-0.9155623167011844, Y=1.1212404605680407E-16,
Z=-0.40359240429408716])]
[junit4] 1> quantized=[X=-0.9155623168963972,
Y=2.3309121299774915E-10, Z=-0.40359240449795253]
{code}
The x value is within range (-0.91 to 1.00), and so is the z value, but the y
value is (barely) not:
{code}
(quantized) Y=2.3309121299774915E-10
ymin=-0.9656813334373919 ymax=1.0000001299807888E-9
{code}
The question in my mind is, what changed with your latest patch that might
cause this? Is it an accidental discovery, or is there something about the
quantization change that might have cause this, e.g. those new hard limits?
The unquantized value is also outside the XYZBounds. It's suspicious because
the longitude value for these points is all essentially -Math.PI.
> Geo3d test failure
> ------------------
>
> Key: LUCENE-7316
> URL: https://issues.apache.org/jira/browse/LUCENE-7316
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/spatial3d
> Affects Versions: master (7.0)
> Reporter: Karl Wright
> Assignee: Karl Wright
> Attachments: LUCENE-7316.patch
>
>
> Reproducible on master with:
> {code}
> ant test -Dtestcase=TestGeo3DPoint -Dtests.method=testGeo3DRelations
> -Dtests.seed=EEA08DD7FAE3C688 -Dtests.multiplier=2 -Dtests.slow=true
> -Dtests.directory=MMapDirectory -Dtests.locale=es
> -Dtests.timezone=America/Manaus -Dtests.asserts=true
> -Dtests.file.encoding=UTF-8
> {code}
> Note: I was initially unable to reproduce this, until I pulled up code that
> [~mikemccand] recently committed. It seems possible that encoding/decoding
> changes are triggering it. Of specific concern is the new way
> maximum/minimum decoded values are computed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
