OSCAR Suggestions & Bug reporting

[BlueDragon]

I agree that it looks better on Windows. But I do think it would be appropriate if it looked non-blurry by default on macOS. Although I prefer Windows over macOS, I would say that when it comes to typography macOS is more than capable of that with any of the preinstalled fonts.

Yes, I’m not arguing about the data of the graphs, but rather how they are rendered. Anti-aliased rendering would make them a bit smoother. Not sure if I’m able to convey it clearly, but it means that nuances of the graph line color is used in order to make it look smoother.

Which font are you using, and have you tried a different font?

[alexander]

Which font are you using, and have you tried a different font?

The default font, if I recall correctly, was Lucida Grande. Looks blurry both with bold enabled or disabled. The font I currently use is Roboto. Looks blurry in both cases with Roboto as well.

Have you considered the rendering of the graph by the way? If you’re using a third party component to render it, then maybe there might be an option to enable anti-aliased rendering. I fully understand however if this is not a priority.

[BlueDragon]

The default font, if I recall correctly, was Lucida Grande. Looks blurry both with bold enabled or disabled. The font I currently use is Roboto. Looks blurry in both cases with Roboto as well.

Have you considered the rendering of the graph by the way? If you’re using a third party component to render it, then maybe there might be an option to enable anti-aliased rendering. I fully understand however if this is not a priority.

Go to File/Prefences/Appearance and check whether Antialiasing is enabled. I haven't seen reports from other Mac users about their fonts being fuzzy, so don't know what to suggest (I'm not a Mac user, nor a graphing expert). I'll log your issues in our trouble log.

[alexander]

Go to File/Prefences/Appearance and check whether Antialiasing is enabled. I haven't seen reports from other Mac users about their fonts being fuzzy, so don't know what to suggest (I'm not a Mac user, nor a graphing expert). I'll log your issues in our trouble log.

Yes, anti-aliasing is enabled (was enabled by default), but it doesn’t seem to affect the rendering of graphs. Thanks for logging. I’m sure there are more important issues to prioritize, but these are my personal pet peeves.

I’d just like to say thanks for continuing the development of this very useful program.

[tsduke]

Is the DreamStation Bipap ST supported? Curious as it imports as a BiPAP AVAPS and IPAP pressure doesn't match what the machine is set too.

Edit: I do see on the Apnea boards that the ST is listed as supported, but for some reason my pressures aren't showing what my machine is set to (IPAP 12 / EPAP 7). I have withnessed on the machine screen that it is move from 7 to 12 and the inhale pressure are definately higher.

Also not sure the model is pulling in correct.

Screen Shot 2019-08-12 at 7.43.15 PM.png (40.6 KiB) Viewed 7093 times

Annotation 2019-08-13 102727.png (2.76 KiB) Viewed 7093 times

[bonjour]

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.
You will be able to run both versions and tell us what is broken and what is fixed.

A lot has been beyond what you can see, OSCAR is more maintainable. Advanced PR devices are now working. Graphics engines now load correctly (you shouldn't need a script to correct graphic engine choice).

NOTE: THIS VERSION HAS NOT BEEN FORMALLY TESTED!!!!! if this makes you uncomfortable don't use it.


I recommend this version to our testers but not for public release (so I would not put it on the public OSCAR download page). We should also make it available to people with special problems such as the recent problem with screen capture on the Mac. We should recommend that people use either a copy of their OSCAR_Data directory or use a new directory entirely as this version may update some tables and caches that are not backwards compatible. And it is a test version and all of the caveats about "it may damage your data" apply. On first use, OSCAR may need to update some caches. This can take a long time if you have many years of data. If OSCAR seems to hang, check Windows Task Manager (or equivalent on other platforms) and see if OSCAR is still using CPU and doing I/O activity. If it is, just wait it out until it gets done. (An issue on our list is to add progress bars for these situations.) For any new commits, we should be aggressive about updating the build number with each commit so that we, as well as users, can easily distinguish builds. The commit id is visible at any time by selecting Help/System Information.


Release notes for Changes and fixes in OSCAR v1.1.0-testing-3 say:

[new] 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.
[new] View/Reset Graphs organizes graphs in their original order
[fix] Format dates for the national region as reported by the operating system
[fix] Improve progress bar for statistics cache update
[fix] Correct calculations of seven-day AHI and leak rate on Welcome page
[fix] Clarify AHI and hours labels on Records tab of right sidebar
[fix] Correct import error resulting in invalid elapsed times and impossibly high AHI values


Release notes for Changes and fixes in OSCAR v1.1.0-testing-2 say:
[new] Show progress bar when Statistics page has to refresh cache with more than 180 days in it
[new] Romanian language is supported
[fix] Show commit id in title bar for testing and beta builds
[fix] Show BMI label and calculated value only when both weight and height are non-zero
[fix] Improve BMI display in Daily/Notes
[fix] Correct profile dialog to show height is measured in cm, not meters, when units system is metric
[fix] Always show event indices on Daily page even when some event flags are turned off
Release notes for Changes and fixes in OSCAR v1.1.0-testing-1 say:
[new] Offer migration if non-default directory is selected on first use
[new] Press SHIFT key when starting OSCAR to use Software Graphics Engine
[new] Support for DreamStation BiPAP autoSV (900X) should now be complete
[new] Improved Dreamstation support
[new] Improve oximeter import for CM550D+
[new] Disable Dark Mode on Mac
[new] Show hours/day constituting compliance on Statistics page
[new] Better order of graphs on Daily page for newly created profiles
[new] Help/System Information shows info about OSCAR, OS, and data location
[new] Move pie chart option from Preferences dialog to View menu
[new] Hide pie chart when capturing screen
[new] --datadir option now allows fully qualified name on Windows
[fix] Fix some oximeter import issues
[fix] Use local time rather than UTC time in oximeter import
[fix] Improve screen capture on Mac
[fix] Fix crashes in CPAP data rebuild, purging of a machine
[fix] Prevent crash if taking screen shot before profile is opened
[fix] Increase mask vent ranges
[fix] Correct session bar if no sessions are present
[fix] Correct months shown on Statistics page monthly view
[fix] Compute compliance on Statistics page based on total days not days used
[fix] Paginate statistics report when printing
[fix] Fix "phantom date" (12/31/1969) on some ResMed imports
[fix] Default font substituted when a specified font is not valid
[fix] Change Preferences measurement units choice to Metric or English
[fix] Improve display of cmH2O numbers
[fix] Show graphics engine in title bar correctly
[fix] Adjust size of Preferences dialog to fit smaller screens
[fix] Label climate control as manual or auto correctly on ResMed import
[fix] Move less useful information from titlebar to Help/System Information
[fix] Change "Prescription Settings" to "Machine Settings" message
[fix] Improve icons, especially smaller ones
[fix] Correct Mac menu issues
[fix] Improve messages in debug pane
[fix] Re-organize build instructions and other cleanup

[gmsmith]

Thank you to all those who have put effort into Oscar, I really appreciate being able to use it and have the data available to me. I had a couple of ideas

• Oscar Feature Request - iPhone/iPad app to present data
• Google Drive support for Oscar data (need to check if this works with Dropbox) - but some sort of shared file system for access from multiple devices/computers

[prodigyplace]

• Oscar Feature Request - iPhone/iPad app to present data

That would not be possible without storing your data on a server in the Internet. Right now OSCAR data stays on your local computer.
This information would likely be classed as HIPAA protected health information in the US, adding to the security requirements of any Internet server with the data.

[Dog Slobber]

• Oscar Feature Request - iPhone/iPad app to present data

That would not be possible without storing your data on a server in the Internet. Right now OSCAR data stays on your local computer.
This information would likely be classed as HIPAA protected health information in the US, adding to the security requirements of any Internet server with the data.

Anyone using OSCAR on a relatively new MacOS is [probably] storing their data on one of Apples servers.

OSCAR is defaulted to store its data in documents, which is a link to iCloud.

[prodigyplace]

That is only by choice and Apple claims the data is encrypted anyway.

[palerider]

• Oscar Feature Request - iPhone/iPad app to present data

That would not be possible without storing your data on a server in the Internet. Right now OSCAR data stays on your local computer.
This information would likely be classed as HIPAA protected health information in the US, adding to the security requirements of any Internet server with the data.

You don't know how HIPPA works, do you?

[BlueDragon]

I had a couple of ideas

• Google Drive support for Oscar data (need to check if this works with Dropbox) - but some sort of shared file system for access from multiple devices/computers

You can certainly put your OSCAR data files in a OneDrive folder, and it would then be available to other computers that had access to your OneDrive account. Unless you were very careful, trying to maintain the data on more than one computer could easily result in database corruption, so I don't recommend that.

[Dog Slobber]

That is only by choice and Apple claims the data is encrypted anyway.

And if it were ported to mobile, people using it wouldn't by by choice? Nor, could it be encrypted.

There are a lot of reasons that the developers have posted why OSCAR isn't on mobile, but HIPPA, choice and encryption on cloud storage don't make sense.

[gmsmith]

I had a couple of ideas

• Google Drive support for Oscar data (need to check if this works with Dropbox) - but some sort of shared file system for access from multiple devices/computers

You can certainly put your OSCAR data files in a OneDrive folder, and it would then be available to other computers that had access to your OneDrive account. Unless you were very careful, trying to maintain the data on more than one computer could easily result in database corruption, so I don't recommend that.

Thanks. I’ll take a look. It doesn’t work with Googles consumer drive option. I haven’t tried it with their enterprise option.

[gmsmith]

• Oscar Feature Request - iPhone/iPad app to present data

That would not be possible without storing your data on a server in the Internet. Right now OSCAR data stays on your local computer.
This information would likely be classed as HIPAA protected health information in the US, adding to the security requirements of any Internet server with the data.

HIPPA wouldn’t apply here. And with the introduction of iPadOS you could certainly do data all on the iPad if you wanted, but frankly I don’t know why you wouldn’t be able to get it from multiple devices.