Papers › ChangeMamba: Remote Sensing Change Detection With Spatiotemporal State Space Model

ChangeMamba: Remote Sensing Change Detection With Spatiotemporal State Space Model

4 Apr 2024arXiv:2404.03425archive 2025-07-28

Hongruixuan Chen, Jian Song, Chengxi Han, Junshi Xia, Naoto Yokoya

Convolutional neural networks (CNN) and Transformers have made impressive progress in the field of remote sensing change detection (CD). However, both architectures have inherent shortcomings: CNN are constrained by a limited receptive field that may hinder their ability to capture broader spatial contexts, while Transformers are computationally intensive, making them costly to train and deploy on large datasets. Recently, the Mamba architecture, based on state space models, has shown remarkable performance in a series of natural language processing tasks, which can effectively compensate for the shortcomings of the above two architectures. In this paper, we explore for the first time the potential of the Mamba architecture for remote sensing CD tasks. We tailor the corresponding frameworks, called MambaBCD, MambaSCD, and MambaBDA, for binary change detection (BCD), semantic change detection (SCD), and building damage assessment (BDA), respectively. All three frameworks adopt the cutting-edge Visual Mamba architecture as the encoder, which allows full learning of global spatial contextual information from the input images. For the change decoder, which is available in all three architectures, we propose three spatio-temporal relationship modeling mechanisms, which can be naturally combined with the Mamba architecture and fully utilize its attribute to achieve spatio-temporal interaction of multi-temporal features, thereby obtaining accurate change information. On five benchmark datasets, our proposed frameworks outperform current CNN- and Transformer-based approaches without using any complex training strategies or tricks, fully demonstrating the potential of the Mamba architecture in CD tasks. Further experiments show that our architecture is quite robust to degraded data. The source code will be available in https://github.com/ChenHongruixuan/MambaCD

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: 5 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 1 violated, 1 with no contract checked; 3 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

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

chenhongruixuan/mambacd officialmentioned in papermentioned on GitHubApache-2.0Syntology: 9 samples, 5 ran (3 instrument-failed) · 4 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: 5 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 1 violated, 1 with no contract checked; 3 where Syntology's instrument failed) · 4 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 · violated contract
3ran · our draft was wrong
1ran
4unverified

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 chenhongruixuan/mambacd. “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.

chenhongruixuan/mambacd official repository 9 samples, 5 ran (3 instrument-failed) · 4 unverified
build_head in 7 papers changedetection/models/builders.py ran · our draft was wrong Apache-2.0 (permissive) · e9c3ba9cd1c348a6 · report fixture: signature out_channels:int/0/int, in_channels:int/0/int · returned Conv2d · level recorded 2026-09-24
extract_model_state_dict changedetection/checkpoints.py ran · our draft was wrong Apache-2.0 (permissive) · 21a17e068ab68253 · report fixture: signature checkpoint:dict/0/? · returned dict · level recorded 2026-09-24
format_log_block changedetection/logging_utils.py ran Apache-2.0 (permissive) · 900d316c3b86d875 · report fixture: signature title:str/0/str, values:dict/0/?, meta:dict/0/?, precision:int/0/int · returned str · level recorded 2026-09-24
format_value in 9 papers changedetection/logging_utils.py ran · our draft was wrong Apache-2.0 (permissive) · 38727dde2f236d95 · report fixture: signature value:ndarray/1/float, precision:int/0/int · returned str · level recorded 2026-09-24
is_interactive_stream changedetection/logging_utils.py ran · violated contract Apache-2.0 (permissive) · e3e2bdd7e980f0f2 · report fixture: signature stream:MockStream/0/? · returned bool · level recorded 2026-09-24
build_backbone in 29 papers changedetection/models/builders.py unverified Apache-2.0 (permissive) · f7fca94a333f0a3d · report
load_encoder_pretrained_weights changedetection/checkpoints.py unverified Apache-2.0 (permissive) · 81509265e2e1fda9 · report
load_model_weights in 6 papers changedetection/checkpoints.py unverified Apache-2.0 (permissive) · c10476d7e491f533 · report
resolve_decoder_components changedetection/models/builders.py unverified Apache-2.0 (permissive) · c1a13c7ad7c5f1a9 · report

Tasks

2D Semantic SegmentationAttributeBuilding Damage AssessmentChange DetectionMambaState Space Models

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
2D Semantic Segmentation xBD MambaBDA-Base Classification F1-score 0.7884 #1 of 5 Archive leaderboard report
2D Semantic Segmentation xBD MambaBDA-Base Localization F1-score 0.8141 #1 of 5 Archive leaderboard report
2D Semantic Segmentation xBD MambaBDA-Base Weighted Average F1-score 0.8141 #1 of 5 Archive leaderboard report
Change Detection LEVIR+ ChangeMamba F1 88.39 #1 of 9 Archive leaderboard report
Change Detection LEVIR+ ChangeMamba IoU 79.20 #1 of 9 Archive leaderboard report
Change Detection LEVIR+ ChangeMamba KC 87.91 #1 of 9 Archive leaderboard report
Change Detection LEVIR+ ChangeMamba OA 99.06 #1 of 9 Archive leaderboard report
Change Detection LEVIR+ ChangeMamba Prcision 89.24 #1 of 9 Archive leaderboard report
Change Detection LEVIR+ ChangeMamba Recall 87.57 #1 of 9 Archive leaderboard report
Change Detection SECOND ChangeMamba Fscd 64.03 #1 of 2 Archive leaderboard report
Change Detection SECOND ChangeMamba SeK 24.11 #1 of 2 Archive leaderboard report
Change Detection SECOND ChangeMamba mIoU 73.68 #1 of 2 Archive leaderboard report
Change Detection SYSU-CD ChangeMamba F1 83.11 #3 of 12 Archive leaderboard report
Change Detection SYSU-CD ChangeMamba IoU 71.10 #3 of 12 Archive leaderboard report
Change Detection SYSU-CD ChangeMamba KC 78.13 #3 of 12 Archive leaderboard report
Change Detection SYSU-CD ChangeMamba OA 92.30 #3 of 12 Archive leaderboard report
Change Detection SYSU-CD ChangeMamba Precision 86.11 #3 of 12 Archive leaderboard report
Change Detection SYSU-CD ChangeMamba Recall 80.31 #3 of 12 Archive leaderboard report
Change Detection WHU-CD ChangeMamba F1 94.19 #4 of 22 Archive leaderboard report
Change Detection WHU-CD ChangeMamba IoU 89.02 #4 of 22 Archive leaderboard report
Change Detection WHU-CD ChangeMamba KC 93.98 #4 of 22 Archive leaderboard report
Change Detection WHU-CD ChangeMamba Overall Accuracy 99.58 #4 of 22 Archive leaderboard report
Change Detection WHU-CD ChangeMamba Precision 96.18 #4 of 22 Archive leaderboard report
Change Detection WHU-CD ChangeMamba Recall 92.23 #4 of 22 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

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