-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Upgrade to 1 0 jessie #7
Conversation
Nice, looks good. Have you tested whether there were improvements in speed the interators, particularly |
Update travis and appveyor files to build 1.0 |
75181ab
to
e2238fb
Compare
* Fixed Voxelization Testset Error's * Fixed Rasterizer and Voxelization testset warnings * Fixed Neighbouring voxel test set errors * Fixed Neighbouring voxel test set * Changed compatablity in Project.toml * Gitignore added * Updates Travis and appveyor files * Appveyor fix * Re added Test to Project.toml
e2238fb
to
762512d
Compare
*using Pkg.METADATA_compatible_uuid("SpatialGrids")
I ran a quick test of the in_cuboid function and was actually surprised by the performace of the SparseVoxelGrid function. I ran the following with rand to use the same seed value:
The second line took 41.29 secs for the v1.0 package whereas it took 92.13 secs for the older package. The fourth line took 0.00014 secs in v1.0 whereas it took 0.000056 secs for v0.6. This was on the second and subsequent function call. First query always took way longer. I think the gain from second line definitely outweights the loss in the fourth line. What say? Also could I get an approve if you're happy with the results and code @JoshChristie @prabodha007 |
2ff0ae7
to
de56623
Compare
de56623
to
c197665
Compare
Travis and Appveyor tests pass now! |
Looks like a nice gain. |
Updated julia version.