Neo4j - How KGs are shaping the future of Generative AI at AWS Summit London ...
Moodscope, subjective ratings and body blogging - Ute Kreplin
1. Moodscope, Subjective
Ratings
and
Body Blogging
Ute Kreplin
PhD Student at Liverpool John Moores
University
Presented at Quantified Self Europe 2011
2. What I did
+
Moodscope Body Blogging
Subjective tracking of mood Continuous recording and live streaming
of my Heart Rate (HR)
3. Moodscope Graph
Uses a slightly altered version
of the Positive & Negative
Affective Scales (PANAS)
Visual tracking of changes in
mood
4. Body Blogging
• Body Blogging is the act of logging how your body changes over
time using web technology
• 8 hour recordings (9am-5pm) with a wearable sensor
• Sharing through Twitter & physiologicalcomputing.net
5. Body
Blogging
• The implication of a 20 BPM drop in HR
• A mother’s reaction
• How do we make this data meaningful to a wider
audience? Heat Map
• What can I learn about my mood?
8. • Bottom-up vs. top-down interpretation
– Top-down: Predisposing the outcome of HR, i.e.
compatibility with moodscope
– Bottom-up: Longitudinal recording allows context
to build up around the data
• The use of heat-maps and how we can add
meaning to the data
9. Heat Map Representation of the
Body Blogging Data
5pm
3pm
Time
12pm
9am
15-Aug
01-Aug
05-Aug
08-Aug
23-Aug
11-Aug
18-Aug
26-Aug
30-Aug
Date
10. In conclusion
• Incompatible modes of recording
– Loss of variation within HR recordings
• Building context around the data
• Heat maps for easier understanding
• The sharing of meaningful events
• BPM a new way of sharing and recording extraordinary events
– BPM as personalised photograph
Hi, My name is Ute My project is about combining moodscope and the body blogger
Moodscope is an online mood tracking tool based on the Positive And Negative Affective Scale PANAS psychological scale tracking subjectively experienced mood
Body Blogging is the act of logging how your body changes over time using web technologyIntroduced by Kiel8 hour recordingsLive stream to twitter – update every 30 minPhysiological computing.net
Some interesting things came out of thisUsing Kiel’s twitter accountMy HR 20bpm lower than Kiels2 implicationsSudden drop on twitterKiel asleep on the physiological computing site before adjusting the systemBut no one asked Kiel about itInviting my mum to follow my HR tweetsHow can we make the sharing of this data more meaningful?
Daily mean and moodscope score2 neg and 1 pos spike but changes aren’t reflected in HRSo why is this the case?Incompatible modes of recordingContinuous recording of HR vs one moodscope scoreloss of variability in HR by reducing it to one score
Looked at the hour the moodscope was recordedA better match for average days, but ups and downs of the moodscope still not reflected to the same extend in HRApart from the first spike, the 4th where there is definitely smth going on but to what we need to add more context to the data
The question of context & the different ways of doing thisI was using a top-down approach by predisposing a context of this, which is my mood or moodscopeTrying to match this to the BBBottom-up approach, such as Kiel’s longitudinal recordings allows to add context to the heart rate after the recording Heat maps – a HR skeleton to add meaning to
Representation of my data for Aug as a heat mapColours reflect levels of activity, green normal yellow active, red very activeGreat deal of variation throughout each dayIf we now look at the 4th we see that my HR was very highWhat’s interesting is that I was asleep at the point of recordingWhat you see here is my body fighting with the common coldIn this way the data becomes more meaning, as I look at unusual eventsWith time I would be able to read this patterns better giving me more instant access
Incompatible modes of recordingBuilding context around HR not HR around contextNot sharing everyday events but special occasions, e.g. job interviewButterflies on your wedding day captured in BPM
