Dynamic Modality Selection for 3D Scenes
Listen to the summary
Uses a voice available on your device
Audio options
On this page
Key Takeaways
- SmartMage uses a dynamic routing module to select only relevant data types like text, RGB, or point cloud inputs for a given query.
- The model achieves state-of-the-art results across five 3D benchmarks including ScanRefer and Multi3DRefer.
- A selective fine-tuning scheme keeps large visual encoders and LLM parameters frozen while training only the router and expert branches.
- The architecture delivers significant gains in diagnostic benchmarks, notably a +27.1 CIDEr increase in material understanding and +15.9 CIDEr in color understanding.
Summary & Methodology Analysis
SmartMage improves 3D scene understanding by replacing fixed modality pipelines with a dynamic orchestration system. It first encodes diverse inputs like text, RGB images, depth maps, and point clouds into a shared embedding space. The core innovation is the SMART module, which employs a semantic prior estimator and similarity scorer to evaluate the necessity of each modality relative to the user query. This data informs the MAGE module, which uses a sparse Mixture of Experts (MoE) architecture, a design that routes data through specialized sub-networks to reduce computation, to activate specific model components based on modality priors. This approach avoids the semantic noise and wasted computation inherent in processing all input types for every query. The implementation relies on a selective fine-tuning strategy that optimizes only the router and expert branches end-to-end, keeping the visual encoders and primary LLM weights frozen to preserve base capabilities. The system shows substantial performance gains over baselines like Ross3D, reaching a +5.1 increase in Acc@0.5 on ScanRefer and a +6.4 F1@0.5 increase on Multi3DRefer. Despite these gains, the architecture faces challenges with input viewpoint selection. The FoVSR algorithm may skip critical angles, leading to potential gaps in spatial context. Furthermore, the use of Farthest Point Sampling to downsample point clouds reduces density, which may constrain the model when representing fine-grained object features.
Interactive System Flowchart
Cross-Examination & FAQs
A deeper dive clarifying mechanics, constraints, and baseline evaluations.
Q1. What is the primary problem with current 3D scene understanding models?
Current models use fixed modality combinations for all queries, which leads to semantic noise, unnecessary computational overhead, and diluted reasoning performance.
Q2. How does SmartMage decide which data types to process?
It uses a Semantic-guided Modality Adaptive RouTng module that includes a semantic prior estimator, a semantic similarity scorer, and a modality quality evaluator to select relevant inputs dynamically.
Q3. Does SmartMage improve over existing models?
Yes, it achieves state-of-the-art performance on five 3D benchmarks, including significant improvements on ScanRefer and Multi3DRefer compared to the Ross3D baseline.
Q4. What is the role of the MAGE module?
The MAGE module acts as a Modality-Aware Gating Expert, leveraging modality priors to guide token routing within a sparse Mixture-of-Experts based LLM.
Q5. How are the visual encoders handled during training?
They are kept frozen, along with the main LLM parameters, as part of a selective fine-tuning scheme that only updates the router and expert branches.
Q6. What are the limitations of the input selection process?
The FoVSR algorithm used for input selection may overlook important viewpoints, and point cloud downsampling via Farthest Point Sampling limits the representation of fine-grained details.
Q7. What specific improvements were noted on the ScanFacet benchmark?
The model achieved gains of +27.1 CIDEr in material understanding and +15.9 CIDEr in color understanding.
Q8. Which specific datasets were used for evaluation?
Evaluations were conducted on ScanQA, SQA3D, Scan2Cap, ScanRefer, Multi3DRefer, VSI-Bench, VSI-SUPER, MMSI-Bench, and ScanFacet.
Q9. Does the paper specify the exact inference latency of SmartMage?
The paper does not specify the exact inference latency.