The too warm, too untied, too tired run

Run 335
Average pace: 5:20/km

Location: Burnaby Lake (CW)
Distance: 6.03 km
Weather: Sunny
Temp: 26-29ºC
Wind: light
Calories burned: 464
Total distance to date: 2809

We are back to Official Summer Weather™ again and it was already warm when I headed out late in the morning and got noticeably warmer during the run. The first km was fine, the second I began to flag but not significantly more than normal. At this point my left shoelace came untied for the billionth time.

I ran with it untied for about 2 km, stopping at a bench on the second boardwalk to re-tie it. I carefully paused the workout on the iPod. I made sure the screen didn’t turn off while I re-tied the lace. I carefully touched the Resume button onscreen when I started running again. Satisfied that I had done everything correctly, I pressed the power button on the iPod (this turns the screen off, to prevent unwanted tapping) and put it back in my shorts pocket.

All seemed well until a few seconds later when Nike Lady piped up to say “workout stopped”. This seemed ominous but slightly less ominous than “workout ended”. I kept running and a moment or so later she said “Workout resumed”. She kept quiet except to count out the km for the remainder. Why this happened I have no idea.

After tying my shoelace back up I found I could not get my pace back. I felt parched and overheated–the main reason I don’t like stopping during a run in warm weather–but I wanted to do better than 5K and managed to hit 6K and a turgid overall pace of 5:20/km before stopping (for real). The last two km definitely felt like a slog but 5:20 still seemed a little slow. Here’s how the splits broke down:

Splits with mystery droop

Everything seems normal until the 4K mark when the pace drops to a strangely sluggish 5:48/km. It picks up again after that and though still slower than normal is probably a better reflection of how I was running for the last two km.

Here’s the split in graph form:

The droop

This is something that never happens during a run. You can tell I really mean it because I have used italics! I’m trying to think if something happened that made me stop or move especially slow and there was a few moments where I had to nearly stop when a clump of people, well, clumped up and blocked the way, but that happened right at the start of the run and had no real effect on my pace (the first km was still under 5:00/km). The only thing I can think is that I slowed as I neared the bench to tie my shoe and the sensor got confused or something and thought I went from jogging to crawling on my hands and knees.

In any case, it probably dragged my overall pace down by ten seconds or something. That’s just a guess because I’m not a mathologist.

As for the run, though I couldn’t muster the stamina to keep going past 6K, my feet and legs held up. The left foot started to hurt on the walk to the lake entrance and by the time I got to the dam was hurting quite nicely. I took a long drink from the faucet near the dam (it’s the best thing ever after a hot run) then sat down at a picnic table, took off my left shoe and thoroughly massaged my stinky and troublesome left foot. It did not hurt to do this and in fact it felt noticeably better after. It continued to feel pretty good until about a block before home.

When I got in I massaged it again and once more it felt much better. This foot is weird. It was kind of nice not riding the SkyTrain back for a change, though. It probably broke down again, anyway.

The other interesting things that happened technically occurred after the run but while i was still on the trail:

  • an adorable fuzzy golden caterpillar made its way across the trail in front of me, looking like a tiny hairy accordion. Or something. It probably got eaten by a robin.
  • an adorable fuzzy little chipmunk made its way across the trail in front of me. It was very tiny but crashed into the brush like it weighed a hundred pounds. Odd chipmunk. Probably not eaten by a robin.

At around the 7K mark I was walking along with my earphones still in but the music turned off. I heard something behind me, that telltale sound of rubber rolling over gravel. A moment later a guy on a bike rode past. I gave him the evil eye, as usual. He was followed by two young daughters on their own bikes. They looked to be about six and nine years old. The three of them disappeared around a corner.

I come around the corner and the younger girl is lying in the “ditch” tangled around her bike. Dad is coming over and chuckling about how she can’t ride a bike or something. He starts to pull the bike off and she yells “Ow ow ow!” but really didn’t appear to be hurt in any way*. I continue to walk by and a short distance ahead is a sign where the path splits. Every time there is a split there are signs. I look back to good ol’ dad and then point to the “No cycling” sign then continue on. I do not see them again.

I don’t know if they went back the way they came, started walking the bikes or got airlifted out by chopper. But it felt like karma had finally come to the Burnaby Lake loop.

Here’s hoping for less heat, fewer bikes and a better pace for the next run.

* I don’t blame the girls for being there and really hope the one who crashed was fine. She appeared more put out than actually injured but I’m not a doctor, nor do I even play one on TV.

You vs. a black bear: the infographic

The CBC News website ran a story on how to survive a black bear encounter (not to be confused with an encounter with Bear) due to a number of unusual bear goings-on of late. They included an infographic that I find strangely adorable and am reproducing here:

Bear Survival Guide

I like the idea of singing, clapping and whistling while hiking, to both ward off bears and convince other hikers that you are a lunatic. Also, the last image suggests using karate on the bear, which would be pretty cool.

[spoiler title=”And now the absolute best cover of Bear: The Novel” icon=”plus-square-1″]Bear[/spoiler]

Various commutes delayed on account of SkyTrain

It’s Black Eye Week for SkyTrain!

On Wednesday there was a problem with a switch at Waterfront Station that forced them to use only one platform during the early morning rush hour. I ended up being twenty minutes late for work (only five in reality as I normally get in fifteen minutes early). The worst part about this was the constant announcements with Mr. Stammer from SkyTrain control. Tip: Write down what you want to say, then read it into the PA. Don’t think off the top of your head every fricking time you turn the PA on. As outages go, this was pretty minor compared to the previous two.

On Thursday the PA system hummed to life as soon as I sat down in a car on the Canada Line at Waterfront Station. Never a good sign. Mr. Stammer said there was a minor power issue in Richmond and delays would be minor, only a few minutes at most. My train, whose ultimate destination was YVR-Airport, headed off. A few minutes later, when the issue should theoretically be resolved, Mr. Stammer came back on and was all, “Hoo boy, nope, this is a major power problem. Richmond is hooped! We’re setting up a bus bridge between Marine Drive and the airport. Sorry. We’ll figure this system out one of these days, lol!” My train’s destination suddenly changed to Marine Drive. That’s the stop after mine so apart from delays amounting to a mere five minutes, I wasn’t particularly affected by this. The overall delay for those who were affected amounted to around thirty minutes. Again, relatively minor compared to the Mega-Outages but still, you start to wonder how much duct tape is involved in holding everything together here.

The pleasantly zippy run

Run 334
Average pace: 4:58/km

Location: Burnaby Lake (CCW)
Ran Spruce and Conifer Loops and Piper Mill Trail
Distance: 5.04 km
Weather: Partly cloudy
Temp: 20ºC
Wind: light
Calories burned: 387
Total distance to date: 2803

After the strangely dismal performance of the previous run I was not looking forward to tonight’s.

Conditions were similar, with the temperature mild but instead of the expected precipitation the sky started to clear up, and while I had plenty o’ puddles to skirt around from an earlier shower, it never rained. This was nice.

My plan was to do the tight counter-clockwise loop: run the three optional trails then loop back along the main trail, coming back to the entrance to Burnaby Lake Park. Given the soggy weather earlier I encountered very few others out and aboot.

All of my body parts started out the run cooperating and remained cooperative throughout. I began with a crisp pace, pushed harder and longer (heh heh) than I normally would, determined to not repeat the terrible time of the last run and by the end I was quite literally gasping for breath.

I waited for the nice Nike lady to make the announcement of my pace and let out a (gasping) sigh of relief when she confirmed my time was 25:02 minutes, with a brisk average pace of 4:58/km. I’m still not sure if the previous run was a weird glitch with the Nike+ sensor or a weird glitch with my body but either way I was happy to see a normal pace again, especially with conditions being so close to the previous sloggy run.

On Sunday I will once again try for a full loop around the lake. It’s supposed to be sunny and 27ºC, which is warm but not unbearably so.

The curiously terrible run

Run 333
Average pace: 5:26/km

Location: Burnaby Lake (CCW)
Ran Spruce and Conifer Loops and Piper Mill Trail
Distance: 5.04 km
Weather: Overcast
Temp: 20ºC
Wind: nil to light
Calories burned: 388
Total distance to date: 2798

Halfway to the Number of the Beast and this run was certainly devilishly bad, time-wise.

On the plus side my left foot was not hurting before the run and even though I could feel it about halfway through it was minor and I don’t feel it affected my pace. Likewise the hip did not seem to affect my start or the run in general and is very close to what I would consider fully healed. From whatever happened to it.

The first km felt good, I had a strong finish and overall it felt like my pace was at least equal to Sunday, if not better. Then the nice Nike lady announced my pace at the end of the run and it was a very not-nice result: 5:26/km. My first km was even worse than the average at 5:28/km and my last km was significantly faster at 5:18/km. Where I normally droop at the 2K mark, today I was allegedly picking up speed, hitting 5:14/km.

All in all, a truly baffling result that makes me think the sensor may be going or has gone haywire.

If you ignore the actual time it was a much better run than Sunday. The temperature was mild and the sky overcast, so it was comfortable running weather. I never developed any weird cramps or stitches, apart from a few brief moments when the upper thigh muscle on my left leg felt a little sore, probably due to the relative lack of runs recently.

I’m pondering what to do for Thursday’s run. I may even get wacky and try the Brooks shoes of doom again or buy a new Nike+ sensor. Or both! Or neither! Who knows!

Commute cancelled on account of SkyTrain

Four days after I missed a run due to a massive breakdown in the SkyTrain system…there was another massive breakdown in the SkyTrain system. Fortunately Jeff was listening to the news on the radio (remember those?) and heard the whole thing had gone on the fritz yet again and he swung over from his work site to pick me up. As a result of getting a ride home in the truck I was actually 15 minutes earlier than usual instead of four hours later. Nice!

As to the issue, I quote from the Translink website (emphasis mine):

Human error led to yesterday’s Millennium and Expo Line disruptions.

An experienced electrician was installing a new circuit breaker for the Evergreen Line at a power distribution panel when he accidently tripped the main breaker feeding the critical systems at SkyTrain’s operations centre, causing a system-wide shut down of train controls.

One can only imagine what an inexperienced electrician might have done. Burned down the operations centre and taken the system offline for several years, perhaps. (Note: the worker has been suspended but union reps are saying the worker was following the orders of a supervisor and the panel shouldn’t have been worked on during SkyTrain operating hours.)

The Vancouver Sun offered this in one of their stories on the breakdown (emphasis again is mine):

TransLink spokeswoman Jiana Ling said passengers involved in last Thursday’s shutdown were trapped for an hour and a half, but it appears those involved in Monday’s incident were more impatient, with many forcing the doors open after just half an hour. One of the doors was pulled off with a crowbar, Kelsey said, which prolonged the delay by two hours because trains won’t operate if a door won’t close.

Tannis Steele, 18, who was stranded Monday on an air-conditioned train near Main Street-Science World Station, said her fellow passengers broke out after half an hour because they were bored.

I’m not sure what to make of passengers on the SkyTrain carrying crowbars with them. But I’m not the slightest bit surprised it only took half an hour for someone to pry the doors open and get out and the rest following, yes, like sheep. And delay the system starting up even longer. Good job, people. Good job, indeed.

And my favorite image. I call this one Mother of the Year:

SkyTrain mom
Mom and the kids out for a walk on the light rail line.

I’m curious why she thought it was better to carry the kid under her arm than put him/her in the stroller. And the mind positively boggles over what she would have done on the Millennium Line where there is a fence going down the middle of the guideway area, preventing things like strollers from even fitting.

All in all, another terrific day for public transit in the Lower Mainland.

The slightly damp mid-summer run

Run 332
Average pace: 5:06/km

Location: Burnaby Lake (CW)
Distance: 5.06 km
Weather: Light showers, cloudy
Temp: 15-17ºC
Wind: light
Calories burned: 389
Total distance to date: 2793

With my regular Thursday run cancelled due to a major SkyTrain malfunction (see previous post) I decided to just wait until my regular Sunday run to continue, thinking that my hip might benefit from the extra days off, even if my pace wouldn’t.

As it turned out my pace did improve over the previous run by seven seconds, coming in at 5:06/km. This is still kind of poopy for a 5K but there were a few extenuating circumstances, one being a six day gap between runs is just enough to start losing a bit of the edge and this year has been a bit of a struggle to find any edge to begin with. The other was my left foot. It was hurting even before I headed out and about 3 km in I knew I would not be able to run a full loop around the lake. I did walk the rest of the way (around 10 km in total, plus the run) and the foot remained sore for a good while after.

I am resolved to get it looked at by a footologist because something just ain’t right with it and as it stands (ho ho) now, it’s the major impediment to improving my runs. The hip actually felt pretty good, both at the start of the run and on the walk home after the SkyTrain ride, where it usually stiffens up. It’s essentially a non-factor now, allowing me to better-focus all my rage on that stupid foot.

The run itself was about as opposite as the last run could get: it was literally half the temperature (15ºC vs. 30ºC), with a mix of light showers and clouds. It was kind of nice, actually. Had my foot not acted up I’d have had no issue doing the full loop. It was weird to hardly sweat on a run in the middle of July.

I don’t think people running beach concessions were as pleased with the weather.

A surprising number of people were out, apparently due to some big rowing shindig, as the rowing pavilion parking lot was replete with boats and people and traffic cones, with more people clogging up the trails with their dogs not on leashes.

This was the second run where the FIRE DANGER signs were out. These signs also inform you that there is NO SMOKING. Two men sitting at the bench on the second boardwalk were both smoking as I jogged by. Granted with the rain they were unlikely to start a giant brush fire with a careless toss of a butt, I just knew that once the signs went up it wouldn’t be long before I saw people smoking. It’s like the signs actually make them smoke.

People are weird.

The next run will hopefully see my left foot better-behaved, with a corresponding better time to go with it.

Run cancelled on account of SkyTrain

On Thursday I began my commute home at 4 p.m. as usual with the plan to do my run before dinner, meaning I’d be heading out around 5:30 p.m. or so. I get home around 5:10 or so and need about twenty minutes to recover from the stupor that results from an hour of riding public transit.

Everything proceeded normally on the Canada Line, so-named because its route from downtown Vancouver to Richmond is just like crossing Canada if you turned the route east-west and added 4,000 km to it.

All proceeded normally on the Expo Line until my train began approaching the Royal Oak station. Sometimes during peak hours trains will stop outside stations because there are so many of them running and they need to give them a minimum safe distance between each other. This usually happens at the busier stop like Waterfront or Commercial-Broadway but it can theoretically happen anywhere so I didn’t take much notice of it.

Shortly after the train stopped the P.A. crackled to life. This immediately triggered my “Uh oh, what broke on the SkyTrain?” alarm.

As it turned out, it was a major computer failure affecting a great swath of the system: all of the Expo line east of Metrotown (Royal Oak being the first station east of Metrotown) right up to an including Braid station on the Millennium Line (Braid is one station past where I get off at Sapperton), as well as the Expo Line spur into Surrey. The fact that the first announcement used the word “major” was bad.

At this point I would normally be about 12 minutes from my final stop of Sapperton. It was a few minutes before 5 p.m.

SkyTrain no go
Like ships not passing in the night because ships need to be moving in order to pass.

Not too long after the initial announcement another came on advising people that this was a “long term” issue and to stay on the trains. Do people actually get out of the trains between stations when the system goes down? As it turns out, yes, they do. Because people are impatient and dumb.

More announcements followed, reiterating what had happened and emphasizing that we would be stuck for a long time and to not get out of the train because then they have to cut power to the whole system to avoid electrocuting idiots and that will only delay things further. No one left my car, fortunately, but some reacted less favorably to the delay than others, as you will see.

My inner English teacher was irritated by the repeated use of the phrase “long term” to describe the problem. Merriam-Webster defines long-term as “occurring over or involving a relatively long period of time“. An outage, even one lasting hours, doesn’t seem to qualify. I almost expected a follow-up announcement advising passengers that “Your train will be delayed for several days. We please ask that you do not leave your train or eat your fellow passengers. We are working to airdrop supplies including food and deodorant.”

About twenty minutes in we were told that workers would be manually bringing in trains to stations and it might take awhile, in case we hadn’t figured that out yet. Oh, and also please don’t leave the trains because we already told you and you’re not listening. It’s only been twenty minutes, people, it’s not quite time for The Lord of the Flies yet.”

Shortly after this announcement I noticed someone using the emergency phone at the other end of the car I was on. Most people on the train were quiet–possibly conserving energy to prepare for the upcoming battle over supplies–so I could hear what he was saying and what he was saying was that a woman was starting to hyperventilate. I looked but couldn’t tell who he was referring to and entertained the idea that he was fibbing to get our train bumped to the top of the “please get us to a station before Survivor starts at 8 o’ clock” list.

It worked! A minute or so later an announcement for our train only informed us that we would be taken back to Metrotown station where emergency services would be arriving. By this time I could see the woman in question and she did not look so good.

The train them hummed to life and rolled back into Metrotown station. Incredibly people tried to get on the train, even though it was going nowhere. This was half an hour into the shutdown and anyone still in a station knew what was happening. As I got off the car I saw the woman was now face-down on the floor. I hope she was okay. I think she was probably okay. She may be riding the bus for awhile after this.

Metrotown has one of the largest bus loops in the system and it was already a sea of people. I finally found the end of the line for the New Westminster bus, the closest that would get me sort of home. It took over 40 minutes for the line to move to where I was close enough to actually be guaranteed a spot on the next bus.

Some people apparently or conveniently could not find the end of the line and formed a blob of people beside the bus, effectively cutting in. This became apparent and after the bus pulled up it sat for minutes without letting anyone board. You could sense tension in the air, along with a lot of body odor. Some in line noted the others not in line and called out to them. One woman started calling out “Shame on you! Shame!” I felt like I was in a European film. A transit officer arrived and tried as diplomatically as possible to tell the blob of people that they were totally cheating and we’re onto you. Some moved back, some stood their ground.

A man in the blob called out, “You can’t even see where the line is! How are we supposed to find where it is?” Several others in the blob murmured agreement. I wondered how the hundreds of people already in the line managed what these people had not but chose not to express this thought out loud.

We were finally allowed to board. It was now 6:47 p.m. I managed to get a seat at the back. The bus driver noted construction on Kingsway (more delays? Sure, why not?) and asked people to be nice to each other and to the bus driver. He said someone pulled a knife on the previous trip. Because pulling a knife works wonders for reducing an already tense situation. The passengers on my bus were either knifeless or not inclined to flash their blades.

The worst thing I had to deal with was the sturdy man sitting next to me constantly falling asleep and slumping onto me. Did I mention he was sturdy? He was, especially when he slumped into me, which was often.

By the time the bus rolled into New Westminster station it was after 7:30 p.m. I would need to walk up the street to Columbia station and catch a bus there that would kind of sort of go through my neighborhood. I was tired and hungry and called my partner and made puppy dog eyes over the phone. I told him it would be way faster for him to pick me up than me taking another bus and we could eat sooner and aren’t you hungry? He agreed.

Shortly after leaving he called back to report an accident blocking the main route. I wouldn’t be surprised if the SkyTrain was somehow responsible. He took an alternate route, I walked a few blocks down and finally got in the door a few minutes past eight.

My commute took four hours, roughly four hours longer than normal. The CBC website has a brief, lazy write-up of the story here, the centerpiece of which is a bland complaint from Twitter. While the story is no great shakes, the comments are predictably even worse.

At least in this modern age we can all ignore the strangers we’re forced to hang out with thanks to technology. A massive failure of the transit system may be inconvenient but it’s no reason to stop checking Facebook on your smartphone instead of talking to the person squashed into the seat beside you on the bus. I confess, I played Threes on my iPhone for most of the bus ride. I’m part of the problem.

After finally having dinner it was, of course, far too late to do a run, the second time in less than a week that a highly unusual event has caused a run to be postponed. And hopefully the last for awhile.

Despite all this, the SkyTrain is still way nicer than riding the bus. When it actually works.

The three days off means you’re out of shape run

Run 331
Average pace: 5:13/km

Location: Burnaby Lake (CCW)
Ran Spruce and Conifer Loops and Piper Mill Trail
Distance: 5.03 km
Weather: Sunny, humid
Temp: 30ºC
Wind: nil to light
Calories burned: 387
Total distance to date: 2788

In which I run under mostly similar conditions with a three day break and manage to add six seconds to my average pace.

It was 30ºC for tonight’s delayed run and while the temperature was the same, it was much more humid. This was good news for my mouth and throat, which were not left feeling desert dry like Thursday’s run. On the other hand it was apparently bad for the run overall as my pace lagged enough to come in at a relatively slovenly pace of 5:13/km.

Apart from a few odd twinges from my left knee, nothing particularly stood out on the run. I slogged along at what I thought was a decent pace for the first few km but in fact the first km was a full ten seconds off compared to the previous run. I guess it really is the humidity.

The weather promises to be a few degrees cooler by the next run so hopefully I will find the eye of the tiger or some other important tiger-related organ by then.

Run cancelled on account of sun

Yesterday I bought a pair of fancy new Nike shorts for running because my current pair are starting to develop a kind of post-run lingering odor that even I’m not liking. I also bought a MEC t-shirt for running that is on sale and will get more if I deem it worthy.

I also–hold onto your hats–bought ankle socks, both for general use and for running. The latter even have a tiny bit of padding in the heel and the ball for extra support. I’ve never been excited about wearing socks before.

I was all set to try these multitude of new items today but the temperature rose so quickly in the morning that I had to cool my jets (ho ho) waiting for the temperature to peak and then start to decline in the afternoon, looking for that sweet spot to arrive where the heat would not be unbearable. I even spent some of this waiting time buying my first-ever hydration gear, a simple North Face belt and bottle. The belt is probably as close to minimal as you can get but still seems bulky to me. I toyed with just carrying the bottle in my hand. I wondered what I could do with duct tape.

I waited and watched as the temperature climbed to 35ºC (95ºF for those south of the border). This is not merely Africa hot, it’s too dang hot to even consider running. Much of the trail around Burnaby Lake is shaded but at 35 the air takes on an aspect that brings to mind a blast furnace.

And so it was that the rarest of things happened: I postponed a run because the weather was too nice.

It’s supposed to be a little cooler tomorrow. I shall try again then.

A pithy comment on the look of Office 2013

From Ars Technica reader jandrese:

For what it is worth, 2013 is also the ugliest version of Office ever. It looks like a web page where the style sheet failed to load.

This is an amusing and clever way of describing the whiteout approach Microsoft has used in the user interface for Office 2013. Rumour has it that we may see changes in the next version (for PC this will probably not be out for another year or more, though). I’m going to offer some of my own thoughts on UI design in iOS 7, Mac OS X, Windows 8 and a few miscellaneous others soon. In the meantime, have a look at the Ars Technica feature The software design trends that we love to hate. And you thought faux leather stitching was bad.

The so very warm, muggy but not really stinky run

Run 330
Average pace: 5:07/km

Location: Burnaby Lake (CCW)
Ran Spruce and Conifer Loops and Piper Mill Trail
Distance: 5.04 km
Weather: Sunny, hot
Temp: 30ºC
Wind: nil to light
Calories burned: 388
Total distance to date: 2783

Tonight’s run was basically a repeat of Tuesday, with the pace being an entire second faster at 5:07/km. The differences:

  • I ran counter-clockwise, so no stinky skunk cabbage. This was GOOD.
  • It was several degrees warmer at 30ºC. This was BAD.
  • It was less humid, which meant my throat and mouth were parched less than 1 KM in. This was BAD.
  • I felt less creaky starting out. This was GOOD.
  • The right shoelace came untied at .65 km in. This was VERY ANNOYING.

Overall I can say I was glad to get this one over with. At least if it’s still hot on the weekend I have a chance to choose a time when it is slightly less hot to run.