Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spatial conditions - eval into cached sub #381

Closed
GoogleCodeExporter opened this issue Mar 27, 2015 · 6 comments
Closed

Spatial conditions - eval into cached sub #381

GoogleCodeExporter opened this issue Mar 27, 2015 · 6 comments
Labels
auto-migrated Priority-Medium Type-Enhancement
Milestone
Release_0.18

Comments

@GoogleCodeExporter
Copy link 

The spatial conditions are currently evaluated as new code for every candidate 
neighbour pair.  This is inefficient.  

The system should eval into a sub and then call the cached sub each time it is 
needed.  Benchmarking shows this to be about 25 times faster, although the 
caching process will soak up some of that speed-up.

Original issue reported on code.google.com by shawnlaffan on 6 Jun 2013 at 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Enhancement
Projects
None yet
Milestone
Release_0.18
Development

No branches or pull requests
2 participants
@shawnlaffan @GoogleCodeExporter