Papers › When2com: Multi-Agent Perception via Communication Graph Grouping

When2com: Multi-Agent Perception via Communication Graph Grouping

30 May 2020CVPR 2020 6arXiv:2006.00176archive 2025-07-28

Yen-Cheng Liu, Junjiao Tian, Nathaniel Glaser, Zsolt Kira

While significant advances have been made for single-agent perception, many applications require multiple sensing agents and cross-agent communication due to benefits such as coverage and robustness. It is therefore critical to develop frameworks which support multi-agent collaborative perception in a distributed and bandwidth-efficient manner. In this paper, we address the collaborative perception problem, where one agent is required to perform a perception task and can communicate and share information with other agents on the same task. Specifically, we propose a communication framework by learning both to construct communication groups and decide when to communicate. We demonstrate the generalizability of our framework on two different perception tasks and show that it significantly reduces communication bandwidth while maintaining superior performance.

PaperPDFConference PDFCodeCode Syntology ran

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

By repository: community (archive-listed): 13 samples from 1 repository, 11 ran (9 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-24 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

coperception/coperception mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Learning Distilled Collaboration Graph for Multi-Agent Perception (arXiv:2111.00643; that paper's own run record: 4 ran (of which 4 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified; every one of the 4 samples that ran constructed an object rather than computing a result); nothing checks that they implement this paper's method. report
GT-RIPL/MultiAgentPerception pytorchMITSyntology: 13 samples, 11 ran (2 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

13 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 2 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 last changed ; 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
1ran; the contract check could not run
9ran
2unverified

Licence: 3 of the 13 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from GT-RIPL/MultiAgentPerception. “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.

GT-RIPL/MultiAgentPerception community (archive-listed) 13 samples, 11 ran (2 instrument-failed) · 2 unverified
alpha_blend in 5 papers ptsemseg/process_img.py ran MIT (permissive) · 3a8e7e1d2e1dc425 · report fixture: signature input_image:ndarray/3/float, segmentation_mask:ndarray/3/float, alpha:float/0/float · returned ndarray · level recorded 2026-09-25
bootstrapped_cross_entropy2d ptsemseg/loss/loss.py ran MIT (permissive) · dfe03b9cbc5639c5 · report fixture: signature input:Tensor/4/float, target:Tensor/3/int, K:int/0/int, weight:Tensor/1/float, size_average:bool/0/bool · returned Tensor · level recorded 2026-09-26
convert_state_dict in 13 papers ptsemseg/utils.py ran MIT (permissive) · e71ba6dcf9b2c854 · report fixture: signature state_dict:dict/0/? · returned OrderedDict · level recorded 2026-09-24
cross_entropy2d in 12 papers ptsemseg/loss/loss.py ran MIT (permissive) · 187e0bb11e846d2d · report fixture: signature input:Tensor/4/float, target:Tensor/3/int, weight:Tensor/1/float, size_average:bool/0/bool · returned Tensor · level recorded 2026-09-24
generate_noise in 8 papers ptsemseg/process_img.py ran fingerprinted MIT (permissive) · a381497cf6bcb48b · report fixture: signature img:Tensor/4/float, noisy_type:str/0/str · returned Tensor · level recorded 2026-09-24
get_interp_size ptsemseg/models/utils.py ran; the contract check could not run (RAISES) MIT (permissive) here; the stored copy is pointer only · 80a82d5149279cdf · report fixture: signature input:Tensor/4/float, s_factor:int/0/int, z_factor:int/0/int · returned tuple · level recorded 2026-09-24
get_vectorize_grad ptsemseg/probe.py ran MIT (permissive) · eb2e6c0fa0a0b86d · report fixture: signature model_parameter:list/1/Tensor · returned Tensor · level recorded 2026-09-24
interp in 22 papers ptsemseg/models/utils.py ran MIT (permissive) · aed5a907c8821d6d · report fixture: signature input:Tensor/4/float, output_size:tuple/1/int, mode:str/0/str · returned Tensor · level recorded 2026-09-25
label_region_n_compute_distance ptsemseg/loader/airsim_loader.py ran MIT (permissive) · fba01581708d4ed6 · report fixture: signature i:int/0/int, path_tuple:tuple/1/tuple · returned tuple · level recorded 2026-09-24
multi_scale_cross_entropy2d ptsemseg/loss/loss.py ran MIT (permissive) · 74ffafeffc94fe17 · report fixture: signature input:tuple/1/Tensor, target:Tensor/3/int, weight:Tensor/1/float, size_average:bool/0/bool, scale_weight:NoneType/0/? · returned Tensor · level recorded 2026-09-24
recursive_glob in 12 papers ptsemseg/utils.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · f1e67bfcea91df50 · report fixture: signature rootdir:str/0/str, suffix:str/0/str · returned list · level recorded 2026-09-24
get_upsampling_weight in 13 papers ptsemseg/models/utils.py unverified MIT (permissive) here; the stored copy is pointer only · 68f02849ad3eb678 · report
recursive_glob in 12 papers ptsemseg/process_img.py unverified MIT (permissive) · aa49d29b2460409a · report

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