Displaying mouvements even with OSD alg disabled / movement alarm #267
Description
Discussed in https://github.com/orgs/OpenSeizureDetector/discussions/266
Originally posted by pmithrandir August 1, 2026
I'm wondering if it would be possible to display power and spectrum even with OSD alg disabled.
It allows to understand if my son move without going at his side.
For example, there are many days when I work while he is resting after seizure, often waiting for the next one.
Knowing that there are no movements is important to me because it would be dangerous for him to walk in that state. Knowing that he is sleeping in his bed is a way to keep my peace of mind.
Activity
pmithrandir commentedon Aug 1, 2026
jbmalfilattre commentedon Sep 30, 2026
Since #278 unused tabs are no longer showing on the display, so maybe this could work as a quick fix:
Set the threshold for the OSD algorithm to a value that correctly detects movements like e.g. walking.
Set the OSD Spectrum Ratio to a high value (like e.g. 999), so that OSD will never trigger an alarm. The movements however will still be visible on the OSD tab, based on the threshold setting.
ML, O2 or heart rate will continue to trigger alarms as before.
The disadvantage: it is not possible to display e.g. the heart rate monitor and other tabs together with the OSD tab.
But maybe this helps until someone has a better solution?
pmithrandir commentedon Sep 30, 2026
that's already quite a good workaround
and I can check other values in the other algo panel
jbmalfilattre commentedon Oct 10, 2026
@pmithrandir
Hi Pierre
You write:
"In an ideal world, I would have added a monitoring panel, showing power and O2 and heart rate. With some possibilities to raise warnings or alerts on certain values."
Currently the alarm type that has been triggered (e.g. OSD, ML, Fall etc.) is already displayed on the main screen.
For a monitoring panel showing multiple algorithms and their respective warning and alarm values on a standard phone screen, the screen width will be too small (unless you have some clever idea that I was too dumb to see myself?).
You write:
"We could even imagine to listen the sound(watch might have a mic) on demand..."
That would be a nice feature to have. Currently I only have PineTime watches. i.e. without microphone. If there are watches with a built-in microphone, then I'm happy to look into that.
There are however already a number of software solutions available that contain such options. Given the apparently small number of users interested in such an audio enhancement built directly into OSD, I'd propose to look into those alternative solutions first - you'll probably find what you are looking for much quicker than waiting for a suitable OSD enhancement.
Let us know what you think...
Peter
pmithrandir commentedon Oct 11, 2026
I imagined something such as :
Left side :
HR
O2
Mvt percent
One the right column all the algo
OSD
ML1
ML2
ML3
HR
...
With a square / bold /red value when they are active (green ok, orange warning, red alarm)
Left column is only information
Right list all algo
What do you think ?
jbmalfilattre commentedon Oct 13, 2026
Your post left me somewhat at a loss about how exactly that screen is supposed to look. Could you simply paste an image (a hand-drawn and then scanned-in picture would be enough) that could give us an idea on how these 8 columns are supposed to fit on the screen?
Thanks
Peter
pmithrandir commentedon Oct 13, 2026
Something like that
jones139 commentedon Oct 15, 2026
I think we already have the algorithm status in the top (FragmentCommon) section of the screen, so I don't think we need to include those? I can see the benefit of seeing HR and movement data in one place to give you a good idea of what is happening. I wonder if HR history and movement power history might be better than the single point in time values? We could have graphs of the hr (and spo2 if you think it reads anything useful) over the last 10 minutes, and the same for the movement power (I might prefer acceleration standard deviation to the spectrum power, but not enough for a serious disagreement!).
Something like this maybe?