掲示板 Forums - Holiday system - feedback and bugs

(In the experimental panel as of May 12th)

The system is doing significant logging on this, so please report any issues you have. However, I cannot reverse review times if something goes wrong, so please keep that in mind before using this feature.

Current stage of development:

Two: Streaks will not grow or be broken on holidays. Additionally, if you had a holiday in the past, it will appear as a 休 mark in your heatmap (if enabled in Stats). Same with the trophy streak on the schedule page.

Stage one:

1. Allow for selection of one or more holidays. On these days, no reviews will be scheduled (see below for technical details).

2. When changing holidays, allow for option to move away all reviews already schedule on those days (as #1 only handles reviews scheduled from here-on out)

Stage two:

1. Integrate system into heat map and streaks. For holidays, streaks will not be broken (although I have not yet decided if to allow them to increase or not). For the heat-map, it'll get a nice little 休 character on it.

Stage three:

1. Expand/rewrite visuals on the options to allow for blocking of new terms as well on days (a separate set of checkboxes). So, you could do something like this "holidays on sat/sun, no new terms on mon/fri".

Stage four:

1. Allow ways to do one-off holidays - this will be quite tricky technically (especially with streaks, so that might not be possible), but I'd like to offer ways to both specify future one-off holidays, or say "hey, so the last two days, mark those as holidays after the fact"

Technical details

1. When a day of the week is marked as a holiday, it effectively ceases to exist in the calendar. So if you are on Monday, and you have Tuesday as a holiday, then when the system says "schedule it for a day in the future", it will not even see Tuesday, and just say "ok, Wednesday is one day away". That's it! Deceptively simple.

2. When you change holidays (or set holidays for the first time), you have the option of moving away all reviews that are on a holiday. So, if you set Tuesday as a holiday, it'll find all reviews on Tuesday and move them to the next non-holiday day (in this case, Wednesday).

Because of this, changes to holidays can create one-time "clumping" as an day after a holiday is going to get all the reviews from that holiday. This will not exist afterwards, as reviews scheduled after that will spread out evenly across all the non-holiday days (in the way it does now).

The user is warned on the settings panel not to frequently change the holidays, as this can amplify the chance of clumping taking place. So saying "oh, I won't be able to study this Wednesday, let's mark it as a holiday, then unmark it after". That would, in this example, potentially take all the Wed reviews (which, in this contrived example, also has the Tue reviews) and move them all to Thursday. The holidays should be set and changed sporadically.

3. Even though you have a holiday on say Tuesday, if you do not finish your reviews on Monday, you'll still have them available to review on Tuesday. It's just that no reviews are specifically scheduled FOR Tuesday.

4. At a point in the future, I'd like to look into more spreading options. For example, for any future reviews 10 or more days in the future, consider a few days around that day as well, and drop it wherever reviews are lightest. The problem with this (compared to anki, for example) is that most renshuu users have multiple schedules (and often with overlapping terms), so actually getting an accurate count of global reviews expected for each day is quite intensive, work-wise

It has ..a bit, but not a ton. I have to work within the confines of the way the scheduling data is stored (it is very simple) so I do not need to severely overhaul both the database and the code that works with that data, so I think the balancing will need to be done on the spot - when the review is scheduled, and not afterwards.

It holds onto a single date (day), that's it. The larger issue is that it does not explicitly hold onto the # of days (as in, "move ahead 7 days"), so if the action is not done right then, then later on, if there are two terms each schedule for "tomorrow", I will not have the info to say if one was scheduled from today to tomorrow compared to the second behind scheduled 3 months ago.

shouldnt matter, I didnt even think about anything aside from the date itself. action transform is ephemeral, it doesnt matter if it was scheduled to be tomorrow from 2 months ago or yesterday. human will lose efficiency if the card is newer versus older by adding a day, but for a function only run in more extreme circumstances, I dont think it matters. what you could do is just check the mastery of the card and have a tunable on that. like "if mastery < n%". so default 20% user changeable. if mastery under 20%, card will NOT get moved because more critical early learning period.

just some ideas for you. sorry if this went off topic. thank you for all u do here, and thanks for always adding new features! and u and family hope had enjoyable and relaxing golden week

coding at the speed of light!

You will have no new reviews to study. Any reviews leftover from previous days will still be there.

New terms will still come up. That's stage 3 in the steps above, so you'll be able to block new terms if you'd like as well.

However, you can fully access the schedule and all features. It'll just be as if, well, no terms were schedule for review that day.

So, to specifically clear up your two questions:

1. Don't finish terms on friday = reviews will be available for studying on Saturday

2. Finish all reviews on Friday = 0 reviews on Saturday (none scheduled)

3. The streak integration will be soon. Getting it to work with the heat map is much harder, and will take more time, but I may get the streak stuff done today! Of course, if you enable it, and a bug in this system causes you to lose your streak, I will happily restore it.

4. Say you have no holidays set on the weekend, and you usually study. But for whatever reason, you didn't touch renshuu on Sat/Sun. Monday rolls around, and you think "ugh, I wish I had frozen it on Friday". This feature will basically be a way to activate a freeze on Sat/Sun, after it happened. You will not be able to do this to restore streaks, but it WILL do the same thing that a streak would do, effectively showing the reviews as if you hadn't missed two days.

Stage 2 (streak integration, not heat maps) should be live!

Bug?: I've got a little holiday mark on my heatmap and schedule-based heatmap for today even though I have no days selected as a holiday under the experimental settings.