Papers › Multi-View Radar Semantic Segmentation

Multi-View Radar Semantic Segmentation

30 Mar 2021ICCV 2021 10arXiv:2103.16214archive 2025-07-28

Arthur Ouaknine, Alasdair Newson, Patrick Pérez, Florence Tupin, Julien Rebut

Understanding the scene around the ego-vehicle is key to assisted and autonomous driving. Nowadays, this is mostly conducted using cameras and laser scanners, despite their reduced performances in adverse weather conditions. Automotive radars are low-cost active sensors that measure properties of surrounding objects, including their relative speed, and have the key advantage of not being impacted by rain, snow or fog. However, they are seldom used for scene understanding due to the size and complexity of radar raw data and the lack of annotated datasets. Fortunately, recent open-sourced datasets have opened up research on classification, object detection and semantic segmentation with raw radar signals using end-to-end trainable models. In this work, we propose several novel architectures, and their associated losses, which analyse multiple "views" of the range-angle-Doppler radar tensor to segment it semantically. Experiments conducted on the recent CARRADA dataset demonstrate that our best model outperforms alternative models, derived either from the semantic segmentation of natural images or from radar scene understanding, while requiring significantly fewer parameters. Both our code and trained models are available at https://github.com/valeoai/MVRSS.

PaperPDFConference PDFCodeCode 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

The archive's official repository (valeoai/MVRSS) was not harvested; the 13 samples below come from 3 community repositories.

Syntology 13 code samples harvested from 3 repositories linked to this paper: 9 ran (of which 7 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 2 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

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

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

valeoai/MVRSS officialmentioned in papermentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
SaifeddineBarkia/Multi-view-radar-semantic-segmentation-for-scene-understanding-in-autonomous-driving mentioned on GitHubpytorchSyntology: 6 samples, 6 ran (0 instrument-failed) · 0 unverified report
zlw9161/carrada-rac mentioned on GitHubSyntology: 2 samples, 2 ran (2 instrument-failed) · 0 unverified report
zlw9161/pkc mentioned on GitHubpytorchSyntology: 5 samples, 1 ran (0 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

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

2ran; the contract check could not run
7ran
4unverified

Licence: 13 of the 13 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 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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 2 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.

SaifeddineBarkia/Multi-view-radar-semantic-segmentation-for-scene-understanding-in-autonomous-driving community (archive-listed) 6 samples, 6 ran (0 instrument-failed) · 0 unverified
ASPPBlock mvrss/models/tmvanet.py ran licence not identified · pointer only · 6df7b4702a1c0365 · report fixture: returned ASPPBlock · level recorded 2026-09-22
ConvBlock in 61 papers
census: 8 implementations from 8 papers, 6 distinct outputs across 2 buckets, one shared input per bucket
mvrss/models/tmvanet.py ran fingerprinted licence not identified · pointer only · 175c34969327a671 · report fixture: returned ConvBlock · level recorded 2026-09-22
Double3DConvBlock mvrss/models/tmvanet.py ran licence not identified · pointer only · e203bdd4cdd5eca3 · report fixture: returned Double3DConvBlock · level recorded 2026-09-22
DoubleConvBlock mvrss/models/tmvanet.py ran fingerprinted licence not identified · pointer only · c2331301d3f0c3b0 · report fixture: returned DoubleConvBlock · level recorded 2026-09-22
EncodingBranch mvrss/models/tmvanet.py ran licence not identified · pointer only · 19ec7de44730bfb3 · report fixture: returned EncodingBranch · level recorded 2026-09-22
TMVANet mvrss/models/tmvanet.py ran licence not identified · pointer only · f6b77ecfe9098d49 · report fixture: returned TMVANet · level recorded 2026-09-22
zlw9161/carrada-rac community (archive-listed) 2 samples, 2 ran (2 instrument-failed) · 0 unverified
gen_ra_proposals_cfar carrada_dataset/annotation_generators/ra_utils.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic fingerprinted GPL-3.0 (copyleft) · pointer only · b80ccae2717d7b4e · report fixture: signature ra_matrix:ndarray/2/float · returned tuple · level recorded 2026-09-22
ra_threshold_filtering_cfar carrada_dataset/annotation_generators/ra_utils.py ran; the contract check could not run (RAISES) fingerprinted GPL-3.0 (copyleft) · pointer only · cf1d08a4383a5692 · report fixture: signature ra_matrix:ndarray/2/float, top_val0:int/0/int · returned tuple · level recorded 2026-09-22
zlw9161/pkc community (archive-listed) 5 samples, 1 ran (0 instrument-failed) · 4 unverified
PeakConv2D mvrss/models/pkcon.py ran no licence file found · pointer only · 483ce3e00a405fbf · report fixture: returned PeakConv2D · level recorded 2026-09-22
DoublePeakConv2D mvrss/models/pkcon.py unverified no licence file found · pointer only · 2fc4d17bcde0f4ba · report
DoubleTPKCBlock mvrss/models/pkcon.py unverified no licence file found · pointer only · 4920b9ab40e22283 · report
EncodingBranch mvrss/models/pkcon.py unverified no licence file found · pointer only · 23bef5ace6ac07c9 · report
PKCOn mvrss/models/pkcon.py unverified no licence file found · pointer only · 99d17cebe30f0f9f · 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. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.

3 assemblies on this paper: 3 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).

3 sibling assemblies for Multi-View Radar Semantic Segmentation (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for Multi-View Radar Semantic Segmentation (graph method: Multi-View Radar Semantic Segmentation). 6 bricks; individually on a fixture: 6 ran (of which 6 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; every one of the 6 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

one of 3 siblings

  1. TMVANet entry · level 1 · ran · f6b77ecfe9098d49
  2. ASPPBlock model · level 1 · ran · 6df7b4702a1c0365
  3. ConvBlock helper · level 1 · ran · 175c34969327a671
  4. DoubleConvBlock helper · level 1 · ran · c2331301d3f0c3b0
  5. EncodingBranch model · level 1 · ran · 19ec7de44730bfb3
  6. Double3DConvBlock helper · level 1 · ran · e203bdd4cdd5eca3

harvested Assembly for Multi-View Radar Semantic Segmentation (graph method: Multi-View Radar Semantic Segmentation). 8 bricks; individually on a fixture: 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) · 4 unverified; every one of the 4 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

one of 3 siblings

  1. PKCOn entry · level 0 · unverified · 99d17cebe30f0f9f
  2. ASPPBlock model · level 1 · ran · 6df7b4702a1c0365
  3. ConvBlock helper · level 1 · ran · 175c34969327a671
  4. DoubleConvBlock helper · level 1 · ran · c2331301d3f0c3b0
  5. EncodingBranch model · level 0 · unverified · 23bef5ace6ac07c9
  6. DoublePeakConv2D model · level 0 · unverified · 2fc4d17bcde0f4ba
  7. DoubleTPKCBlock model · level 0 · unverified · 4920b9ab40e22283
  8. PeakConv2D model · level 1 · ran · 483ce3e00a405fbf

harvested Assembly for Multi-View Radar Semantic Segmentation (graph method: Multi-View Radar Semantic Segmentation). 2 bricks; individually on a fixture: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

one of 3 siblings

  1. gen_ra_proposals_cfar entry · level 1 · ran; the contract check could not run (RAISES) · b80ccae2717d7b4e
  2. ra_threshold_filtering_cfar helper · level 1 · ran; the contract check could not run (RAISES) · cf1d08a4383a5692

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

Tasks

Autonomous DrivingObject DetectionScene UnderstandingSegmentationSemantic Segmentationobject-detection

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