Papers › PolyMaX: General Dense Prediction with Mask Transformer

PolyMaX: General Dense Prediction with Mask Transformer

9 Nov 2023arXiv:2311.05770archive 2025-07-28

Xuan Yang, Liangzhe Yuan, Kimberly Wilber, Astuti Sharma, Xiuye Gu, Siyuan Qiao, Stephanie Debats, Huisheng Wang, Hartwig Adam, Mikhail Sirotenko, Liang-Chieh Chen

Dense prediction tasks, such as semantic segmentation, depth estimation, and surface normal prediction, can be easily formulated as per-pixel classification (discrete outputs) or regression (continuous outputs). This per-pixel prediction paradigm has remained popular due to the prevalence of fully convolutional networks. However, on the recent frontier of segmentation task, the community has been witnessing a shift of paradigm from per-pixel prediction to cluster-prediction with the emergence of transformer architectures, particularly the mask transformers, which directly predicts a label for a mask instead of a pixel. Despite this shift, methods based on the per-pixel prediction paradigm still dominate the benchmarks on the other dense prediction tasks that require continuous outputs, such as depth estimation and surface normal prediction. Motivated by the success of DORN and AdaBins in depth estimation, achieved by discretizing the continuous output space, we propose to generalize the cluster-prediction based method to general dense prediction tasks. This allows us to unify dense prediction tasks with the mask transformer framework. Remarkably, the resulting model PolyMaX demonstrates state-of-the-art performance on three benchmarks of NYUD-v2 dataset. We hope our simple yet effective design can inspire more research on exploiting mask transformers for more dense prediction tasks. Code and model will be made available.

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 3 code samples harvested from 1 repository linked to this paper: 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 3 samples from 1 repository, 3 ran (3 with no instrument failure; 0 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 on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

google-research/deeplab2 officialmentioned in papertfApache-2.0Syntology: 3 samples, 3 ran (0 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

3 samples harvested: 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 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 has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran

Licence: 0 of the 3 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from google-research/deeplab2. “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.

google-research/deeplab2 official repository 3 samples, 3 ran (0 instrument-failed) · 0 unverified
resolve_batch_size model/utils.py ran Apache-2.0 (permissive) · 5e915628f1149a2f · report fixture: signature tensor:EagerTensor/2/float · returned int · level recorded 2026-09-24
scale_int_list model/utils.py ran Apache-2.0 (permissive) · e0df865e93d2e0db · report fixture: signature int_list:list/1/int, scale:float/0/float · returned list · level recorded 2026-09-24
scale_mutable_sequence model/utils.py ran Apache-2.0 (permissive) · 315f2fdd4f533108 · report fixture: signature input_sequence:list/1/int, scale:float/0/float · returned list · level recorded 2026-09-24

Tasks

Depth EstimationMonocular Depth EstimationPredictionSemantic SegmentationSurface Normal EstimationSurface Normals Estimation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Monocular Depth Estimation NYU-Depth V2 PolyMaX(ConvNeXt-L) Delta < 1.25 0.969 #20 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 PolyMaX(ConvNeXt-L) Delta < 1.25^2 0.9958 #20 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 PolyMaX(ConvNeXt-L) Delta < 1.25^3 0.999 #20 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 PolyMaX(ConvNeXt-L) RMSE 0.25 #20 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 PolyMaX(ConvNeXt-L) absolute relative error 0.067 #20 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 PolyMaX(ConvNeXt-L) log 10 0.029 #20 of 85 Archive leaderboard report
Semantic Segmentation NYU Depth v2 PolyMaX(ConvNeXt-L) Mean IoU 58.08% #12 of 121 Archive leaderboard report
Surface Normals Estimation NYU Depth v2 PolyMaX(ConvNeXt-L) % < 11.25 65.66 #2 of 6 Archive leaderboard report
Surface Normals Estimation NYU Depth v2 PolyMaX(ConvNeXt-L) % < 22.5 82.28 #2 of 6 Archive leaderboard report
Surface Normals Estimation NYU Depth v2 PolyMaX(ConvNeXt-L) % < 30 87.83 #2 of 6 Archive leaderboard report
Surface Normals Estimation NYU Depth v2 PolyMaX(ConvNeXt-L) Mean Angle Error 13.09 #2 of 6 Archive leaderboard report
Surface Normals Estimation NYU Depth v2 PolyMaX(ConvNeXt-L) RMSE 20.4 #2 of 6 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.

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