[jira] [Commented] (LUCENE-4419) Test RecursivePrefixTree indexing non-point data

2013-03-22 Thread Commit Tag Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13610458#comment-13610458
 ] 

Commit Tag Bot commented on LUCENE-4419:


[branch_4x commit] David Wayne Smiley
http://svn.apache.org/viewvc?view=revisionrevision=1418011

LUCENE-4419: Test indexing non-point shapes; and add 
SpatialOperation.evaluate(s1,s2)


 Test RecursivePrefixTree indexing non-point data
 

 Key: LUCENE-4419
 URL: https://issues.apache.org/jira/browse/LUCENE-4419
 Project: Lucene - Core
  Issue Type: Improvement
  Components: modules/spatial
Reporter: David Smiley
Assignee: David Smiley
 Fix For: 4.1, 5.0

 Attachments: LUCENE-4419_Test_indexing_non-point_shapes.patch


 RecursivePrefixTreeFilter was modified in ~July 2011 to support spatial 
 filtering of non-point indexed shapes.  It seems to work when playing with 
 the capability but it isn't tested.  It really needs to be as this is a major 
 feature.
 I imagine an approach in which some randomly generated rectangles are indexed 
 and then a randomly generated rectangle is queried.  The right answer can be 
 calculated brute-force and then compared with the filter.  In order to deal 
 with shape imprecision, the randomly generated shapes could be generated to 
 fit a course grid (e.g. round everything to a 1 degree interval).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-4419) Test RecursivePrefixTree indexing non-point data

2012-12-07 Thread Commit Tag Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527044#comment-13527044
 ] 

Commit Tag Bot commented on LUCENE-4419:


[branch_4x commit] David Wayne Smiley
http://svn.apache.org/viewvc?view=revisionrevision=1418011

LUCENE-4419: Test indexing non-point shapes; and add 
SpatialOperation.evaluate(s1,s2)



 Test RecursivePrefixTree indexing non-point data
 

 Key: LUCENE-4419
 URL: https://issues.apache.org/jira/browse/LUCENE-4419
 Project: Lucene - Core
  Issue Type: Improvement
  Components: modules/spatial
Reporter: David Smiley
Assignee: David Smiley
 Fix For: 4.1, 5.0

 Attachments: LUCENE-4419_Test_indexing_non-point_shapes.patch


 RecursivePrefixTreeFilter was modified in ~July 2011 to support spatial 
 filtering of non-point indexed shapes.  It seems to work when playing with 
 the capability but it isn't tested.  It really needs to be as this is a major 
 feature.
 I imagine an approach in which some randomly generated rectangles are indexed 
 and then a randomly generated rectangle is queried.  The right answer can be 
 calculated brute-force and then compared with the filter.  In order to deal 
 with shape imprecision, the randomly generated shapes could be generated to 
 fit a course grid (e.g. round everything to a 1 degree interval).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-4419) Test RecursivePrefixTree indexing non-point data

2012-12-07 Thread Commit Tag Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527061#comment-13527061
 ] 

Commit Tag Bot commented on LUCENE-4419:


[trunk commit] David Wayne Smiley
http://svn.apache.org/viewvc?view=revisionrevision=1418007

LUCENE-4419: Test indexing non-point shapes; and add 
SpatialOperation.evaluate(s1,s2)



 Test RecursivePrefixTree indexing non-point data
 

 Key: LUCENE-4419
 URL: https://issues.apache.org/jira/browse/LUCENE-4419
 Project: Lucene - Core
  Issue Type: Improvement
  Components: modules/spatial
Reporter: David Smiley
Assignee: David Smiley
 Fix For: 4.1, 5.0

 Attachments: LUCENE-4419_Test_indexing_non-point_shapes.patch


 RecursivePrefixTreeFilter was modified in ~July 2011 to support spatial 
 filtering of non-point indexed shapes.  It seems to work when playing with 
 the capability but it isn't tested.  It really needs to be as this is a major 
 feature.
 I imagine an approach in which some randomly generated rectangles are indexed 
 and then a randomly generated rectangle is queried.  The right answer can be 
 calculated brute-force and then compared with the filter.  In order to deal 
 with shape imprecision, the randomly generated shapes could be generated to 
 fit a course grid (e.g. round everything to a 1 degree interval).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-4419) Test RecursivePrefixTree indexing non-point data

2012-12-04 Thread David Smiley (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510077#comment-13510077
 ] 

David Smiley commented on LUCENE-4419:
--

Whoops; there's a stupid if (i != 5) continue; on line ~68 which I should 
have labelled with a NOCOMMIT that's in the patch.

 Test RecursivePrefixTree indexing non-point data
 

 Key: LUCENE-4419
 URL: https://issues.apache.org/jira/browse/LUCENE-4419
 Project: Lucene - Core
  Issue Type: Improvement
  Components: modules/spatial
Reporter: David Smiley
Assignee: David Smiley
 Attachments: LUCENE-4419_Test_indexing_non-point_shapes.patch


 RecursivePrefixTreeFilter was modified in ~July 2011 to support spatial 
 filtering of non-point indexed shapes.  It seems to work when playing with 
 the capability but it isn't tested.  It really needs to be as this is a major 
 feature.
 I imagine an approach in which some randomly generated rectangles are indexed 
 and then a randomly generated rectangle is queried.  The right answer can be 
 calculated brute-force and then compared with the filter.  In order to deal 
 with shape imprecision, the randomly generated shapes could be generated to 
 fit a course grid (e.g. round everything to a 1 degree interval).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-4419) Test RecursivePrefixTree indexing non-point data

2012-09-23 Thread Chris Male (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461548#comment-13461548
 ] 

Chris Male commented on LUCENE-4419:


I really don't see the benefit of randomly generating Shapes.  There isn't much 
to be revealed with a rectangle that say covers one small part of the pacific 
ocean and another rectangle which covers another small part.  The number of 
possible Shapes is just too massive to ever reveal anything.

What I feel would be better is if we defined Shapes that test particularly 
troublesome areas.  Datelines, equators, poles.  We can also include massive 
Shapes and tiny Shapes, circles, points, and whatever else we end up supporting.

Having this standardized Shape suite would be a big benefit to testing all the 
Strategys.  I don't think it would be particularly difficult to create and once 
created, it wouldn't require much maintenance at all.

 Test RecursivePrefixTree indexing non-point data
 

 Key: LUCENE-4419
 URL: https://issues.apache.org/jira/browse/LUCENE-4419
 Project: Lucene - Core
  Issue Type: Improvement
  Components: modules/spatial
Reporter: David Smiley

 RecursivePrefixTreeFilter was modified in ~July 2011 to support spatial 
 filtering of non-point indexed shapes.  It seems to work when playing with 
 the capability but it isn't tested.  It really needs to be as this is a major 
 feature.
 I imagine an approach in which some randomly generated rectangles are indexed 
 and then a randomly generated rectangle is queried.  The right answer can be 
 calculated brute-force and then compared with the filter.  In order to deal 
 with shape imprecision, the randomly generated shapes could be generated to 
 fit a course grid (e.g. round everything to a 1 degree interval).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-4419) Test RecursivePrefixTree indexing non-point data

2012-09-23 Thread David Smiley (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461561#comment-13461561
 ] 

David Smiley commented on LUCENE-4419:
--

I'm all for what you suggest -- a test that could be used by multiple 
strategies.  We're doing that already in fact in PortedSolr3Test.  And the 
StrategyTestCase has methods that facilitate using test files of sample data, 
which is used by several tests such as TestPointVectorStrategy.

bq. I really don't see the benefit of randomly generating Shapes.

I could have sworn you told me we should add that to the Spatial4j todo list.

I like randomized tests because it can catch errors that a static test simply 
didn't test for.  This helped out tremendously when I worked out the bugs in 
Circle-Rectangle intersection in Spatial4j.


 Test RecursivePrefixTree indexing non-point data
 

 Key: LUCENE-4419
 URL: https://issues.apache.org/jira/browse/LUCENE-4419
 Project: Lucene - Core
  Issue Type: Improvement
  Components: modules/spatial
Reporter: David Smiley

 RecursivePrefixTreeFilter was modified in ~July 2011 to support spatial 
 filtering of non-point indexed shapes.  It seems to work when playing with 
 the capability but it isn't tested.  It really needs to be as this is a major 
 feature.
 I imagine an approach in which some randomly generated rectangles are indexed 
 and then a randomly generated rectangle is queried.  The right answer can be 
 calculated brute-force and then compared with the filter.  In order to deal 
 with shape imprecision, the randomly generated shapes could be generated to 
 fit a course grid (e.g. round everything to a 1 degree interval).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-4419) Test RecursivePrefixTree indexing non-point data

2012-09-23 Thread Chris Male (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461564#comment-13461564
 ] 

Chris Male commented on LUCENE-4419:


bq. I'm all for what you suggest – a test that could be used by multiple 
strategies

I didn't suggest that.  I suggested a common suite of Shapes.  I don't like the 
idea of having a single test for all Strategys since they work in different 
ways and support different things.

bq. I like randomized tests because it can catch errors that a static test 
simply didn't test for

Theres a difference between randomized tests and randomized Shape generation 
(again I didn't suggest we stopped randomized testing).  The world is massive, 
much of it isn't remotely interesting or challenging to our spatial 
implementations.  Just generating arbitrary Shapes somewhere on the globe seems 
a total waste of time.  

If we have a standard set of Shapes then we can use randomized testing to 
handle the permutations between them, but we shouldn't waste days waiting for 
tests to hit an interesting Shape.

 Test RecursivePrefixTree indexing non-point data
 

 Key: LUCENE-4419
 URL: https://issues.apache.org/jira/browse/LUCENE-4419
 Project: Lucene - Core
  Issue Type: Improvement
  Components: modules/spatial
Reporter: David Smiley

 RecursivePrefixTreeFilter was modified in ~July 2011 to support spatial 
 filtering of non-point indexed shapes.  It seems to work when playing with 
 the capability but it isn't tested.  It really needs to be as this is a major 
 feature.
 I imagine an approach in which some randomly generated rectangles are indexed 
 and then a randomly generated rectangle is queried.  The right answer can be 
 calculated brute-force and then compared with the filter.  In order to deal 
 with shape imprecision, the randomly generated shapes could be generated to 
 fit a course grid (e.g. round everything to a 1 degree interval).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org