Page 19 of 26
Re: OSCAR Suggestions & Bug reporting
Posted: Fri Oct 18, 2019 3:02 pm
by djams
palerider wrote: ↑Thu Oct 17, 2019 11:55 am
Other non-numerical things, snores, flow limitations.
And yet for Resmed machines they're presented as numeric values in OSCAR.
I don't understand, can you explain?
Re: OSCAR Suggestions & Bug reporting
Posted: Fri Oct 18, 2019 3:27 pm
by palerider
djams wrote: ↑Fri Oct 18, 2019 3:02 pm
palerider wrote: ↑Thu Oct 17, 2019 11:55 am
Other non-numerical things, snores, flow limitations.
And yet for Resmed machines they're presented as numeric values in OSCAR.
I don't understand, can you explain?
Because that is the only way you can make the graphing engine plot things.
Re: OSCAR Suggestions & Bug reporting
Posted: Thu Oct 24, 2019 3:58 pm
by talzahr
First time posting on the forum. I started APAP therapy just over a week ago for the first time. Using OSCAR version 1.1.r2930.2e1069b8-1 on Arch Linux standard kernel 5.3.7. I have my PR DreamStation Auto CPAP set to a 15mm hose diameter however OSCAR is reporting PRS1HoseDiam as 22mm. Will this affect the calculations and reporting in any way? I was looking for a way to change it but it appears as if $HOME/Documents/OSCAR-Data-makepkg/Profiles/$USER/channels.xml is for the parsed and formatted input and not user set, so I am assuming it needs to be reported from the machine's data. If the hose diameter is an issue, can I just switch the key IDs around? Thanks.
Re: OSCAR Suggestions & Bug reporting
Posted: Thu Oct 24, 2019 4:45 pm
by palerider
talzahr wrote: ↑Thu Oct 24, 2019 3:58 pm
I have my PR DreamStation Auto CPAP set to a 15mm hose diameter however OSCAR is reporting PRS1HoseDiam as 22mm. Will this affect the calculations and reporting in any way?
No, it's just a bug in oscar, it means nothing, since all the calculations are done in the machine.
Re: OSCAR Suggestions & Bug reporting
Posted: Sun Oct 27, 2019 5:35 am
by JDS74
FYI - Differences in OSCAR and Encore Pro reporting for 10/26/2019:
Edit: DreamStation ASV
Oscar reports:
OSCAR v1.0.1-r-1
Machine Settings
PAP Mode ASV (Variable EPAP)
Min EPAP 6.40 cmH2O
Max EPAP 20.00 cmH2O
Min IPAP 10.40 cmH2O
Max IPAP 25.00 cmH2O
PS Min 4.00 cmH2O
PS Max 16.00 cmH2O
Encore Pro Reports:
EncorePro - version: 2.24.0.1
Device Settings as of 10/26/2019
ASV - Bi-Flex
Max Pressure 25 cmH2O
Min EPAP 13 cmH2O
Max EPAP 17 cmH2O
Min Pressure Support 5 cmH2O
Max Pressure Support 12 cmH2O
Re: OSCAR Suggestions & Bug reporting
Posted: Sun Oct 27, 2019 2:59 pm
by StormyToo
Deleted
Re: OSCAR Suggestions & Bug reporting
Posted: Mon Oct 28, 2019 10:03 am
by Ron10
Since I have an issue with my blood oxygen levels during sleep, I am interested in the best method to sync the data from my KENEK EDGE OXIMETER with the daily output from my MedRes10 autoset. I am enclosing a sample of the file produced from the KENEK Edge which creates one entry per second as shown below. This is currently in Excel.CSV format but I could reformat to a compatible format if necessary.
Heart signal
Date and Time Rate SpO2 Quality
8/26/2019 21:54:23 62 96 95
8/26/2019 21:54:24 62 96 87
8/26/2019 21:54:25 62 96 90
8/26/2019 21:54:26 62 96 92
8/26/2019 21:54:27 62 96 94
8/26/2019 21:54:28 61 96 95
8/26/2019 21:54:29 61 95 96
8/26/2019 21:54:30 61 95 97
8/26/2019 21:54:31 61 95 98
8/26/2019 21:54:32 61 95 98
8/26/2019 21:54:33 61 95 99
8/26/2019 21:54:34 61 95 99
8/26/2019 21:54:35 61 96 99
8/26/2019 21:54:36 62 96 99
8/26/2019 21:54:37 62 96 99
8/26/2019 21:54:38 62 96 99
Thanks for you assistance,
Ron Mason
Re: OSCAR Suggestions & Bug reporting
Posted: Tue Oct 29, 2019 9:27 am
by bonjour
I would graph the data then take the graph and on an OSCAR screenshot overlay the oximeter chart matching the timeline.
Re: OSCAR Suggestions & Bug reporting
Posted: Wed Oct 30, 2019 1:48 pm
by slowriter
System info:
Code: Select all
OSCAR 1.1.0-testing-4 (linux x86_64)
Built with Qt 5.12.5 on Oct 30 2019 06:55:55
Revision fda9fcd1
App key: OSCAR-test
Operating system: Fedora 31 (Workstation Edition)
Graphics Engine: 4.3 (Compatibility Profile) Mesa 19.2.0
Graphics Engine type: OpenGL
Two bugs:
- import of Zeo data often doesn't persist in the UI, and I have to reimport
- I can't edit the override y-axis config for the FL overview to a value below 1
Re: OSCAR Suggestions & Bug reporting
Posted: Thu Oct 31, 2019 5:20 am
by Jay Aitchsee
slowriter wrote: ↑Wed Oct 30, 2019 1:48 pm
I can't edit the override y-axis config for the FL overview to a value below 1
Did you try entering discrete values rather than using the up/down arrows?
Re: OSCAR Suggestions & Bug reporting
Posted: Thu Oct 31, 2019 5:33 am
by slowriter
Jay Aitchsee wrote: ↑Thu Oct 31, 2019 5:20 am
slowriter wrote: ↑Wed Oct 30, 2019 1:48 pm
I can't edit the override y-axis config for the FL overview to a value below 1
Did you try entering discrete values rather than using the up/down arrows?
Of course; there's no other way. I can't change the values with the keyboard.
Re: OSCAR Suggestions & Bug reporting
Posted: Thu Oct 31, 2019 6:20 am
by Jay Aitchsee
slowriter wrote: ↑Thu Oct 31, 2019 5:33 am
Jay Aitchsee wrote: ↑Thu Oct 31, 2019 5:20 am
slowriter wrote: ↑Wed Oct 30, 2019 1:48 pm
I can't edit the override y-axis config for the FL overview to a value below 1
Did you try entering discrete values rather than using the up/down arrows?
Of course; there's no other way. I can't change the values with the keyboard.
I'm not sure we understand one another. I can enter values into the dialog box by highlighting the number to be changed and then typing the desired number into the box, such as 0.04, for example. However, using the up/down arrows of the dialog box or keyboard only permits changes in whole number increments. Decimal fractions must be entered discretely via the keyboard.
Re: OSCAR Suggestions & Bug reporting
Posted: Thu Oct 31, 2019 8:42 am
by palerider
slowriter wrote: ↑Wed Oct 30, 2019 1:48 pm
- I can't edit the override y-axis config for the FL overview to a value below 1
Why would you want to?
A design limitation isn't a bug.
Edit: ignore me... See below.
Re: OSCAR Suggestions & Bug reporting
Posted: Thu Oct 31, 2019 10:23 am
by Jay Aitchsee
palerider wrote: ↑Thu Oct 31, 2019 8:42 am
slowriter wrote: ↑Wed Oct 30, 2019 1:48 pm
- I can't edit the override y-axis config for the FL overview to a value below 1
Why would you want to?
A design limitation isn't a bug.
I don't know about slowriter, but I have mine set at min=0.04 and max=0.25. My ResMed machine reacts to FL above 0.04 and I seldom see FL which exceed 0.25, so these settings make the graphic more meaningful (to me).
Re: OSCAR Suggestions & Bug reporting
Posted: Thu Oct 31, 2019 11:41 am
by palerider
Jay Aitchsee wrote: ↑Thu Oct 31, 2019 10:23 am
palerider wrote: ↑Thu Oct 31, 2019 8:42 am
slowriter wrote: ↑Wed Oct 30, 2019 1:48 pm
- I can't edit the override y-axis config for the FL overview to a value below 1
Why would you want to?
A design limitation isn't a bug.
I don't know about slowriter, but I have mine set at min=0.04 and max=0.25. My ResMed machine reacts to FL above 0.04 and I seldom see FL which exceed 0.25, so these settings make the graphic more meaningful (to me).
Huh, well ok then, I sit corrected.
Thanks