Tag Archives: qstop
Like many people, Christel de Maeyer felt that her sleep could be better. Presenting at our 2013 conference in Europe, Christel shares what she learned from collecting over three years of sleep data.
What did Christel do?
Christel tracked her sleep for 2 years with various devices. She tested the effects of different variables on her sleep quality, including consumption of alcohol, keeping a consistent wake time and changing her mattress.
How did she do it?
She used the Zeo to track sleep for two years, before switching over to a BodyMedia device. While making changes she monitored how her sleep data changed, as well as how she felt.
What did she learn?
Before self-tracking, Christel felt that she woke up frequently during the night, and the Zeo confirmed this. On average she woke up around 8 to 9 times. She suspected the mattress could be part of the problem. After considerable research, she replaced her mattress (to one that had a foam top), successfully reducing her wake-ups to 4 or 5.
Christel discovered that her sleep patterns looked significantly different after just two glasses of alcohol. Her REM diminishes to nearly 0% (though deep sleep seems unaffected).
Christel also found that total sleep time was less important for how she felt the next day than the combination of REM and deep sleep. Even if she only sleeps for six hours, as long as she gets at least 2 hours of combined REM/deep sleep, she feels good.
In addition to these findings and others she explores in the video above, Christel has taken her lessons and now helps others with sleeping issues. You can find more at her website.
This week there will be three meetups in three countries on three continents. The theme for the Bogotá group will be the quantification of emotions. The Brussels meetup will take a look at AmWell’s tools for monitoring stress, sleep and activity. And in Pittsburgh, they will feature casual hands-on demos before their talks.
To see when the next meetup in your area is, check the full list of the over 100 QS meetup groups in the right sidebar. Don’t see one near you? Why not start your own!
We hope you enjoy this weeks list. Feel free to submit articles, show&tell self-tracking stories, and QS data visualizations. Just email me!
Why can’t you track periods in Apple’s Health app? by Nat Buckley. With the recent re-release of Apple’s HealthKit enabled self-tracking and personal data system it no wonder that people are taking a long hard look at what data is being excluded. With the popularity of menstruation tracking apps (this app has nearly 30,000 ratings) it’s surprising this was overlooked. This excellent post is a must read on the topic.
Now That Cars Have Black Boxes, Am I Being Tracked? by Popular Science Editors. Questions and concerns about surveillance are becoming more commonplace. As someone who is looking to purchase a car in the next year or so I was happy to see this post come across my stream.
The Quantified Self community, lifelogging and the making of “smart” publics by Aristea Fotopoulou. I love it when people take a thoughtful look at the Quantified Self community and write about their experiences:
For me, the potential of QS for public participation lies in the show and tell meet-ups that constitute a central feature of this community. Meet-ups enable the exchange of stories about the success or failure of lifelogging practices; they allow people to connect and form synergies around common interests, and to explore wider questions such as personal data management and ownership. [...] members touch upon key political issues and create temporary spaces of dialogue: what happens to personal data, who has access to these data (is it private individuals, governments or corporations)? For what purposes (medical research)? And how can these data be interpreted (by algorithms, visualisations) and used to tell stories about people?
Stepping Down: Rethinking the Fitness Tracker by Sara M. Watson. Sara uses her personal journey of recovery from hip surgery to frame an interesting question: Should we trust our fitness trackers to prescribe movement goals?
Practical Statistical Modeling: The Dreaded After-School Carpool Pickup by Jamie Todd Rubin. Jamie wanted to understand if there was a way he could reduce how much time he spent waiting in line to pick up his son from school. Why not track it and model it!
Bulletproof Diet and Intermittent Fasting: 1.5 Year Results by Bob Troia. Bob takes a deep dive into his data to see if this particular diet is having beneficial health effects. Click for the great data, stay for the wonderful discussion and very, very thorough write-up.
Quotidian Record by Brian House. I’ve been a fan of Brian House since his early days visualizing Fitbit data. I was reminded of this work during a conversation about geolocation data and thought it would be a nice addition to our visualization list.
Visualizing My Daily Self-Management by Katie McCurdy.
What does my daily medication and self-management look like? How could I visualize this regimen? How can I communicate the ‘burden’ and work of caring for myself?
I decided to draw pictures of the things that I need to do on a daily basis; that way I could show the workshop attendees what my day was like instead of just telling them.
It’s Time to Eat by Karl Krehbiel. Karl, a data science intern at Jawbone used the data from their global community of users the determine the likelihood of food and drink consumption during the day. Really fun and interesting visualizations here.
Earlier this week we posted an update to our How To instructions for downloading your Fitbit data to Google Spreadsheets. This has been one of our most popular posts over the past few years. One of the most common requests we’ve received is to publish a guide to help people download and store their minute-by-minute level step and activity data. Today we’re happy to finally get that up.
The ability to access and download the minute-by-minute level (what Fitbit calls “intraday”) data requires one more step than what we’ve covered previously for downloading your daily aggregate data. Access to the intraday data is restricted to individuals and developers with access to the “Partner API.” In order to use the Partner API you must email the API team at Fitbit to request access and let them know what you intend to do with that data. Please note that they appear to encourage and welcome these type of requests. From their developer documentation:
Fitbit is very supportive of non-profit research and personal projects. Commercial applications require additional review and are subject to additional requirements. To request access, email api at fitbit.com.
In the video and instructions below I’ll walk you through setting up and using the Intraday Script to access and download your minute-by-minute Fitbit Data.
- Set up your FitBit Developer account and register an app.
- Go to dev.fitbit.com and sign in using your FitBit credentials.
- Click on the “Register an App” at the top right corner of the page.
- Fill in your application information. You can call it whatever you want.
- Make sure to click “Browser” for the Application Type and “Read Only” for the Default Access type fields.
- Read the terms of service and if you agree check the box and click “Register.”
- Request Access to the Partner API
- Email the API team at Fitbit
- They should email you back within a day or two with response
- Copy the API keys for the app you registered in Step 1
- Go to dev.fitbit.com and sign in using your FitBit credentials.
- Click on “Manage My Apps” at the top right corner of the page
- Click on the app you created in Step 1
- Copy the Consumer Key.
- Copy the Consumer Secret.
- You can save these to a text file, but they are also available anytime you return to dev.fitbit.com by clicking on the “Manage my Apps” tab.
- Set up your Google spreadsheet and script
- Open your Google Drive
- Create a new google spreadsheet.
- Go to Tools->Script editor
- Download this script, copy it’s contents, and paste into the script editor window. Make sure to delete all text in the editor before pasting. You can then follow along with the instructions below.
- Select “renderConfigurationDialog” in the Run drop down menu. Click run (the right facing triangle).
- Authorize the script to interact with your spreadsheet.
- Navigate to the spreadsheet. You will see an open a dialog box in your spreadsheet.
- In that dialog paste the Consumer Key and Consumer Secret that you copied from your application on dev.fitbit.com. Click “Save”
- Navigate back to the scrip editor window.
- Select “authorize” in the Run drop down menu. Click run (the right facing triangle).
- Select “authorize” in the Run drop down menu. This will open a dialog box in your spreadsheet. Click yes.
- A new browser window will open and ask you to authorize the application to look at your Fitbit data. Click allow to authorize the spreadsheet script.
- Download your Fitbit Data
- Go back to your script editor window.
- Edit the DateBegin and DateEnd variables with the date period you’d like to download. Remember, this script will only allow 3 to 4 days to be downloaded at a time.
- Select “refreshTimeSeries” in the Run drop down menu. Click run (the right facing triangle).
- Your data should be populating the spreadsheet!
If you’re a developer or have scripting skills we welcome your help improving this intraday data script. Feel free to check out the repo on Github!
How many times during the course of the day do you find your mental state drifting into negativity, feeling like you’re lost, or just plain stressed? How could you even keep track of this, and why would you want to?
What Did Paul Do?
Paul LaFontaine has been tracking what he calls “upsets” to better understand himself, the way he works, and to see if he can improve his mental and physiological response and recovery.
Upsets are something physiological that were happening beneath the surface, and they’re trackable. It didn’t have to be emotional, but there had to be a signal. This project is part of an longer ongoing study. Before this current iteration I manually logged over 3,000 upsets and what I found is that most of my upsets were self-induced. I’d be in a calm environment, but then become upset about something. I wanted to use technology because I was afraid of bias and I know I was missing some upsets.
How Did He Do It?
I used the HeartMath EMWave2 that measures heart rate variability and indicates when you’re in and out of coherence. When I was out of coherence I captured that as an upset. I would stop what I was doing and use an audio recorder to keep track of the time, how long I was upset, the reason, and what method I used to recover. I tracked 71 sessions (each session was 25-45 minutes) totaling 42 hours of tracking time. I logged 1292 upsets during this period.
What Did He Learn?
Paul analyzed his data and found some very interesting insights about his upsets, his reasons for being upset, and the effectiveness of his recovery techniques.
I found that I was triggering an upset every 2 minutes. My wife said something must be wrong with me, but this stayed relatively constant through the tracking period. I started to think of it like skiing a mogul course. The moguls didn’t move, it was about how effective I could move through them. And, dealing with upsets is like playing whack-a-mole. They come fast and furious and every second counts.
For recovery I was able to find that my most effective technique was breathing. By returning to six breaths per minute routine I was able to improve recovery time from 33 seconds to 17.8 seconds. It was the primary way I could remove myself from being upset and make myself calmer.
We want to thank Paul for presenting this great QS project at the Bay Area QS Meetup group. Make sure to watch the full talk below to learn more about Paul’s methods and findings, then hop over to his website where you can read about how he tracked his stress during this talk.
We’re posting a quick note today to let you know that we’ve updated our “How To Download Your Fitbit Data” post. It now included separate instructions for both the old and new versions of Google Spreadsheets. This is just the first in a series of planned updates. We hope to post additional updates to allow you to have deeper access to your Fitbit data including, heart rate, blood pressure, and daily goal data.
If you’re using this how-to we’d love to hear from you! Are you learning something new? Making interesting data visualizations? Discussing the data with your health care team? Let us know. You can email us or post here in the comments.
This week will see eight meetups in three countries on three continents and will show the different forms that Quantified Self meetups take. There will be longstanding groups like New York, who are putting on their 26th meetup, while Miami will be hosting their very first. London will be convening over 100 people with formal presentations, while Ashland will have an engaging discussion within a small group.
Show&Tell presentations will include Vienna’s Leonard Tulipan on how he applied his startup’s classification of “vanity metrics” vs. “actionable metrics” to his own medical data. Oxford member John Courouble will talk about the data around his weight loss plateau.
In addition to the standard show&tell format, Sydney will have breakout groups, while the Minnesota group will discuss the tools that their community is using. The Vienna and Portland groups will have guest speakers, including Vestigen, a company that tracks blood biomarkers for disease and Zenobase, which helps people aggregate and visualize their data, respectively.
If you are near any of these special events, you will definitely want to attend. To see when the next meetup in your area is, check the full list of the over 100 QS meetup groups in the right sidebar. Don’t see one near you? Why not start your own!
Thursday (September 25)
We hope you enjoy this week’s list!
Big Data in the 1800s in surgical science: A social history of early large data set development in urologic surgery in Paris and Glasgow by Dennis J Mazur. An amazing and profoundly interesting research paper tracing the use of “large numbers” in medical science. Who knew that is all began with bladder stones!
Civil Rights, Big Data, and our Algorithmic Future by Aaron Rieke, David Robinson and Harlan Yu. A very thorough and thoughtful report on the role of data in civil and social rights issues. The report focuses on four areas: Financial Inclusion, Jobs, Criminal Justice, and Government Data Collection and Use.
Caution in the Age of the Quantified Self by J. Travis Smith. If you’ve been following the story of self-tracking, data privacy, and data sharing this article won’t be all that surprising. Still, I can’t help but read with fascination the reiteration of tracking fears, primarily a fear of higher insurance premiums.
Patient Access And Control: The Future Of Chronic Disease Management? by Dr. Kaveh Safavi. This article is focused on providing and improving access and control of medical records for patients, but it’s only a small mental leap to take the arguments here and apply them all our personal data. (Editors note: If you haven’t already, we invite you to take some time and read our report: Access Matters.)
Perspectives of Patients with Type 1 or Insulin-Treated Type 2 Diabetes on Self-Monitoring of Blood Glucose: A Qualitative Study by Johanna Hortensius, Marijke Kars, and Willem Wierenga, et al. Whether or not you have experience with diabetes you should spend some time reading about first hand experiences with self-monitoring. Enlightening and powerful insights within.
Building a Sleep Tracker for Your Dog Using Tessel and Twilio by Ricky Robinett. Okay, maybe not strictly a show&tell here, but this was too fun not to share. Please, if you try this report back to us!
Digging Into my Diet and Fitness Data with JMP by Shannon Conners, PhD. Shannon is a software development manager at JMP, a statical software company. In this post she describes her struggle with her weight and her experience with using a BodyMedia Fit to track her activity and diet for four years. Make sure to take some time to check out her amazing poster linked below!
The following two visualizations are part of Shannon Conners’ excellent poster detailing her analysis of data derived from almost four years of tracking (December 2010 through July 2014). The poster is just excellent and these two visualizations do not do it justice. Take some time to explore it in detail!
Tracking Energy use at home by reddit user mackstann.
“The colors on the calendar represent the weather, and the circles represent how much power was used that day. The three upper charts are real-time power usage charts, over three different time spans. I use a Raspberry Pi and an infrared sensor that is taped onto my electric meter. The code is on github but it’s not quite up to date (I work on it in bits and pieces as time permits I have kids).”
Today we are excited and honored to announce that Steven Jonas has joined QS Labs as our Senior Editor/Information Architect. As has been the case with previous additions to QS Labs, we welcome Steven as a friend and fellow community member. Steven serves as a co-organizer of the Portland QS meetup group, and has participated as our speaker coordinator for our past two conferences.
In addition to his work supporting our global QS community, Steven is an active self-tracker, having engaged in many different projects. We’ve been delighted to highlight a few of those here on the QS website. We invite you to welcome Steven and get to know him a bit by exploring the posts linked below.
Photo by Mark Krynsky
Like many of us, James Norris remembers his first kiss. Unlike many of us, he also knows who it was with, where it was, and his age. How does he know this information? When he was 13, he realized that he forgot some detail about his life that he thought was important. To prevent that from happening again, he decided to carry around sticky notes to record important life events and has been doing it ever since. Fast forward 15 years and James has recorded 1,500 “firsts.” Watch this talk, presented at the Washington DC QS meetup group, to hear James talk about the data he collects, and the lessons he’s learned along the way.