Papers › DAS3H: Modeling Student Learning and Forgetting for Optimally Scheduling Distributed...
DAS3H: Modeling Student Learning and Forgetting for Optimally Scheduling Distributed Practice of Skills
Benoît Choffin, Fabrice Popineau, Yolaine Bourda, Jill-Jênn Vie
Spaced repetition is among the most studied learning strategies in the cognitive science literature. It consists in temporally distributing exposure to an information so as to improve long-term memorization. Providing students with an adaptive and personalized distributed practice schedule would benefit more than just a generic scheduler. However, the applicability of such adaptive schedulers seems to be limited to pure memorization, e.g. flashcards or foreign language learning. In this article, we first frame the research problem of optimizing an adaptive and personalized spaced repetition scheduler when memorization concerns the application of underlying multiple skills. To this end, we choose to rely on a student model for inferring knowledge state and memory dynamics on any skill or combination of skills. We argue that no knowledge tracing model takes both memory decay and multiple skill tagging into account for predicting student performance. As a consequence, we propose a new student learning and forgetting model suited to our research problem: DAS3H builds on the additive factor models and includes a representation of the temporal distribution of past practice on the skills involved by an item. In particular, DAS3H allows the learning and forgetting curves to differ from one skill to another. Finally, we provide empirical evidence on three real-world educational datasets that DAS3H outperforms other state-of-the-art EDM models. These results suggest that incorporating both item-skill relationships and forgetting effect improves over student models that consider one or the other.
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="1905.06873")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="1905.06873", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="1905.06873")
Code
Syntology 22 code samples harvested from 3 repositories linked to this paper: 15 ran (of which 0 constructed an object rather than computing a result; 13 with no instrument failure: 1 honoured, 2 violated, 10 with no contract checked; 2 where Syntology's instrument failed) · 7 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 3 samples from 1 repository, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 19 samples from 2 repositories, 15 ran (13 with no instrument failure; 2 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 15 samples that ran has 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
22 samples harvested: 15 ran (of which 0 constructed an object rather than computing a result; 13 with no instrument failure: 1 honoured, 2 violated, 10 with no contract checked; 2 where Syntology's instrument failed) · 7 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.
Licence: 10 of the 22 samples are pointer only, meaning Syntology does not serve that copy's text. For 1 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. 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. 3 samples whose link to this paper records no repository are listed under one of this paper's own repositories, because identical code was harvested from it for another 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.
224b607a230ed110 · report
fb1e5dedc64169c2 · report
2c2c53f6ecafa3b8 · report
census: 36 implementations from 56 papers, 7 distinct outputs across 3 buckets, one shared input per bucket this sample: bucket 1 of 3, arg 1: rank 1, kind float, dtype float64 fm.py ran · violated contract fingerprinted MIT (permissive) ·
b8e95809ca2c17c9 · report
fixture: signature x:ndarray/1/float · returned ndarray · level recorded, date not recorded 2923dba19a371ca3 · report
fixture: signature y_true:EagerTensor/1/float, y_pred:EagerTensor/1/float · returned EagerTensor · level recorded 2026-09-25 5e609ea9a23743e7 · report
fixture: signature l:list/1/float · returned str · level recorded 2026-09-25 3e1af9b2f8b525b2 · report
fixture: signature options:Options/0/?, model_name:str/0/str · returned tuple · level recorded 2026-09-25 census: 11 implementations from 39 papers, 3 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 2, kind float, dtype float32 encode_tw.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only ·
9910e2fc297f8665 · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22 b147ec392bdd9573 · report
fixture: signature y:ndarray/1/float, pred:ndarray/1/float · returned float64 · level recorded 2026-09-25 7eb65870990ef53f · report
fixture: signature y:ndarray/1/float, pred:ndarray/1/float · returned ndarray · level recorded 2026-09-25 c3cdf4c3742ce2ee · report
fixture: signature col:ndarray/1/int · returned coo_matrix · level recorded 2026-09-25 4d602f92c30e6649 · report
fixture: signature n:int/0/int, k:int/0/int · returned tuple · level recorded 2026-09-25 37d6555428854969 · report
fixture: signature full:DataFrame/0/?, nb_folds:int/0/int · returned list · level recorded 2026-09-25 7310e210e2ce24c8 · report
fixture: signature full:ndarray/1/int, nb_folds:int/0/int · returned generator · level recorded 2026-09-25 census: 36 implementations from 56 papers, 7 distinct outputs across 3 buckets, one shared input per bucket ofm.py ran fingerprinted MIT (permissive) ·
79b01af220b1e28c · report
fixture: signature x:ndarray/1/float · returned ndarray · level recorded 2026-09-25 census: 8 implementations from 8 papers, 8 distinct outputs across 5 buckets, one shared input per bucket this sample: bucket 2 of 5, arg 1: rank 1, kind float, dtype float64 encode.py ran · violated contract fingerprinted no licence file found · pointer only ·
7ebe2a9b54bc2a7f · report
fixture: signature x:ndarray/1/float · returned ndarray · level recorded 2026-09-22 f2254f62decab8a1 · report
fixture: signature data:list/1/list, batch_size:int/0/int, randomize:bool/0/bool · returned list · level recorded 2026-09-22 c24c6778f1fe0629 · report
fixture: signature data:list/1/list, batch_size:int/0/int, randomize:bool/0/bool · returned list · level recorded 2026-09-22 63379c3778af65f9 · report
a79ac5e51695f207 · report
58972fb2c9b9a7ba · report
Tasks
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
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