So I checked the forecast for this weekend, and apparently it’s going to be hotter than hell at the zombie race this weekend:
38 degrees??? That’s insanity! The zombies won’t have a chance to eat me – I’m going to die of heat stroke first!
In preparation for the upcoming zombie-eating-Beth fest, I decided to try out the Zombies, Run! app. It’s an iPhone app that you use while you are out running – it’s plays an audiotrack that tells you a storyline as you run. A storyline about you (affectionately known as “Runner #5”) during a zombie apocalypse. You can select to have the “zombie chase” option on or off – I chose “on”, naturally – and the “zombie chase” options means that at random times, the audio will tell you that zombies are chasing you and you have to sprint! It’s sort of a highly motivating interval training system. I only went out for a *very* short run this evening to test out the app, so I didn’t get chased by any zombies yet.
Here’s a summary of my “mission” so far:
It’s probably a pretty good thing that I picked up a radio, some tinned food, and some first aid kits, but I’m not sure why I needed to pick up a sports bra (WTF?). You can do as much of a given “mission” as you like on a run, and then pick it up again next time from where you left off. Next time I intend to do a much longer run and hopefully I’ll get chased by some zombies at some point.
Though I should point out that while I wasn’t actually chased by any zombies, there was a point where I was told some were nearby and I could hear them breathing. You can actually pinpoint when that happened on my Runkeeper summary of the run – the shorter the bar in the following graph, the faster the pace:
I’m hoping that means that I will, in fact, sprint when being chased by zombies this weekend!
So I’ve been meaning since forever ago to write a blog posting about the Sleep Cycle iPhone app. It’s a free app that tracks your sleeping patterns and then works as an alarm to wake you up when you are in the lightest stage of sleep. But mostly I love it because I get to look at a graph every morning when I wake up! A graph that looks like this:
Or maybe this:
Of course, what prompted me to write this blog posting today, of all days, is that Dr. Dan just blogged about this app! I didn’t even know that he used the Sleep Cycle app, and here he is scooping me! Of course, the data from our respective Sleep Cycle apps show that I spend, on average, 7 hrs 02 mins sleeping per night compared to his 5 hours 40 minutes per night and so clearly he used his extra awake time to scoop me on this blog topic! As I suggested in my comment on his blog posting, “Beth snoozes, Beth loses… literally!”
Like Dr. Dan, I wish that this app had the option to overlay all my graphs on top of each other to see if some sort of pattern emerges. I mean, I have data from 243 nights and it’s pretty hard to spot patterns just by flipping through the graphs one at a time. I’d also like to see what my maximum and minimum sleep times were (or some other measure of the spread of my data); though my average across 243 nights is 7 hrs and 2 mins, I routinely sleep 5-6 hours per night during the week and 9-10 hours on the weekends.
Now speaking of sleep, that actually sounds like a good idea right about now. BETH SLEEPY!
I’ve mentioned before that I’m using the RunKeeper iPhone app to track my training runs. One of the things I really like about RunKeeper is that it gives you a graph of your pace and the elevation of the runs you do. And you know I’m a sucker for graphs.
This is a graph from last week’s hill run:
The blue line represents pace, which is in mins per kilometer – that is, how many minutes it takes to run you one kilometre. It’s a little counter intuitive at first, because lower = faster (unlike speed, where higher = faster). Incidentally, I’m not sure why they have “speed” in the legend, since they don’t show speed on the graph.
The green line represents elevation – it’s easier because higher on the graph = higher in real life. You can tell the app isn’t perfect though, because on this run I ran up and down *the exact same hill* four times, so the elevation at the 1 km mark, which was the bottom of the hill, should be at the same elevation as the other troughs in the graph.
Also, I’m a little surprised that pace doesn’t mirror elevation – I feel like I run so much faster on the downhill than on the uphill. It’s starts to show up that way a little near the end, but I would have expected it to be more pronounced.
Also, I think the graph is missing a line. If I were the one drawing the graph, it would look like this:
Where the red line = will to live.
I hate you hill runs. I hate you long time.
A few weeks ago I mentioned that my run tracking app, which uses the iPhone’s GPS to map out where you run as you run, occasionally has crazy ideas about where I actually ran. In the comments, extragoode mentioned that it was possible that sometimes the phone might lose its GPS connection for a second and jump to using cell towers instead until the GPS kicks back in. I’m guessing that’s what happened on tonight’s run (planned route in blue, “actual” route in red):
because I’m pretty sure I did not traverse False Creek like this!