npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

sm2-plus

v1.0.6

Published

A javascript implementation of an improved version of SM2 spaced repetition algorithm

Downloads

5

Readme

Warning: this project has been deprecated

The algorithm itself has some inherent flaws, open this post to see why this lib is being deprecated.

If you are still looking for a space repetition lib, check memory-scheduler in lieu of this lib.


sm2-plus


This is a JS implementation of a refined version of the SM2 space repetition learning algorithm invented by BlueRaja overcoming some of the inherent issues of the original version. Details about what these issuses are and how BlueRaja solved them can be found in this post.

Installation

$ npm install sm2-plus --save

Usage

import { WORST, BEST, calculate, getPercentOverdue } from 'sm2-plus';

const DAY_IN_MINISECONDS = 24 * 60 * 60 * 1000;
const getDaysSinceEpoch = () => (
    Math.round(new Date().getTime() / DAY_IN_MINISECONDS)
);

const TODAY = getDaysSinceEpoch();

const testWord = {
  word: 'test',
  update: TODAY - 17,    
  difficulty: 0.2,
  interval: 100
};

console.info(calculate(testWord, BEST, TODAY));

The output should be:

{ 
  difficulty: 0.19,    
  interval: 1,
  dueDate: TODAY+1,
  update: TODAY,
  word: 'test' 
  }

Among them dueDate is the date the next time when the item should be reviewed.

Simulation

It is good to be able to make a evaluation about how many times does the user has to study to totally remember a word in the best case.

Thus a simulation method was export to do this job.

The first argument is the initial difficulty and the second argument is the threshold below which a word can be seen as remembered.

import { simulate } from 'sm2-plus'
simulate(0.3, 0.1);

The output would be like this, meaning that in the best condition, a user has to remember a word and select BEST 4 times to make sure that he has mastered the word whose initial difficulty is 0.3.

| Day | Index | Difficulty | | ------------- | ------------- | -------------| | 0 | 1 | 0.3 | | 1 | 2 | 0.24117647058823527| | 2 | 3 | 0.18235294117647055| | 3 | 4 | 0.12352941176470585| | 4 | 5 | 0.06470588235294114|

Algorithm Abstract

Each item should be stored as the following structure:

  • difficulty: How difficult the item is, from [0.0, 1.0]. Defaults to 0.3 (if the software has no way of determining a better default for an item).
  • interval: How many days should occur between review attempts for this item.
  • update: The last date this item was reviewed.

When reviewing item, choose a performanceRating from [0.0, 1.0], with 1.0 being the best. Set a cutoff point for the answer being “correct” (default is 0.6). Then the item data can be updated using the way described below:

  • percentOverdue= (today - update) / interval) (2 <= percentOverdue)

  • difficulty = difficulty + percentOverdue * (8 - 9 * performanceRating) / 17 (0 <= difficulty <= 1)

  • difficultyWeight = 3 - 1.7 * difficulty

  • interval =

    • 1 + (difficultyWeight - 1) * percentOverdue (for correct answer)
    • 1 / difficultyWeight / difficultyWeight (for incorrect answer)