In my original thinking, FX and FY, which was focus lenth of camera, is trivial. They play a role of just an actually non-sense part to the final output.
Today I test orb-slam2 with my own video.
I inherit the Kitti00-02.yaml config file. That's means, I use their FX and FY.
It turns out traking module is not working correctly.
Then I do another test. I changed Tum1.yaml to different FX and FY values to check whether it matters.
Results is shocking. Tracking can be lost.
Here is the screenshot.
After change,
fx:100.306408 (his raw values 517.306408)
fy:100.469215 (his raw values 516.469215)
Trajectory:nothing out.
Then I test another change version. i.e., fx= 350.306408 fy=516.469215
Sometimes it tracks, sometimes it get lost. And the TRAJEC is different from the origial.
Another puzzling phenomenon is that same setting, different output.
This was this, next time it changes though FX and FY remain the same. Why
The same FX and FY as above. Traje Output is:
Camera calibration ' s FX and FY do Cares in SLAM