SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 01071 · ECCV · 2024

VISAGE: Video Instance Segmentation with Appearance-Guided Enhancement

Seon Kim, Seoung Oh, Miran Heo, Jaehyun Kang, Hanjung Kim, Sukjun Hwang

Open in the Atlas

Code that ran

1 of 2 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 0 have no contract verdict; 1 failure of our instrument; 1 no recorded run), measured 2026-11-22; 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/01071.json · badge: /api/ran/01071.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
KimHanjung/VISAGE canonical (classifier label)
classifier basis: census
1 ran · 1 no recorded run
FunctionStatusWhere it lives
filter_images_with_only_crowd_annotations Ran
ran; our contract draft was wrong, not the code
KimHanjung/VISAGE/visage/data_video/build.py
code served (permissive licence) · get_code("a21a61e41d986b6a")
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 list, 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 logging

# Set up logging to avoid warnings
logging.basicConfig(level=logging.INFO)

# Create sample dataset_dicts in Detectron2 format
dataset_dicts = [
    {
        'image_id': 1,
        'file_name': 'image1.jpg',
        'annotations': [
            {'id': 1, 'category_id': 1, 'bbox': [10, 20, 100, 150], 'iscrowd': 0},
            {'id': 2, 'category_id': 2, 'bbox': [50, 60, 80, 120], 'iscrowd': 0},
        ]
    },
    {
        'image_id': 2,
        'file_name': 'image2.jpg',
        'annotations': [
            {'id': 3, 'category_id': 1, 'bbox': [30, 40, 120, 160], 'iscrowd': 1},
        ]
    },
    {
        'image_id': 3,
        'file_name': 'image3.jpg',
        'annotations': [
            {'id': 4, 'category_id': 2, 'bbox': [15, 25, 110, 155], 'iscrowd': 0},
        ]
    },
    {
        'image_id': 4,
        'file_name': 'image4.jpg',
        'annotations': []
    },
]

# Create sample dataset_names
dataset_names = ['coco_train', 'coco_val']

ARGS = {
    'dataset_dicts': dataset_dicts,
    'dataset_names': dataset_names,
}
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 list, ndim 1, dtype family float — a list 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
filter_empty_instances Not yet run
unverified (harvested, no recorded run)
KimHanjung/VISAGE/visage/data_video/dataset_mapper.py
code served (permissive licence) · get_code("783873d38889bf2e")
How it ran

no invocation recorded.

Also present in other papers' code

Of 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 distinct functions with an identity, 1 are also present in other papers whose code we hold (1 with at least one paper dated earlier, 0 the same month, 1 later) and 1 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
filter_images_with_only_crowd_annotations 5 other papers
3 dated earlier, 1 later, 1 same year, order not determinable
2306.09347 (2023-06)
Segment Any Point Cloud Sequences by Distilling Vision Foundation Models
2311.00571 (2023-11)
LLaVA-Interactive: An All-in-One Demo for Image Chat, Segmentation, Generation and Editing
2311.01373 (2023-11)
Recognize Any Regions
and 2 more not named here

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

In recent years, online Video Instance Segmentation (VIS) methods have shown remarkable advancement with their powerful querybased detectors. Utilizing the output queries of the detector at the framelevel, these methods achieve high accuracy on challenging benchmarks. However, our observations demonstrate that these methods heavily rely on location information, which often causes incorrect associations between objects. This paper presents that a key axis of object matching in trackers is appearance information, which becomes greatly instructive under conditions where positional cues are insufficient for distinguishing their identities. Therefore, we suggest a simple yet powerful extension to object decoders that explicitly extract embeddings from backbone features and drive queries to capture the appearances of objects, which greatly enhances instance association accuracy. Furthermore, recognizing the limitations of existing benchmarks in fully evaluating appearance awareness, we have constructed a synthetic dataset to rigorously validate our method. By effectively resolving the over-reliance on location information, we achieve state-of-the-art results on YouTube-VIS 2019/2021 and Occluded VIS (OVIS). Code is available at https://github.com/KimHanjung/VISAGE.

For agents

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

get_harvested_code_for_paper("01071")
get_code_for_paper("01071")
have("01071")

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

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

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

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

Connect an agent — have() is free.