I have just bought an Angel Sensor M1 wristband to try it out as an alternative seizure detector to the Pebble.
The OpenSeizureDetector Android App is written to allow extra ‘data sources’ to be used, so I will have a go at writing a DataSorurce that uses the angel sensor instead of the pebble. The first effort will be to repeat the same functionality as you get with the Pebble, then extend it to use the other sensors such as skin conductivity and heart rate. This should reduce the number of false alarms compared to the Pebble…If I can make it work!
- The Open Source Angel Sensor Android app installed ok and said it was scanning looking for the device.
- The instructions (http://angelsensor.com/start) said press the button on the device to switch it on – it was hard to see the button – there is a hard plastic blister on the top, but it doesn’t move when you squeeze it. Started to think the device is dead…..
- Tried plugging it into the charger – the LEDs in the device came on, which is a good sign, but nothing else.
- Waited a while…..
- Now squeezing the plastic blister on the device makes it vibrate a bit – I think long and short presses do different things….
- After a few presses must have managed to switch it on and the phone app connected to it – phone app displaying temperature and has placeholders for other parameters such as steps and heart rate, but they are not displaying values…. Display says battery is
I have finally fixed the last few bugs (that I know about), and have Released V2.0 of the OpenSeizureDetector Pebble Watch App and Android App.
There are a lot of ‘behind the scenes’ changes to the Android App to make the code easier to maintain in the future. From a user’s perspective, the changes you will see are:
- You can mute the alarms using the top watch button (long press).
- You can manually initiate an alarm using the bottom watch button (long press).
- The system should be easier to install from scratch because it will prompt you to install the Pebble Android App and the OpenSeizureDetector watch app if they are not installed.
- There is a new start-up screen that shows which bits of the system are working – this will help with fault diagnosis as the main screen is not displayed until everything is ok.
- The main screen has two graphs that show how far the system is off alarming – when both bars get to the right and side and turn red, it alarms.
- The system settings have been organised into different screens to make it easier to find things.
- The ‘general’ settings allow the user to select a ‘datasource’ this is either ‘Pebble’, in which case the system talks to the pebble directly, or ‘network’, in which case it will receive data from another device running OpenSeizureDetector – this is useful to extend the range of alarms to other parts of the house (this is what the OpenSeizureDetector Client app does – so the client app is now redundant).
Although I have fixed a lot of bugs in this release, the changes have been so significant that I am bound to have introduced new issues – please feed back any issues you have – ideally to the Facebook page I have set up so others can see it, otherwise email me (firstname.lastname@example.org)
I have been thinking about seizure detection algorithms. The one I use for the OpenSeizureDetector Pebble watch looks for movement in the range 5-10 Hz, which seems to work for the high frequency jerky type of movements that I associate with a tonic-clonic seizure. Although they have not published their algorithm, this seems similar to the Neutun app detection method. Ryan Clark’s PebbleSeizureDetect uses a band pass filter to select a 1-3 Hz range, which is a much slower movement. I am sure he has found that this works for the sort of seizures he is trying to detect.
I have made a couple of videos showing the sort of movement that the two algorithms detect – the watch on the left is running OpenSeizureDetector, and the one on the right PebbleSeizureDetect – you can hear the buzz when PebbleSeizureDetect alarms, or see the ‘WARNING’ or ‘ALARM’ phrase on the OpenSeizureDetector screen.
My concern is that the two algorithms are quite different – a seizure that alarms with OpenSeizureDetector will not trigger PebbleSeizureDetect. I am pretty happy with the OpenSeizureDetector one – I have had some positive reports of it detecting seizures ok, and the movement it detects is consistent with some of the movement you can find on some slightly disturbing YouTube videos of people having seizures, But Ryan developed his to work for his application…so which one is best to give the highest detection reliability?
Any thoughts would be appreciated – please either email email@example.com or use the Facebook OpenSeizureDetector page.
Video 1 – shows the ‘borderline’ movement that just alarms OpenSeizureDetector – first a few intermittent ‘WARNING’ alarms, then with a slightly higher amplitude movement, goes into ‘ALARM’ – PebbleSeizureDetect does not respond.
Video 2 – lower frequency movement that alarms PebbleSeizureDetect (about 25 seconds in), but not OpenSeizureDetector – demonstration of the higher frequency movement that alarms OpenSeizureDetector at the end of the video.
I am just doing some final testing of V2.0 of OpenSeizureDetector, with a view to releasing it at the weekend, which will be exactly a year since I published the original version.
The things that have changed for V2.0 are:
- Manually raise an alarm by pressing and holding the DOWN watch button.
- Mute the alarms (for a selectable period) by pressing and holding the UP watch button.
- Major internal re-write of the android companion app, so it can use different data sources – this means it is ready for when Embrace ship their seizure detector watches – I will be able to make it compatible with the OpenSeizureDetector phone app.
- The Android app acts as both the server (which talks to the watch) and also the client (which talks to the server to give remote alarm annunciation) – no need for a separate client app any more.
- Pretty bar graphs showing how close you are to an alarm state.
- Tidier settings screens.
- Start-up screen to show the system initialising.
- User selectable data transfer period – you can reduce the amount of data sent from the watch to the phone – this is the most disappointing feature because it does not give the saving in battery power that I had hoped for.
I am pretty close to releasing V2.0 of the OpenSeizureDetector Android App.
If anyone would like to try it out, and feedback any difficulties or suggestions, you can get the app from the projects github repository: app-release-2.0d.apk.
The main changes from the 1.x version currently on Android Play store are:
- Added start-up screen that shows the bits of the system starting and confirms they work before showing the main screen.
- If pebble datasource is selected, start-up screen has an option to
open the pebble app to manage pebble connection issues, and to install the watch-app directly.
- The main screen has been tidied up a bit, and now includes bar graphs to show how close to alarming the current movement is..
- Settings screen broken down into different logical screens to make it easier to find a setting to change.
- Changing a setting now re-starts the whole app to make sure the new setting is being used.
- Added an ‘about’ page with links to http://openseizuredetector.org.uk web site and copyright and acknowledgement notices.
- Added ability to latch alarms so they have to be actively accepted to silence the alarm, rather than it re-setting when the movement stops.
- Fixed problem with the system being difficult to shut down if as multiple instances of main screen could be active at once.
- It is now compatible with both the original Pebble Android App and the new Pebble Time Android App, and works with both the original Pebble and Pebble Time watches.
- Merged the ‘server’ and ‘client’ apps into one, so you can select the ‘data source’ in settings to be either the pebble watch directly or the network. This means you can install the app on two devices and the second one, selected to ‘network’ data source will mirror the screen and alarms that are shown on the other device.
The OpenSeizureDetector git repository has become quite big, and contains several different applications. This means it is difficult to use the GitHub issue tracking tools and commit logs to see what is happening with different apps.
So, I have split it by doing the following:
- Created an OpenSeizureDetector organisation on github.
- Transferred ownership of the OpenSeizureDetector repository to the new organisation.
- Checked out the repository to ~/OpenSeizureDetector, and created a new directory ~/OpenSeizureDetector_split then:
- Create a copy of the whole OpenSeizureDetector Repository
git clone ../OpenSeizureDetector
- Filter it down to just the required folder
git filter-branch --prune-empty --subdirectory-filter pebble_version/Android_SD_Client_AS/ master
- Create a new repository under the OpenSeizureDetector organisation in Github (using the github web interface) (called for example Android_SD_Client.git)
- Copy our new trimmed down repository to a sensible folder name:
git clone OpenSeizureDetector Android_SD_Client
- Point the new copy to the new github repository:
git remote set-url origin https://github.com/OpenSeizureDetector/Android_SD_Client.git
- And finally push it up to github with
We have added a simple fall detection function to the OpenSeizureDetector app. This means that the system will alarm if either the shaking associated with a tonic-clonic seizure is detected, or if a period of free-fall followed by large acceleration, which could indicate a person falling to the ground is detected. See Seizure Detection Algorithm for more info.
The fall detection function is disabled by default and needs to be switched on using the Android app settings screen.
Please report any issues (or successes) with this new version (Android App and Pebble App).
After my bad experience of wordpress plugins adding annoying popups, I thought I’d add the Google Plus ‘+1’ and Facebook ‘like’ buttons back myself.
Added the relevant code to the wordpress content-page.php file from https://developers.google.com/+/web/+1button/ and https://developers.facebook.com/docs/plugins/like-button.
Seems to work, but maybe not as nicely formatted as the simple-share plugin. Not sure I believe that 1.5M people ‘like’ my posts though, which is what the Facebook code is saying…
Not sure what happened, but this web site suddenly started showing an annoying “join our userbase” popup.
It appears to be due to an upgrade of the ‘Really Simple Share’ plugin that gives the Facebook Like, Google Plus +1 buttons etc.
The popup seems to be from an organisation galled ReadyGraph, but I don’t want it, and the the ‘Really Simple Share’ settings were not accessible, even from my administrator log-in. I have disabled the plugin for now…..