Papers › Towards End-to-End Lane Detection: an Instance Segmentation Approach
Towards End-to-End Lane Detection: an Instance Segmentation Approach
Davy Neven, Bert de Brabandere, Stamatios Georgoulis, Marc Proesmans, Luc van Gool
Modern cars are incorporating an increasing number of driver assist features, among which automatic lane keeping. The latter allows the car to properly position itself within the road lanes, which is also crucial for any subsequent lane departure or trajectory planning decision in fully autonomous cars. Traditional lane detection methods rely on a combination of highly-specialized, hand-crafted features and heuristics, usually followed by post-processing techniques, that are computationally expensive and prone to scalability due to road scene variations. More recent approaches leverage deep learning models, trained for pixel-wise lane segmentation, even when no markings are present in the image due to their big receptive field. Despite their advantages, these methods are limited to detecting a pre-defined, fixed number of lanes, e.g. ego-lanes, and can not cope with lane changes. In this paper, we go beyond the aforementioned limitations and propose to cast the lane detection problem as an instance segmentation problem - in which each lane forms its own instance - that can be trained end-to-end. To parametrize the segmented lane instances before fitting the lane, we further propose to apply a learned perspective transformation, conditioned on the image, in contrast to a fixed "bird's-eye view" transformation. By doing so, we ensure a lane fitting which is robust against road plane changes, unlike existing approaches that rely on a fixed, pre-defined transformation. In summary, we propose a fast lane detection algorithm, running at 50 fps, which can handle a variable number of lanes and cope with lane changes. We verify our method on the tuSimple dataset and achieve competitive results.
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):
get_harvested_code_for_paper(arxiv_id="1802.05591")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="1802.05591", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="1802.05591")
Code
Syntology 34 code samples: 33 from 6 repositories linked to this paper, 1 identical to code harvested from another paper's repository. Across all 34: 16 ran (of which 0 constructed an object rather than computing a result; 16 with no instrument failure: 2 honoured, 1 violated, 13 with no contract checked; 0 where Syntology's instrument failed) · 18 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.
By repository: community (archive-listed): 33 samples from 6 repositories, 15 ran (15 with no instrument failure; 0 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. 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-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
22 repositories listed; official and paper-mentioned ones first.
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
34 samples harvested: 16 ran (of which 0 constructed an object rather than computing a result; 16 with no instrument failure: 2 honoured, 1 violated, 13 with no contract checked; 0 where Syntology's instrument failed) · 18 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.
Licence: 2 of the 34 samples are pointer only, meaning Syntology does not serve that copy's text. For 1 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 6 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. 1 sample is listed last, in a group without a repository. “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.
b69809ec726c0388 · report
fixture: signature value:bytes/0/? · returned Feature · level recorded 2026-09-26 f505a06000043773 · report
fixture: signature value:int/0/int · returned Feature · level recorded 2026-09-26 183604870fe9c8d4 · report
00dec105fe4f01ce · report
fd0afd75c819b7e6 · report
fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int, atrous:int/0/int · returned Conv2d · level recorded 2026-09-26 8a2af0442a27e321 · report
fixture: signature pred:Tensor/4/float, target:Tensor/4/float · returned Tensor · level recorded 2026-09-26 2e15559b9d73d461 · report
fixture: signature pretrained:bool/0/bool, os:int/0/int · returned ResNet_Atrous · level recorded 2026-09-26 05ccc649d997c21e · report
fixture: signature pretrained:bool/0/bool, os:int/0/int · returned ResNet_Atrous · level recorded 2026-09-26 census: 2 implementations from 5 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 model/lanenet/train_lanenet.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only ·
7a27709bcab8b8f3 · report
fixture: signature variable:Tensor/2/float · returned Tensor · level recorded 2026-09-22 af03f9caeca5f651 · report
0081d5f06f6dbd99 · report
d96578a3d1da04a2 · report
fixture: signature image:ndarray/2/int, gamma:float/0/float · returned ndarray · level recorded 2026-09-26 2fd5bb4df89f9a50 · report
fixture: signature data_dir:str/0/str, image_shape:tuple/1/int · returned tuple · level recorded 2026-09-26 cbb808498994f295 · report
fixture: signature x:EagerTensor/4/float, p:float/0/float, seed:int/0/int, scope:str/0/str, is_training:bool/0/bool · returned SymbolicTensor · level recorded 2026-09-26 c56423bdcf53292c · report
0884d3e46f716e9e · report
fixture: signature a:float/0/float · returned ndarray · level recorded 2026-09-26 3507ceaedfd6c2f5 · report
fixture: signature a:float/0/float · returned ndarray · level recorded 2026-09-26 f99d82f51d3fa1b9 · report
fixture: signature a:float/0/float · returned ndarray · level recorded 2026-09-26 1971608da6ee2771 · report
fixture: signature input_arr:ndarray/2/float · returned ndarray · level recorded 2026-09-22 b3a22ff74e021b94 · report
fixture: signature x:EagerTensor/4/float, p:float/0/float, seed:int/0/int, scope:str/0/str, is_training:bool/0/bool · returned SymbolicTensor · level recorded 2026-09-26 289fe15b8aee7918 · report
42e6180b7b1164c2 · report
6e8cae7f5bf90dac · report
748bfd352080d1ca · report
cc97231448e8fa54 · report
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
eba8919c2ae4a92f · report
fixture: signature arg_value:str/0/str · returned bool · level recorded 2026-09-22 Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Lane Detection | TuSimple | LaneNet | Accuracy | 96.4% | #19 of 43 | Archive leaderboard | report |
| Lane Detection | TuSimple | LaneNet | F1 score | 94.80 | #19 of 43 | Archive leaderboard | report |
Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.
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