SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2103.14962 · CVPR · 2021

Panoptic-PolarNet: Proposal-free LiDAR Point Cloud Panoptic Segmentation

Yang Zhang, Hassan Foroosh, Zixiang Zhou

arXiv · PDF · Open in the Atlas

Code that ran

11 of 11 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; 3 honoured the contract we drafted, 1 violated it and 0 have no contract verdict; 7 failures of our instrument; 0 no recorded run), measured 2026-11-22; 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/2103.14962.json · badge: /api/ran/2103.14962.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
edwardzhou130/Panoptic-PolarNet canonical (classifier label)
classifier basis: census
11 ran · 0 no recorded run
FunctionStatusWhere it lives
cart2polar Ran
ran, honoured the contract we drafted
edwardzhou130/Panoptic-PolarNet/dataloader/dataset.py
code served (permissive licence) · get_code("4cbfcba4a545864d")
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, 3) 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 numpy as np

# Create a small sample of 3D Cartesian coordinates (batch of 2, with x, y, z)
input_xyz = np.array([
    [1.0, 2.0, 3.0],
    [4.0, 5.0, 6.0]
], dtype=np.float32)

ARGS = {
    'input_xyz': input_xyz
}
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 ndarray, ndim 2, dtype family float, shape (2, 3) — shape (2, 3) 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
find_instance_center Ran
ran; our contract draft was wrong, not the code
edwardzhou130/Panoptic-PolarNet/network/instance_post_processing.py
code served (permissive licence) · get_code("fc243db80e389fd9")
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 int, shape (1, 2) 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 torch.nn.functional as F

torch.manual_seed(0)

# Create a small center heatmap tensor
# Shape: [N, 1, H, W] where N=1 (batch size must be 1), C=1, H=4, W=3
ctr_hmp = torch.rand(1, 1, 4, 3) * 0.5 + 0.05  # Values between 0.05 and 0.55

# Set some values above threshold to ensure we have detectable centers
ctr_hmp[0, 0, 1, 1] = 0.8
ctr_hmp[0, 0, 2, 2] = 0.7
ctr_hmp[0, 0, 3, 0] = 0.6

ARGS = {
    'ctr_hmp': ctr_hmp,
    'threshold': 0.1,
    'nms_kernel': 5,
    'top_k': None,
    'polar': False
}
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 Tensor, ndim 2, dtype family int, shape (1, 2) — shape (1, 2) 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
flow_to_img Ran
ran, honoured the contract we drafted
edwardzhou130/Panoptic-PolarNet/utils/visual.py
code served (permissive licence) · get_code("c6bec7161a69d697")
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 3, dtype family int, shape (4, 3, 3) 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 cv2
import numpy as np

# Create a small optical flow array
# flow should be of shape (height, width, 2) where the last dimension contains (dx, dy) components
height, width = 4, 3
flow = np.random.randn(height, width, 2).astype(np.float32)

ARGS = {
    "flow": flow,
    "normalize": True,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
cv2, numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 3, dtype family int, shape (4, 3, 3) — shape (4, 3, 3) 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
get_instance_segmentation Ran
ran; our contract draft was wrong, not the code
edwardzhou130/Panoptic-PolarNet/network/instance_post_processing.py
code served (permissive licence) · get_code("d82bcfb095aecca2")
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.functional as F

torch.manual_seed(0)

# Create small tensors with distinct dimensions
batch_size = 1
height = 4
width = 3
num_classes = 2

# sem_seg: [1, H, W, Z] - semantic segmentation prediction
sem_seg = torch.randint(0, num_classes, (batch_size, height, width, num_classes))

# ctr_hmp: [N, 1, H, W] - center heatmap (batch size must be 1)
ctr_hmp = torch.rand(batch_size, 1, height, width)

# offsets: [N, 2, H, W] - offset predictions (batch size must be 1)
offsets = torch.randn(batch_size, 2, height, width)

# thing_list: list of thing class ids
thing_list = [0, 1]

# thing_seg: [1, H, W, Z] - foreground mask (optional, can be inferred)
thing_seg = torch.randint(0, 2, (batch_size, height, width, num_classes))

ARGS = {
    'sem_seg': sem_seg,
    'ctr_hmp': ctr_hmp,
    'offsets': offsets,
    'thing_list': thing_list,
    'threshold': 0.1,
    'nms_kernel': 3,
    'top_k': 2,
    'thing_seg': thing_seg,
    'polar': False
}
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
group_pixels Ran
ran; our contract draft was wrong, not the code
edwardzhou130/Panoptic-PolarNet/network/instance_post_processing.py
code served (permissive licence) · get_code("7291f525ec6a9e79")
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 3, dtype family int, shape (1, 4, 5) 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)

# ctr: A Tensor of shape [K, 2] where K is the number of center points
# The order of second dim is (y, x)
ctr = torch.tensor([
    [2.0, 3.0],
    [5.0, 4.0],
    [1.0, 6.0]
], dtype=torch.float32)

# offsets: A Tensor of shape [N, 2, H, W] of raw offset output
# N must be 1 (batch size), 2 is (offset_y, offset_x), H and W are height/width
offsets = torch.randn(1, 2, 4, 5, dtype=torch.float32)

# polar: boolean flag
polar = False

ARGS = {
    'ctr': ctr,
    'offsets': offsets,
    'polar': polar
}
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 Tensor, ndim 3, dtype family int, shape (1, 4, 5) — shape (1, 4, 5) 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
grp_range_torch Ran
ran; our contract draft was wrong, not the code
edwardzhou130/Panoptic-PolarNet/network/ptBEV.py
code served (permissive licence) · get_code("bb6f31439534fc4b")
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 1, dtype family int, shape (6,) 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 `a` for the group range function
# This should be a 1D tensor of positive integers representing group sizes
a = torch.tensor([2, 3, 1], dtype=torch.int64)

# Device should be CPU
dev = 'cpu'

ARGS = {
    'a': a,
    'dev': dev
}
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 Tensor, ndim 1, dtype family int, shape (6,) — shape (6,) 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
iou Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
edwardzhou130/Panoptic-PolarNet/network/lovasz_losses.py
code served (permissive licence) · get_code("d94639b28b2134ff")
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 1, dtype family float, shape (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 numpy as np
import torch

torch.manual_seed(0)

# Construct valid arguments for the iou function
# preds: prediction array/tensor with class indices
# labels: ground truth array/tensor with class indices
# C: number of classes
# EMPTY: value to return for empty unions (default 1.0)
# ignore: class index to ignore (default None)
# per_image: whether to compute per-image IoU (default False)

# Create small prediction and label arrays
# Using shape (2, 4) - batch of 2, spatial dimension of 4
preds = np.array([[0, 1, 2, 3],
                   [1, 2, 0, 1]], dtype=np.int64)

labels = np.array([[0, 1, 1, 3],
                    [1, 2, 2, 1]], dtype=np.int64)

# Number of classes
C = 4

# EMPTY value for classes with no union
EMPTY = 1.0

# Class to ignore during computation
ignore = None

# Whether to compute per-image IoU
per_image = False

ARGS = {
    "preds": preds,
    "labels": labels,
    "C": C,
    "EMPTY": EMPTY,
    "ignore": ignore,
    "per_image": per_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 ndarray, ndim 1, dtype family float, shape (4,) — shape (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
iou_binary Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
edwardzhou130/Panoptic-PolarNet/network/lovasz_losses.py
code served (permissive licence) · get_code("1211530cd527bd0b")
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 float, ndim 0, dtype family float, shape () 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 numpy as np

def isnan(x):
    return x != x

def mean(l, ignore_nan=False, empty=0):
    """
    nanmean compatible with generators.
    """
    l = iter(l)
    if ignore_nan:
        from itertools import filterfalse
        l = filterfalse(isnan, l)
    try:
        n = 1
        acc = next(l)
    except StopIteration:
        if empty == 'raise':
            raise ValueError('Empty mean')
        return empty
    for n, v in enumerate(l, 2):
        acc += v
    if n == 1:
        return acc
    return acc / n

def iou_binary(preds, labels, EMPTY=1.0, ignore=None, per_image=True):
    """
    IoU for foreground class
    binary: 1 foreground, 0 background
    """
    if not per_image:
        preds, labels = ((preds,), (labels,))
    ious = []
    for pred, label in zip(preds, labels):
        intersection = ((label == 1) & (pred == 1)).sum()
        union = ((label == 1) | (pred == 1) & (label != ignore)).sum()
        if not union:
            iou = EMPTY
        else:
            iou = float(intersection) / float(union)
        ious.append(iou)
    iou = mean(ious)
    return 100 * iou

# Setup code
np.random.seed(0)

# Create small prediction and label arrays for binary segmentation
# Shape: (height=4, width=3) for two images
preds_img1 = np.array([[0, 1, 1],
                       [1, 1, 0],
                       [0, 1, 1],
                       [1, 0, 0]], dtype=np.int32)

labels_img1 = np.array([[0, 1, 0],
                        [1, 1, 1],
                        [0, 1, 0],
                        [1, 0, 1]], dtype=np.int32)

preds_img2 = np.array([[1, 1, 0],
                       [0, 1, 1],
                       [1, 1, 0],
                       [0, 0, 1]], dtype=np.int32)

labels_img2 = np.array([[1, 0, 0],
                        [0, 1, 1],
                        [1, 0, 0],
                        [0, 1, 1]], dtype=np.int32)

# Arguments for iou_binary function
ARGS = {
    'preds': np.array([preds_img1, preds_img2]),
    'labels': np.array([labels_img1, labels_img2]),
    'EMPTY': 1.0,
    'ignore': 0,
    'per_image': True,
}
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 float, ndim 0, dtype family float, shape () — shape () 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
lovasz_grad Ran
ran, violated the contract we drafted
edwardzhou130/Panoptic-PolarNet/network/lovasz_losses.py
code served (permissive licence) · get_code("e85b5d21dc5b8382")
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 1, dtype family float, shape (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)

# gt_sorted should be a 1D tensor of binary/boolean values
# representing ground truth sorted by some error metric
# The function expects a tensor with sum(), float(), cumsum() methods
gt_sorted = torch.tensor([0, 0, 1, 1], dtype=torch.long)

ARGS = {
    "gt_sorted": gt_sorted
}
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 Tensor, ndim 1, dtype family float, shape (4,) — shape (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
merge_configs Ran
ran; our contract draft was wrong, not the code
edwardzhou130/Panoptic-PolarNet/utils/configs.py
code served (permissive licence) · get_code("493b63fa4db39051")
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 dict. 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

class ConfigObj:
    """Stand-in config object that can have arbitrary attributes."""
    def __init__(self, **kwargs):
        for key, value in kwargs.items():
            setattr(self, key, value)

# Create cfgs object with optional attributes
cfgs = ConfigObj(
    data_dir="/path/to/data",
    model_save_path="/path/to/model.pt",
    pretrained_model="/path/to/pretrained.pt"
)

# Create new_cfgs dict with nested structure
new_cfgs = {
    'dataset': {
        'path': '/default/path'
    },
    'model': {
        'model_save_path': '/default/model.pt',
        'pretrained_model': '/default/pretrained.pt'
    }
}

ARGS = {
    'cfgs': cfgs,
    'new_cfgs': new_cfgs
}
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 dict — a dict output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a dict output the recorded ndim 0 and dtype family float describe that coercion, not the output, and are not 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
polar2cat Ran
ran, honoured the contract we drafted
edwardzhou130/Panoptic-PolarNet/dataloader/dataset.py
code served (permissive licence) · get_code("dd197502413d486a")
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 (3, 2) 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 numpy as np

# The function polar2cat takes input_xyz_polar which is indexed as:
# input_xyz_polar[0] - radius/rho component
# input_xyz_polar[1] - angle/theta component
# input_xyz_polar[2] - z component (height)
# These are used with np.cos, np.sin, and np.stack operations

# Create a simple input: array with shape (3,) or (3, batch_size)
# Using shape (3, 2) for batched polar coordinates
radius = np.array([1.0, 2.0])
angle = np.array([0.0, np.pi/4])
z = np.array([0.5, 1.5])

input_xyz_polar = np.stack((radius, angle, z), axis=0)

ARGS = {
    "input_xyz_polar": input_xyz_polar
}
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 ndarray, ndim 2, dtype family float, shape (3, 2) — shape (3, 2) 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

Also present in other papers' code

Of 11 samples lifted from this paper's linked repositories, 11 carry a function identity and 0 do not. Of the 11 distinct functions with an identity, 6 are also present in other papers whose code we hold (6 with at least one paper dated earlier, 0 the same month, 6 later) and 5 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
lovasz_grad 40 other papers
8 dated earlier, 32 later · 1 only as an assembly brick
1505.04597 (2015-05)
U-Net: Convolutional Networks for Biomedical Image Segmentation
1807.10165 (2018-07)
UNet++: A Nested U-Net Architecture for Medical Image Segmentation
1811.11721 (2018-11)
CCNet: Criss-Cross Attention for Semantic Segmentation
and 37 more not named here
iou 24 other papers
5 dated earlier, 19 later
1807.10165 (2018-07)
UNet++: A Nested U-Net Architecture for Medical Image Segmentation
1811.11721 (2018-11)
CCNet: Criss-Cross Attention for Semantic Segmentation
2003.10778 (2020-03)
PanNuke Dataset Extension, Insights and Baselines
and 21 more not named here
iou_binary 24 other papers
5 dated earlier, 19 later
1807.10165 (2018-07)
UNet++: A Nested U-Net Architecture for Medical Image Segmentation
1811.11721 (2018-11)
CCNet: Criss-Cross Attention for Semantic Segmentation
2003.10778 (2020-03)
PanNuke Dataset Extension, Insights and Baselines
and 21 more not named here
cart2polar 3 other papers
1 dated earlier, 2 later
2003.14032 (2020-03)
PolarNet: An Improved Grid Representation for Online LiDAR Point Clouds Semantic Segmentation
2109.05441 (2021-09)
Cylindrical and Asymmetrical 3D Convolution Networks for LiDAR-based Perception
2308.01686 (2023-08)
LiDAR-Camera Panoptic Segmentation via Geometry-Consistent and Semantic-Aware Alignment
polar2cat 3 other papers
1 dated earlier, 2 later
2003.14032 (2020-03)
PolarNet: An Improved Grid Representation for Online LiDAR Point Clouds Semantic Segmentation
2109.05441 (2021-09)
Cylindrical and Asymmetrical 3D Convolution Networks for LiDAR-based Perception
2308.01686 (2023-08)
LiDAR-Camera Panoptic Segmentation via Geometry-Consistent and Semantic-Aware Alignment
grp_range_torch 2 other papers
1 dated earlier, 1 later
2003.14032 (2020-03)
PolarNet: An Improved Grid Representation for Online LiDAR Point Clouds Semantic Segmentation
2308.01686 (2023-08)
LiDAR-Camera Panoptic Segmentation via Geometry-Consistent and Semantic-Aware Alignment

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-22.

Repositories linked to this paper

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

Abstract

Panoptic segmentation presents a new challenge in exploiting the merits of both detection and segmentation, with the aim of unifying instance segmentation and semantic segmentation in a single framework. However, an efficient solution for panoptic segmentation in the emerging domain of LiDAR point cloud is still an open research problem and is very much under-explored. In this paper, we present a fast and robust LiDAR point cloud panoptic segmentation framework, referred to as Panoptic-PolarNet. We learn both semantic segmentation and class-agnostic instance clustering in a single inference network using a polar Bird's Eye View (BEV) representation, enabling us to circumvent the issue of occlusion among instances in urban street scenes. To improve our network's learnability, we also propose an adapted instance augmentation technique and a novel adversarial point cloud pruning method. Our experiments show that Panoptic-PolarNet outperforms the baseline methods on SemanticKITTI and nuScenes datasets with an almost real-time inference speed. Panoptic-PolarNet achieved 54.1% PQ in the public SemanticKITTI panoptic segmentation leaderboard and leading performance for the validation set of nuScenes.

For agents

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

get_harvested_code_for_paper("2103.14962")
get_code_for_paper("2103.14962")
have("2103.14962")

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

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

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

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

Connect an agent — have() is free.