Sachin Guruswamy

> And to verify... there are devices, for example the OAK-D, sold to people around with world that have calibration.getEepromData().boardName equal to the exact case-sensitive string OAK-D or BW1098OBC Yes.

Hello @tachiuhy , Thanks alot for the detailed tests. On the Chart 1 and Chart 2 tests. 1. ArUco targets depth was on RGB camera ? (If yes. Did you...

Thanks @tachiuhy . Yeah for that close distance to align properly we need to figure a way to change the intrinsics as the lens position changes and then apply it...

Using Open3D code would be pretty much similar. And we don't have an official example that converts the depth to pointcloud but I can point you to some examples. 1....

> Actually, the Eigen solution looks better. I will give that one a try first.... Sounds good. Just a heads up. Make sure to Cherry Pick the `DepthAlignment` class and...

> Sachin - what is the best way to "get_right_homography" using the latest depthai-core API's? Bob Davies > […](#) It needs to be done similar to the `H_left` [here](https://github.com/luxonis/depthai-python/blob/a675ac1a939f6b7fc6e02be9b27fbc2224ae4b68/examples/calibration_reader.py#L28)

Thanks alot for the PR.

Hello @diablodale, Thanks alot for the feedback. On the rgb not being calibrated can you share when was the device bought? As of adding a Try/Catch the scripts needs more...

> I also am thinking how I will detect/manage different OAK device models with my C++ app if you mean detecting multiple OAK Devices then you can use `getAllAvailableDevices()` function...

> Do you want my OAK-D for testing? No. that is fine. I can recreate the issue. And as of OAK-D-Lite you can get which camera it is using `getConnectedCameraProperties()`...