I’m sorry, the screenshot was taken after I changed the settings!
What are your thoughts? Will the FSRS scheduler work properly?
Thanks!
I’m sorry, the screenshot was taken after I changed the settings!
What are your thoughts? Will the FSRS scheduler work properly?
Thanks!
It didn’t work well in your case, so I need more details about your settings and actions.
OMG, I just changed my previous settings to the ones on the screenshot. If I ever face that same issue again, I’ll let you know because I can’t remember how I answered that particular card at that time as I’m revising 160 review cards and 35 new ones.
Thank you!
Thank you for your work!
I’m new to Anki and don’t have a lot of usage logs, but I did the export and ran the optimizer, but in " 2.2 Train the model" there is an error at the line “dataset[‘tensor’]” the error is: “ValueError: Wrong number of items passed 16, placement implies 1”
Is it because my logs are too small?
Could you share your uploaded files with me? I need it to check the problem.
Sure! How can I share it with you?
You can use it:
I can’t include links. Does the QR Code work for you?
Thank you for looking into this. I did a new export and ran the optimizer and it worked with no errors.
So, If I am using the AnkiMobile iOS beta and I see the code in the custom scheduling on the iOS app, do I need the FSRS4Ankihelper addon?
It is unnecessary to use the Helper add-on if you use FSRS on AnkiMobile and Anki PC.
How do I get the FSRS enabled logo to appear in the bottom left corner of my review screen. It is a bit distracting to see it in that location.
Also, when you update the repository on GitHub, do we have to change any files in the custom scheduling? Or does it automatically update?
I will improve it tomorrow. I have tried to put in the bottom, but it doesn’t show correctly in the AnkiMobile.
@L.M.Sherlock If you’re planning to use position: fixed
, this might save you some time:
Ah yes, it seems like Safari for iOS makes some weird use of a visual viewport, allowing you to zoom/scroll independently of the actual document boundaries.
I think the -webkit-fixed
can be omitted by now (I just posted it without testing hoping it might help). Regarding your use case: As the element you’re styling is contained inside the document body, it is displayed relative to the body’s dimensions. By default the body only takes as much height as it needs for the content. If you want the element to display at the bottom left of the screen, you’ll have to give the body a min-height, e.g. 100vh
.
I have fixed it in the latest version:
Thanks for @kleinerpirat’s suggestion.
So how do we go about updating FSRS? Is it automatic or do we have to change the code after every update?
I’m sorry for the frequent updating recently. You need to change the code if the new patch or feature is your need. FSRS is stable if I stop introducing new functions.