This page gives some instructions for users who have volunteered to test OpenSeizureDetector V4 and gives some questions that I would like you to think about when using it.
Contents
Install OpenSeizureDetector Version 4 (Alpha Test Version)
Version 4.0.x is now approved for release on Google Play Store. It is currently only available in the ‘Beta Test’ part of Play Store while I wait for feedback from volunteers so I can tweak the user interface if necessary before releasing it to all users.
To register as a Beta tester to receive the new version, please visit this page: https://play.google.com/apps/testing/uk.org.openseizuredetector.
Initial Start-Up
Start OpenSeizureDetector. You should see:
- A ‘Thank you for installing (or upgrading) OpenSeizureDetector message, with buttons to take you to the Privacy Policy and to the Data Sharing web page for more information.
- A dialog box warning that OpenSeizureDetector battery usage is being optimised. In phone settings Apps->OpenSeizureDetector->Battery->Battery Optimisation select OpenSeizureDetector to NOT be optimised. See video here.
- Accept the battery optimisation warning dialog – you should see the start-up screen quickly change to the main screen.
- The default data source is ‘Phone’ which uses the phone accelerometer rather than a watch for ease of testing – there is no need to connect a watch for this initial testing. But if you want to use the system for real during the testing, change the data source to Garmin and check it works with your watch.
Create a Data Sharing Account
Create an account on the Data Sharing system, and log into it using the OpenSeizureDetector App
See the instructions on the Data Sharing Set-up Instructions page.
Note that the account confirmation email may either end up in your Spam folder, or not be delivered at all because it is rejected by your email system. If you do not receive the email, please email graham@openseizuredetector.org.uk and I will enable your account manually for you.
The main app display should say “Data Sharing Setup OK”
Generate some Seizure-Like Events
Shake the phone gently to generate a warning and an alarm initiation.
After about 5 minutes you should see an extra OpenSeizureDetector notification appear saying there are unconfirmed seizure events in the database.
Press the new ‘Raise Alarm’ button on the main screen to generate a seizure alert (the idea is that if you find a seizure in progress and the system has not alarmed, this will force the data to be recorded and shared).
Note that it takes a few minutes between an alarm being generated and the data being uploaded to the database – this is because we record a couple of minutes of data after the alarm so we can see what happens after the initial event.
Confirm the Seizure-Like Events
Use the new notification to get to the seizure events screen and select an event to classify whether it is a genuine seizure or a false alarm (if you are testing recording something as a genuine seizure but it is not please put ‘testing’ in the notes field so we do not think it is real.
Use the OpenSeizureDetector App menu to get to the seizure events screen (the “Data Log Manager” menu item). Classify the remaining events as false alarms or genuine seizures. See the Reporting Seizures and False Alarms page for more information.
Confirm that the ‘Unconfirmed Events’ notification disappears once all events have been edited and saved.
Classify the Events generated during Normal Use
Please continue to use OpenSeizureDetector V4.x normally as you did with the previous version, but check for Unconfirmed events regularly and classify them as genuine seizures or false alarms as described in the Reporting Seizures and False Alarms page. This is really important because without that we do not know how to use the data you are sharing with us and we will have to discard it.
Provide Feedback
It is important that you provide feedback of your experiences, good and bad:
- How was the installation process (noting the one you used is much more difficult than using Google Play Store!).
- Did the Data Sharing account creation and login work ok. Is there any terminology that seems odd (or overly technical) that we should change before we release it to general users?
- Does the notification of unconfirmed seizure events appear ok – is it clear what it means or do we need to change any terminology?
- Does editing events to record genuine seizures or false alarms work ok? Does the list of false alarm causes seem right, or should we add or remove anything?
- Can you shout down the app and re-start it ok (with the stop/start server menu item)? I think there may still be an issue to fix there. If you have trouble stopping it go into the phone settings->Apps->OpenSeizureDetector and select ‘Force Stop’ to shut it down.
- Are the displayed times of the seizure events in the Data Log Manager screen correct? (There might be an issue with timezones, because I am working in GMT at the moment….).
- Any other comments or concerns that you think we should address before publishing it?
Please provide feedback either on our Facebook page (https://facebook.com/openseizuredetector) or by email to graham@openseizuredetector.org.uk.
Thank you so much for your help with testing this!
Graham. (graham@openseizuredetector.org.uk)