CPAPtalk.com

bonjour wrote: ↑

Wed Aug 14, 2019 5:08 pm

OSCAR Testing Release planned in August 2019

DreamStation BiPAP autoSV (900X)
DreamStation BiPAP S/T and AVAPS ventilators (1030X and 1130X) are now supported. The settings aren't yet displayed correctly, but therapy events and graphs should now display properly
Improve oximeter import for CM550D+

If these devices are yours, and you would like to join our Beta team and test, Please PM me (Bonjour) and request to be a Beta Tester.

Looking at about 2 weeks This will let you protect your current data by placing all data in a "testing" folder separate from the production release version.

Nice to know it is supported. Just DL Oscar and imported data to it from my Dreamstation ASV. Did note that it lists the EPAP as less than what it is set for, and the Pressure Support, ditto.

Not sure I want to beta-test.....

Just FYI, I just installed OSCAR and it did not offer to import my Sleepyhead Data. Maybe because I chose the route of setting the OSCAR data directory manually instead of allowing it to choose.

Luckily, the directions for a manual import were not too difficult, and I'm pretty comfortable with this stuff.

I have just peeked at it so far, but it looks very similar to Sleepyhead.

One issue I have is that on macOS the waveform time markers don’t seem to follow the OS time zone.

One humble suggestion is to add a ⌘, keyboard shortcut to preferences for the macOS version.

alexander wrote: ↑

Tue Aug 27, 2019 6:41 am

One issue I have is that on macOS the waveform time markers don’t seem to follow the OS time zone.

Interesting, I have not seen that report before. Can you describe the situation in more detail? Are you recording data in one timezone but displaying in another? Or...? The time markers should match the clock in your CPAP machine.

Thanks.

BlueDragon wrote: ↑

Tue Aug 27, 2019 7:22 am

alexander wrote: ↑

Tue Aug 27, 2019 6:41 am

One issue I have is that on macOS the waveform time markers don’t seem to follow the OS time zone.

Interesting, I have not seen that report before. Can you describe the situation in more detail? Are you recording data in one timezone but displaying in another? Or...? The time markers should match the clock in your CPAP machine.

Thanks.

I’m sorry, I just checked the settings on my machine. That’s where the problem is. I thought that it used the built in modem to retrieve the date and time, but that’s probably not the case.

alexander wrote: ↑

Tue Aug 27, 2019 7:30 am

BlueDragon wrote: ↑

Tue Aug 27, 2019 7:22 am

alexander wrote: ↑

Tue Aug 27, 2019 6:41 am

One issue I have is that on macOS the waveform time markers don’t seem to follow the OS time zone.

Interesting, I have not seen that report before. Can you describe the situation in more detail? Are you recording data in one timezone but displaying in another? Or...? The time markers should match the clock in your CPAP machine.

Thanks.

I’m sorry, I just checked the settings on my machine. That’s where the problem is. I thought that it used the built in modem to retrieve the date and time, but that’s probably not the case.

ResMeds do not use any kind of facility to synchronize the time and date with external clocks, nor automatically adjust for Day Lift Savings. All time adjustments must be done manually from Clinician Mode.

Manually adjusting is awkward as one can move the time forward easily, but backwards can problematic, as you can't move back into a previous day, nor into a session where there is data. This can result in having to set the time multiple times over several days.

Dog Slobber wrote: ↑

Tue Aug 27, 2019 9:27 am

ResMeds do not use any kind of facility to synchronize the time and date with external clocks, nor automatically adjust for Day Lift Savings. All time adjustments must be done manually from Clinician Mode.

Manually adjusting is awkward as one can move the time forward easily, but backwards can problematic, as you can't move back into a previous day, nor into a session where there is data. This can result in having to set the time multiple times over several days.

Thanks for the warning.

Luckily, it had to be turned forward.

As long as you change the time after noon, and before starting treatment for the night, it can be set back as long as you do not take the time back past 12:00, noon.

alexander wrote: ↑

Fri Aug 09, 2019 1:24 pm

Labels such as “Event Flags” and “Flow Rate” look blurry on my machine (macOS).

This turns out to be a result of a change in font rendering on MacOS Mojave, apparently specifically for non-retina displays. For an example of this same report for another product, see this vscode problem report: https://github.com/Microsoft/vscode/issues/51132. We have logged this as an issue for later examination.

As an interim solution, you could try the fix on this page: https://www.howtogeek.com/358596/how-to ... ialiasing/ Let me know if that solves the blurry font problem (I don't have a Mac, so cannot test it myself).

First, is there not a public issue tracker?

Second, I tried to install the debian package on my fedora notebook, and ran into some problems.

So, a suggestion: offer an AppImage download.

Instructions on how I got it working below. Note that, while it works, there are a few minor issues (icon doesn't look right, and not sure the desktop integration gets integrated properly).

First, grab the linuxdeploy AppImage and make it executable.
Second, run the tool by specifying the key resources (executable, icon, desktop) and target dir.
Third, grab the appimagetool AppImage and make it executable.
Run the tool to package up the final download file.
I did have to tweak the desktop file a bit to get it to work. Here's the final version, with commented explanations.

BlueDragon wrote: ↑

Tue Aug 27, 2019 5:53 pm

alexander wrote: ↑

Fri Aug 09, 2019 1:24 pm

Labels such as “Event Flags” and “Flow Rate” look blurry on my machine (macOS).

This turns out to be a result of a change in font rendering on MacOS Mojave, apparently specifically for non-retina displays. For an example of this same report for another product, see this vscode problem report: https://github.com/Microsoft/vscode/issues/51132. We have logged this as an issue for later examination.

As an interim solution, you could try the fix on this page: https://www.howtogeek.com/358596/how-to ... ialiasing/ Let me know if that solves the blurry font problem (I don't have a Mac, so cannot test it myself).

I understand. I don’t want to change any settings at the moment, but it seems like you’ve found the problem. I hope someone else is willing to see if that fix works.

bonjour wrote: ↑

Sun Mar 24, 2019 11:18 am

In another thread I was asked for where to submit suggestions.
You can feel free to PM me if you wish, either here or over on AB. But in this thread will work.
Suggestions will be considered, but no guarantee that or when they will be implemented. Most of the suggestions we have seen so far will, IMHO, be implemented.

Anyone that would like to contribute to OSCAR, please PM me (bonjour) over on Apnea Board http://www.apneaboard.com/forums/index.php. We can always use C++ / QT developers, Testers, and Translators for languages we do not yet have covered.

Fred Bonjour - Project Manager and Lead Tester for OSCAR - Open Source CPAP Analysis Reporter

I have been using Oscar for awhile. Got a new machine recently and no initial problems with Oscar.However recently I noticed under Statistics that there was a change to prescription settings. It was dated Wed Dec 31 1969 for 1 day and had the same pressure settings as my last prescription settings. Bizarre! My sleep doc will certainly notice when I show him my data next visit. Any idea how this occurred.

Chapalauser wrote: ↑

Thu Aug 29, 2019 12:21 pm

I have been using Oscar for awhile. Got a new machine recently and no initial problems with Oscar.However recently I noticed under Statistics that there was a change to prescription settings. It was dated Wed Dec 31 1969 for 1 day and had the same pressure settings as my last prescription settings. Bizarre! My sleep doc will certainly notice when I show him my data next visit. Any idea how this occurred.

We are aware of several situations where a 12/31/1969 date will appear. That happens when your CPAP machine generates a record that contains no data of interest to Oscar and Oscar ends up thinking there is a date with a value of of 0, which translates to 12/31/1969 when formatted as a date. We think we have fixed most of those problems in our current test builds. When it is the prescription settings table, sometimes the problem goes away if you close and restart Oscar.

Hi,

I have been using OSCAR and it has been very helpful to understand my sleep. Recently I imported data from Somnopose opening the .csv file. On Oscar, the time appeared dislocated 2 hours in relation to the correct time.

In the .cvs file the initial time was 22:33:52 but on OSCAR it appeared two hours later, like 00:30.

Timestamp,Orientation,Inclination,Time_of_day,Date
588735232.69,-94.82,36.58,22:33:52,
588735234.69,31.01,9.73,22:33:54,
588735236.68,50.79,71.33,22:33:56,
588735238.67,61.32,12.31,22:33:58,
588735240.71,-177.17,52.48,22:34:00,2019-08-28
588735242.70,-170.94,81.13,22:34:02,

Should I change some configuration to adjust that?

Thanks in advance,

Bamford wrote: ↑

Fri Aug 30, 2019 8:42 am

I have been using OSCAR and it has been very helpful to understand my sleep. Recently I imported data from Somnopose opening the .csv file. On Oscar, the time appeared dislocated 2 hours in relation to the correct time.

Wow! Somnopose must suddenly be popular! We received the first report of this problem -- a five hour dislocation -- just this morning! We had not known about the problem but suspect it is the same one that affected oximetry import. We plan to fix it for the next release of Oscar.

Is your timezone two hours different than GMT?

Thanks for your report. We do appreciate people letting us know of problems.

I'll log this as the second report of the problem.