Papers › A Self-Attentive model for Knowledge Tracing

A Self-Attentive model for Knowledge Tracing

16 Jul 2019arXiv:1907.06837archive 2025-07-28

Shalini Pandey, George Karypis

Knowledge tracing is the task of modeling each student's mastery of knowledge concepts (KCs) as (s)he engages with a sequence of learning activities. Each student's knowledge is modeled by estimating the performance of the student on the learning activities. It is an important research area for providing a personalized learning platform to students. In recent years, methods based on Recurrent Neural Networks (RNN) such as Deep Knowledge Tracing (DKT) and Dynamic Key-Value Memory Network (DKVMN) outperformed all the traditional methods because of their ability to capture complex representation of human learning. However, these methods face the issue of not generalizing well while dealing with sparse data which is the case with real-world data as students interact with few KCs. In order to address this issue, we develop an approach that identifies the KCs from the student's past activities that are relevant to the given KC and predicts his/her mastery based on the relatively few KCs that it picked. Since predictions are made based on relatively few past activities, it handles the data sparsity problem better than the methods based on RNN. For identifying the relevance between the KCs, we propose a self-attention based approach, Self Attentive Knowledge Tracing (SAKT). Extensive experimentation on a variety of real-world dataset shows that our model outperforms the state-of-the-art models for knowledge tracing, improving AUC by 4.43% on average.

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

By repository: community (archive-listed): 12 samples from 3 repositories, 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.

No sample is linked to this paper from 3 of its repositories that Syntology harvested for other papers:

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.

Machine-Learning-for-Everyone-ML4E/CoP-Code-of-Papers mentioned on GitHubtfMITSyntology: not harvested report
arshadshk/SAKT-pytorch mentioned on GitHubpytorchSyntology: not harvested report
jdxyw/deepKT mentioned on GitHubpytorchMITSyntology: 3 samples, 2 ran (0 instrument-failed) · 1 unverified report
theophilee/learner-performance-prediction mentioned on GitHubpytorchSyntology: not harvested report
theophilegervet/learner-performance-prediction mentioned on GitHubpytorchSyntology: 6 samples, 4 ran (3 instrument-failed) · 2 unverified report
MindCode-4/code-11 mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Entropy Law: The Story Behind Data Compression and LLM Performance (arXiv:2407.06645; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 2 honoured, 1 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
MindCode-4/code-6 mindsporeSyntology: not harvested report
MindSpore-scientific/code-3 mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Coneheads: Hierarchy Aware Attention (arXiv:2306.00392; that paper's own run record: 7 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
nanzhaogang/contrib mindsporeApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Hyperspherical Consistency Regularization (arXiv:2206.00845; that paper's own run record: 3 ran (of which 1 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 1 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
shalini1194/SAKT tfSyntology: 3 samples, 2 ran (1 instrument-failed) · 1 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

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

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

Licence: 9 of the 12 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 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

jdxyw/deepKT community (archive-listed) 3 samples, 2 ran (0 instrument-failed) · 1 unverified
dkt_predict deepkt/loss/loss.py ran MIT (permissive) · 258c9e181f3270df · report fixture: signature logits:Tensor/3/float, qid:Tensor/3/int · returned tuple · level recorded 2026-09-24
sakt_eval deepkt/utils/utils.py ran MIT (permissive) · c408856774ceda9f · report fixture: signature logits:Tensor/2/float, qid:Tensor/2/int, targets:Tensor/2/float, mask:Tensor/2/int · returned tuple · level recorded 2026-09-24
deepirt_eval deepkt/utils/utils.py unverified MIT (permissive) · 845ba6090f20db7e · report
theophilegervet/learner-performance-prediction community (archive-listed) 6 samples, 4 ran (3 instrument-failed) · 2 unverified
attention in 144 papers
census: 11 implementations from 10 papers, 7 distinct outputs across 5 buckets, one shared input per bucket
model_sakt.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic no licence file found · pointer only · 47e44e2cbc1d0361 · report fixture: signature query:Tensor/3/float, key:Tensor/3/float, value:Tensor/3/float, mask:Tensor/3/bool, dropout:callable/0/? · returned tuple · level recorded 2026-09-22
clone in 7 papers model_sakt.py ran · our draft was wrong no licence file found · pointer only · 1b483db3c68fe2df · report fixture: signature module:callable/0/?, num:int/0/int · returned ModuleList · level recorded 2026-09-22
future_mask model_sakt.py ran · violated contract no licence file found · pointer only · 77174654ec32c686 · report fixture: signature seq_length:int/0/int · returned Tensor · level recorded 2026-09-22
prepare_batches train_sakt.py ran · our draft was wrong fingerprinted no licence file found · pointer only · f2254f62decab8a1 · report fixture: signature data:list/1/list, batch_size:int/0/int, randomize:bool/0/bool · returned list · level recorded 2026-09-22
compute_auc in 13 papers train_sakt.py unverified no licence file found · pointer only · 63379c3778af65f9 · report
get_data in 223 papers train_sakt.py unverified no licence file found · pointer only · a79ac5e51695f207 · report
shalini1194/SAKT community (archive-listed) 3 samples, 2 ran (1 instrument-failed) · 1 unverified
read_data_from_csv_file 2019-EDM/main1.py ran · our draft was wrong no licence file found · pointer only · dc76ab08d0c550d9 · report fixture: signature fileName_train:str/0/str, fileName_test:str/0/str, max_num_problems:int/0/int · returned tuple · level recorded 2026-09-22
str2bool in 533 papers 2019-EDM/main1.py ran · violated contract no licence file found · pointer only · 37e217915347c2dc · report fixture: signature s:str/0/str · returned bool · level recorded 2026-09-22
run_epoch in 18 papers 2019-EDM/main1.py unverified no licence file found · pointer only · ce77a64f3aefc943 · report

Tasks

Ad-Hoc Information RetrievalKnowledge TracingQuestion Answeringmodel

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Memory Network

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