Papers › MARS: Multimodal Active Robotic Sensing for Articulated Characterization

MARS: Multimodal Active Robotic Sensing for Articulated Characterization

1 Jul 2024arXiv:2407.01191archive 2025-07-28

Hongliang Zeng, Ping Zhang, Chengjiong Wu, Jiahua Wang, Tingyu Ye, Fang Li

Precise perception of articulated objects is vital for empowering service robots. Recent studies mainly focus on point cloud, a single-modal approach, often neglecting vital texture and lighting details and assuming ideal conditions like optimal viewpoints, unrepresentative of real-world scenarios. To address these limitations, we introduce MARS, a novel framework for articulated object characterization. It features a multi-modal fusion module utilizing multi-scale RGB features to enhance point cloud features, coupled with reinforcement learning-based active sensing for autonomous optimization of observation viewpoints. In experiments conducted with various articulated object instances from the PartNet-Mobility dataset, our method outperformed current state-of-the-art methods in joint parameter estimation accuracy. Additionally, through active sensing, MARS further reduces errors, demonstrating enhanced efficiency in handling suboptimal viewpoints. Furthermore, our method effectively generalizes to real-world articulated objects, enhancing robot interactions. Code is available at https://github.com/robhlzeng/MARS.

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

By repository: official repository: 14 samples from 1 repository, 12 ran (9 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 between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

robhlzeng/mars officialmentioned in paperpytorchSyntology: 14 samples, 12 ran (3 instrument-failed) · 2 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

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

1ran · our draft was wrong
2ran; the contract check could not run
9ran
2unverified

Licence: 0 of the 14 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 robhlzeng/mars. “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”. For 3 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

robhlzeng/mars official repository 14 samples, 12 ran (3 instrument-failed) · 2 unverified
FeatureFusionBlock mars/models/mffp.py ran MIT (permissive) · 474eb4816b8052da · report fixture: returned FeatureFusionBlock · level recorded 2026-09-22
JointTypeDecoder mars/models/mffp.py ran MIT (permissive) · 483e652824478152 · report fixture: returned JointTypeDecoder · level recorded 2026-09-22
MLDM mars/models/mffp.py ran MIT (permissive) · eb00ee7e20d6b31d · report fixture: signature rgb_features:list/1/Tensor, pc_per_point:Tensor/3/float · returned Tensor · level recorded 2026-09-24
MovabilityDecoder mars/models/mffp.py ran MIT (permissive) · 6a155f8b4cb6ef1e · report fixture: returned MovabilityDecoder · level recorded 2026-09-22
PerceptionScoreDecoder mars/models/mffp.py ran MIT (permissive) · f4f15d43acc68ec9 · report fixture: signature cls_feature:Tensor/2/float · returned Tensor · level recorded 2026-09-24
PointNetFeaturePropagation in 6 papers mars/models/mffp.py ran fingerprinted MIT (permissive) · ac744ada43a50a0e · report fixture: signature xyz1:Tensor/3/float, xyz2:Tensor/3/float, features1:Tensor/3/float, features2:Tensor/3/float · returned Tensor · level recorded 2026-09-24
PointNetSetAbstraction in 7 papers mars/models/mffp.py ran MIT (permissive) · bf8d6ab94618b20c · report fixture: returned PointNetSetAbstraction · level recorded 2026-09-22
ResNetBackbone in 10 papers mars/models/mffp.py ran fingerprinted MIT (permissive) · d452cf2b41931a14 · report fixture: signature x:Tensor/4/float · returned list · level recorded 2026-09-24
VotingModule mars/models/mffp.py ran MIT (permissive) · 12732a2ba582423d · report fixture: signature seed_xyz:Tensor/3/float, seed_features:Tensor/3/float · returned tuple · level recorded 2026-09-24
farthest_point_sample in 64 papers mars/models/mffp.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · 9735279d0bc3aa74 · report fixture: signature xyz:Tensor/3/float, npoint:int/0/int · returned Tensor · level recorded 2026-09-22
index_points in 49 papers mars/models/mffp.py ran; the contract check could not run (RAISES) MIT (permissive) · 947dcee3f577f6cd · report fixture: signature points:Tensor/3/float, idx:Tensor/3/int · returned Tensor · level recorded 2026-09-22
square_distance in 89 papers
census: 11 implementations from 18 papers, 4 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 3, kind float, dtype float32 · arg 2: rank 3, kind float, dtype float32
mars/models/mffp.py ran · our draft was wrong fingerprinted MIT (permissive) · 24896468cac00905 · report fixture: signature src:Tensor/3/float, dst:Tensor/3/float · returned Tensor · level recorded 2026-09-22
MFFP mars/models/mffp.py unverified MIT (permissive) · 0cda0dd251868fc7 · report
PointNet2Backbone mars/models/mffp.py unverified MIT (permissive) · 5975f43c484850be · 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 MARS (graph method: MARS). 14 bricks; individually on a fixture: 12 ran (of which 4 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. MFFP entry · level 0 · unverified · 0cda0dd251868fc7
  2. FeatureFusionBlock model · level 1 · ran · 474eb4816b8052da
  3. JointTypeDecoder helper · level 1 · ran · 483e652824478152
  4. MLDM model · level 1 · ran · eb00ee7e20d6b31d
  5. MovabilityDecoder helper · level 1 · ran · 6a155f8b4cb6ef1e
  6. PerceptionScoreDecoder helper · level 1 · ran · f4f15d43acc68ec9
  7. PointNet2Backbone model · level 0 · unverified · 5975f43c484850be
  8. ResNetBackbone helper · level 1 · ran · d452cf2b41931a14
  9. VotingModule helper · level 1 · ran · 12732a2ba582423d
  10. PointNetFeaturePropagation helper · level 1 · ran · ac744ada43a50a0e
  11. PointNetSetAbstraction helper · level 1 · ran · bf8d6ab94618b20c
  12. index_points helper · level 1 · ran; the contract check could not run (RAISES) · 947dcee3f577f6cd
  13. square_distance helper · level 1 · ran · our draft was wrong · 24896468cac00905
  14. farthest_point_sample helper · level 1 · ran; the contract check could not run (RAISES) · 9735279d0bc3aa74

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="2407.01191") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

parameter estimation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Focus

1 archive method tag without a method page not shown.

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