SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2305.04276 · 2023

AdaptiveClick: Clicks-aware Transformer with Adaptive Focal Loss for Interactive Image Segmentation

arXiv · PDF · Open in the Atlas

Code that ran

4 of 4 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 1 has no contract verdict; 3 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/2305.04276.json · badge: /api/ran/2305.04276.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
lab206/adaptiveclick canonical (classifier label)
classifier basis: census
4 ran · 0 no recorded run
FunctionStatusWhere it lives
dice_loss Ran
ran; our contract draft was wrong, not the code
lab206/adaptiveclick/isegm/model/criterion.py
code served (permissive licence) · get_code("89f75e54ff128be0")
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 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 torch

torch.manual_seed(0)

# Create small tensors for inputs and targets
# inputs should be arbitrary shape that can be flattened
inputs = torch.randn(2, 4, requires_grad=False)  # batch_size=2, features=4
targets = torch.randint(0, 2, (2, 4), dtype=torch.float32)  # same shape as inputs, binary labels

# num_masks is a float representing the number of masks for normalization
num_masks = 2.0

ARGS = {
    "inputs": inputs,
    "targets": targets,
    "num_masks": num_masks,
}
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 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
handle_exception Ran
ran; our contract draft was wrong, not the code
lab206/adaptiveclick/interactive_demo/canvas.py
code served (permissive licence) · get_code("954d2116dbc85a7b")
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 function. 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 sys
import torch
import torch.nn as nn

torch.manual_seed(0)

# Analyze the function:
# handle_exception takes one parameter: exit_code (default 0)
# It returns a decorator that wraps functions
# The decorator catches exceptions and optionally calls sys.exit(exit_code)
# To test this, we need to provide an exit_code value

# Create a simple test function to decorate
def sample_function():
    """A simple function that can be decorated"""
    return "success"

def sample_function_with_error():
    """A function that raises an exception"""
    raise ValueError("Test exception")

ARGS = {
    "exit_code": 0
}
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 function — a function output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a function 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
sigmoid_ce_loss Ran
ran; our contract draft was wrong, not the code
lab206/adaptiveclick/isegm/model/criterion.py
code served (permissive licence) · get_code("d0c61e8dba511aa3")
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 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 torch
import torch.nn.functional as F

torch.manual_seed(0)

# Create small tensors for inputs and targets
# inputs: predictions (logits), arbitrary shape
# targets: binary labels (0 or 1), same shape as inputs
batch_size = 2
num_elements = 4

inputs = torch.randn(batch_size, num_elements, dtype=torch.float32)
targets = torch.randint(0, 2, (batch_size, num_elements), dtype=torch.float32)

# num_masks: used as divisor in the loss computation
num_masks = 2.0

ARGS = {
    "inputs": inputs,
    "targets": targets,
    "num_masks": num_masks,
}
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 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
sigmoid_focal_loss Ran
ran on a synthesized input
lab206/adaptiveclick/isegm/model/criterion.py
code served (permissive licence) · get_code("71e149dc0c33b040")
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 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 torch
import torch.nn.functional as F

torch.manual_seed(0)

# Create small test tensors
# inputs: predictions (logits), shape [batch_size, num_elements]
# targets: binary labels, shape [batch_size, num_elements]
batch_size = 2
num_elements = 4

inputs = torch.randn(batch_size, num_elements, dtype=torch.float32)
targets = torch.randint(0, 2, (batch_size, num_elements), dtype=torch.float32)

# num_masks: normalization factor (positive integer)
num_masks = 3

ARGS = {
    "inputs": inputs,
    "targets": targets,
    "num_masks": num_masks,
    "alpha": 0.25,
    "gamma": 2.0
}
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 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

Also present in other papers' code

Of 4 samples lifted from this paper's linked repositories, 4 carry a function identity and 0 do not. Of the 4 distinct functions with an identity, 4 are also present in other papers whose code we hold (4 with at least one paper dated earlier, 0 the same month, 4 later) and 0 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
dice_loss 46 other papers
11 dated earlier, 32 later, 3 same year, order not determinable
2112.01527 (2021-12)
Masked-attention Mask Transformer for Universal Image Segmentation
2112.10764 (2021-12)
Mask2Former for Video Instance Segmentation
2203.03605 (2022-03)
DINO: DETR with Improved DeNoising Anchor Boxes for End-to-End Object Detection
and 43 more not named here
sigmoid_ce_loss 45 other papers
10 dated earlier, 32 later, 3 same year, order not determinable
2112.01527 (2021-12)
Masked-attention Mask Transformer for Universal Image Segmentation
2112.10764 (2021-12)
Mask2Former for Video Instance Segmentation
2203.03605 (2022-03)
DINO: DETR with Improved DeNoising Anchor Boxes for End-to-End Object Detection
and 42 more not named here
sigmoid_focal_loss 4 other papers
2 dated earlier, 2 later
2111.14821 (2021-11)
End-to-End Referring Video Object Segmentation with Multimodal Transformers
2211.16799 (2022-11)
NOPE-SAC: Neural One-Plane RANSAC for Sparse-View Planar 3D Reconstruction
2308.01045 (2023-08)
Dynamic Token Pruning in Plain Vision Transformers for Semantic Segmentation
and 1 more not named here
handle_exception 3 other papers
1 dated earlier, 2 later
2210.11006 (2022-10)
SimpleClick: Interactive Image Segmentation with Simple Vision Transformers
2404.00741 (2024-04)
Rethinking Interactive Image Segmentation with Low Latency, High Quality, and Diverse Prompts
2405.00587 (2024-05)
GraCo: Granularity-Controllable Interactive Segmentation

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

Interactive Image Segmentation (IIS) has emerged as a promising technique for decreasing annotation time. Substantial progress has been made in pre- and post-processing for IIS, but the critical issue of interaction ambiguity, notably hindering segmentation quality, has been under-researched. To address this, we introduce AdaptiveClick -- a click-aware transformer incorporating an adaptive focal loss that tackles annotation inconsistencies with tools for mask- and pixel-level ambiguity resolution. To the best of our knowledge, AdaptiveClick is the first transformer-based, mask-adaptive segmentation framework for IIS. The key ingredient of our method is the Click-Aware Mask-adaptive transformer Decoder (CAMD), which enhances the interaction between click and image features. Additionally, AdaptiveClick enables pixel-adaptive differentiation of hard and easy samples in the decision space, independent of their varying distributions. This is primarily achieved by optimizing a generalized Adaptive Focal Loss (AFL) with a theoretical guarantee, where two adaptive coefficients control the ratio of gradient values for hard and easy pixels. Our analysis reveals that the commonly used Focal and BCE losses can be considered special cases of the proposed AFL. With a plain ViT backbone, extensive experimental results on nine datasets demonstrate the superiority of AdaptiveClick compared to state-of-the-art methods. The source code is publicly available at https://github.com/lab206/AdaptiveClick.

For agents

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

get_harvested_code_for_paper("2305.04276")
get_code_for_paper("2305.04276")
have("2305.04276")

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

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

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

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

Connect an agent — have() is free.