Odd Sleepyhead Stuff - Explain?

I don't understand this... I reinserted the SD card twice, think it might not have been completely reinserted yesterday. I do have the LCD data... AHI is 3.3, but in sleepyhead AHI appears to be cumulative.... What the ?





I assume that whatever the error, it will correct itself overnight....

It's a known bug but unknown how to fix it yet.
Known to happen with the model 960 machines for sure but on occasion happens with the 560 and 460 machines....don't know why.

It may or may not repeat the error tomorrow. You can omit this night by turning off the session...at least removing the high AHI from totally messing up overall averages...on the left side scroll below the statistic numbers clear down to the bottom and turn off the session by turning the green/black bar to red/black. It will turn off any graphs on the right and show zero hours used but at least won't skew your AHI averages.

Which SleepyHead version are you using?
What is the operating system on your computer?

I turned off the graph for today.... I'm running Windows 8.1 and sleepyhead 0.9.3

library lady wrote:sleepyhead 0.9.3

I assume the May of 2013 build.
I don't know if the newest unstable build for Windows will fix the issue or not. Something to think about.
If this continues then we have to talk about using Encore and with Win 8.1...that means Pro 2.13 if you want to use the installer.

You can try the unstable SH build along beside of the 0.9.3 build but there is no installer...have to go into the folder to find the application.exe file to launch the program.

I don't know why SleepyHead works fine and then all of the sudden comes up with these whacko numbers.
One would think it either works or doesn't work...not work fine and then all of the sudden not work.

Let's see if the problem continues and if it does we can discuss your options. Cross your fingers that it was just a fluke bad file affecting calculations.

I had the same type issue and I installed the latest unstable version and it fixed the problem. I'd say it's at least worth a shot.

I tried both the latest version and the latest unstable build. neither fixed the problem. The program was working just fine then one day it starts showing all of these weird numbers like in the OP's post. Had to resort to using Encore.