Papers › An Extensible Framework for Open Heterogeneous Collaborative Perception

An Extensible Framework for Open Heterogeneous Collaborative Perception

25 Jan 2024arXiv:2401.13964archive 2025-07-28

Yifan Lu, Yue Hu, Yiqi Zhong, Dequan Wang, Yanfeng Wang, Siheng Chen

Collaborative perception aims to mitigate the limitations of single-agent perception, such as occlusions, by facilitating data exchange among multiple agents. However, most current works consider a homogeneous scenario where all agents use identity sensors and perception models. In reality, heterogeneous agent types may continually emerge and inevitably face a domain gap when collaborating with existing agents. In this paper, we introduce a new open heterogeneous problem: how to accommodate continually emerging new heterogeneous agent types into collaborative perception, while ensuring high perception performance and low integration cost? To address this problem, we propose HEterogeneous ALliance (HEAL), a novel extensible collaborative perception framework. HEAL first establishes a unified feature space with initial agents via a novel multi-scale foreground-aware Pyramid Fusion network. When heterogeneous new agents emerge with previously unseen modalities or models, we align them to the established unified space with an innovative backward alignment. This step only involves individual training on the new agent type, thus presenting extremely low training costs and high extensibility. To enrich agents' data heterogeneity, we bring OPV2V-H, a new large-scale dataset with more diverse sensor types. Extensive experiments on OPV2V-H and DAIR-V2X datasets show that HEAL surpasses SOTA methods in performance while reducing the training parameters by 91.5% when integrating 3 new agent types. We further implement a comprehensive codebase at: https://github.com/yifanlu0227/HEAL

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 15 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 5 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 3 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: 15 samples from 1 repository, 11 ran (6 with no instrument failure; 5 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.

yifanlu0227/heal officialmentioned in papermentioned on GitHubpytorchNOASSERTIONSyntology: 15 samples, 11 ran (5 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

15 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 5 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.

3ran · our draft was wrong
2ran; the contract check could not run
6ran
4unverified

Licence: 15 of the 15 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 yifanlu0227/heal. “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 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “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.

yifanlu0227/heal official repository 15 samples, 11 ran (5 instrument-failed) · 4 unverified
add_sin_difference in 9 papers opencood/loss/ciassd_loss.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 725b188cee8a1577 · report fixture: signature boxes1:Tensor/3/float, boxes2:Tensor/3/float · returned tuple · level recorded 2026-09-25
clip_sigmoid opencood/loss/center_point_loss.py ran · our draft was wrong fingerprinted licence not identified · pointer only · 9163c6bd787ad901 · report fixture: signature x:Tensor/4/float, eps:float/0/float · returned Tensor · level recorded 2026-09-24
gaussian_2d in 11 papers opencood/loss/center_point_loss.py ran; the contract check could not run (RAISES) licence not identified · pointer only · ea036153b550642a · report fixture: signature shape:list/1/int, sigma:float/0/float · returned ndarray · level recorded 2026-09-24
gaussian_focal_loss opencood/loss/center_point_loss.py ran licence not identified · pointer only · 17eaeb2d97f99989 · report fixture: signature pred:Tensor/2/float, gaussian_target:Tensor/2/float, alpha:float/0/float, gamma:float/0/float · returned Tensor · level recorded 2026-09-24
get_direction_target in 8 papers opencood/loss/ciassd_loss.py ran no licence file found · pointer only · 71d71587ce799f91 · report fixture: signature reg_targets:Tensor/3/float, anchors:Tensor/2/float, one_hot:bool/0/bool, dir_offset:float/0/float · returned Tensor · level recorded 2026-09-25
indices_to_dense_vector in 11 papers opencood/loss/fpvrcnn_loss.py ran · our draft was wrong no licence file found · pointer only · 3acf861a2d1c5a22 · report fixture: returned Tensor · level recorded 2026-09-25
one_hot_f in 10 papers opencood/loss/ciassd_loss.py ran no licence file found · pointer only · cbb724502b77baff · report fixture: signature tensor:Tensor/2/int, depth:int/0/int, dim:int/0/int, on_value:float/0/float, dtype:dtype/0/? · returned Tensor · level recorded 2026-09-25
one_hot_f in 10 papers opencood/loss/point_pillar_loss.py ran no licence file found · pointer only · 3508d3e1819272d8 · report fixture: signature tensor:Tensor/2/int, num_bins:int/0/int, dim:int/0/int, on_value:float/0/float, dtype:dtype/0/? · returned Tensor · level recorded 2026-09-25
softmax_cross_entropy_with_logits in 5 papers opencood/loss/point_pillar_loss.py ran fingerprinted no licence file found · pointer only · 44590278c8d435af · report fixture: signature logits:Tensor/2/float, labels:Tensor/2/float · returned Tensor · level recorded 2026-09-25
weighted_fuse opencood/models/fuse_modules/pyramid_fuse.py ran; the contract check could not run (RAISES) licence not identified · pointer only · b71305155503d272 · report fixture: signature x:Tensor/4/float, score:Tensor/4/float, record_len:Tensor/1/int, affine_matrix:Tensor/5/float, align_corners:bool/0/bool · returned Tensor · level recorded 2026-09-22
weighted_smooth_l1_loss in 5 papers opencood/loss/point_pillar_loss.py ran no licence file found · pointer only · 3318bc2d0e244104 · report fixture: signature preds:Tensor/2/float, targets:Tensor/2/float, sigma:float/0/float, weights:Tensor/2/float · returned Tensor · level recorded 2026-09-25
PyramidFusion opencood/models/fuse_modules/pyramid_fuse.py unverified licence not identified · pointer only · ed44d5f305f13abf · report
ResNetBEVBackbone opencood/models/fuse_modules/pyramid_fuse.py unverified licence not identified · pointer only · f207202c769a25e7 · report
ResNetModified opencood/models/fuse_modules/pyramid_fuse.py unverified licence not identified · pointer only · c11267840a1cb208 · report
weighted_sigmoid_binary_cross_entropy in 8 papers opencood/loss/fpvrcnn_loss.py unverified no licence file found · pointer only · cbe2c496241c0635 · 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 Pyramid Fusion network (graph method: Pyramid Fusion network). 10 bricks; individually on a fixture: 7 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 5 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.

  1. PyramidFusion entry · level 0 · unverified · ed44d5f305f13abf
  2. Bottleneck helper · level 1 · ran · 6d8a817f41286a76
  3. ResNetBEVBackbone helper · level 0 · unverified · f207202c769a25e7
  4. ResNetModified helper · level 0 · unverified · c11267840a1cb208
  5. weighted_fuse helper · level 1 · ran; the contract check could not run (RAISES) · b71305155503d272
  6. conv1x1 helper · level 1 · ran · our draft was wrong · 2a80220dabcb742a
  7. conv3x3 helper · level 1 · ran · our draft was wrong · 600ff2c45e0de056
  8. BasicBlock helper · level 1 · ran · d42ae3fd7fcd5024
  9. regroup helper · level 1 · ran; the contract check could not run · 9008b01722ea4e92
  10. warp_affine_simple helper · level 1 · ran; the contract check could not run · 3019b9af698a296f

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

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

ALIGN

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