atlas

Research map / Detection and segmentation / CNN features

E2E-MFD: Towards End-to-End Synchronous Multimodal Fusion Detection

NeurIPS 2024 · Detection and segmentation › CNN features · approach: Context for hard detection conditions · 26 citations (OpenAlex)

Read the paperCheck your idea against 108,967 papers

AI-extracted summary. Written by AI from the paper's full text. Numbers and claims can be wrong or missing context, so check the paper before you cite or build on it.

Proposes E2E-MFD, a single-stage end-to-end framework that jointly trains visible-infrared image fusion and object detection (ORPPT fusion net + CFDP diffusion detection head) with a gradient-matrix task-alignment (GMTA) step on shared parameters.

Problem

Visible-infrared multimodal fusion and object detection are usually trained as cascaded, multi-step pipelines, which is inefficient and suffers from task conflicts and local optima when sharing parameters.

Approach

Synchronously and jointly optimize a fusion network (Object-Region-Pixel Phylogenetic Tree) and a diffusion-based detection head (Coarse-to-Fine Diffusion Process) sharing a backbone, and align shared-parameter gradients via a condition-number-based orthogonalization (GMTA, derived from Aligned-MTL).

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
Use GMTA instead of joint optimization without GMTA (ablation)E2E-MFD · M3FD validationmAP50: 90.05 -> 91.80Helped
Use GMTA instead of separate OD-only training (ablation)E2E-MFD · M3FD validationmAP50: 90.28 -> 91.80Helped
Replace GMTA with PCGrad, CAGrad, or Nash-MTL (ablation)E2E-MFD · M3FD validationmAP50: 90.59; 90.71; 90.91 vs 91.80Hurt
Set GMTA interval to n=500, 1500, or 2000 instead of 1000 (ablation)E2E-MFD · M3FD validationmAP50: 90.93; 91.10; 90.35 vs 91.80Mixed
Use branch configurations 0 only, 0,1, or 0,1,2 instead of 0,1,2,3 (ablation)ORPPT in E2E-MFD · M3FD validationmAP50: 91.51; 91.65; 91.73 vs 91.80Hurt
Add ORPPT branch 4 (ablation)ORPPT in E2E-MFD · M3FD validationmAP50: 91.80 -> 91.73Hurt
Replace CFDP with RPN (ablation)E2E-MFD · M3FD validationmAP50: 90.13 vs 91.80Hurt
Change CFDP proposal count to 300 or 1000 instead of 500 (ablation)E2E-MFD · M3FD validationmAP50: 90.89; 92.05 vs 91.80Mixed
Use E2E-MFD rather than CFT with YOLOv5sM3FD object detection · M3FDmAP50: 89.8 -> 91.8Helped
Use E2E-MFD rather than CALNetDroneVehicle oriented detection · DroneVehicle test setmAP50: 75.4 -> 77.4Helped

Surprising findings

Limitations

Experimental setup

Datasets: M3FD DroneVehicle

Benchmarks: TNO RoadScene M3FD DroneVehicle

Metrics: EN MI VIF mAP50 mAP50:95

Baselines: DIDFuse U2Fusion PIAFusion SwinFusion CDDFuse Tardal MetaFusion CFT ICAFusion PCGrad CAGrad Nash-MTL

Builds on: DiffusionDet MetaFusion Aligned-MTL LSKNet

Closest papers by meaning

Writing a paper in this area? scime draft is a free LaTeX editor with AI included, real-time co-authors and a check of your references and venue rules before you submit. It also imports OpenAI Prism projects.

Open scime draft

Get the next scime Dispatch and a monthly field update

Free. We send a confirmation link first; every email has a one-click unsubscribe. Privacy