Papers › Reconstructive Visual Instruction Tuning

Reconstructive Visual Instruction Tuning

12 Oct 2024arXiv:2410.09575archive 2025-07-28

Haochen Wang, Anlin Zheng, Yucheng Zhao, Tiancai Wang, Zheng Ge, Xiangyu Zhang, Zhaoxiang Zhang

This paper introduces reconstructive visual instruction tuning (ROSS), a family of Large Multimodal Models (LMMs) that exploit vision-centric supervision signals. In contrast to conventional visual instruction tuning approaches that exclusively supervise text outputs, ROSS prompts LMMs to supervise visual outputs via reconstructing input images. By doing so, it capitalizes on the inherent richness and detail present within input images themselves, which are often lost in pure text supervision. However, producing meaningful feedback from natural images is challenging due to the heavy spatial redundancy of visual signals. To address this issue, ROSS employs a denoising objective to reconstruct latent representations of input images, avoiding directly regressing exact raw RGB values. This intrinsic activation design inherently encourages LMMs to maintain image detail, thereby enhancing their fine-grained comprehension capabilities and reducing hallucinations. Empirically, ROSS consistently brings significant improvements across different visual encoders and language models. In comparison with extrinsic assistance state-of-the-art alternatives that aggregate multiple visual experts, ROSS delivers competitive performance with a single SigLIP visual encoder, demonstrating the efficacy of our vision-centric supervision tailored for visual outputs.

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

By repository: community (archive-listed): 13 samples from 1 repository, 9 ran (3 with no instrument failure; 6 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-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 9 samples that ran have no recorded date.

haochen-wang409/ross mentioned on GitHubpytorchApache-2.0Syntology: 13 samples, 9 ran (6 instrument-failed) · 4 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

13 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 1 violated, 1 with no contract checked; 6 where Syntology's instrument failed) · 4 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.

1ran · honoured contract
1ran · violated contract
2ran · our draft was wrong
4ran; the contract check could not run
1ran
4unverified

Licence: 4 of the 13 samples are pointer only, meaning Syntology does not serve that copy's text. For 4 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 haochen-wang409/ross. “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.

haochen-wang409/ross community (archive-listed) 13 samples, 9 ran (6 instrument-failed) · 4 unverified
count_consecutive_blocks ross/model/ross_arch.py ran fingerprinted Apache-2.0 (permissive) · 25d7c8f510336006 · report fixture: signature lst:list/1/int, v:int/0/int · returned int · level recorded 2026-09-24
divide_to_patches in 65 papers ross/mm_utils.py ran · our draft was wrong Apache-2.0 (permissive) · 7e03b180fa317c9a · report fixture: signature image:Image/0/?, patch_size:int/0/int · returned list · level recorded 2026-09-24
get_1d_sincos_pos_embed_from_grid in 75 papers
census: 8 implementations from 17 papers, 2 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 2 of 2, arg 1: rank 1, kind float, dtype float32
ross/model/utils.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant Apache-2.0 (permissive) here; the stored copy is pointer only · 5c8ea92d43ead77d · report fixture: signature embed_dim:int/0/int, pos:ndarray/1/float · returned ndarray · level recorded 2026-09-22
get_2d_sincos_pos_embed in 170 papers ross/model/utils.py ran · honoured contract fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 77e8a3ac46f3afec · report fixture: signature embed_dim:int/0/int, grid_size:int/0/int, cls_token:bool/0/bool · returned ndarray · level recorded 2026-09-24
resize_and_pad_image in 70 papers ross/mm_utils.py ran · our draft was wrong Apache-2.0 (permissive) · 468eedeba67f1b00 · report fixture: signature image:Image/0/?, target_resolution:tuple/1/int · returned Image · level recorded 2026-09-24
select_best_resolution in 71 papers ross/mm_utils.py ran; the contract check could not run (RAISES) · metamorphic tier: well formed Apache-2.0 (permissive) · 3999ff487573f32c · report fixture: signature original_size:tuple/1/int, possible_resolutions:list/1/tuple · returned tuple · level recorded 2026-09-22
split_to_even_chunks in 41 papers ross/ross_trainer.py ran; the contract check could not run (RAISES) · metamorphic tier: well formed Apache-2.0 (permissive) · 10893c4608c08075 · report fixture: signature indices:list/1/int, lengths:dict/0/?, num_chunks:int/0/int · returned list · level recorded, date not recorded
unpad_image in 72 papers
census: 4 implementations from 34 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 3, kind float, dtype float32
ross/model/ross_arch.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted Apache-2.0 (permissive) · 55c32993da87759b · report fixture: signature tensor:Tensor/3/float, original_size:tuple/1/int · returned Tensor · level recorded, date not recorded
violates_moderation in 59 papers ross/utils.py ran · violated contract Apache-2.0 (permissive) here; the stored copy is pointer only · f9939a84b9a65279 · report fixture: signature text:str/0/str · returned bool · level recorded 2026-09-26
get_2d_sincos_pos_embed_from_grid in 140 papers ross/model/utils.py unverified Apache-2.0 (permissive) here; the stored copy is pointer only · 2884deadbb637c3e · report
get_mm_adapter_state_maybe_zero_3 in 44 papers ross/ross_trainer.py unverified Apache-2.0 (permissive) · bb35e3ac741bb2c9 · report
maybe_zero_3 in 74 papers ross/ross_trainer.py unverified Apache-2.0 (permissive) · 735025744c1ab0cf · report
pretty_print_semaphore in 55 papers ross/utils.py unverified Apache-2.0 (permissive) · 37899f22fb191b37 · report

Tasks

Denoising

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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