Archived SH Discussions [Q&A Thread from Sep-2011 thru May 2014]

[zonk]

From encore basic glossary
Snore: A loud upper airway breathing sound during sleep, without episodes of apnea.
Vibratory Snore (VS) Index
The Vibratory Snore Index is the total number of vibratory snoring events per night divided by the hours of use

[MrSafety]

I have been unable to find how to reset either Date or Time for my PRS1!
The reason I was looking for this is that I would like to adjust the time when we go through a change in DayLight Savings time!
Q - Does SleepyHead take whatever time my Operating System has?

Also from time to time, my SleepyHead appears to NOT be able to show data for the previous night when "Import" the new data from my SD chip!
Some times it does and some times it doesn't... even though I wait until Noon-time which is where I have "PREFERENCES/Import/Day Split Time" set for "12:00 PM" (Noon) inside SleepyHead.
For instance, right now I'l have to wait until tomorrow a.m. to see yesterday's data even though I have already downloaded and made it available to SleepyHead !
Am I making any sense??
Regards,
Sam Ross

[robysue]

From encore basic glossary
Snore: A loud upper airway breathing sound during sleep, without episodes of apnea.
Vibratory Snore (VS) Index
The Vibratory Snore Index is the total number of vibratory snoring events per night divided by the hours of use

Yes, the Encore basic glossary says that. But---if you look at the snoring data in Encore and you look at the same snoring data in SH you can get very different impressions. And if SH is counting the number of VS and VS2's correctly, then the Encore VSI is just plain NOT equal to the number of vibratory snore events divided by the hours of use.

As an example: Here are screen shots of the same night's data from way back when (Feb. 16, 2011), when I was still using my BiPAP in fixed pressure mode at 7/4 and had a particularly bad night for snoring:

First Encore's view of the night:

The Encore VSI = 118.3, which is one of my highest Encore VSI numbers in three years of data. Although what this means is not clear. The usage for this night was a bit over 5.5 hours. If we use the standard idea that Event Index = (number of events)/(run time) to try to compute the number of "Encore VS" snores for the night, we wind up with an astonishing 650 "Encore VS" snores, which seems somewhat unlikely given the fact that the snore ticks are not so densely packed as to become solid red rectangles and there's a huge part of the night with no snoring recorded.

When we look at the same data in SH, we pick up different things based on whether we have the Details or the Events tab selected in the left side bar. When Details is selected, we see this information:

Several things stand out in this picture of the data. First and foremost, all of the indices except the VSI equal the corresponding Encore index once you round the SH indices to one decimal place. Next: the SH VSI = 0.0 even though some serious snoring is obviously going on. (Remember, the Encore VSI = 118.3 and there are a lot of tick marks on that VS2 line in the event table.) The Snoring statistics show nonzero numbers for the 90% and Maximum values, although the Max Snore = 25, which is still way, way smaller than the Encore VSI = 118.3. And the Snore graph clearly has some (serious) bumps in it.

Part of trying to reconcile the SH version of the data with the Encore version involves understanding that when JediMark stared working with the System One data, he discovered that it records two kinds of snoring data, which he called VS and VS2 snores.

But ....
What the heck distinguishes a VS snore from a VS2 snore? No one knows except the engineers at PR and they're not telling us.

And VS snores are recorded by System One machines ONLY when they are run in Auto mode. So if you are using a PR System One in fixed pressure mode, your SH VSI = 0.0 night after night after night, no matter how badly you are snoring. Your Encore VSI, on the other hand will NOT be 0.0 when you are using fixed pressure mode. And that's worth knowing if you are a PR System One user trying to make sense of the snoring data presented in SH.

Also note that in this night's data, the VS2 tick marks are not so densely packed in the SH event table simply because the table itself is larger. It's actually possible to try to count them. If you do, you should get around 60 of them. That's less than 1/10 of the expected number of "Encore Snores" if we assume that the Encore VSI is computed in the same way the Encore OAI, HI, CAI, RERA I, and FLI are computed. (Although the FLI = 0.0 is also misleading because a System One records FL data only when running in Auto mode.)

When we select the Events tab in SH, we get this picture:

SleepyHead finds a record of 59 VS2s recorded in the data. (The list is too long to show them all.) Note that we can't simply divide 59 by the run time of 5.5 and get the Encore VSI that way: 59/5.5 = 10.72. If Encore were computing the VSI in the same way it computes the other indices (the OAI, CAI, HI, RE I, and FLI), then the Encore VSI = 10.7.

In all the data that I've carefully looked at (including this night), I've found the same calculation works for computing the Encore VSI. If you add up all those numbers in parenthesis by the individual VS2's in the SH version of the data and divide that sum by the run time, low and behold, you get the correct Encore VSI. In other words, it seems that

• Encore VSI = (Sum of the VS2 snore numbers in SH)/(total run time)

Why Encore computes the official Encore VSI in this fashion is a mystery to me. I've found nothing in the Encore documentation that even hints at the fact that this is how the Encore VSI is computed or why it's computed in the way it is. What is clear is that once a set of persistent snoring starts in my data, there's a VS2 snore flag detected by Encore every two minutes with a number associated with that two minute interval.

Perhaps each SH VS2 is actually some kind of a conglomerate of multiple "snoring" events. But then the question goes back to "What is a snoring event?" Is a "snoring event" a fixed amount of time (or a fixed number of breaths) in which snoring was detected where the number following a VS2 indicate how long the snoring lasted, and hence counts the number of "snoring events" recorded (at or near) that time stamp? Or does a single breath with a snore count as a "snoring event"?

Clearly SH does not represent the snoring data coming from a PR System One machine in the same way that Encore does. That's not a criticism of SH or JediMark, by the way. JediMark has made some reasonable attempts at presenting the confusing snoring data in a way that makes some innate mathematical sense, whence comes his decision to make SH VSI = (number of VS snores)/(total run time) and to present the VS2 data graphically while not trying to compute a SH VS2 Index.

[robysue]

I have been unable to find how to reset either Date or Time for my PRS1!
The reason I was looking for this is that I would like to adjust the time when we go through a change in DayLight Savings time!
Q - Does SleepyHead take whatever time my Operating System has?

There is no way to reset the clock on a PRS1. The clock is set to GMT at the factory. Sleepy Head uses your computer's time zone setting to adjust the GMT timestamps to the local time. Encore uses the "Company Time Zone" setting to adjust the GMT timestamps in the data to local time. Both pieces of software should handle the change to/from daylight savings time without too much trouble. (SH will have a discrepancy between the timestamps shown in the "Details" side bar as compared to the times shown on the graphs themselves on the days where daylight savings time is in effect---or at least that's true on my Mac.

Also it's worth noting that PR S1 clocks are known to have some drift in them over time and some may simply come from the factory with an incorrect time. I've been using my PR S1 BiPAP since April 2011 and its clock is currently 21 minutes too fast. (i.e. If I got to bed at 1:00AM, the data says I went to bed at 1:21 AM). Under the preferences table you can set a clock offset which will make the times show up correctly in SH. But the incorrect times will still show up in Encore.

Also from time to time, my SleepyHead appears to NOT be able to show data for the previous night when "Import" the new data from my SD chip!
Some times it does and some times it doesn't... even though I wait until Noon-time which is where I have "PREFERENCES/Import/Day Split Time" set for "12:00 PM" (Noon) inside SleepyHead.
For instance, right now I'l have to wait until tomorrow a.m. to see yesterday's data even though I have already downloaded and made it available to SleepyHead !

I have not run into this problem. What version are you using? And are you using a Series 60 System One or the older Series 50 System One?

One thought though: Date changes happen in the middle of the night for most folks. And the data for the night that STARTS on Dec 16, 2013 and ENDS on Dec. 17, 2013 is located on Dec. 16---regardless of when you actually go to bed. And sometimes folks click on today's date when they want last night's data. You need to click on yesterday's date to see the data recorded last night---regardless of when bedtime was.

So for example: When I go to bed tonight (Dec. 16) at 1:30AM Dec. 17 and wake up tomorrow morning (Dec. 17) at 8:00AM, the data for the night will be under Dec 16 even though all of it was recorded on after midnight in the wee hours of Dec. 17. Does that make any sense?

[RSO]

Hi,

I've been using Sleepyhead for about a year now. Most recenty, as using 0.9.2 on Mac (OSX 10.6.8, Snow Leopard) with Respironics 950P ASV Bi-Flex CPAP. Love the program. Then card reader died and under warranty the unit was replaced with a Respironics 960P with integrated heated hose. Now SH reads hours of use and some other data correctly, but the new AHI, Tidal volumes for the 960P are nonsense, reading ten thousand or more (old machine data still OK). I managed to find SH 0.9-3 but it didn't run on SL. So I upgraded a separate drive to Lion (10.7.5) and SH 0.9-3 now runs, but the problem is still the same as 0.9.2 with incorrect AHI, etc.

Any solutions?

[DOOM_NX]

Hi.

SleepyHead has a serious flaw that interferes with correct data logging.

1. You forget to put the SD card in the ResMed S9
2. You insert it when you wake up, so that at least it gets the basic data.
3. ResScan logs everything but the detailed data.
4. SleepyHead shows that you skipped therapy that night.

Can it be fixed?

[me50]

If you left the SD card out of your machine, the data will not be put on the card after you put it back in the machine. You can see limited data on the machine from your LCD and that would be all for the night the card wasn't in the machine.

[Sleepster]

Then card reader died and under warranty the unit was replaced with a Respironics 960P with integrated heated hose.

SH had to be patched up when the newer 60 Series machines came out. If you have a version of SH that works with the 60 Series machines, it may be that it just doesn't work with your 960 machine. The higher end BiPAP's don't play well with SH.

[DOOM_NX]

If you left the SD card out of your machine, the data will not be put on the card after you put it back in the machine.

Yes, it will. ResScan is able to read the data minus the detailed graphs. SleepyHead can't read anything, not even usage data.

[me50]

If you left the SD card out of your machine, the data will not be put on the card after you put it back in the machine.

Yes, it will. ResScan is able to read the data minus the detailed graphs. SleepyHead can't read anything, not even usage data.

There have been different opinions on this question. All I can say is that I left my card out of the machine one night and the data was never on the SD card.