Papers › Flexible 3D Lane Detection by Hierarchical Shape MatchingFlexible 3D Lane Detection by...

Flexible 3D Lane Detection by Hierarchical Shape MatchingFlexible 3D Lane Detection by Hierarchical Shape Matching

13 Aug 2024arXiv:2408.07163archive 2025-07-28

Zhihao Guan, Ruixin Liu, Zejian yuan, Ao Liu, Kun Tang, Tong Zhou, Erlong Li, Chao Zheng, Shuqi Mei

As one of the basic while vital technologies for HD map construction, 3D lane detection is still an open problem due to varying visual conditions, complex typologies, and strict demands for precision. In this paper, an end-to-end flexible and hierarchical lane detector is proposed to precisely predict 3D lane lines from point clouds. Specifically, we design a hierarchical network predicting flexible representations of lane shapes at different levels, simultaneously collecting global instance semantics and avoiding local errors. In the global scope, we propose to regress parametric curves w.r.t adaptive axes that help to make more robust predictions towards complex scenes, while in the local vision the structure of lane segment is detected in each of the dynamic anchor cells sampled along the global predicted curves. Moreover, corresponding global and local shape matching losses and anchor cell generation strategies are designed. Experiments on two datasets show that we overwhelm current top methods under high precision standards, and full ablation studies also verify each part of our method. Our codes will be released at https://github.com/Doo-do/FHLD.

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 10 code samples harvested from 1 repository linked to this paper: 8 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; 1 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 10 samples from 1 repository, 8 ran (7 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.

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

doo-do/fhld officialmentioned in paperpytorchSyntology: 10 samples, 8 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.

Code Syntology ran Syntology

10 samples harvested: 8 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; 1 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
7ran
2unverified

Licence: 0 of the 10 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 doo-do/fhld. “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 5 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.

doo-do/fhld official repository 10 samples, 8 ran (1 instrument-failed) · 2 unverified
BaseConv models/py_utils/network_point.py ran fingerprinted BSD-3-Clause (permissive) · 5016fadc85ccc8b7 · report fixture: returned BaseConv · level recorded 2026-09-22
Bottleneck in 98 papers models/py_utils/network_point.py ran fingerprinted BSD-3-Clause (permissive) · e21f306668b1b117 · report fixture: returned Bottleneck · level recorded 2026-09-22
CSPLayer models/py_utils/network_point.py ran fingerprinted BSD-3-Clause (permissive) · e92f66119f68c563 · report fixture: returned CSPLayer · level recorded 2026-09-22
Conv2D_BatchNorm_Relu models/py_utils/network_point.py ran fingerprinted BSD-3-Clause (permissive) · 0318337c6b18ef55 · report fixture: returned Conv2D_BatchNorm_Relu · level recorded 2026-09-22
DWConv in 14 papers models/py_utils/network_point.py ran fingerprinted BSD-3-Clause (permissive) · c65c73256219c02b · report fixture: returned DWConv · level recorded 2026-09-22
Output models/py_utils/network_point.py ran BSD-3-Clause (permissive) · 8d1df689bce9310d · report fixture: returned Output · level recorded 2026-09-22
Output_mask models/py_utils/network_point.py ran BSD-3-Clause (permissive) · 96e20d71af0cc91b · report fixture: returned Output_mask · level recorded 2026-09-22
get_activation in 218 papers models/py_utils/network_point.py ran · our draft was wrong BSD-3-Clause (permissive) · 6a5a4380075ed801 · report fixture: signature name:str/0/str, inplace:bool/0/bool · returned SiLU · level recorded 2026-09-22
Config in 46 papers models/py_utils/network_point.py unverified BSD-3-Clause (permissive) · f6d143fec97e8f50 · report
network_point models/py_utils/network_point.py unverified BSD-3-Clause (permissive) · acee9f9342baca4e · 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 Flexible 3D Lane Detection by Hierarchical Shape Matching (graph method: Flexible 3D Lane Detection by Hierarchical Shape Matching). 10 bricks; individually on a fixture: 8 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; 1 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. network_point entry · level 0 · unverified · acee9f9342baca4e
  2. BaseConv helper · level 1 · ran · 5016fadc85ccc8b7
  3. CSPLayer helper · level 1 · ran · e92f66119f68c563
  4. Output model · level 1 · ran · 8d1df689bce9310d
  5. Output_mask helper · level 1 · ran · 96e20d71af0cc91b
  6. get_activation helper · level 1 · ran · our draft was wrong · 6a5a4380075ed801
  7. Bottleneck helper · level 1 · ran · e21f306668b1b117
  8. Conv2D_BatchNorm_Relu model · level 1 · ran · 0318337c6b18ef55
  9. DWConv helper · level 1 · ran · c65c73256219c02b
  10. Config helper · level 0 · unverified · f6d143fec97e8f50

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

Tasks

3D Lane DetectionLane 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