# Optical Flow and Camera Pose for RGB vs GENX320

**URL:** <https://forums.openmv.io/t/optical-flow-and-camera-pose-for-rgb-vs-genx320/11214>\
**Category:** OpenMV Boards\
**Created:** [July 8, 2025, 9:39pm UTC](https://forums.openmv.io/t/optical-flow-and-camera-pose-for-rgb-vs-genx320/11214 "2025-07-08T21:39:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eventual](https://avatars.discourse-cdn.com/v4/letter/e/eb8c5e/32.png) [@eventual](https://forums.openmv.io/u/eventual)\
**Post date:** [July 8, 2025, 9:39pm UTC](https://forums.openmv.io/t/optical-flow-and-camera-pose-for-rgb-vs-genx320/11214/1 "2025-07-08T21:39:33Z")

</div>

How is the OpenMV software suite configured for optical flow and camera pose estimations? I have found that the find\_displacement function is a bit inaccurate, but that my event camera running at 100fps is more accurate than my rgb at 50fps. I would have thought the contrast trails formed by accumulated event sensing would cause the function to fail.

---

<div class="post-metadata">

**Author:** ![kwagyeman](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.openmv.io/kwagyeman/32/4_2.png) [@kwagyeman](https://forums.openmv.io/u/kwagyeman)\
**Post date:** [July 8, 2025, 10:49pm UTC](https://forums.openmv.io/t/optical-flow-and-camera-pose-for-rgb-vs-genx320/11214/2 "2025-07-08T22:49:09Z")

</div>

Find\_displacement works via phase correlation. So, it’s comparing FFTs. It greatly improves it’s ability to operate thanks to the strong edges.

Honestly, we don’t really have a great framework for pose estimation of the camera, though. However, you can pretty much do any math you like via ULAB onboard using ndarrays. You can convert images into ndarrays, run FFTs on the values, and etc. So, any math you want to do onboard is possible.