Blahah wrote:
This doesn't work in chrome or safari - is this a problem with a framework you're using?
It should work fine on both now.
Daichi wrote:
Can you explain what variables you stick in with a bit more detail?
The model works like this: each card has an interval, measured in days, and a due date. When the due date equals the current date, the card is tested. The test is probabilistic: if the interval is less than or equal to 21 days, the card has a young rate probabilty of passing; if the interval is greater than 21 days, the card has a mature rate probability of passing. When a card passes the test, its interval is multiplied by the success multiplier and it's scheduled to tested again in interval days. When it fails, its interval is multiplied by the failure multiplier and it's scheduled to be tested again in the following day. After all due cards are tested, up to new cards per day are created, and are scheduled to be tested in the following day. You can define the initial interval of the new cards.
This model differs from SRS'ing with Anki in two ways: first, there are only two buttons: pass or fail. Second, the success multiplier is fixed; Anki changes it based on how you grade the cards.
This model differs from reality in at least one significant way: the test is probabilistic and the rates are fixed. To see why this is a problem, just imagine a deck with a fixed number of cards. No matter how hard the cards are, it's almost certain you'll master them in a finite amount of time. In other words, it's almost certain that your rates will raise until they reach 1. As the simulator uses fixed rates, this will never happen.
But anyway, I hope it's close enough for a rough estimate. If you can think of a better model, please do suggest it, and I'll try to implement it. 
Last edited by iSoron (2010 May 27, 1:00 pm)