Graeme22
Variations in heart rates
Heart rates vary largely based on age, gender, health and activity. This can be difference of 50 bpm in a young male athletes resting heart rate to 200 bpm in an unhealthy 20 year old. Due to this the application would need to take into account information regarding the user to ensure every user has a similar experience rather than some users shifting to the high end of the selected colours and causing users to be unsatisfied. Options to solve this:
- Create a sequence that people must follow for a set time before first using it to be able to get a basic idea of their heart patterns.
- Program in averages for multiple age, health gender and activity ranges and get the user to enter this on first starting.
- Allow the user to create an offset so if they feel they are in certain sections for too long they can adjust.
I am recommending the first one is investigated to at least see if it possible to do as this would give the best experience to the end user. However if this is too difficult it should not be too hard to do the second one without too much trouble. The offset could also be included if the user still feels like there is an issue.
Once we have this solved colour mapping will be very easy.
Noted. It'd be good to get some more opinions on the best way to do this. Another thing to mention is variations in real time. We'll have to use a smoothing function over, say, the past 5 seconds to prevent erroneous spikes or too rapid of transitions.
I agree it would be nice to hear any other suggestions to ways to overcome this issue. Also may I add that I do like the sound of using a five second average to ensure that there is no rapid spiking however due to the fact that currently it is suggested to poll every second then I do believe it may be better to have an option in the computer program side that you can enable to stop this smoothing and get more real time reactions like jump scares games may cause.
I think the average should be weighted a bit so that a severe change would still register immediately. E.g. 0.1 * 3 seconds ago + 0.1 * 2 seconds ago + 0.3 * 1 second ago + 0.5 * now
There's probably something more formal for this but it wouldn't look so so different