Papers › ScanDL: A Diffusion Model for Generating Synthetic Scanpaths on Texts
ScanDL: A Diffusion Model for Generating Synthetic Scanpaths on Texts
Lena S. Bolliger, David R. Reich, Patrick Haller, Deborah N. Jakobi, Paul Prasse, Lena A. Jäger
Eye movements in reading play a crucial role in psycholinguistic research studying the cognitive mechanisms underlying human language processing. More recently, the tight coupling between eye movements and cognition has also been leveraged for language-related machine learning tasks such as the interpretability, enhancement, and pre-training of language models, as well as the inference of reader- and text-specific properties. However, scarcity of eye movement data and its unavailability at application time poses a major challenge for this line of research. Initially, this problem was tackled by resorting to cognitive models for synthesizing eye movement data. However, for the sole purpose of generating human-like scanpaths, purely data-driven machine-learning-based methods have proven to be more suitable. Following recent advances in adapting diffusion processes to discrete data, we propose ScanDL, a novel discrete sequence-to-sequence diffusion model that generates synthetic scanpaths on texts. By leveraging pre-trained word representations and jointly embedding both the stimulus text and the fixation sequence, our model captures multi-modal interactions between the two inputs. We evaluate ScanDL within- and across-dataset and demonstrate that it significantly outperforms state-of-the-art scanpath generation methods. Finally, we provide an extensive psycholinguistic analysis that underlines the model's ability to exhibit human-like reading behavior. Our implementation is made available at https://github.com/DiLi-Lab/ScanDL.
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):
get_harvested_code_for_paper(arxiv_id="2310.15587")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2310.15587", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2310.15587")
Code
Syntology 20 code samples harvested from 1 repository linked to this paper: 14 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 0 violated, 5 with no contract checked; 7 where Syntology's instrument failed) · 6 unverified. Where Syntology's instrument failed: 7 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 20 samples from 1 repository, 14 ran (7 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-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 3 of the 14 samples that ran have no recorded date.
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
20 samples harvested: 14 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 0 violated, 5 with no contract checked; 7 where Syntology's instrument failed) · 6 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.
Licence: 20 of the 20 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 dili-lab/scandl. “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.
census: 5 implementations from 5 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 scandl/sp_transformer_model.py ran · metamorphic tier: invariant fingerprinted no licence file found · pointer only ·
f378e3c2e0e7259f · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22 census: 4 implementations from 14 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 scandl/utils/losses.py ran · our draft was wrong fingerprinted no licence file found · pointer only ·
cfd76fd0d89574a4 · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded 2ab2316ac6fdd869 · report
fixture: signature num_diffusion_timesteps:int/0/int, alpha_bar:callable/0/?, max_beta:float/0/float · returned ndarray · level recorded, date not recorded ec3425eb7cd519f7 · report
fixture: signature num_diffusion_timesteps:int/0/int, alpha_bar:callable/0/?, max_beta:float/0/float · returned ndarray · level recorded 2026-09-24 561d61dd0e3e3459 · report
fixture: signature args:Args/0/?, sn_sp_repr_embedding:callable/0/?, text_emb:Tensor/3/float, t:Tensor/1/int · returned Tensor · level recorded 2026-09-24 census: 6 implementations from 10 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32 · arg 3: rank 2, kind float, dtype float32 scandl/utils/losses.py ran · our draft was wrong no licence file found · pointer only ·
cd33283d615fb3d7 · report
fixture: signature x:Tensor/2/float, means:Tensor/2/float, log_scales:Tensor/2/float · returned Tensor · level recorded, date not recorded 4b8663c67f958eca · report
fixture: signature sn_sp_repr_embedding_weight:Tensor/2/float, text_emb:Tensor/2/float · returned tuple · level recorded 2026-09-24 7c426de92b7ed6df · report
fixture: signature schedule_name:str/0/str, num_diffusion_timesteps:int/0/int · returned ndarray · level recorded 2026-09-24 a863803cdd5f3ce6 · report
fixture: signature model_params:list/1/Tensor · returned list · level recorded 2026-09-25 bcd8b4acab199405 · report
fixture: signature format:str/0/str, ev_dir:str/0/str, log_suffix:str/0/str · returned HumanOutputFormat · level recorded 2026-09-24 e515a67f7f32e76d · report
fixture: signature comm:MockComm/0/?, local_name2valcount:dict/0/? · returned dict · level recorded 2026-09-26 census: 14 implementations from 24 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32 · arg 3: rank 2, kind float, dtype float32 · arg 4: rank 2, kind float, dtype float32 scandl/utils/losses.py ran · honoured contract fingerprinted no licence file found · pointer only ·
cf2798b666b231ca · report
fixture: signature mean1:Tensor/2/float, logvar1:Tensor/2/float, mean2:Tensor/2/float, logvar2:Tensor/2/float · returned Tensor · level recorded 2026-09-22 30e43bcf12d042b0 · report
fixture: signature model_params:list/1/Tensor, master_params:list/1/Tensor · returned tuple · level recorded 2026-09-25 129b804760b3115f · report
fixture: signature module:callable/0/? · returned SimpleModule · level recorded 2026-09-22 35e096f40fc8ed50 · report
ecd0fc28815b65ae · report
b6fb1c1dab4fdbf7 · report
9906cf99104415ef · report
474a3911f75068af · report
9136b5f9b735334b · report
Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.
1 assembly on this paper: 1 harvested, 0 generated.
harvested Assembly for SCANDL (graph method: SCANDL). 4 bricks; individually on a fixture: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.
- TransformerNetModel entry · level 0 · unverified ·
35e096f40fc8ed50 - SiLU helper · level 1 · ran ·
f378e3c2e0e7259f - linear helper · level 1 · ran · our draft was wrong ·
0e30585f04efffbe - timestep_embedding helper · level 1 · ran · our draft was wrong ·
88867f4df8cef2a9
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2310.15587") returns these assemblies with each brick's role and wiring (how to connect).
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
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