openvslam VS open_vins

This might be the case. However there is an additional risk and process component:

- you might not want to risk because you don't have lawyers etc in your company.

- even if you have lawyers etc in your company, if there are 2 alternatives one which is just an MIT license, you'll probably go for that one because you don't want to have a 1.5 month review of the use of this AGPL licensed alternative.

In general things like this https://github.com/xdspacelab/openvslam/wiki/Termination-of-... (repo with 3k stars), an effort terminated because of some traces of GPL code MIGHT be somewhere in there comes to light. Even though Grafana etc are mostly tools, for my startup I would probably not risk any of this (for my own sake and also for any kind of due diligence in case it ever gets acquired)

OpenVSLAM

From what I have understood after reading research papers related to the VSLAM, the modularity aspect is not easy to achieve given the extracted features and descriptors are intrinsically linked with feature matching and handling of map points. I would like to know if there are some good Open Source VSLAM projects available which can be used with different feature extractors so I can get a comparative results with respect to just changing the feature extractors . I have tried pyslam project which is actually quite good considering the modularity but as the author himself points out this is only for academic purposes and when I compared the results of ORB_SLAM2 feature extractor using this module vs the original ORB_SLAM2 for KITTI data set , the results are not comparable. I am also looking into OpenVINS ( and from initial reading it is also using ORB Features, although it does have a base Tracker class which can be modified to create a new Tracker with different descriptor) If anyone has worked with custom feature extractor incorporated into prebuilt SLAM pipeline and can guide me as to how to proceed with the implementation of custom Feature extractor into a SLAM Front end using a Open Source VSLAM framework, it will be really helpful.

Because the standard MSCKF is the only one that doesn't contain the map points in the state. Note that this is only for the standard MSCKF. More modern MSCKFS variations like OpenVINS will actually add some SLAM features because it improves the accuracy.

Aside from that there have been some publications of some high quality open source SLAM systems like OpenVINS and ORB-SLAM3.

Check out open vins. Its an implementation of the vins slam project. https://github.com/rpng/open_vins

Generally you want to use a Kalman Filter based method if you want access to the uncertainties. This is because it is much easier to extract a subset of the covariance in the kalman filter form. I would recommend OpenVins. One of the best open source visual odometry projects, and it is pretty well documented.