Papers › Positional encoding is not the same as context: A study on positional encoding for...

Positional encoding is not the same as context: A study on positional encoding for sequential recommendation

16 May 2024arXiv:2405.10436archive 2025-07-28

Alejo Lopez-Avila, Jinhua Du, Abbas Shimary, Ze Li

The rapid growth of streaming media and e-commerce has driven advancements in recommendation systems, particularly Sequential Recommendation Systems (SRS). These systems employ users' interaction histories to predict future preferences. While recent research has focused on architectural innovations like transformer blocks and feature extraction, positional encodings, crucial for capturing temporal patterns, have received less attention. These encodings are often conflated with contextual, such as the temporal footprint, which previous works tend to treat as interchangeable with positional information. This paper highlights the critical distinction between temporal footprint and positional encodings, demonstrating that the latter offers unique relational cues between items, which the temporal footprint alone cannot provide. Through extensive experimentation on eight Amazon datasets and subsets, we assess the impact of various encodings on performance metrics and training stability. We introduce new positional encodings and investigate integration strategies that improve both metrics and stability, surpassing state-of-the-art results at the time of this work's initial preprint. Importantly, we demonstrate that selecting the appropriate encoding is not only key to better performance but also essential for building robust, reliable SRS models.

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

By repository: official repository: 8 samples from 1 repository, 8 ran (4 with no instrument failure; 4 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.

researcher1741/position_encoding_srs officialmentioned in paperpytorchSyntology: 8 samples, 8 ran (4 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

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

3ran · honoured contract
1ran · violated contract
4ran · our draft was wrong

Licence: 8 of the 8 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 researcher1741/position_encoding_srs. “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.

researcher1741/position_encoding_srs official repository 8 samples, 8 ran (4 instrument-failed) · 0 unverified
check_device src/utils.py ran · our draft was wrong no licence file found · pointer only · 0ee87fa991912f33 · report fixture: signature printit:bool/0/bool · returned device · level recorded 2026-09-24
convert_to_float in 13 papers Results/results_analysis.py ran · honoured contract fingerprinted no licence file found · pointer only · 18fbb3595177237b · report fixture: signature s:str/0/str · returned float · level recorded 2026-09-24
get_UserData src/data_preprocessing.py ran · honoured contract no licence file found · pointer only · 58bc3f1d6b757fa7 · report fixture: signature usernum:int/0/int · returned ndarray · level recorded 2026-09-24
get_files in 30 papers Results/results_analysis.py ran · our draft was wrong no licence file found · pointer only · ea5d9e3461446c08 · report fixture: signature folder:str/0/str · returned tuple · level recorded 2026-09-24
load_data in 700 papers src/utils.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 32656231792740e8 · report fixture: signature filename:str/0/str · returned dict · level recorded 2026-09-24
random_neq in 8 papers src/sampler.py ran · honoured contract no licence file found · pointer only · 2660cad125666143 · report fixture: signature l:int/0/int, r:int/0/int, s:set/0/? · returned int · level recorded 2026-09-24
seed_filter Results/results_analysis.py ran · our draft was wrong no licence file found · pointer only · 66c8a630be3ca9f6 · report fixture: signature text:str/0/str · returned str · level recorded 2026-09-24
str2bool in 533 papers src/utils.py ran · violated contract no licence file found · pointer only · 8f8983954debe79b · report fixture: signature s:str/0/str · returned bool · level recorded 2026-09-24

Tasks

Recommendation SystemsSequential Recommendation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Recommendation Systems Amazon Beauty CARCA Abs + Con Hit@10 0.6793 #1 of 6 Archive leaderboard report
Recommendation Systems Amazon Beauty CARCA Abs + Con NDCG 0.4871 #1 of 6 Archive leaderboard report
Recommendation Systems Amazon Beauty CARCA-Rotatory Hit@10 0.6187 #3 of 6 Archive leaderboard report
Recommendation Systems Amazon Beauty CARCA-Rotatory NDCG 0.4260 #3 of 6 Archive leaderboard report
Recommendation Systems Amazon Fashion RMHA-4 Hit@10 0.7726 #4 of 4 Archive leaderboard report
Recommendation Systems Amazon Fashion RMHA-4 NDCG 0.4975 #4 of 4 Archive leaderboard report
Recommendation Systems Amazon Games CARCA-Rotatory + Con. Hit@10 0.8062 #2 of 6 Archive leaderboard report
Recommendation Systems Amazon Games CARCA-Rotatory + Con. NDCG 0.5607 #2 of 6 Archive leaderboard report
Recommendation Systems Amazon Men CARCA Learnt + Con Hit@10 0.7386 #1 of 3 Archive leaderboard report
Recommendation Systems Amazon Men CARCA Learnt + Con NDCG 0.5889 #1 of 3 Archive leaderboard report
Recommendation Systems Amazon Men RMHA-4 Hit@10 0.7013 #2 of 3 Archive leaderboard report
Recommendation Systems Amazon Men RMHA-4 NDCG 0.4641 #2 of 3 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.

Methods

SRS

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