Papers › UniRef++: Segment Every Reference Object in Spatial and Temporal Spaces

UniRef++: Segment Every Reference Object in Spatial and Temporal Spaces

25 Dec 2023arXiv:2312.15715archive 2025-07-28

Jiannan Wu, Yi Jiang, Bin Yan, Huchuan Lu, Zehuan Yuan, Ping Luo

The reference-based object segmentation tasks, namely referring image segmentation (RIS), few-shot image segmentation (FSS), referring video object segmentation (RVOS), and video object segmentation (VOS), aim to segment a specific object by utilizing either language or annotated masks as references. Despite significant progress in each respective field, current methods are task-specifically designed and developed in different directions, which hinders the activation of multi-task capabilities for these tasks. In this work, we end the current fragmented situation and propose UniRef++ to unify the four reference-based object segmentation tasks with a single architecture. At the heart of our approach is the proposed UniFusion module which performs multiway-fusion for handling different tasks with respect to their specified references. And a unified Transformer architecture is then adopted for achieving instance-level segmentation. With the unified designs, UniRef++ can be jointly trained on a broad range of benchmarks and can flexibly complete multiple tasks at run-time by specifying the corresponding references. We evaluate our unified models on various benchmarks. Extensive experimental results indicate that our proposed UniRef++ achieves state-of-the-art performance on RIS and RVOS, and performs competitively on FSS and VOS with a parameter-shared network. Moreover, we showcase that the proposed UniFusion module could be easily incorporated into the current advanced foundation model SAM and obtain satisfactory results with parameter-efficient finetuning. Codes and models are available at https://github.com/FoundationVision/UniRef.

PaperPDFCodeCode Syntology ran

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):

Code

Syntology 9 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 2 honoured, 0 violated, 0 with no contract checked; 7 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 9 ran (2 with no instrument failure; 7 where Syntology's instrument failed). 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 9 samples that ran has no recorded date.

foundationvision/uniref officialmentioned in paperpytorchMITSyntology: 9 samples, 9 ran (7 instrument-failed) · 0 unverified report

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

9 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 2 honoured, 0 violated, 0 with no contract checked; 7 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · honoured contract
5ran · our draft was wrong
2ran; the contract check could not run

Licence: 2 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 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 foundationvision/uniref. “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.

foundationvision/uniref official repository 9 samples, 9 ran (7 instrument-failed) · 0 unverified
aligned_bilinear in 17 papers projects/UniRef/uniref/models/ddetrs.py ran · our draft was wrong fingerprinted MIT (permissive) · 29dbbaafa4be18e1 · report fixture: signature tensor:Tensor/4/float, factor:int/0/int · returned Tensor · level recorded 2026-09-22
bounding_box projects/UniRef/uniref/uniref.py ran · honoured contract MIT (permissive) · 8243ac0c601917dc · report fixture: signature img:ndarray/2/int · returned list · level recorded 2026-09-24
compute_locations in 14 papers projects/UniRef/uniref/models/ddetrs.py ran · honoured contract MIT (permissive) here; the stored copy is pointer only · ed1a308adb65f645 · report fixture: signature h:int/0/int, w:int/0/int, device:device/0/?, stride:int/0/int · returned Tensor · level recorded, date not recorded
compute_mask_iou projects/UniRef/uniref/models/uniref_sam.py ran · our draft was wrong fingerprinted MIT (permissive) · 4de0dcaf9f33183b · report fixture: signature inputs:Tensor/2/float, targets:Tensor/2/float · returned Tensor · level recorded 2026-09-24
concat_mask_dict_features projects/UniRef/uniref/uniref.py ran · our draft was wrong MIT (permissive) · 286983a8483318b8 · report fixture: signature ref_feats_dict1:dict/0/?, ref_feats_dict2:dict/0/? · returned dict · level recorded 2026-09-24
dice_loss in 193 papers
census: 10 implementations from 16 papers, 7 distinct outputs across 4 buckets, one shared input per bucket this sample: bucket 2 of 4, arg 1: rank 3, kind float, dtype float32 · arg 2: rank 3, kind float, dtype float32
projects/UniRef/uniref/models/uniref_sam.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · a1c2083ec2eaeb22 · report fixture: signature inputs:Tensor/3/float, targets:Tensor/3/float, num_masks:float/0/float, scale:int/0/int, eps:float/0/float · returned Tensor · level recorded 2026-09-22
parse_dynamic_params in 14 papers projects/UniRef/uniref/models/ddetrs.py ran · our draft was wrong MIT (permissive) · 46f34dc9f9a94b67 · report fixture: signature params:Tensor/2/float, channels:int/0/int, weight_nums:list/1/int, bias_nums:list/1/int · returned tuple · level recorded 2026-09-22
sigmoid_ce_loss in 70 papers
census: 4 implementations from 8 papers, 3 distinct outputs across 2 buckets, one shared input per bucket
projects/UniRef/uniref/models/uniref_sam.py ran · our draft was wrong fingerprinted MIT (permissive) · e28a878991e1e696 · report fixture: signature inputs:Tensor/3/float, targets:Tensor/3/float, num_masks:float/0/float · returned Tensor · level recorded 2026-09-24
unfold_wo_center in 5 papers projects/UniRef/uniref/uniref.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) here; the stored copy is pointer only · 6bc62d34967e2917 · report fixture: signature x:Tensor/4/float, kernel_size:int/0/int, dilation:int/0/int · returned Tensor · level recorded 2026-09-22

Tasks

Image SegmentationObjectReferring Expression SegmentationReferring Video Object SegmentationSegmentationSemantic SegmentationVideo Object SegmentationVideo Semantic Segmentation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Referring Expression Segmentation Refer-YouTube-VOS (2021 public validation) UniRef++-L F 69.0 #12 of 33 Archive leaderboard report
Referring Expression Segmentation Refer-YouTube-VOS (2021 public validation) UniRef++-L J 64.8 #12 of 33 Archive leaderboard report
Referring Expression Segmentation Refer-YouTube-VOS (2021 public validation) UniRef++-L J&F 66.9 #12 of 33 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.

Methods

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSAMSoftmaxTransformerVOS

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