Learn : Postpone can be used to move outstanding material review to a later time whenever you cannot cope with your daily load of repetitions. This option is particularly useful in heavily overloaded incremental reading. To fully understand the importance of Postpone, you need to master the concept of incremental reading first.
Before the advent of incremental reading in SuperMemo, you had two extreme alternatives:
Neither alternative provides a complete solution to the problem of forgetting. The balance between the two alternatives was left to the student. The optimum strategy was to use traditional learning to sift the strategic material, and then to memorize mission-critical material with SuperMemo.
The confinement of SuperMemo to strategic high-retention material was a powerful inhibitory force against SuperMemo's universal adoption:
Incremental reading bridges the worlds of traditional learning and that of SuperMemo by providing a fluent transition between all priority levels starting from quick review, to repeated passive review, to active review, and to active recall at all levels of the forgetting index down to 3% (i.e. nearly 99% recall rate). Incremental reading also includes an anti-overload option: Postpone that blurs the concept of the must-do outstanding material that had levied a heavy toll on the ranks of SuperMemo users.
Before SuperMemo 2002, incremental reading did not automate the process of "prioritizing by overflow". In other words, high volumes of learning would force the student to manually reschedule learning in branches or subsets of lower priority. Manual rescheduling of the material was necessary to protect core knowledge from a dramatic drop in retention. Substantially reduced retention slows down the learning process not only via the forgetting index vs. acquisition rate relationship, but also through unraveling of the incremental reading process where the new knowledge is built on a shaky foundation of what has been learned earlier. In addition, the flow of thought in incrementally read articles becomes disrupted if the core knowledge retention is not protected.
SuperMemo 2002 introduced Postpone to make it possible to reschedule lower priority material with a keystroke. The student could now painstakingly work out priorities for individual subsets or branches of knowledge and then apply these easily on a daily basis.
SuperMemo 2006 dramatically simplified the process of handling material overflow by introducing the auto-postpone option (Learn : Postpone : Auto-postpone). With auto-postpone, you only need to define the priority of your elements. You can safely leave all postpone parameters in their default settings as these are now primarily used only to define the degree of postpone, which only defines the size of the pool of the low priority material used in interspersing the repetition queue without affecting the high priority material. In simple terms, you do not need to understand Postpone to use it effectively in incremental reading. Just leave Learn : Postpone : Auto-postpone checked. You can re-visit the subject if auto-postpone does not sufficiently reduce the workload in your collection.
Warning! Each time you use Postpone you depart from your chosen level of knowledge retention! Never use Postpone on your most important learning material!
Before you turn auto-postpone make sure that your material is well prioritized. Only then you will be sure that only low-priority elements suffer more forgetting.
The Postpone dialog box presented below includes three tabs: Scope, Parameters, and Adjust. The Scope tab settings are mostly done automatically for you depending on the context in which you use Postpone. The Parameters tab makes it possible to define the degree to which items and/or topics are postponed in the selected subset, and which items and/or topics are exempt from rescheduling. Once you define Parameters you can save the new setting with Scope : Settings : Save. Later you can restore the setting by using Settings : Name box.
Figure: A typical use of Postpone in the browser: you can select the number of elements to remain outstanding (here 50), and click Postpone
You need to understand the Parameters tab if you want to customize the degree of delay in rescheduling.
Figure: Exemplary settings of Postpone parameters. Delay factor of 10 for topics means that topic intervals will be multiplied by 10, but will not be longer than 199 days, or shorter than 33 days. Intervals beyond 2500 days will qualify for a postpone skip (i.e. those elements will not be postponed, unless forced by the Method used on the Scope page). Postpone skip will also affect: items with the forgetting index less than 6, topics with A-Factors less than 1.01, elements that have been postponed more than 250 times, and items with priority greater than 3.5% (i.e. falling into the 0% to 3.5% range) and topics with priority greater than 0.0065%.
Delay factor determines how much elements should be delayed. For example, if you choose the delay of 1.1 (10%) on an element with the interval of 100 days, it will be delayed by ten days, i.e. rescheduled to the interval of 110 days. Postpone will always increase intervals by no less than one day from the present day. This way, all items on which Postpone is executed fall out of the outstanding subset.
Maximum interval puts a ceiling on the length of the delay interval. For example, if you choose the delay of 1.1 on an element with the interval of 200 days, and the maximum interval is 5 days, the element will be delayed only by 5 days (instead of the 20 days produced by multiplying the original interval by the delay factor).
Minimum interval puts a floor on the length of the delay interval. For example, if you set it to 3, all delayed elements will be delayed by no less than 3 days.
Skip conditions determine which elements will be exempt from delay.
- if you check Skip items or Skip topics, items or topics (respectively) will not be rescheduled
- Interval beyond will exempt elements with intervals longer than a selected value. For example, if you set Interval beyond to 320 days, no elements with interval longer than 320 days will be rescheduled. This can help you avoid infinite postpones. Once the element is postponed beyond a given interval, it will automatically enter the core of elements that will not be postponed
- Forgetting index below makes it possible to determine the level of the forgetting index that will prevent items from being postponed. For example, if you set Forgetting index below to 5%, items with the forgetting index of 3% and 4% will not be rescheduled. This way you can make sure that the most important items in your collection are protected from a drop in retention
- A-Factor below is analogous to Forgetting index below. The only difference is that you will use it with topics instead of items. Set A-Factor of most important articles to a very low value (e.g. 1.01). This way you will be able to filter them out at Postpone and make sure they never get rescheduled
- Postpone count helps you prevent numerous postpones. For example, if you set the postpone count to 6 in the Items column, items will only be postponed 6 times. After that, Postpone will not affect them
- Priority (%) makes it possible to avoid rescheduling of elements whose priority falls into a selected percentile bracket (low % indicates high priority)
The Adjust tab can be used for fine tuning delays on subsets with a complex priority structure of individual branches of knowledge. Sub-branch postpones determine how the rescheduling procedure interprets branches included in the subset that have their own postpone settings defined. Here are the possible options:
Advanced settings on the Adjust tab include:
Once you define the settings on the Parameters tab and, optionally, fine tune them on the Adjust tab, save them with Save on the Scope tab. You can now test the postpone procedure by clicking Simulate. If you are not satisfied with the results, redefine Parameters. Once you are happy with the result of the simulation, Save the settings and choose Postpone.
The option Dilute (e.g. Learning : Dilute on the subset processing menu) should only be used in rare circumstances. It is analogous to Postpone but it also delays elements that are not outstanding. There are two main reasons for using Dilute:
Auto-postpone affects only outstanding elements scheduled on preceding days. For example, on Dec 1, 2009, repetitions from all days up to Nov 30, 2009 will be subject to default Postpone. Only repetitions scheduled on Dec 1, 2009 (and in the future) will not be affected.
To edit the default postpone settings, use View : Outstanding and Process browser> : Postpone on the browser menu. Skip the following number of top priority elements can be used to determine how many elements will be skipped when executing Auto-postpone. This field is independent of Skip conditions. If you set this field to 50, you will ensure that on any given day, only that day's repetitions and 50 unexecuted outstanding repetitions will be kept in the outstanding queue.
For example, if (1) Skip the following number of top priority elements is set to 50, and if (2) you have 600 outstanding repetitions from previous days, and if (3) you have 200 new outstanding repetitions, then 550 repetitions will be auto-postponed (600-50=550). This way, you will have 50+200=250 repetitions to make.
If your daily load of items and topics keeps increasing, you can dilute the learning process with selective postpones from time to time. For example, you can opt to delay repetitions in subsets such as:
Here are some typical ways in which you will execute Postpone:
For more details see: Postpone, Advance and Mercy