-
Notifications
You must be signed in to change notification settings - Fork 57
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
Can Vicalib be used to calibrate pose of 2 real sense cameras w.r.t each other? #43
Comments
Somehow it's only detecting only one intel d415 camera when both are connected to USB 3.0 |
If you're using the "realsense2" HAL driver to capture the camera stream, I can confirm it does not currently support capturing two devices simultaneously. I'll look into implementing that, but if this is more time sensitive, I would recommend capturing images from the Intel's realsense applications, writing them to disk, then feeding them into vicalib via HAL's "file" driver. |
Thanks@mkaspr. I will try this out and update you. I also have a follow up query as to if is there an algorithmic limit to how many camera poses can be computer relative to reach other assuming a daisy chain of 5-6 with consecutive overlapping pairs. |
There’s no algorithmic limit.
…On Mon, Nov 12, 2018 at 9:21 PM Inder Singh ***@***.***> wrote:
***@***.*** I will try this out and update you. I also have a follow
up query as to is there an algorithmic limit to how many camera poses can
be computer relative to reach other assume a daisy chain of 5-6 with
consecutive overlapping pairs.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#43 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIl6BRjduWR-MXeDDzPxLCyAwfpH8vPyks5uukiwgaJpZM4YZU7H>
.
|
Thanks @crheckman |
RealSense2 Multi Camera support is now implemented in arpg/HAL#151 |
Can Vicalib be used to calibrate pose of 2 real sense cameras w.r.t each other or can it be used only for one camera?
The text was updated successfully, but these errors were encountered: