Papers › Preference Diffusion for Recommendation
Preference Diffusion for Recommendation
Shuo Liu, An Zhang, Guoqing Hu, Hong Qian, Tat-Seng Chua
Recommender systems predict personalized item rankings based on user preference distributions derived from historical behavior data. Recently, diffusion models (DMs) have gained attention in recommendation for their ability to model complex distributions, yet current DM-based recommenders often rely on traditional objectives like mean squared error (MSE) or recommendation objectives, which are not optimized for personalized ranking tasks or fail to fully leverage DM's generative potential. To address this, we propose PreferDiff, a tailored optimization objective for DM-based recommenders. PreferDiff transforms BPR into a log-likelihood ranking objective and integrates multiple negative samples to better capture user preferences. Specifically, we employ variational inference to handle the intractability through minimizing the variational upper bound and replaces MSE with cosine error to improve alignment with recommendation tasks. Finally, we balance learning generation and preference to enhance the training stability of DMs. PreferDiff offers three key benefits: it is the first personalized ranking loss designed specifically for DM-based recommenders and it improves ranking and faster convergence by addressing hard negatives. We also prove that it is theoretically connected to Direct Preference Optimization which indicates that it has the potential to align user preferences in DM-based recommenders via generative modeling. Extensive experiments across three benchmarks validate its superior recommendation performance and commendable general sequential recommendation capabilities. Our codes are available at https://github.com/lswhim/PreferDiff.
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="2410.13117")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2410.13117", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2410.13117")
Code
Syntology 19 code samples: 15 from 1 repository linked to this paper, 4 identical to code harvested from another paper's repository. Across all 19: 15 ran (of which 5 constructed an object rather than computing a result; 10 with no instrument failure: 4 honoured, 0 violated, 6 with no contract checked; 5 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 3 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: 15 samples from 1 repository, 11 ran (7 with no instrument failure; 4 where Syntology's instrument failed); 4 identical to code first harvested elsewhere. 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.
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
19 samples harvested: 15 ran (of which 5 constructed an object rather than computing a result; 10 with no instrument failure: 4 honoured, 0 violated, 6 with no contract checked; 5 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.
Licence: 19 of the 19 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 lswhim/preferdiff. 4 samples are listed last, in a group without a repository. “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”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.
9cee7b29292819c9 · report
fixture: returned AbstractModel · level recorded 2026-09-22 94f2a9e6aa1676eb · report
fixture: returned BaseDiffusion · level recorded 2026-09-22 census: 9 implementations from 7 papers, 9 distinct outputs across 3 buckets, one shared input per bucket models/PreferDiff/_model.py ran · metamorphic tier: deterministic no licence file found · pointer only ·
63814a6938fa994f · report
fixture: returned MultiHeadAttention · level recorded 2026-09-22 89f25d4ab4d600e3 · report
fixture: returned PositionwiseFeedForward · level recorded 2026-09-22 census: 5 implementations from 5 papers, 3 distinct outputs on one shared input models/PreferDiff/_model.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only ·
2b5245040c13c182 · report
fixture: returned SinusoidalPositionEmbeddings · level recorded 2026-09-22 f63384aa09f6504a · report
fixture: signature seq:Tensor/3/float, mask:Tensor/3/float · returned Tensor · level recorded 2026-09-24 3cc2ff4c20cc6053 · report
fixture: signature e:Tensor/2/float, epsilon:float/0/float · returned Tensor · level recorded 2026-09-22 2c8cfbc6db313670 · report
fixture: signature timesteps:int/0/int, beta_min:float/0/float, beta_max:int/0/int · returned Tensor · level recorded 2026-09-22 dc3094c7e25c1afa · report
fixture: signature data:Tensor/3/float, indices:Tensor/1/int · returned Tensor · level recorded 2026-09-22 4675e6612ba76877 · report
fixture: signature batch_items:Tensor/1/int, num_neg:int/0/int · returned Tensor · level recorded 2026-09-22 351f47117a6acd3b · report
fixture: signature unparsed:list/1/str · returned dict · level recorded 2026-09-24 5d6aca7f0ee74315 · report
7d68851af1d4f86e · report
c250ef81a5f76f3c · report
3d3f56b8afc1b831 · report
4 samples are identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
6cdc8772f5db6f48 · report
fixture: signature num_diffusion_timesteps:int/0/int, alpha_bar:callable/0/?, max_beta:float/0/float · returned ndarray · level recorded 2026-09-22 3a6233722b4f0cd6 · report
fixture: signature timesteps:int/0/int, s:float/0/float · returned Tensor · level recorded 2026-09-22 census: 9 implementations from 12 papers, 4 distinct outputs across 3 buckets, one shared input per bucket repository not located ran; the contract check could not run (RAISES) · metamorphic tier: invariant licence of this copy not recorded ·
df116dde4bb6ab3e · report
fixture: signature a:Tensor/2/float, t:Tensor/2/int, x_shape:tuple/1/int · returned Tensor · level recorded 2026-09-22 4b3d941e8a7485c5 · report
fixture: signature timesteps:int/0/int, beta_start:float/0/float, beta_end:float/0/float · returned Tensor · level recorded 2026-09-22 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 PreferDiff (graph method: PreferDiff). 18 bricks; individually on a fixture: 14 ran (of which 5 constructed an object rather than computing a result; 10 with no instrument failure: 4 honoured, 0 violated, 6 with no contract checked; 4 where Syntology's instrument failed) · 4 unverified. The assembly has not been run end-to-end.
- PreferDiff entry · level 0 · unverified ·
5d6aca7f0ee74315 - PreferenceDiffusion sampler · level 0 · unverified ·
7d68851af1d4f86e - SASRec helper · level 0 · unverified ·
c250ef81a5f76f3c - SinusoidalPositionEmbeddings model · level 1 · ran ·
2b5245040c13c182 - diagonalize_and_scale helper · level 1 · ran · our draft was wrong ·
3cc2ff4c20cc6053 - in_batch_negative_sampling data_transform · level 0 · unverified ·
3d3f56b8afc1b831 - in_batch_negative_sampling_sample helper · level 1 · ran · our draft was wrong ·
4675e6612ba76877 - BaseDiffusion helper · level 1 · ran ·
94f2a9e6aa1676eb - AbstractModel helper · level 1 · ran ·
9cee7b29292819c9 - TransformerEncoder model · level 1 · ran ·
f63384aa09f6504a - extract_axis_1 helper · level 1 · ran; the contract check could not run (RAISES) ·
dc3094c7e25c1afa - betas_for_alpha_bar helper · level 1 · ran · honoured contract ·
6cdc8772f5db6f48 - cosine_beta_schedule helper · level 1 · ran · honoured contract ·
3a6233722b4f0cd6 - exp_beta_schedule helper · level 1 · ran · honoured contract ·
2c8cfbc6db313670 - extract helper · level 1 · ran; the contract check could not run (RAISES) ·
df116dde4bb6ab3e - linear_beta_schedule helper · level 1 · ran · honoured contract ·
4b3d941e8a7485c5 - MultiHeadAttention helper · level 1 · ran ·
63814a6938fa994f - PositionwiseFeedForward helper · level 1 · ran ·
89f25d4ab4d600e3
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="2410.13117") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
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