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.

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

On RPi estimate-px-per-mm takes about 6s for 400x400 image #12

Open
firepick1 opened this issue Jul 20, 2014 · 1 comment
Open

On RPi estimate-px-per-mm takes about 6s for 400x400 image #12

firepick1 opened this issue Jul 20, 2014 · 1 comment
Assignees

Comments

@firepick1
Copy link
Owner

The current FirePick Raspberry Pi FireSight takes about 6 seconds to execute estimate-px-per-mm. This is a lot of time and one solution would be to support the specification of a region-of-interest to reduce computational load and speed up processing. To specify the ROI, we could add to following parameter to the stage:

"roi":[150,0,100,400]

Such an ROI would be about 4x faster.

PRIORITY: Medium (it takes about 10-20 tries to get a good image that shows correct resolution)

@firepick1
Copy link
Owner Author

Oh, I just realized that it's a two-stage pipeline, and I'm not sure where the slowness is. ROI would only help Hough, because Ransac takes points. Not sure if Hough or Ransac is slowest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants