Papers › G²SF-MIAD: Geometry-Guided Score Fusion for Multimodal Industrial Anomaly Detection

G²SF-MIAD: Geometry-Guided Score Fusion for Multimodal Industrial Anomaly Detection

13 Mar 2025arXiv:2503.10091archive 2025-07-28

Chengyu Tao, Xuanming Cao, Juan Du

Industrial quality inspection plays a critical role in modern manufacturing by identifying defective products during production. While single-modality approaches using either 3D point clouds or 2D RGB images suffer from information incompleteness, multimodal anomaly detection offers promise through the complementary fusion of crossmodal data. However, existing methods face challenges in effectively integrating unimodal results and improving discriminative power. To address these limitations, we first reinterpret memory bank-based anomaly scores in single modalities as isotropic Euclidean distances in local feature spaces. Dynamically evolving from Eulidean metrics, we propose a novel Geometry-Guided Score Fusion (G²SF) framework that progressively learns an anisotropic local distance metric as a unified score for the fusion task. Through a geometric encoding operator, a novel Local Scale Prediction Network (LSPN) is proposed to predict direction-aware scaling factors that characterize first-order local feature distributions, thereby enhancing discrimination between normal and anomalous patterns. Additionally, we develop specialized loss functions and score aggregation strategy from geometric priors to ensure both metric generalization and efficacy. Comprehensive evaluations on the MVTec-3D AD dataset demonstrate the state-of-the-art detection performance of our method with low positive rate and better recall, which is essential in industrial application, and detailed ablation analysis validates each component's contribution.

PaperPDFCode Syntology ranMethod as code

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

By repository: found in paper text by Syntology: 11 samples from 1 repository, 5 ran (3 with no instrument failure; 2 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 between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

ctaoaa/G2SF found in paper text by SyntologySyntology: 11 samples, 5 ran (2 instrument-failed) · 6 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

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

2ran · honoured contract
2ran · our draft was wrong
1ran
6unverified

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 ctaoaa/G2SF. “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.

ctaoaa/G2SF found in paper text by Syntology 11 samples, 5 ran (2 instrument-failed) · 6 unverified
WDSADMarginLoss G2SF_GITHUB/Fusion/fusion_engine_v2.py ran · metamorphic tier: invariant MIT (permissive) · b292ef3ea5250431 · report fixture: signature rep:Tensor/2/float, targets:Tensor/1/int, is_weighted:bool/0/bool · returned tuple · level recorded 2026-09-22
get_dataloader in 111 papers G2SF_GITHUB/Fusion/fusion_engine_v2.py ran · our draft was wrong MIT (permissive) · 7c4de0bc86a2ecd7 · report fixture: signature path:str/0/str, batch_size:int/0/int, test_batch_size:int/0/int · returned tuple · level recorded 2026-09-25
get_scale in 14 papers G2SF_GITHUB/Fusion/fusion_engine_v2.py ran · our draft was wrong fingerprinted MIT (permissive) · dab20c12aac5426b · report fixture: signature scale:Tensor/1/float · returned Tensor · level recorded 2026-09-22
l1_regularization in 6 papers G2SF_GITHUB/Fusion/fusion_engine_v2.py ran · honoured contract MIT (permissive) · 16199d8c3e9c8b3a · report fixture: signature model:callable/0/? · returned Tensor · level recorded 2026-09-22
l2_regularization G2SF_GITHUB/Fusion/fusion_engine_v2.py ran · honoured contract MIT (permissive) · 3857baec9affd767 · report fixture: signature model:callable/0/? · returned Tensor · level recorded 2026-09-22
FusionModelV2 G2SF_GITHUB/Fusion/fusion_engine_v2.py unverified MIT (permissive) · 120da69785b147cc · report
LinearBlock in 8 papers G2SF_GITHUB/Fusion/fusion_engine_v2.py unverified MIT (permissive) · 49e18d07c7924b81 · report
MLPnet G2SF_GITHUB/Fusion/fusion_engine_v2.py unverified MIT (permissive) · cf61e747b2182da7 · report
MMScoringTrainer G2SF_GITHUB/Fusion/fusion_engine_v2.py unverified MIT (permissive) · 44b75c572fb89506 · report
MultiModalGateNet G2SF_GITHUB/Fusion/fusion_engine_v2.py unverified MIT (permissive) · e89daa54904fb1fb · report
get_sampler in 20 papers G2SF_GITHUB/Fusion/fusion_engine_v2.py unverified MIT (permissive) · 163820e4f0bc74bd · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for G2SF (graph method: G2SF). 11 bricks; individually on a fixture: 5 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 2 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 6 unverified. The assembly has not been run end-to-end.

  1. FusionModelV2 entry · level 0 · unverified · 120da69785b147cc
  2. MMScoringTrainer update_rule · level 0 · unverified · 44b75c572fb89506
  3. MultiModalGateNet model · level 0 · unverified · e89daa54904fb1fb
  4. WDSADMarginLoss loss · level 1 · ran · b292ef3ea5250431
  5. get_dataloader helper · level 1 · ran · our draft was wrong · 7c4de0bc86a2ecd7
  6. get_scale helper · level 1 · ran · our draft was wrong · dab20c12aac5426b
  7. l1_regularization helper · level 1 · ran · honoured contract · 16199d8c3e9c8b3a
  8. l2_regularization helper · level 1 · ran · honoured contract · 3857baec9affd767
  9. MLPnet helper · level 0 · unverified · cf61e747b2182da7
  10. get_sampler helper · level 0 · unverified · 163820e4f0bc74bd
  11. LinearBlock helper · level 0 · unverified · 49e18d07c7924b81

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2503.10091") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Anomaly Detection

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