You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When setting easy days in a week, the review quantity in the remaining non-easy days can become unevenly distributed. This can lead to an unintended buildup of reviews towards the end of the week, making the review load on certain days (e.g., Fridays) significantly higher than on other days (e.g., Mondays). I would like a feature that allows for a decremental load balance, where the review quantity can be adjusted dynamically based on the actual review performance throughout the week.
Describe the solution you'd like
I would like to have a feature that enables decremental load balance within a continuous non-easy day period. This feature should allow the review load to decrease over a cycle of non-easy days, based on factors like daily review volume and success rates. The goal is to simulate a balanced review distribution throughout the week, ensuring that the total review quantity remains consistent.
Describe alternatives you've considered
Without this feature, users have to manually monitor and adjust their review schedules, which is time-consuming and inefficient.
Additional context
This feature will help to maintain a steady review workload, preventing the end-of-week review load from becoming overwhelming. It will make the spaced repetition system more adaptable to the user's actual study and review habits.
The text was updated successfully, but these errors were encountered:
I would like a feature that allows for a decremental load balance, where the review quantity can be adjusted dynamically based on the actual review performance throughout the week.
Such a feature is unlikely to be implemented in the Helper add-on mainly because doing it the right way requires rescheduling after every review. However, rescheduling after every review using an add-on causes problems (see #205 (comment)).
Fortunately, a load balancer is going to be implemented natively in Anki. See ankitects/anki#3230
When setting easy days in a week, the review quantity in the remaining non-easy days can become unevenly distributed.
The native load balancer doesn't have an easy days feature yet. So, the users will need to keep using the add-on's easy days feature unless that developer also implements easy days natively.
But, I believe that the add-on's easy days feature will need significant reworking after the implementation of native load balancer. So, you will need to re-evaluate the feature at that time and tell us if more improvements are needed.
Is your feature request related to a problem? Please describe.
When setting easy days in a week, the review quantity in the remaining non-easy days can become unevenly distributed. This can lead to an unintended buildup of reviews towards the end of the week, making the review load on certain days (e.g., Fridays) significantly higher than on other days (e.g., Mondays). I would like a feature that allows for a decremental load balance, where the review quantity can be adjusted dynamically based on the actual review performance throughout the week.
Describe the solution you'd like
I would like to have a feature that enables decremental load balance within a continuous non-easy day period. This feature should allow the review load to decrease over a cycle of non-easy days, based on factors like daily review volume and success rates. The goal is to simulate a balanced review distribution throughout the week, ensuring that the total review quantity remains consistent.
Describe alternatives you've considered
Without this feature, users have to manually monitor and adjust their review schedules, which is time-consuming and inefficient.
Additional context
This feature will help to maintain a steady review workload, preventing the end-of-week review load from becoming overwhelming. It will make the spaced repetition system more adaptable to the user's actual study and review habits.
The text was updated successfully, but these errors were encountered: