-
Notifications
You must be signed in to change notification settings - Fork 2
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
Investigate Access of Pixel Data #4
Comments
@dhalperi Here is a query that builds off of our previous work intersecting trajectories with runs and then images. It uses the UDF we put together earlier this quarter.
Will check timings next. |
I'm pretty sure ingesting pixels will never be worth it. So if we go the Daniel Halperin On Tue, Dec 9, 2014 at 3:06 PM, Andy Becker notifications@github.com
|
Getting strange results on these timings. Here are a couple versions to see where the time is being taken up:
|
can you post the explains? Daniel Halperin On Wed, Dec 10, 2014 at 10:28 AM, Andy Becker notifications@github.com
|
Q1:
|
Q2:
|
Q3:
|
There are a couple of options to accessing the actual pixel data:
The latter issue might be problematic as there are 10^12 pixels and ingest (and index building and clustering) could take a substantial amount of time (CPU years). A parallel database might help solve this.
I will start this investigation by looking at how to turn the ra,decl of a Trajectory/Image intersection into a pixel address within the image. This can happen
The text was updated successfully, but these errors were encountered: