4 of 7 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; 4 failures of our instrument; 3 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/2312.04302.json · badge: /api/ran/2312.04302.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.
| Repository | Role | Ran |
|---|---|---|
| dvlab-research/prompt-highlighter | canonical (classifier label) classifier basis: census |
4 ran · 3 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| llama_new_forward | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
dvlab-research/prompt-highlighter/highlighter_modules/attention_llama_llava.py code served (permissive licence) · get_code("3b5481f5e9be9f14") How it ranRan 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 tuple. The image it ran in was not recorded. The code mentions cuda, and the harness aliases cuda to the CPU for every sample; whether this run needed that is 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.
|
| prepare_llava_hl_inputs_for_generation | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
dvlab-research/prompt-highlighter/highlighter_modules/attention_llama_llava.py code served (permissive licence) · get_code("39225cb7adeb18ef") How it ranRan 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 dict. 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.
|
| qformer_new_forward | Ran ran; our contract draft was wrong, not the code |
dvlab-research/prompt-highlighter/highlighter_modules/attention_qformer.py code served (permissive licence) · get_code("c28cc1cc33573efa") How it ranRan 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 tuple. The image it ran in was not recorded. The code mentions cuda, and the harness aliases cuda to the CPU for every sample; whether this run needed that is 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.
|
| txt_highlight_mask | Ran ran; our contract draft was wrong, not the code |
dvlab-research/prompt-highlighter/highlighter_modules/utils.py code served (permissive licence) · get_code("b043cf35354245c1") How it ranRan 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 tuple, ndim 2, 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.
|
| blip_hl_generate | Not yet run unverified (harvested, no recorded run) |
dvlab-research/prompt-highlighter/highlighter_modules/attention_qformer.py code served (permissive licence) · get_code("92a6bceb61aa27f7") How it ranno invocation recorded. |
| llama_attn_forward | Not yet run unverified (harvested, no recorded run) |
dvlab-research/prompt-highlighter/highlighter_modules/attention_llama_llava.py code served (permissive licence) · get_code("22268c65d02b5f37") How it ranno invocation recorded. |
| qformer_attn_forward | Not yet run unverified (harvested, no recorded run) |
dvlab-research/prompt-highlighter/highlighter_modules/attention_qformer.py code served (permissive licence) · get_code("8bfff27cc6e1ad26") How it ranno invocation recorded. |
Of 7 samples lifted from this paper's linked repositories, 7 carry a function identity and 0 do not. Of the 7 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 7 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.
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.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
This study targets a critical aspect of multi-modal LLMs' (LLMs&VLMs) inference: explicit controllable text generation. Multi-modal LLMs empower multi-modality understanding with the capability of semantic generation yet bring less explainability and heavier reliance on prompt contents due to their autoregressive generative nature. While manipulating prompt formats could improve outputs, designing specific and precise prompts per task can be challenging and ineffective. To tackle this issue, we introduce a novel inference method, Prompt Highlighter, which enables users to highlight specific prompt spans to interactively control the focus during generation. Motivated by the classifier-free diffusion guidance, we form regular and unconditional context pairs based on highlighted tokens, demonstrating that the autoregressive generation in models can be guided in a classifier-free way. Notably, we find that, during inference, guiding the models with highlighted tokens through the attention weights leads to more desired outputs. Our approach is compatible with current LLMs and VLMs, achieving impressive customized generation results without training. Experiments confirm its effectiveness in focusing on input contexts and generating reliable content. Without tuning on LLaVA-v1.5, our method secured 70.7 in the MMBench test and 1552.5 in MME-perception. The code is available at: https://github.com/dvlab-research/Prompt-Highlighter/
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2312.04302")
get_code_for_paper("2312.04302")
have("2312.04302")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2312.04302.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2312.04302)
Connect an agent — have() is free.