#NaN log loss

9 messages · Page 1 of 1 (latest)

marble spear
#

Got this while trying to evaluate my FSRS params, any idea what might be causing this?

image.png
solid yacht
#

That's crazy. I would imagine that NaN shows up because of an unhandled exception when calculating your stats. It's possible you might be able to see it if you start Anki from the command line and watch the output in the command line. (The instructions will be slightly different depending on what OS you're using.)

The newest version of Anki (1) has a newer, better version of FSRS (FSRS-6 vs. FSRS-7) and (2) no longer exposes the evaluate button.

@tall citrus might still be interested in why this error occurs (even though it's on an older version of Anki using a deprecated feature), because it might affect the invisible evaluation that occurs after training.

#

Can you post your Anki version and OS here, @marble spear? (Go to Help -> About Anki and copy the version number.)

#

Apparently you can run Anki to see error logs in Windows (which I assume you're using) by

cd /d "%LOCALAPPDATA%\Programs\Anki"

anki-console.bat

In the console.

  1. Change directory to where anki is installed.
  2. Run the batch file that runs Anki and makes sure to output messages.

I don't use Windows so I can't confirm.

marble spear
#

i'll try updating my anki ver, then i'll report back here.

#

i haven't used anki in a while lmao

solid yacht
#

You won't see the error in the new one, because there isn't an evaluate button anymore.

solid yacht
#

I guess I would be curious to see if the built in health check errors out as well 🤔 since it does the evaluate in the background