migaku-official / migaku-vacation-addon

Migaku Vacation Addon

An Anki add-on that adds various helpful features such as the ability to set a weekly review schedule, take vacations, schedule overdue reviews our over a period of days so you can catch up on them easily. It also allows you to take a sick day and push your reviews back by a single day whenever you're not feeling very well!

Table of Contents

• Installation
• Documentation
• Contributing
• License and Credits

Installation

1. Install the version of Anki that is listed under the "Migaku Development Cycles" section of the AnkiWeb add-on page
2. Download the latest version of the addon from AnkiWeb

Contributing

Contributions are welcome! Please review the contribution guidelines on how to:

• Report issues
• File pull requests
• Support the project as a non-developer

License and Credits

Migaku Vacation is

*Copyright © 2020 Migaku ltd.

Migaku Vacation is free and open-source software. The add-on code that runs within Anki is released under the GNU AGPLv3 license, extended by a number of additional terms. For more information please see the LICENSE file that accompanied this program.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY.

---

migaku-vacation-addon's Issues

Auto-run optimization on start can overwrite state from a second Anki instance

I duplicate my extensions' folder, so I can access Anki in 2 computers, but this extension might cause a problem, as I explain below.

Today I

1. studied my cards in one computer (computer 1), 0 cards to study in the end;
2. sync with Anki web;
3. started Anki in the 2nd computer (computer 2), which ran the optimization automatically;
4. Anki displayed 60 cards to study.

My guess is that:

1. Optimization was run in computer 2 before fetching the new statuses from Anki web, updating the dates;
2. Then, sync was run, overwriting the Anki web database instead of fetching the statuses uploaded from computer 1.

Running optimization on start seems to hurt consistency.

Intereference with ease?

Hi there,

I love this add on, but also have been a heavy user of Auto Ease Factor, which amends Card Ease on each review to hit a target retention rate. (https://github.com/brownbat/autoEaseFactor)

I'm trying to understand from the code how Migaku Vacation interacts / changes Ease in ways that may make them incompatible (assuming Ease is not set to be maintained at 250%).

From what I can tell, MV and AEF should be compatible since the Interval Modifier is left at 1, and MV just calculates the schedule optimization based on the card Ease determined at point of review by AEF. Is this correct? It seems from my tests that there are some very slight modifications of Ease (1-2%) by MV even with Maintain 250% Ease set to off, but I can't understand what's driving them and they seem (inconsequentially) small.

Any help appreciated and apologies if this is the wrong place to ask!