Sachin Guruswamy

Thats a great sumay. Thanks @borongyuan > It would be better if you could ship each device with a reprojection error statistical report similar to [that in Kalibr](https://github.com/ethz-asl/kalibr/wiki#tutorial-start-to-end-guide-and-discussion). This will...

> Wrap node should be able to do this. But we need to prepare the mesh ourselves using cv::initUndistortRectifyMap(). Yes. but that is not needed if you use generic Camera...

As of RANSAC we need to see how computationally expensive it would be and how many shaves are available. > we can simply subtract the dispairty from the features positions...

@matlabbe @borongyuan Do you have a recommendation on IMU. We are looking for a better one for the upcoming product.

Can I know when this OAK-1 eas purchased ? the initial versions didn't come with Eeprom to store the calibration data for them.

ok. can you try [this](https://docs.luxonis.com/projects/api/en/latest/samples/calibration/calibration_reader/#calibration-reader) and see what error it gives ? If it throws an error. the work around would be to do an external calibration and use those...

> @saching13 can you explain the workaround in context of the referenced problems, aka simply starting the ROS nodes to publish _any_ topic related to the cameras. you can calibrate...

> my goal would be to simply make it work transparently for anyone that happens to own said camera variant, and chooses to use the existing ROS nodes. I understand...