SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2002.06604 · 2020

Key Points Estimation and Point Instance Segmentation Approach for Lane Detection

arXiv · PDF · Open in the Atlas

Code that ran

7 of 8 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 6 have no contract verdict; 1 failure of our instrument; 1 no recorded run), measured 2026-11-21; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2002.06604.json · badge: /api/ran/2002.06604.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
koyeongmin/PINet canonical (classifier label)
classifier basis: census
3 ran · 1 no recorded run
pandamax/Lane-Detection-Based-PINet community (classifier label)
classifier basis not recorded on the link
4 ran · 0 no recorded run
FunctionStatusWhere it lives
Rotate_Points Ran
ran on a synthesized input
koyeongmin/PINet/data_loader.py
code served (permissive licence) · get_code("fd57fbb1c2fa7ecf")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import math

# Rotate_Points takes:
# - origin: a tuple of two numbers (ox, oy)
# - point: a tuple of two numbers (px, py)
# - angle: a number (in radians)

origin = (0.0, 0.0)
point = (1.0, 0.0)
angle = math.pi / 4  # 45 degrees in radians

ARGS = {
    'origin': origin,
    'point': point,
    'angle': angle
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
none outside the standard library — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple, ndim 1, dtype family float — a tuple output has no array shape of its own; none is stated
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
Translate_Points Ran
ran on a synthesized input
koyeongmin/PINet/data_loader.py
code served (permissive licence) · get_code("ece40a59cb52c91c")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 2, dtype family float, shape (2, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import numpy as np

torch.manual_seed(0)

# Create small tensors for point and translation
# point: shape (2, 4) - batch of 2 points with 4 dimensions
# translation: shape (2, 4) - translation vector(s)
point = torch.randn(2, 4)
translation = torch.randn(2, 4)

ARGS = {
    "point": point,
    "translation": translation
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 2, dtype family float, shape (2, 4) — shape (2, 4) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
convert_to_original_size Ran
ran on a synthesized input
koyeongmin/PINet/util.py
code served (permissive licence) · get_code("bb96561c0895c102")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple, ndim 3, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import numpy as np

# Analyze the function:
# - x: iterable of items that can be converted to np.array and divided by ratio_w, then .tolist()
# - y: iterable of items that can be converted to np.array and divided by ratio_h, then .tolist()
# - ratio_w: scalar (used for division)
# - ratio_h: scalar (used for division)

# The function iterates over x and y in parallel with zip, converts each element to numpy array,
# divides by ratios, and converts back to list.

# Create sample data
x = [
    [10, 20, 30, 40],
    [50, 60, 70, 80]
]

y = [
    [100, 200, 300, 400],
    [500, 600, 700, 800]
]

ratio_w = 2.0
ratio_h = 4.0

ARGS = {
    "x": x,
    "y": y,
    "ratio_w": ratio_w,
    "ratio_h": ratio_h
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple, ndim 3, dtype family float — a tuple output has no array shape of its own; none is stated
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
crop_img Ran
ran on a synthesized input
pandamax/Lane-Detection-Based-PINet/inference/merged_caffemodel_inference.py
code served (permissive licence) · get_code("1d87d42816416711")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import numpy as np

torch.manual_seed(0)

# Create a small test image tensor
# The function expects temp_image to have shape[0], shape[1], shape[2] attributes
# It indexes with [crop_start_h:crop_end_h, :, :], so it needs 3 dimensions
# Using distinct sizes: (8, 5, 3) for height, width, channels
temp_image = torch.randn(8, 5, 3)

ARGS = {
    "temp_image": temp_image
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple — a tuple output has no array shape of its own; none is stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
eliminate_fewer_points Ran
ran on a synthesized input
pandamax/Lane-Detection-Based-PINet/inference/merged_caffemodel_inference.py
code served (permissive licence) · get_code("76f306f3af07e93e")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import torch.nn as nn

torch.manual_seed(0)

# Analyze the function:
# - x and y are iterables of items
# - The function zips them together
# - For each pair (i, j), it checks len(i) > 2
# - Items that pass are appended to output lists
# - So x contains items with len() method (like lists or tensors)
# - y contains corresponding labels/values

# Create x: list of items with varying lengths
# Some should have len <= 2 (filtered out), some > 2 (kept)
x = [
    [1, 2],           # len=2, filtered out
    [1, 2, 3],        # len=3, kept
    [1],              # len=1, filtered out
    [1, 2, 3, 4, 5],  # len=5, kept
]

# Create y: corresponding labels/values for each item in x
y = ['label_a', 'label_b', 'label_c', 'label_d']

ARGS = {
    'x': x,
    'y': y,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple — a tuple output has no array shape of its own; none is stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
sort_along_y Ran
ran on a synthesized input
pandamax/Lane-Detection-Based-PINet/inference/merged_caffemodel_inference.py
code served (permissive licence) · get_code("63dab5202594bf68")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple, ndim 4, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import numpy as np

# Construct valid arguments for sort_along_y
# The function takes x and y, which are iterables of arrays
# It sorts along the y values in descending order and returns sorted (out_x, out_y)

# Create sample x data - list of 2D arrays
x = [
    np.array([[1.0, 2.0, 3.0, 4.0],
              [5.0, 6.0, 7.0, 8.0]]),
    np.array([[9.0, 10.0, 11.0, 12.0],
              [13.0, 14.0, 15.0, 16.0]])
]

# Create sample y data - list of 2D arrays with values to sort by
y = [
    np.array([[0.5, 0.2, 0.9, 0.1],
              [0.3, 0.7, 0.4, 0.6]]),
    np.array([[0.8, 0.1, 0.5, 0.9],
              [0.2, 0.6, 0.3, 0.7]])
]

ARGS = {
    'x': x,
    'y': y
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple, ndim 4, dtype family float — a tuple output has no array shape of its own; none is stated
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
to_numpy Ran
ran; our contract draft was wrong, not the code
pandamax/Lane-Detection-Based-PINet/inference/diff_pytorch_caffemodel.py
code served (permissive licence) · get_code("9d103c391b8dbe33")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned ndarray, ndim 2, dtype family float, shape (2, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch

torch.manual_seed(0)

# Create a small tensor with requires_grad=True to test the gradient case
tensor_with_grad = torch.randn(2, 4, requires_grad=True)

ARGS = {
    "tensor": tensor_with_grad
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 2, dtype family float, shape (2, 4) — shape (2, 4) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
cross_entropy2d Not yet run
unverified (harvested, no recorded run)
koyeongmin/PINet/util_hourglass.py
code served (permissive licence) · get_code("57e9d54adac6bc85")
How it ran

no invocation recorded.

Also present in other papers' code

Of 8 samples lifted from this paper's linked repositories, 8 carry a function identity and 0 do not. Of the 8 distinct functions with an identity, 1 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 1 later) and 7 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

FunctionAlso present inEarliest-datedOthers named
to_numpy 2 other papers
2 later
2003.00482 (2020-03)
State-Aware Tracker for Real-Time Video Object Segmentation
2308.06904 (2023-08)
Exploring Lightweight Hierarchical Vision Transformers for Efficient Visual Tracking

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-21.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Perception techniques for autonomous driving should be adaptive to various environments. In the case of traffic line detection, an essential perception module, many condition should be considered, such as number of traffic lines and computing power of the target system. To address these problems, in this paper, we propose a traffic line detection method called Point Instance Network (PINet); the method is based on the key points estimation and instance segmentation approach. The PINet includes several stacked hourglass networks that are trained simultaneously. Therefore the size of the trained models can be chosen according to the computing power of the target environment. We cast a clustering problem of the predicted key points as an instance segmentation problem; the PINet can be trained regardless of the number of the traffic lines. The PINet achieves competitive accuracy and false positive on the TuSimple and Culane datasets, popular public datasets for lane detection. Our code is available at https://github.com/koyeongmin/PINet_new

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2002.06604")
get_code_for_paper("2002.06604")
have("2002.06604")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2002.06604.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2002.06604.svg)](https://syntology.ai/paper/2002.06604)

Connect an agent — have() is free.