Sleepyhead Leak Graph Anomaly

[dxdy]

I have been using Sleepyhead 0.9.3 with my new PRS1 560P for a month now. The one thing I look at every morning is leaks, because that is something I can actually affect - adjusting my Mirage Quattro mask, cleaning it, etc. The other night I came up with the following graph for leaks. For some reason, the total leaks line is crossing the leaks line. This has not happened before or since.
Any thoughts?

(If I need to post this to the SourceForge bug page, I will, if I can figure out how!)

[jdm2857]

That leak graph is very strange.

As you know, SleepyHead subtracts it's guesstimate of mask intentional leak from the total leak to obtain
the leak numbers. As such leak should always be less that total leak.

So something is wrong. It will be interesting to see if this anomaly has been seen by anyone else.

[Pugsy]

Only one night or have all the nights began to look like this?

If one night...might just be a little problem in the data file on the SD card that does the leak report as in corrupted file for that one night.
Might also be a bug for the 760 that just popped up. The 60 series and SH is probably the most buggy and has the least amount of work.

I don't know if this will help or not or if really needed but go to Preferences/Appearance tab and remove the check mark for "use pixmap caching" and see what happens.

I am using a 60 series machine now...the 660..and so far leak line is fine.
I turned off pixmap caching a while back due to squirrelly pressure lines on my 750...

[dxdy]

Thanks for the quick replies.

This only happened the one night. Since then it has been fine. I tried removing the check mark for "use pixmap caching" and it has not made a difference. This is happening on two different computers.

This is a PRS1 560P, and I realize the 60 series may have some issues with SH.

The only thing unusual about this night was no oximetry data - I had fat-fingered my CS50d+ and deleted its data prior to import.

[Pugsy]

If it is a one time issue and no one else can repeat the problem then I don't see the need to send a bug report at this time.
It could simply have been a little blip in the file on the SD card and SH choked on it.
You could also use EncoreBasic to see what it shows but I bet it doesn't show anything out of the ordinary...if it did and was repeating itself then we have a machine recording issue instead of a hiccup in the data file for one night.

I would blame the usual suspects in this case unless the error returns and stays....aliens.