[v3] Scheduling is broken, card is always moved to 1 about incremental-reading HOT 6 CLOSED

I'm not sure if there are any other issues with the scheduler, but the problem that @Smingvin mentions, in particular, is due to the way that python 2 deals with the division of integer values, which are not automatically cast to float, this can be solved one of two ways, both in scheduler.py,

Either change the following line, (which was resulting in 0 every time due to loss of precision):

    newPos = totalCards * (value / 100)

to

    newPos = totalCards * (float(value) / 100)

or, my preferred way is to import the more robust division, by changing the very first line to

from __future__ import unicode_literals, division

from incremental-reading.

@SijanC147, thanks so much for that. I've made the suggested change. Hopefully this resolves the main issue here.

from incremental-reading.

Also, unlike with v4, scheduling is recorded in the card's history:

Date	Type	Rating	Interval	Ease	Time
2017-12-10 @ 23:19	Learn	3	3d	250%	3.2s
2017-12-10 @ 23:18	Learn	2	1d	250%	1.2s
2017-12-10 @ 23:16	Learn	1	1m	250%	1.7s
2017-12-10 @ 23:16	Learn	2	1d	250%	1.7s
2017-12-10 @ 23:15	Learn	2	1d	250%	1.6s
2017-12-10 @ 23:14	Learn	2	1d	250%	4.5s
2017-12-10 @ 23:12	Learn	2	1d	250%	15.6s

from incremental-reading.

I do remember fixing a lot of issues with scheduling in v4. I'll see how much of that I can backport to v3. I understand that Anki 2.0 isn't going anywhere any time soon.

Thanks.

from incremental-reading.

New user here (a couple of days), Anki 2.0.41, ir cards always moved to 1 regardless of what I click.

from incremental-reading.

I tested the scheduler a bit. This is what happens:

Settings: percentage, randomize.

1. Any percentage between 0 and 99 will return the card to position 1.
2. If you set percentage to 100, cards will be moved to (or near) the bottom of the pile.
3. If you set percentage to above 100 (either 150 or 1000) the cards will be moved to the bottom, while the tooltip will report a proportionate but non-existing index (for example: "card is moved to position 350", even though the deck has 50 cards so it is actually moved to 50)

I hope this information will be helpful for debugging.

from incremental-reading.