Papers › Visual-Inertial Mapping with Non-Linear Factor Recovery

Visual-Inertial Mapping with Non-Linear Factor Recovery

13 Apr 2019arXiv:1904.06504archive 2025-07-28

Vladyslav Usenko, Nikolaus Demmel, David Schubert, Jörg Stückler, Daniel Cremers

Cameras and inertial measurement units are complementary sensors for ego-motion estimation and environment mapping. Their combination makes visual-inertial odometry (VIO) systems more accurate and robust. For globally consistent mapping, however, combining visual and inertial information is not straightforward. To estimate the motion and geometry with a set of images large baselines are required. Because of that, most systems operate on keyframes that have large time intervals between each other. Inertial data on the other hand quickly degrades with the duration of the intervals and after several seconds of integration, it typically contains only little useful information. In this paper, we propose to extract relevant information for visual-inertial mapping from visual-inertial odometry using non-linear factor recovery. We reconstruct a set of non-linear factors that make an optimal approximation of the information on the trajectory accumulated by VIO. To obtain a globally consistent map we combine these factors with loop-closing constraints using bundle adjustment. The VIO factors make the roll and pitch angles of the global map observable, and improve the robustness and the accuracy of the mapping. In experiments on a public benchmark, we demonstrate superior performance of our method over the state-of-the-art approaches.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 2 repositories linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 5 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 11 samples from 2 repositories, 6 ran (5 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

LONG-9621/Derivative_Efficient mentioned on GitHubBSD-3-ClauseSyntology: not harvested report
VladyslavUsenko/basalt-headers-mirror mentioned on GitHubBSD-3-ClauseSyntology: 7 samples, 3 ran (0 instrument-failed) · 4 unverified report
berndpfrommer/basalt-headers mentioned on GitHubBSD-3-ClauseSyntology: not harvested report
chengguizi/basalt-headers mentioned on GitHubnot reachable when probed 2026-09-18 — repositories for recent papers often appear after camera-readySyntology: not harvested report
minxuanjun/basalt-mirror mentioned on GitHubBSD-3-ClauseSyntology: not harvested report
minxuanjun/basalt_class mentioned on GitHubBSD-3-ClauseSyntology: 4 samples, 3 ran (1 instrument-failed) · 1 unverified report
gitlab.com/VladyslavUsenko/basalt-headers mentioned on GitHubSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 5 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
5ran
5unverified

Licence: 0 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

VladyslavUsenko/basalt-headers-mirror community (archive-listed) 7 samples, 3 ran (0 instrument-failed) · 4 unverified
cse_as_cxx python/radtan8/main_jacobians.py ran BSD-3-Clause (permissive) · 7df6e4cd3c9216f9 · report fixture: signature cse_tuple:tuple/1/list, expr_names:list/1/str · returned str · level recorded 2026-09-24
numeric_J_f_from_xy python/radtan8/main_compute_rpmax.py ran BSD-3-Clause (permissive) · e8b20f856e5b2566 · report fixture: signature f:callable/0/? · returned function · level recorded 2026-09-24
test_point_inyective python/radtan8/main_test_points.py ran BSD-3-Clause (permissive) · 96295c855c9e8f08 · report fixture: signature x:float/0/float, y:float/0/float, z:float/0/float, rpmax:float/0/float, mut:MockMutation/0/?, N:NoneType/0/?, eps:float/0/float · returned bool · level recorded 2026-09-24
distort_symbolic python/radtan8/main_jacobians.py unverified BSD-3-Clause (permissive) · fbca7d1bafd2f67f · report
my_least_squares python/radtan8/main_compute_rpmax.py unverified BSD-3-Clause (permissive) · 0217fe5140cc51c7 · report
my_least_squares_old python/radtan8/main_compute_rpmax.py unverified BSD-3-Clause (permissive) · 9c1d9a0899486422 · report
project_symbolic python/radtan8/main_jacobians.py unverified BSD-3-Clause (permissive) · 02ed0223995b4028 · report
minxuanjun/basalt_class community (archive-listed) 4 samples, 3 ran (1 instrument-failed) · 1 unverified
Vector2 thirdparty/basalt-headers/thirdparty/Sophus/py/sophus/matrix.py ran BSD-3-Clause (permissive) · 3fb6584cf4dc0220 · report fixture: signature x:int/0/int, y:int/0/int · returned MutableDenseMatrix · level recorded 2026-09-24
dot in 68 papers thirdparty/basalt-headers/thirdparty/Sophus/py/sophus/matrix.py ran BSD-3-Clause (permissive) · 27d2ed826241f29f · report fixture: signature left:MutableDenseMatrix/0/?, right:MutableDenseMatrix/0/? · returned Integer · level recorded 2026-09-24
squared_norm in 5 papers thirdparty/basalt-headers/thirdparty/Sophus/py/sophus/matrix.py ran · our draft was wrong BSD-3-Clause (permissive) · 8e30df616b00e951 · report fixture: signature m:MutableDenseMatrix/0/? · returned Integer · level recorded 2026-09-24
cse_codegen thirdparty/basalt-headers/thirdparty/Sophus/py/sophus/cse_codegen.py unverified BSD-3-Clause (permissive) · bcddb9f81acc6e7a · report

Tasks

Motion Estimation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections