The Story Behind the 11hr Cup of Tea, Wifi Kettles, & How it Was All About... Data

The Story Behind the 11hr Cup of Tea, Wifi Kettles, & How it Was All About... Data

Presented in London to an analytics user group and explaining the story behind the WiFi kettle that got me in the news ... and how it was part of a personal "quantified self" Hadoop data lake project, landing all of my data into a Hadoop analysis environment and using the data to help me live a healthier life, automate my home and automatically boil the kettle when I woke up in the morning.

825a63052b050519b749070c52e87ae1?s=128

Mark RIttman

October 17, 2016
Tweet

Transcript

  1. T : @markrittman THE STORY BEHIND THE 11HR CUP OF

    TEA, WIFI KETTLES, & HOW IT WAS ALL ABOUT... DATA Mark Rittman, Oracle ACE Director OCTOBER 2016
  2. •Oracle ACE Director, now Independent Analyst •Regular columnist for Oracle

    Magazine •Past ODTUG Executive Board Member •Author of two books on Oracle BI •Co-founder & CTO of Rittman Mead •15+ Years in Oracle BI, DW, ETL + now Big Data •Implementor, trainer, consultant + company founder •Based in Brighton, UK About The Presenter 2
  3. 3

  4. ONE MORNING (AND THEN ALL DAY) 
 LAST WEEK… 4

  5. 5

  6. THE FOLLOWING MORNING… 6

  7. 7

  8. 8

  9. 9

  10. 10

  11. 11

  12. 12

  13. WHY? 13

  14. 14

  15. DATA 15

  16. D A T A 16

  17. AND WHAT’S POSSIBLE WHEN
 YOU JOIN THAT DATA TOGETHER 17

  18. SIX MONTHS AGO… 18

  19. •Over the past months I’ve been on sabbatical, taking time

    out to look at new Hadoop tech •Building prototypes, working with with startups & analysts outside of core Oracle world •Asking myself the question “What will an analytics platform look like in 5 years time?” •But also during this time, getting fit, getting into cycling and losing 14kg over 12 months •Using Wahoo Elemnt + Strava for workout recording •Withings Wifi scales for weight + body fat measurement •Jawbone UP3 for steps, sleep, resting heart rate •All the time, collecting data and storing it in Hadoop Personal Data Science Project - “Quantified Self” 19
  20. •Quantified Self is about self-knowledge through numbers •Decide on some

    goals, work out what metrics to track •Use wearables and other smart devices to record steps, heart rate, workouts, weight and other health metrics •Plot, correlate, track trends and combine datasets •For me, goal was to maintain new “healthy weight” •Understand drivers of weight gain or loss •See how sleep affected productivity •Understand what behaviours led to a “good day” Personal Data Science Project - “Quantified Self” 20
  21. MY OTHER SABBATICAL PROJECT… 21

  22. 22 HOME AUTOMATION 22

  23. 23

  24. •Data extracted or transported to target platform using LogStash, CSV

    file batch loads •Landed into HDFS as JSON documents, then exposed as Hive tables using Storage Handler •Cataloged, visualised and analysed using Oracle Big Data Discovery + Python ML Hadoop Cluster Dataset - “Personal Data Lake" 24 Data Transfer Data Access “Personal” Data Lake Jupyter
 Web Notebook 6 Node Hadoop Cluster (CDH5.5) Discovery & Development Labs
 Oracle Big Data Discovery 1.2 Data sets and samples Models and programs Oracle DV
 Desktop Models BDD Shell,
 Python, 
 Spark ML Data Factory LogStash
 via HTTP Manual
 CSV U/L Data streams CSV, IFTTT
 or API call Raw JSON log files in HDFS Each document an event, daily record or comms message Hive Tables
 w/ Elastic
 Storage Handler Index data turned into tabular format Health Data Unstructured Comms Data Smart Home
 Sensor Data
  25. •Uses IFTTT cloud workflow service to subscribe to events on

    wearables’ APIs •Triggers HTTP GET request via IFTTT Maker Channel to Logstash running at home •Event data sent as JSON documents, loaded
 into HDFS via webhdfs protocol •Structured in Hadoop using Hive JSONSerDe •Then loaded hourly into DGraph using
 Big Data Discovery dataprocessing CLI •Event data automatically enriched, and can
 be joined to smart home data for analysis Landing Wearables Data In Real-Time 25 New workout
 logged using
 Strava 1 Workout details uploaded
 to Strava using cloud API 2 3 IFTTT recipe gets workout event from Strava API, triggers an HTTP GET web request 4 JSON document received by
 Logstash, then forwarded to 
 Hadoop using webhdfs PUT 5 JSON documents landed in HDFS in raw form, then structured using Hive JSONSerDe 6 Hive data uploaded into Oracle Big Data Discovery, visualised and wrangled, and modelled using pySpark In the Cloud Home
  26. •All smart device events and sensor readings are routed through

    Samsung Smart Things hub •Including Apple HomeKit devices, through custom integration •Event data uploads to Smart Things cloud service + storage •Custom Groovy SmartApp subscribes to
 device events, transmits JSON documents
 to Logstash using HTTP GET requests •Then process flow the same as with
 wearables and social media / comms data Landing Smart Home Data In Real-Time 26 Sensor or other smart device
 raises a Smart Things event 1 Event logged in Samsung Smarthings Cloud Service from Smart Things Hub 2 4 JSON document received by
 Logstash, then forwarded to 
 Hadoop using webhdfs PUT 5 JSON documents landed in HDFS in raw form, then structured using Hive JSONSerDe 6 Hive data uploaded into Oracle Big Data Discovery, visualised and wrangled, and modelled using pySpark In the Cloud Home SmartApp subscribes to device events, forwards them as JSON document using HTTP GET requests 3
  27. •As well as visualising the combined dataset, we could also

    use “machine learning” •Find correlations, predict outcomes based on regression analysis, classify and cluster data •Run algorithms on the full dataset to answer questions like: •“What are the biggest determinants of weight gain or loss for me?” •“On a good day, what are the typical combination of behaviours I exhibit”? •“If I raised my cadence RPM average, how much further could I cycle per day?” •“Is working late or missing lunch self-defeating in terms of overall weekly output?” And Use Machine Learning For Insights… 27 MODELING AND INFERRING
  28. •Analysis started with data from Jawbone UP2 ecosystem (manual export,

    and via IFTTT events) •Base activity data (steps, active time, active calories expended) •Sleep data (time asleep, time in-bed, light and deep sleep, resting heart-rate) •Mood if recorded; food ingested if recorded •Workout data as provided by Strava integration •Weight data as provided by Withings integration Initial Base Dataset - Jawbone Up Extract 28 1 2 3
  29. •Understand the “spread” of data using histograms •Use box-plot charts

    to identify outliers and range of “usual” values •Sort attributes by strongest correlation to a target attribute Perform Exploratory Analysis On Data 29
  30. •Initial row-wise preparation and transformation of data using Groovy transformations

    Transform (“Wrangle”) Data As Needed 30
  31. •Very typical with self-recorded healthcare and workout data •Most machine-learning

    algorithms expect every attribute to have a value per row •Self-recorded data is typically sporadically recorded, lots of gaps in data •Need to decide what to do with columns of poorly populate values Dealing With Missing Data (“Nulls”) 31 1 2 3
  32. •Previous versions of BDD allowed you to create joins for

    views •Used in visualisations, equivalent to a SQL view i.e. SELECT only •BDD 1.2.x allows you to add new joined attributes to data view, i.e. materialise •In this instance, use to bring in data on emails, and on geolocation Joining Datasets To Materialize Related Data 32
  33. •Only sensible option when looking at change in weight compared

    to prior period •Change compared to previous day too granular Aggregate Data To Week Level 33 1 2 3
  34. NOW FOR THE CLEVER BIT MODELING AND INFERRING 34

  35. Use BDD Shell API to Identify Main Dataset ID 35

  36. Use Python PANDAS to Calculate % CHG W/w 36

  37. Identify Correlations Between Attributes 37

  38. Use Linear Regression on BDD Dataset via Python 38 •To

    answer the question - which metric is the most influential when it comes to weight change?
  39. And the Answer … Amount of Sleep Each Night 39

    •Most influential variable/attribute in my weight / loss gain is “# of emails sent” •Inverse correlation - more emails I sent, the more weight I lose - but why? •In my case - unusual set of circumstances that led to late nights, burst of intense work •So busy I skipped meals, didn’t snack, stress and overwork perhaps •And then compensated once work over by getting out on bike and exercising •Correlation and most influential variable 
 will probably change in time •This is where the data, measuring it, 
 and analysing it comes in •Useful basis for experimenting •And bring in the Smart Home data too
  40. •Load device + event data into Cloudera Kudu rather than

    HDFS + Hive •Current limitation is around Big Data Discovery - does not work with Kudu or Impala •But useful for real-time metrics (BDD requires batch ingest, and samples the data) •Use Kafka for more reliable event routing •Push email, social media, saved documents etc into Cloudera Search •Do more on the machine learning / data integration + correlation side For The Future..? 40
  41. 41

  42. 42

  43. 43

  44. 44

  45. 45

  46. THANK YOU E X A M P L E S

    O F T E X T - S I M P L E A N D E A S Y T O U S E T H E T H E M E O F T H E D E M O T E M P L AT E B L A C K A N D W H I T E W O R L D THANK YOU 46
  47. T : @markrittman THE STORY BEHIND THE 11HR CUP OF

    TEA, WIFI KETTLES, & HOW IT WAS ALL ABOUT... DATA Mark Rittman, Oracle ACE Director OCTOBER 2016