Papers › FlowNet3D: Learning Scene Flow in 3D Point Clouds

FlowNet3D: Learning Scene Flow in 3D Point Clouds

4 Jun 2018CVPR 2019 6arXiv:1806.01411archive 2025-07-28

Xingyu Liu, Charles R. Qi, Leonidas J. Guibas

Many applications in robotics and human-computer interaction can benefit from understanding 3D motion of points in a dynamic environment, widely noted as scene flow. While most previous methods focus on stereo and RGB-D images as input, few try to estimate scene flow directly from point clouds. In this work, we propose a novel deep neural network named FlowNet3D that learns scene flow from point clouds in an end-to-end fashion. Our network simultaneously learns deep hierarchical features of point clouds and flow embeddings that represent point motions, supported by two newly proposed learning layers for point sets. We evaluate the network on both challenging synthetic data from FlyingThings3D and real Lidar scans from KITTI. Trained on synthetic data only, our network successfully generalizes to real scans, outperforming various baselines and showing competitive results to the prior art. We also demonstrate two applications of our scene flow output (scan registration and motion segmentation) to show its potential wide use cases.

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 7 code samples harvested from 2 repositories linked to this paper: 5 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 2 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: official repository: 1 sample from 1 repository, 1 ran (0 with no instrument failure; 1 where Syntology's instrument failed); community (archive-listed): 6 samples from 1 repository, 4 ran (3 with no instrument failure; 1 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 3 of its repositories that Syntology harvested for other papers:

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.

xingyul/flownet3d officialtfSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
iremarpag/Comp423 mentioned on GitHubtfSyntology: not harvested report
iremarpag/Computer-Vision-for-Autonomous-Driving mentioned on GitHubpytorchSyntology: not harvested report
multimodallearning/flownet3d.pytorch mentioned on GitHubpytorchSyntology: not harvested report
rabbityl/DeformingThings4D mentioned on GitHubSyntology: not harvested report
valeoai/FLOT mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to FLOT: Scene Flow on Point Clouds Guided by Optimal Transport (arXiv:2007.11142; that paper's own run record: 0 ran · 2 unverified); nothing checks that they implement this paper's method. report
vinits5/learning3d mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to PointNet: Deep Learning on Point Sets for 3D Classification and Segmentation (arXiv:1612.00593; that paper's own run record: 103 ran (of which 45 constructed an object rather than computing a result; 74 with no instrument failure: 0 honoured, 0 violated, 74 with no contract checked; 29 where Syntology's instrument failed) · 61 unverified), Dynamic Graph CNN for Learning on Point Clouds (arXiv:1801.07829; that paper's own run record: 16 ran (of which 5 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 9 where Syntology's instrument failed) · 28 unverified), PointConv: Deep Convolutional Networks on 3D Point Clouds (arXiv:1811.07246; that paper's own run record: 14 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 3 honoured, 0 violated, 1 with no contract checked; 10 where Syntology's instrument failed) · 1 unverified) and 1 more (every one in this page's JSON twin); nothing checks that they implement this paper's method. report
xingyul/cpnet mentioned on GitHubtfNOASSERTIONSyntology: not harvested report
xingyul/meteornet mentioned on GitHubtfSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to MeteorNet: Deep Learning on Dynamic 3D Point Cloud Sequences (arXiv:1910.09165; that paper's own run record: 3 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; 3 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
hyangwinter/flownet3d_pytorch pytorchMITSyntology: 6 samples, 4 ran (1 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

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

2ran; the contract check could not run
3ran
2unverified

Licence: 1 of the 7 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, 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 2 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”. “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.

xingyul/flownet3d official repository 1 sample, 1 ran (1 instrument-failed) · 0 unverified
scene_flow_EPE_np evaluate.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · ad28e10d41422ea2 · report fixture: signature pred:ndarray/3/float, labels:ndarray/3/float, mask:ndarray/2/bool · returned tuple · level recorded 2026-09-22
hyangwinter/flownet3d_pytorch community (archive-listed) 6 samples, 4 ran (1 instrument-failed) · 2 unverified
jitter_pointcloud in 7 papers data.py ran fingerprinted MIT (permissive) · 0eecf33500f60f91 · report fixture: signature pointcloud:ndarray/2/float, sigma:float/0/float, clip:float/0/float · returned ndarray · level recorded 2026-09-24
quat2mat in 26 papers
census: 5 implementations from 5 papers, 3 distinct outputs across 2 buckets, one shared input per bucket
util.py ran fingerprinted MIT (permissive) · 838e2078ad9224da · report fixture: signature quat:Tensor/2/float · returned Tensor · level recorded 2026-09-24
transform_point_cloud in 6 papers util.py ran MIT (permissive) · 421c2d3aa126a3e8 · report fixture: signature point_cloud:Tensor/3/float, rotation:Tensor/2/float, translation:Tensor/2/float · returned Tensor · level recorded 2026-09-24
translate_pointcloud in 15 papers data.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) here; the stored copy is pointer only · 791051c3e72b67d2 · report fixture: signature pointcloud:ndarray/2/float · returned ndarray · level recorded 2026-09-25
load_data in 700 papers data.py unverified MIT (permissive) · de4ec31e485abce5 · report
npmat2euler util.py unverified MIT (permissive) · 5aaf14d09c81093c · report

Tasks

Motion Segmentation

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