Papers › FireANTs: Adaptive Riemannian Optimization for Multi-Scale Diffeomorphic Matching

FireANTs: Adaptive Riemannian Optimization for Multi-Scale Diffeomorphic Matching

1 Apr 2024arXiv:2404.01249archive 2025-07-28

Rohit Jena, Pratik Chaudhari, James C. Gee

The paper proposes FireANTs, the first multi-scale Adaptive Riemannian Optimization algorithm for dense diffeomorphic image matching. One of the most critical and understudied aspects of diffeomorphic image matching algorithms are its highly ill-conditioned nature. We quantitatively capture the extent of ill-conditioning in a typical MRI matching task, motivating the need for an adaptive optimization algorithm for diffeomorphic matching. To this end, FireANTs generalizes the concept of momentum and adaptive estimates of the Hessian to mitigate this ill-conditioning in the non-Euclidean space of diffeomorphisms. Unlike common non-Euclidean manifolds, we also formalize considerations for multi-scale optimization of diffeomorphisms. Our rigorous mathematical results and operational contributions lead to a state-of-the-art dense matching algorithm that can be applied to generic image data with remarkable accuracy and robustness. We demonstrate consistent improvements in image matching performance across a spectrum of community-standard medical and biological correspondence matching challenges spanning a wide variety of image modalities, anatomies, resolutions, acquisition protocols, and preprocessing pipelines. This improvement is supplemented by 300x to 3200x speedup over existing CPU-based state-of-the-art algorithms. For the first time, we perform diffeomorphic matching of sub-micron mouse isocortex volumes at native resolution, and generate a 25μm mouse brain atlas in under 25 minutes. Our fast implementation also enables hyperparameter studies that were intractable with existing correspondence matching algorithms.

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 9 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 2 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 9 samples from 1 repository, 9 ran (9 with no instrument failure; 0 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.

rohitrango/fireants officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 9 samples, 9 ran (0 instrument-failed) · 0 unverified 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

9 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 2 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 0 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.

2ran · honoured contract
7ran

Licence: 0 of the 9 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 rohitrango/fireants. “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.

rohitrango/fireants official repository 9 samples, 9 ran (0 instrument-failed) · 0 unverified
gaussian_1d fireants/losses/cc.py ran Apache-2.0 (permissive) · 32686de6a67a9e9a · report fixture: signature sigma:Tensor/0/float, truncated:float/0/float, approx:str/0/str, normalize:bool/0/bool · returned Tensor · level recorded 2026-09-24
get_mask_function fireants/losses/maskedutils.py ran Apache-2.0 (permissive) · b9a0f0381c308152 · report fixture: signature mask1:Tensor/2/float, mask2:Tensor/2/float, masked_mode:str/0/str · returned Tensor · level recorded 2026-09-24
get_max_coords3d fireants/interpolator/grid_sample.py ran Apache-2.0 (permissive) · dd8aadbfe86ce427 · report fixture: signature Z:int/0/int, Y:int/0/int, X:int/0/int, align_corners:bool/0/bool · returned tuple · level recorded 2026-09-24
get_min_coords2d fireants/interpolator/grid_sample.py ran Apache-2.0 (permissive) · 970d4450171b0247 · report fixture: signature Y:int/0/int, X:int/0/int, align_corners:bool/0/bool · returned tuple · level recorded 2026-09-24
get_min_coords3d fireants/interpolator/grid_sample.py ran Apache-2.0 (permissive) · 2a480b12e7eff3a8 · report fixture: signature Z:int/0/int, Y:int/0/int, X:int/0/int, align_corners:bool/0/bool · returned tuple · level recorded 2026-09-24
get_tensors_and_mask fireants/losses/maskedutils.py ran Apache-2.0 (permissive) · 38edae2fdcaabaa9 · report fixture: signature image1:Tensor/4/float, image2:Tensor/4/float, masked_mode:str/0/str · returned tuple · level recorded 2026-09-24
make_rectangular_kernel fireants/losses/cc.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 731ca37947c80e23 · report fixture: signature kernel_size:int/0/int · returned Tensor · level recorded 2026-09-24
make_triangular_kernel fireants/losses/cc.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 5fb7bd7001b1878b · report fixture: signature kernel_size:int/0/int · returned Tensor · level recorded 2026-09-24
mask_loss_function fireants/losses/maskedutils.py ran Apache-2.0 (permissive) · 7713035c73c97dec · report fixture: signature loss_tensor:Tensor/2/float, mask_tensor:Tensor/2/float, reduction:str/0/str · returned Tensor · level recorded 2026-09-24

Tasks

Image RegistrationRiemannian optimization

1 archive task tag without a task page not shown.

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