# Anki 23.10 Beta 1-4

**URL:** <https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912>\
**Category:** Beta Testing\
**Created:** [September 24, 2023, 7:14am UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912 "2023-09-24T07:14:31Z")\
**Posts on this page:** 20\
**Page:** 10

<div class="post-metadata">

**Author:** ![zZH2z](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/zzh2z/32/23935_2.png) [@zZH2z](https://forums.ankiweb.net/u/zZH2z)\
**Post date:** [October 8, 2023, 7:19pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/186 "2023-10-08T19:19:23Z")

</div>

Hi,

I try to figure out what is the relationship between FSRS settings and “New cards/day”. Is there any? Are they independent? May it is under development? I ask to better understand how to manage my workload.

“Compute optimal retention” suggest that there is some relationship due to “Minutes study/day” but when I change “New cards/day” then it compute the same values.

Thanks

---

<div class="post-metadata">

**Author:** ![szalejot](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/szalejot/32/16310_2.png) [@szalejot](https://forums.ankiweb.net/u/szalejot)\
**Post date:** [October 8, 2023, 7:37pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/187 "2023-10-08T19:37:20Z")

</div>

FSRS retention calculation doesn’t take other deck settings into consideration, only the values you provide in this section.

---

<div class="post-metadata">

**Author:** ![Expertium](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/expertium/32/24176_2.png) [@Expertium](https://forums.ankiweb.net/u/Expertium)\
**Post date:** [October 8, 2023, 7:46pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/188 "2023-10-08T19:46:45Z")

</div>

“New cards/day” works exactly the same way with and without FSRS, and it doesn’t affect the output of “Compute optimal retention”.

---

<div class="post-metadata">

**Author:** ![Expertium](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/expertium/32/24176_2.png) [@Expertium](https://forums.ankiweb.net/u/Expertium)\
**Post date:** [October 8, 2023, 9:27pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/189 "2023-10-08T21:27:42Z")

</div>

I know I said this before, but an option to reoptimize parameters after a certain number of days (or reviews) would be amazing. Right now, users have to remember to re-optimize parameters periodically, which is much less convenient than leaving it to Anki.

---

<div class="post-metadata">

**Author:** ![chrislg](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/chrislg/32/32411_2.png) [@chrislg](https://forums.ankiweb.net/u/chrislg)\
**Post date:** [October 8, 2023, 9:29pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/190 "2023-10-08T21:29:38Z")

</div>

I agree. And could be based on the number of reviews someone does, not necessarily to a time period

---

<div class="post-metadata">

**Author:** ![aerreteagauerre](https://avatars.discourse-cdn.com/v4/letter/a/b77776/32.png) [@aerreteagauerre](https://forums.ankiweb.net/u/aerreteagauerre)\
**Post date:** [October 8, 2023, 10:01pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/191 "2023-10-08T22:01:09Z")

</div>

I get this every time I try to activate FSRS:

DbError { info: “SqliteFailure(Error { code: Unknown, extended\_code: 1 }, Some(\“Expression tree is too large (maximum depth 1000)\”))”, kind: Other }

anyone got any idea?

---

<div class="post-metadata">

**Author:** ![ghranx](https://avatars.discourse-cdn.com/v4/letter/g/e79b87/32.png) [@ghranx](https://forums.ankiweb.net/u/ghranx)\
**Post date:** [October 9, 2023, 12:58am UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/192 "2023-10-09T00:58:54Z")

</div>

Anki doesn’t remember the preview window size, it did remember it in 2.1.65 but stopped in .66 and still isn’t fixed.

---

<div class="post-metadata">

**Author:** ![Shigeyuki](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/shigeyuki/32/23878_2.png) [@Shigeyuki](https://forums.ankiweb.net/u/Shigeyuki)\
**Post date:** [October 9, 2023, 3:30am UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/193 "2023-10-09T03:30:49Z")

</div>

> This is a big update, and it’s going to break some stuff. Addons that were using pointVersion() instead of doing their own version parsing will be unaffected.

This is not an important question, but why not “Anki 2.2.10”, “Anki 2.3.10” or “Anki 3.0”?

---

<div class="post-metadata">

**Author:** ![jcznk](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/jcznk/32/15215_2.png) [@jcznk](https://forums.ankiweb.net/u/jcznk)\
**Post date:** [October 9, 2023, 3:52am UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/194 "2023-10-09T03:52:23Z")

</div>

The logic is `year.month` (and eventually `year.month.patch`)  
So 23.10 stands for october 2023.

This way, it becomes easier to identify when a version was published, and to distinguish at a glance between minor and major releases.

> [@Use a different versioning system? SemVer, perhaps?](https://forums.ankiweb.net/t/use-a-different-versioning-system-semver-perhaps/20046/8):
>
> If 2.1.45+ corresponded to 21.7.0~21.7.4 and 2.1.50+ to 22.4.0~22.4.4, there’s more semantic info than what we currently have where only the patch number is used.

> [@Use a different versioning system? SemVer, perhaps?](https://forums.ankiweb.net/t/use-a-different-versioning-system-semver-perhaps/20046):
>
> As an addon developer I find Anki’s versioning a bit… unfortunate. Specifically, I have a problem with Anki not using patch versioning. A lot of users are stuck with older versions of Anki since they need addons that do not support later Anki versions. So I also want to support a few older versions. The problem with this is, from Anki version numbers I can’t tell which versions I should test against and which I should ignore. For instance, Anki 2.1.49 was a “stable” version. Anki 2.1.52 was ju…

---

<div class="post-metadata">

**Author:** ![Shigeyuki](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/shigeyuki/32/23878_2.png) [@Shigeyuki](https://forums.ankiweb.net/u/Shigeyuki)\
**Post date:** [October 9, 2023, 4:05am UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/195 "2023-10-09T04:05:38Z")

</div>

Thanks, that’s efficient.

---

<div class="post-metadata">

**Author:** ![jcznk](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/jcznk/32/15215_2.png) [@jcznk](https://forums.ankiweb.net/u/jcznk)\
**Post date:** [October 9, 2023, 10:59am UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/196 "2023-10-09T10:59:45Z")

</div>

After disabling FSRS, when I click on Save I get this error message and Anki crashes.  
No add-ons active.

```auto
A fatal error occurred, and Anki must close. Please report this message on the forums.
Anki 23.10 (02ade8e7) Python 3.9.15 Qt 6.5.2 PyQt 6.5.2
Platform: Windows-10-10.0.19045
Flags: frz=True ao=False sv=?
Add-ons, last update check: 2023-10-09 07:51:30

Caught exception:
Traceback (most recent call last):
  File "aqt.progress", line 118, in handler
  File "aqt.taskman", line 126, in <lambda>
  File "aqt.operations", line 122, in wrapped_done
  File "concurrent.futures._base", line 439, in result
  File "concurrent.futures._base", line 391, in __get_result
  File "concurrent.futures.thread", line 58, in run
  File "aqt.operations", line 107, in wrapped_op
  File "aqt.operations.deck", line 88, in <lambda>
  File "anki.decks", line 297, in update_deck_configs
  File "anki._backend_generated", line 1557, in update_deck_configs_raw
  File "anki._backend", line 151, in _run_command
pyo3_runtime.PanicException: command requires weights to be set on creation

```

---

<div class="post-metadata">

**Author:** ![meliache](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@meliache](https://forums.ankiweb.net/u/meliache)\
**Post date:** [October 9, 2023, 11:58am UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/197 "2023-10-09T11:58:46Z")

</div>

Since there was no other reply, I think this bug seems to have been fixed in this commit: [Fix 'Expression tree is too large' when user has many decks · ankitects/anki@0e6104a · GitHub](https://github.com/ankitects/anki/commit/0e6104a96b5adb2caf1f8845d4bb9407510e787). So this will be fixed in the next beta release if you don’t want to compile the source. I didn’t try yet to read the code and understand the nature of the bug, but judging from the commit title it has to do with the number of decks. So if you can’t wait for the next beta and don’t want to compile from source you might try a workaround of using fewer decks per preset (e.g. assigning preset copies to decks). Though I didn’t test whether that would work in practice.

---

<div class="post-metadata">

**Author:** ![Filipe](https://avatars.discourse-cdn.com/v4/letter/f/35a633/32.png) [@Filipe](https://forums.ankiweb.net/u/Filipe)\
**Post date:** [October 9, 2023, 5:08pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/198 "2023-10-09T17:08:15Z")

</div>

Integrated FSRS not apply parameters “per preset” ??? 😵

I think this is a big problem for my type of decks. 🥴

---

<div class="post-metadata">

**Author:** ![cjdduarte](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/cjdduarte/32/29286_2.png) [@cjdduarte](https://forums.ankiweb.net/u/cjdduarte)\
**Post date:** [October 9, 2023, 5:35pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/199 "2023-10-09T17:35:26Z")

</div>

For me it was too. But I adapted. See if your situation is for the same reason as mine.

Here is the proposed solution.

> <https://github.com/open-spaced-repetition/fsrs4anki-helper/issues/253#issuecomment-1741769211>
>
> \*\*Describe the bug\*\*
> 
> With the same weights in both versions and using the sam…e database, when triggering the "Reschedule all cards" function in Anki 2.1.66 for today, there are 175 cards to review.
> 
> In Anki 23.10 using the integrated FSRS, and again triggering the "Reschedule all cards" function, it tells me to review 325 cards.
> 
> \*\*Environment\*\*
> - Anki version: \[e.g. 2.1.66 and 23.10\]

---

<div class="post-metadata">

**Author:** ![Filipe](https://avatars.discourse-cdn.com/v4/letter/f/35a633/32.png) [@Filipe](https://forums.ankiweb.net/u/Filipe)\
**Post date:** [October 9, 2023, 6:02pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/200 "2023-10-09T18:02:51Z")

</div>

![IMG_6975](https://us1.discourse-cdn.com/flex002/uploads/anki2/original/3X/c/e/ce6334cf26a386f27e2f4c03d2592168fd431dbf.png)

I’m confusing now

---

<div class="post-metadata">

**Author:** ![pavreh](https://avatars.discourse-cdn.com/v4/letter/p/0ea827/32.png) [@pavreh](https://forums.ankiweb.net/u/pavreh)\
**Post date:** [October 9, 2023, 7:19pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/201 "2023-10-09T19:19:19Z")

</div>

If you switch the integrated FSRS on, it is activated for all presets, but parameters are set for each preset independently. First, you cannot use V3 for one deck and FSRS for another deck. You must use either V3 or FSRS. It is actually the same logic as there has been V2 and V3 scheduler. Second, If you switch FSRS on, you need to calculate weights for every preset.

---

<div class="post-metadata">

**Author:** ![pavreh](https://avatars.discourse-cdn.com/v4/letter/p/0ea827/32.png) [@pavreh](https://forums.ankiweb.net/u/pavreh)\
**Post date:** [October 9, 2023, 7:40pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/202 "2023-10-09T19:40:33Z")

</div>

I have tested FSRS a bit. I changed presets, set parameters, answered few cards and finally I wanted to switch FSRS off. I have got the message as below after switching off the FSRS toggle.

> **A fatal error occurred, and Anki must close. Please report this message on the forums.**
> 
> Anki 23.10 (02ade8e7) Python 3.9.15 Qt 6.5.2 PyQt 6.5.2  
> Platform: Windows-10-10.0.22621  
> Flags: frz=True ao=True sv=?  
> Add-ons, last update check: 2023-10-09 21:04:09
> 
> Caught exception:  
> Traceback (most recent call last):  
> File “aqt.progress”, line 118, in handler  
> File “aqt.taskman”, line 126, in   
> File “aqt.operations”, line 122, in wrapped\_done  
> File “concurrent.futures.\_base”, line 439, in result  
> File “concurrent.futures.\_base”, line 391, in \_\_get\_result  
> File “concurrent.futures.thread”, line 58, in run  
> File “aqt.operations”, line 107, in wrapped\_op  
> File “aqt.operations.deck”, line 88, in   
> File “anki.decks”, line 297, in update\_deck\_configs  
> File “anki.\_backend\_generated”, line 1557, in update\_deck\_configs\_raw  
> File “anki.\_backend”, line 151, in \_run\_command  
> pyo3\_runtime.PanicException: command requires weights to be set on creation

---

<div class="post-metadata">

**Author:** ![meliache](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@meliache](https://forums.ankiweb.net/u/meliache)\
**Post date:** [October 10, 2023, 4:16pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/203 "2023-10-10T16:16:13Z")

</div>

Regarding the re-optimizing discussion, the main reason why I find it annoying is that I have to go through each preset and optimize it individually. Therefore I would also like to have either an automatic periodic optimization or a _“Optimize all presets”_ option. With the latter I would only need one click, so it would be less annoying to do that periodically.

As optimization takes a while there should be considerations whether that can run in the background. And some thought should be put into how to treat errors during automatic optimization. So I think this is a good feature for future releases, but I have doubts that we’ll get that for 23.10.

---

<div class="post-metadata">

**Author:** ![Filipe](https://avatars.discourse-cdn.com/v4/letter/f/35a633/32.png) [@Filipe](https://forums.ankiweb.net/u/Filipe)\
**Post date:** [October 10, 2023, 4:31pm UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/204 "2023-10-10T16:31:17Z")

</div>

Ah, ok.

Using weights per preset is enough for me.

---

<div class="post-metadata">

**Author:** ![Expertium](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/expertium/32/24176_2.png) [@Expertium](https://forums.ankiweb.net/u/Expertium)\
**Post date:** [October 11, 2023, 8:18am UTC](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912/205 "2023-10-11T08:18:26Z")

</div>

About “Loss aversion”. Right now, I don’t see any way to understand what it does without:  
a) Asking the devs or LMSherlock  
b) Looking into the source code  
It’s safe to assume that the average person will have no idea what it does. So either it needs to be removed or there should be a tip that appears when you click on it. Of course, that would be helpful for all FSRS-related settings, it’s just that this is the least intuitive one, it would benefit from having a tip the most. But ideally, it should be hidden. FSRS already has problems with being intuitive and easy to understand, “Loss aversion” is straddling the line between “hard to understand” and “you literally need to be a developer to understand”.

[Previous page](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912.md?page=9)

[Next page](https://forums.ankiweb.net/t/anki-23-10-beta-1-4/34912.md?page=11)
