SleepyHead Qt v0.8 alpha

jedimark wrote:Hey, I do have to sleep and have a life sometimes..

This software is a developer preview.. Anyone is welcome to try it, but please be aware it's kind of meant for people who can find their way around developer previews, willing to accept the fact it's unfinished and buggy, and know how to report bugs or have very specific suggestions for improving parts of the software. (Generalized suggestions don't help me much, I'm as foggy/headachy as hell from CFS/FM + OSA)

Oh, okay, I see I would be of no help then. I was only responding to your post in the "Re: ASV users: join the everything ASV thread" on Tue Jul 12, 2011 5:59 am. It wasn't clear from that post what qualified one as brave and willing tester. Guess for now it will be most helpful for me to stay out of the way.

Deborah

viewtopic.php?f=1&t=65791&st=0&sk=t&sd=a&start=30

jedimark wrote:Hi ASV guys & gals.

I just finished the ASV importer for SleepyHead (family 5 models anyway), and it needs brave willing testers to verify the loader works.

See the Sleepyhead v0.8 thread if your interested in trying it out.

Paper_Nanny wrote:

jedimark wrote:Hey, I do have to sleep and have a life sometimes..

This software is a developer preview.. Anyone is welcome to try it, but please be aware it's kind of meant for people who can find their way around developer previews, willing to accept the fact it's unfinished and buggy, and know how to report bugs or have very specific suggestions for improving parts of the software. (Generalized suggestions don't help me much, I'm as foggy/headachy as hell from CFS/FM + OSA)

Oh, okay, I see I would be of no help then. I was only responding to your post in the "Re: ASV users: join the everything ASV thread" on Tue Jul 12, 2011 5:59 am. It wasn't clear from that post what qualified one as brave and willing tester. Guess for now it will be most helpful for me to stay out of the way.

Deborah

viewtopic.php?f=1&t=65791&st=0&sk=t&sd=a&start=30

jedimark wrote:Hi ASV guys & gals.

I just finished the ASV importer for SleepyHead (family 5 models anyway), and it needs brave willing testers to verify the loader works.

See the Sleepyhead v0.8 thread if your interested in trying it out.

Don't get me wrong.. It's certainly useable.. It just could be scary

I'm currently redesigning the way in which information stuff is stored. not really a extremely large change, but on that may make the plan even simpler to hold out with. ASV help is coming along nicely..

wangyin wrote:I'm currently redesigning the way in which information stuff is stored. not really a extremely large change, but on that may make the plan even simpler to hold out with. ASV help is coming along nicely..

I was actually thinking of dropping SleepyHeads database in relation to PRS1 stuff, and just importing via a copy of the native session files. There's too many unknowns with PRS1 data, and the native format may make a bit more sense in this case. (My code originally worked this way.. the database idea came later)
"
ResMed is suited to a database, as the format is fully known.. same with CMS50 (and obviously SleepyHeads "journal" machine)

My "old" Vista 32 bit laptop is ailing (unrelated to testing SleepyHead) so in preparation I bought a new laptop with Window 7 and 64 bit. Now the new laptop supposedly has a slightly larger monitor. I know it does but some of my stuff has the bottom of it under the toolbar at the bottom. SleepyHead's green import status bar is one of the items. The other is Encore Pro's bottom of pages showing the EDIT button along with the summary and detailed choices for viewing reports.

Once I realized that this is a limitation of my desktop resolution I can work around it with moving stuff a bit.
I mention this just in case others run into same situation. I can see the green status bar under my bottom toolbar if I look closely.

This new monitor is 15.6 in. Old laptop (hate to say old because it is only 3 yrs old) was 15 inch. I didn't have either item off screen with it. It is not enough of a problem to warrant changing screen resolution.

SleepyHead's latest 0.8 version has been stable for me on both computers. No bugs and no crashes. Only problem I have had was the momentary panic when I didn't see the green import status bar. I wonder if some of the "failures" experienced by a few with importing is related to simply not seeing the import bar?

I think you have done a helluva good job.

Pugsy wrote:My "old" Vista 32 bit laptop is ailing (unrelated to testing SleepyHead) so in preparation I bought a new laptop with Window 7 and 64 bit. Now the new laptop supposedly has a slightly larger monitor. I know it does but some of my stuff has the bottom of it under the toolbar at the bottom. SleepyHead's green import status bar is one of the items. The other is Encore Pro's bottom of pages showing the EDIT button along with the summary and detailed choices for viewing reports.

Once I realized that this is a limitation of my desktop resolution I can work around it with moving stuff a bit.
I mention this just in case others run into same situation. I can see the green status bar under my bottom toolbar if I look closely.

This new monitor is 15.6 in. Old laptop (hate to say old because it is only 3 yrs old) was 15 inch. I didn't have either item off screen with it. It is not enough of a problem to warrant changing screen resolution.

SleepyHead's latest 0.8 version has been stable for me on both computers. No bugs and no crashes. Only problem I have had was the momentary panic when I didn't see the green import status bar. I wonder if some of the "failures" experienced by a few with importing is related to simply not seeing the import bar?

I think you have done a helluva good job.

Hmm, The funny thing is on the flipside I've got people saying the initial screen size is too small

Maybe I should just issue a maximize call on startup? (I don't mean to fullscreen, I just mean to fit within the available screen size minus the panel/taskbar) This will shrink it to fit in cases where it won't fit.

Can always move it/resize it afterwards. F11 Key to fullscreens it is handy.. But I need to change this keypress to satisfy apple macintrash function key neurosis.(Curse you Steve Jobs!)

I'll add a dialog box that nags when the wrong data directory was selected, hopefully removing another source of import frustration.

CMS50 importing just got a whole lot easier.. Don't need to hunt the windows software or the associated SPO2 folder any more as it can import directly from the USB serial device. (Can still do the other method)

I wonder how mac users currently deal with CMS50 oximeter data? virtual machine?

jedimark wrote: Hmm, The funny thing is on the flipside I've got people saying the initial screen size is too small

Maybe I should just issue a maximize call on startup? (I don't mean to fullscreen, I just mean to fit within the available screen size minus the panel/taskbar) This will shrink it to fit in cases where it won't fit.

Well... remember I now have issues with EncorePro when I didn't have before and this makes no sense at all. Could simply be this new computer and the default screen resolution. It is not a huge problem for me. I mentioned it because I have had a few people tell me that SleepyHead would not import and since I can't see what they are seeing I don't know if they didn't choose the P series folder or the import status is out of sight.

Some people do use a larger screen resolution because of eye sight problems. Things will definitely be off screen then.
If you could do a "open fit to available" that would be especially nice for those users. It's hard to satisfy all in one fell swoop. I do think it is easier to manually resize to larger than the other way around. Especially for novice users or sight impaired users who already have everything larger and don't realize some features may be off screen.

I know I was working with Gabe and Encore Pro and he had no access to the EDIT button because of his choice of screen resolution and no amount of dragging got it into view. Changing desktop resolution of course will remedy that situation but many people either forget or don't know how.

On this new computer it is already set at maximum resolution. I cannot make items any smaller. Not a huge problem for me as I can work around it. I was just thinking about some of the others that maybe computer challenged or have eye sight problems requiring lower screen resolution.

In my PRS1 Auto data, I have "Vibratory Snore" events and "Vibratory Snore (Graph)" events in the daily events view on SleepyHead QT v0.8. It appears that SH displays the VS events on the event flags display, but does not display the VS(Graph) events on the events flag display.

Encore and EncorePro display these events as "VS" in the event flags display.

Should the VS(Graph) events be shown as VS events in the events flags display on SH?

archangle wrote:In my PRS1 Auto data, I have "Vibratory Snore" events and "Vibratory Snore (Graph)" events in the daily events view on SleepyHead QT v0.8. It appears that SH displays the VS events on the event flags display, but does not display the VS(Graph) events on the events flag display.

Encore and EncorePro display these events as "VS" in the event flags display.

Should the VS(Graph) events be shown as VS events in the events flags display on SH?

Good spotting. There are two reasons for doing it this way:

1) In this case here, I believe Encore is simply "doing it wrong".

There are two vibratory snore events used in Encore.. The "Snore Graph" values (code 0x11) when >0 is shown as the Sleep Therapy Flags on machines which have this data available. On the older basic CPAP-only system one models, Encore shows code 0x0d snore events instead in the Sleep Therapy Flags.

For all (family 0) system one machines, Encore only shows the 0x0d snore events in the Encores waveform overlay.

0x0d events are the only ones that affect the pressure, so they are the ones I show in the Event flags, the other ones are just "fluff" to look pretty. When I did display the 0x11 data in Event flags, I assure you, it looked exactly the same as Encores.

I find this inconsistency idiotic, so I don't try to replicate it.

2) SleepyHead is designed for multiple machines, and is not meant to simply replicate Encore.

Even though PRS1's snore graph is comparitively rudimentary, it parallels the ResMed one, and where I find a common ground between machines of the same type, I choose a display and storage method that's optimal in both cases.

If I was to fill SleepyHeads with crudloads of subconditions based on machine brand, it would be an absolute nightmare to maintain, and kind of defeats the purpose of what it's being designed for.

That said.. This software is not just for me.. If enough people request it, it is possible to replicate Encore's crummy behaviour.. The important ones won't display anymore outside of events, waveform overlays won't match up to the flags, or there will be two vsnore event flags (like I did before the Qt version, which I really didn't like)

The alternative is I probably should just hide the SnoreGraph from events to lessen confusion. (Like I do with the other raw graph data)
As I said before, they don't affect pressure, so what's the use of them apart from a visual glance at the actual Graph?

jedimark wrote:That said.. This software is not just for me.. If enough people request it, it is possible to replicate Encore's crummy behaviour.. The important ones won't display anymore outside of events, waveform overlays won't match up to the flags, or there will be two vsnore event flags (like I did before the Qt version, which I really didn't like)

I am cool with it like it is. I don't need it to duplicate Encore.

Please don't hide any events from the events list. That's the sort of thing I hate from the manufacturers. It's already configurable in the sense that you can choose whether or not to click the drop down to show them or not. I wouldn't object if there were some configuration option to hide them entirely.

I have no strong opinion whether the snore(graph) should be shown in events. I was just reporting the difference I noticed.

A sneak peak into latest changes to the source code.

I just added keyboard control for the graphs. Can use the cursor keys, left and right to pan around and zoom with up & down. It followed keyboard focus, so you have to alt-tab to the graphs or click on it first with the mouse. I could of made it application wide, but I figured it's too darn handy using the keys in the Events tab. I'll see how people go using the focus stuff and tweak if it doesn't work well.

Also, now you can click on the title area (left margin) of a graph and drag the graphs to change the order. Still figuring out how to present the ability to hide graphs the user isn't interested in.. (Currently automatically hide graphs that aren't relevant to the machines.) You can drag the handles between visible graphs up or down all the way to close them, but it's fidgety.

In the new oximetry main view, I have the basic concept figured out for live view stuff for the CMS50. I'm trying to decide if I should do the live view like the SPO2 application does, and overwrite the not-so-awsomely-accurate plethy data on the screen every time it gets to the right side (thus ditching the plethy data).

or alternatively try to automatically follow the 3 graphs (pulse, spo2 & plethy) as it records, but allowing the user to break from following and zoom & pan while it's still recording, with an option to keep the recording session when done (probably a message box asking if they want to keep it when the user clicks stop) (A checkbox would probably be down the bottom of the Oximetry screen to allow resuming of following, automatically would get unchecked when the graphs are panned/zoomed)

Anyone have any suggestions on this?

This doesn't affect the data import process from the devices Recording mode, as the machine doesn't store Plethysomogram data in it's internal memory. That import bit works well by the way. I need to find a way to stop it from being imported twice by accident. I figure showing the new imported session in the graph used by the live view wouldn't be a bad start. Maybe block import if done within the last recorded session length of time?

I would like to know what the "flags" are in SpO2 review on the top and bottom.. Seems to be a simple indicate of sudden changes.. Anyone got a more accurate explanation?

/Mark

When I first used it, the graph interface seemed "klunky." Now, it seems natural, like "of course it works that way." I just sort of think about what I want to view and my hands do the work. Good job.

One thing is still a little counterintuitive. When I left click at a point in the graph, it seems it should center on that point and zoom in. I think it zooms in on the current center of the graph. I know I can highlight and zoom, but it seems that a click should center and zoom.

archangle wrote:Please don't hide any events from the events list. That's the sort of thing I hate from the manufacturers. It's already configurable in the sense that you can choose whether or not to click the drop down to show them or not. I wouldn't object if there were some configuration option to hide them entirely.

I have no strong opinion whether the snore(graph) should be shown in events. I was just reporting the difference I noticed.

There main problem with displaying the graph data amongst the Events list, is resmed graphs can have upwards of 4000 entries (in some cases, crap-loads more). System One ASV graphs can be quite big too. If I displayed all the graphs data, it would take a lot longer to switch dates, chew a lot more memory, and be pretty hard to navigate through for someone not expecting it.

Navigation wise, it would probably be a lot easier if I could get the left arrow key to collapse in the middle of the event list. (Maybe even ctrl-left so it doesn't get bumped and lose your place? then again, apple macs are utterly stupid when it comes to modifier key combos..)

With the event list, I've been focusing on displaying things that change pressure. (which is why the basic pressure graph shows there)

Your idea of a config switch to hide them isn't bad, it's not hard to implement either. I'll see what I can figure out.. I do feel the default mode should be hiding them.

Some things aren't practical to put there at all, eg: Minute Ventilation, Tidal Volume, Respiratory Rate to name a few (both ResMed & Sys-One ASV have those)

archangle wrote:When I first used it, the graph interface seemed "klunky." Now, it seems natural, like "of course it works that way." I just sort of think about what I want to view and my hands do the work. Good job.

One thing is still a little counterintuitive. When I left click at a point in the graph, it seems it should center on that point and zoom in. I think it zooms in on the current center of the graph. I know I can highlight and zoom, but it seems that a click should center and zoom.

I'm glad it's starting to make a bit of sense..

Do you mean the when you click on an event in Event flags? At the moment I cheat and just centre on the area around where the mouse clicks, rather than doing the relatively computationally expensive lookup to find the event within say 5 pixel radius of the mouse cursor.

Edit: Half Misread.. I get you now.. You mean on a waveform.. That code is already there to do it properly, it got temporarily turned off for some reason.. I've gotta go hunting through the rabbits warren that is the Mouse Handling code. (which will get rewritten one day when I have less fog (along with quite a few other things))

Edit Edit: Easier than I thought.. Fixed in the code now.. Thanks for reminding me