Keep It Simple, Part II

“It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience.”  Albert Einstein (1879-1955), during a lecture, Oxford, June 1933

Einstein’s goal of achieving simplicity without loss of the necessary holds true, especially for runners.  Figure out the amount of data you absolutely need to track progress, after that it's simple to gradually acquire the stuff which works best, or to steer clear of the stuff which won't work at all.

First, let me explain that I’m not slamming brick-and-mortar running specialty stores.  If given the choice between a major retail sports store, a locally-owned/operated running specialist and an interlink-based provider I'd much rather deal with the guy who's paying local property taxes and hiring passionate young men and women from my town's high school or local college; someone who really has some skin in the game when it comes to the running community.  Usually that's a person who's going to do the right thing.  But you can tell when a shopkeeper has become too-mercenary when (new) runners toe the line at a local 5-kilometer race with a four-bottle hydration waist belt.

I have a love-hate relationship with the consumer grade GPS receiver.  As a course measurer I love to use the GPS to provide ballpark estimations of where my intermediate splits will fall on the race course, and to get latitude/longitude references in those rare instances when no permanent reference point exists.  The hatred comes when runners who have no understanding of the necessary technological limitations of the GPS try to tell me a course is "too long."  Upload a run to Google Earth and you'll see some places you never thought you could run.  Runners who do most or all of their workouts on a treadmill or a track most likely aren't going to need GPS devices; there are times I would dare to say that for most a GPS is little more than a very expensive running watch.  I've also played with running watches which used accelerometers those little pods attach to the running shoe and track how fast and how far you ran, without the need for all those satellites.  They're a little expensive and the batteries tend to die at the wrong time, but they're very reliable if all you need is distance and speed.  If all your courses are known distances, choose a running watch or a heart rate monitor. 

Good ballpark distance figures for runs on sidewalks, roadways, and now even trails can be mapped out on map programs like MapMyRun, GMaps Pedometer, the USA Track and Field "My Running Routes" program, and Google Earth (which requires a little more patience).  There are a few disadvantages to these programs:  When flat photographs are used to try and measure distance on a rounded surface (our world) there can be varying degrees of inaccuracy; a half-marathon course I measured last year proved this to be true.  As a plus, MapMyRun allows runners to track workouts they've run on a particular route, and even gives runners the ability to print out courses...if you purchase a membership.  Go on the cheap like me and you best be able to read what can best be called “gibberish.”  A race director sent me his MMR files last year and all the street names were “Asflkue Ib.”  And worse.

You'd rather not wear a heart rate monitor, you say?  My wife is one of the many who would agree with you.  Some folks don't like to have that fabric/plastic strap around their chest, especially guys who like to run shirtless (I like data, therefore I run with a shirt).  Those persons who still want to check their intensity every so often can purchase a watch which has finger contact plates; place the two fingers of the non-watch wearing hand (of course…) on the plates and the heart rate reading appears in seconds.  Runners who use fairly modern treadmills with heart rate equipment attached can most likely forego this and use the handrail plates, which are about as accurate as chest strap monitors. 

You Luddites can lay a couple of fingers along your carotid artery on the left side of the neck immediately after the run is completed, or gauge your effort on a scale of one to ten, where one aligns to ”am I awake?” and ten means ”if I take another step my chest will explode!”  Some of the really good heart rate monitors will not only break down your workout effort by average heart rate, but by amount of time spent at a particular intensity level.  Entire books have been written about training by heart rate, and quickly leaves the beaten path to go into the weeds of the “should I use the ‘220-minus-age’ formula to calculate my heart rate?” question, the “male-versus-female max-heart-rate” debate (which my wife and I have had on many occasions), and so on.  Surprisingly enough, physiology researchers found a strong correlation between perceived effort (that “one-to-ten-scale” thing) and percentage of maximum heart rate; a perceived effort of “five” was found to be right around the fifty-percent of maximum heart rate point, and so on.

So now we've talked about the simple "where," "how far," and "how hard" of running.  I'll talk in the next installment on what to do with that information.

One Excuse Is As Good As Another

Even coaches suffer from demotivation, especially coaches who like bright, sunny mornings. I used to think seasonal affective disorder was a bunch of bologna until I spent an autumn in Chicago. September was great, the first half of October was pretty good. The last four weeks I spent in a deep blue funk, praying for sunshine that never seemed to come. So I guess that's one of the reasons I sat, grumbling, over a cup of coffee and a slice of toast with Nutella the other morning. Was I ready to go out and run with my wife and a couple of our friends? Not necessarily. The gray skies had me wishing for a pot of coffee and a thick book of mindless reading.

On top of this, my mood was not helped by the gentle, persistent ache in my ankles and feet. I raced a 10K the previous day. I commented about the previous day's exertions, saying something like "a tale of two 5Ks, one good and one bad." I ran the first half at my desired 10K pace, then realized my (5K) fitness did not transfer well to the (10K) distance. Rather than risk regression, or worse, reinjury, I shut down the effort on the return trip, adjusting the pace to a minute slower per mile.

Most "hobby joggers" (as some would judge by my performance) would be pleased with a 46-minute 10K. Most people (still) recovering from injuries would call it a good day. However, the ghost of race performances past can trouble the aging and rehabilitating runner. Really, I should be happy to be out on the roads and still running, right?

How many times do runners use a variety of excuses - some lame, others less so - to justify a performance that did not quite meet up to their expectations?

Some of the better excuses I like to hear sound a lot like these:

"I wore the wrong shoes." - In my humble opinion, one of the best and most valid. This excuse is more common with guys who keep half-a-dozen pair of running shoes, in varying states of life, around the house. I've put my singlet, extra socks, race belt, dry post-race clothes, and so on, in my bag the night before, left the house on the morning of the race with all my gear in my bag, but forgot the shoes in which I was going to race. So, I had to wear the pair of retired "kick-around" shoes which had no cushioning left. That's one of those 5Ks I wanted to get over with quickly; one that felt like it would take forever.

The only situation worse than to show up to the race with the wrong shoes is to show with no shoes.

"I wore too much clothing." - This is particularly true for less-experienced runners taking on longer-distance events. I've stood at marathon finish lines, five (or more) hours after the start, with temperatures twenty degrees above the optimum race day temperature. It scares me to see participants layered in tights and warm-up suits staggering toward the chute.

Less often heard is the converse; very few runners under-dress for the conditions. I'm one of those crazy persons who will race in a singlet, high-cut racing shorts, and a hat or gloves. This last weekend I used a pair of arm-warmers and felt good until the end...a little on the warm side because of the knit cap, though. And, strangely enough, there were at least two guys out shirtless in the 40-degree weather.

"It was too (hot/cold/windy/humid)." - Weather conditions happen. And in many cases, unless you're talking marathons, the entire field contends with identical factors. There's not much a runner can do, except train when and where the weather dictates. And don't forget to take advantage of tactics which involve the climate. There's no law that says you have to not draft behind a runner when you're traveling into the wind, right?

"I didn't hydrate/eat properly." In many ways runners are like charcoal grills. You can pile fuel for the burning and light a match, but sometimes, in order to burn fuel you have to have some tinder or an accelerant. Some runners can eat as little as a candy bar before a race; others have to hit the buffet table.

Then comes the issue of hydration, which can be screwed up in quantity or quality. Ask any runner who's had a "barley-based liquid dinner" the night before a race how they performed. Most - after a couple of aspirin - will tell you they would like to have had the previous evening as a "do-over." Beer has fewer carbohydrates than most of us care to admit.

"The course was too long/short." - I measure courses, so I hear this one more often than I care to admit. The fallacy behind this complaint lies in a couple of factors: First, the length discrepancy is most often described in terms of time, rather than in distance. Second, the persons who complain in terms of distance usually gauge it based upon a consumer-grade GPS receiver.

If I hear 'the course was (number) seconds long,' my hearing shuts off. If I hear 'my GPS said the course was...' I patiently explain to them the limitations of consumer-grade GPS receivers, the exact distance of the race course, and the protocols (often) used to measure. For thirty seconds. At which point their hearing shuts off.

"This was a training run." - This is not necessarily a bad excuse, in my opinion. At least, if you're a top-shelf runner in training for a big race somewhere down the line.

If you are in a situation where you pin a bib number on your shirt/top, or attach it to your race number belt, it's a race. I've always been of the opinion that one should not race unless one is race-ready.

Which is probably why I shouldn't have raced the other weekend. But sometimes we have to get out among our fellow runners and blow the carbon out of the exhaust pipes. Maybe the best thing we can do is be honest with ourselves and say, 'I'm out running, and whatever happens, happens.'

Certainly sounds a lot better than all the unsavory alternatives of not running, right?

Help Wanted

MB comment: A little something written for my friends in New Orleans. The Times-Picayune (www.nola.com) has a running section in the on-line version of the paper...blogs and all...have to love a city that loves running. Happy Chanukkah and Happy Christmas to you, also. See you guys soon.
Six times a year I receive phone calls from race directors. While they may not know it, the call’s an advertisement that sounds like:
“HELP WANTED – Fearless, anal-retentive, detail-oriented person/s to ensure running course accuracy. Skilled in problem-solving, math calculation, line-drawing, detail elaboration. Bike-handling skills & lack of fear a must. Track, cross-country or road running experience highly recommended. Must own bicycle, CPSC-certified helmet, & RRTC-approved measuring device – no GPS users! Must memorize simple mathematical calculations, exact metric & English course distances. Know capabilities & limitations of GPS/alternative measuring systems. Can communicate USA Track & Field definition of ‘accurate course’ to general public. Skin thickness, selective hearing, & love-of-travel, able to adapt courses at whim of race directors/police necessary. Compensation varies by difficulty of job, prior experience of applicant. Hours: Flexible; highly-dependent on auto traffic. Resume to (850) 867 5309.”
In Florida, there are over 30 of us listed with USA Track & Field (USATF) as course measurers. Some have been measuring courses for decades, others for a handful of years. We do it because we love the sport of running; we understand the need for accurate courses, & in many cases, because very few others will do the job.
When I tell people I am a runner I receive two questions immediately afterward: ‘Have you done a marathon? Have you done Boston?’ To do Boston, you have to qualify on a certified, accurate course. USATF, the national governing body for the sport of running, defines an accurate course as one that is NOT SHORT. It’s important to know the course you run on is not short; you need to know how well your training is progressing. You want to compare your race performance to others in your age group, another town, or around the country…even year-to-year in your town. If you think of a race director like the manager of a Subway shop, you want to make certain the five-dollar foot-long you paid five dollars for is really 12 inches in length. Any smaller would upset you, & you would go some place else to eat lunch. So, the race director wants you to come to their race rather than somewhere else. One good way to ensure this is by having a USATF-certified course.

Just because you get a USATF course measurer to measure your course doesn’t mean it’s certified by USATF. But having a USATF course measurer measure the course will ensure the job is done properly. The measurer does this by use of several tools and a simple protocol.
The first tool is a bicycle with a counter mounted to the front wheel hub, which provides a fixed count for each turn of the front wheel. The earliest model of counter is accurate to within three inches, more accurate than the GPS receivers used by fitness enthusiasts. The measurer does a series of calibration rides to determine the number of counts (turns of the wheel) per miles/kilometers. These rides are performed on a calibration course, measured out using spring tension & steel surveyor’s tape; most measurers have one or more calibration courses in their area.
Once the count (wheel revolutions) per mile/kilometer is determined, the measurer adds a 1/1000 factor to the count to help prevent a course from being shorter than the actual distance. So, a ten-kilometer (6.213172 miles exactly) run, such as the Crescent City Classic, is actually closer to 6.219925712 miles in distance.
The measurer, once on the course, begins to act like a runner. They ride the shortest possible distance from start to finish; riding 12-inch tangents on curved sections of the course. If runners are going to be restricted from part of the road, these are noted. Distance splits are made at multiples of each count per mile/kilometer, marked (temporarily) & noted relative to fixed points. The counts at the finish are also noted. During a second ride of the course, the count from start to split points & finish are noted again.
The total counts between the first & second rides are divided to ensure the difference between the two rides is no more than .08 percent (26 feet, 4 inches for a 10-kilometer race). Once the course rides are complete, the measurer returns to the calibration course to repeat the calibration done before the measurement rides. The calibration rides before & after the measurement are compared, with the smaller count used to measure course length. The smaller count per mile/kilometer is used to compare the shortest course measurement to the desired distance. If the course distance varies from the desired distance, the measurer adds or subtracts distance – if necessary – to make the course distance accurate.
The measurer then draws up the map, showing detailed location of start, turn points, and finish. Each of the distance splits are noted, as well as places where runners are restricted by cones or barriers. This map, the calibration form, the measurement form, & an application for course certification is sent to the USATF state course certifier, along with a check (in FL, it’s $30). The certifier reviews the paperwork, certifies the measurement met USATF protocols (sometimes after asking for more data), then prepares the certificate. The certificate number & map is placed in the USATF course database, where it can be found by the general public. The race director is asked to place the certificate number on all documents related to their event, both before & after the event. Course distances are valid for ten years from the date of certification, after which the course needs to be measured again & submitted to the certifier.
So, racing on accurate certified courses benefits the individual athlete because they can truly compare their performance to other days or other persons. Accurate certified courses benefit the race director because it’s another proof to market to potential customers of their event’s quality. In fact, USATF and Road Runners Club of America championship races are required to be held on certified courses. So, think twice before you take that GPS receiver-wearing runner’s opinion of the course measurement as gospel – look it up on the USATF web site. If it isn’t there, it isn’t accurate.

Hammer Time!

Tempo run of seven miles yesterday at the beach. The group - which includes most of our team officers, several of our active membership, and not a few of our former members (who I graciously classify on my nicer days as alumni) meets every Wednesday evening at 6:00 to run anywhere from four to six miles, then eat, drink and be merry until they can't stand it any longer...or the management kicks them out.

I've used the treadmill for the majority of the summer because it has been too d@mned hot to get any quality mileage in otherwise...at least while I was healthy enough to run (so maybe there was a good side to breaking my arm!). Two weeks ago I went to the beach to do a six-mile tempo and completely exploded in a blaze of glory at the three-mile point. BRAAP! Back to the treadmill for a couple of more weeks, Coach Mike. I bumped up the pace on the treadmill runs to ~6:44/mile, taking a three-minute cool-down cycle between each mile. Then, I decided to extend the tempo repeat from 1 mile to 1.2 miles, so I got the mileage in five pieces, vice six. That's three less minutes of easier running/jogging/walking, too.

We were talking about the beach loop the other night, and Scott, my assistant and club secretary mentions something in passing about the six-mile loop being only 5.8 miles. I almost asked him, 'says who?' We've never really measured a course out there, and I have little love for GPS wearers and their complete dogmatic trust (dependence?) on that gadget. I have to admit I'm not as violently opposed to them as I was in the past, and I would use one if it were given to me (Note to my loving wife: no, I really do not need a GPS, not unless it does the street navigation, too.) by a company wanting someone to wear-test. Dude, if there's anyone who can destroy a piece of technology with just casual, everyday use, it's me. Ask Nike; that's why they are no longer in the MP3 player market.

I probably could have used one last night, though, to run the tempo run. I have a good idea where the two-mile point on the course is located, so I figured what I would need to add on in time duration (ten minutes) to lengthen the 5.8 mile loop run into a 7-mile tempo run. Hammer ten more minutes (five out, five back), on top of what I guessed would be a 40-to-41-minute run normally and voila! Done.

Well, I went out at a comfortable (7 minute/mile) pace for the first two miles. Who knew I would pick up the pace that much after two? Who knew I would race the sun coming back? Who knew I'd run 49:34 for 7.8 miles!? That's a little bit fast (ya think, Coach?) for a tempo run. That's about 20 seconds faster than my average pace for a half marathon.

However, I tend to run on feel, not on gauges. When I had a Suunto POD and heart rate monitor, I spent a lot of time looking at the data rather than running more by feel. That's the liberty of going by physiological markers, especially after you've done enough training. Translates well into racing and you don't have to worry about if or when the technology bites the big one (like the Suunto did)...Murphy's Law...and it goes wrong after you become dependent on the technology.

Working that hard makes it interesting the morning after, especially if you're doing any kind of cross-training or you have a real daytime job. When our organization provided employees the option of working flexible work schedules; the kind where you do your 40 hours of weekly work over the course of four days, or your 80 hours of a pay period over the course of nine, I decided immediately it was not for me. Sorry, boss. I'm a creature of habit, and I coach. I have places to be in the early afternoon, and I like having not to worry about taking two hours of annual leave in conjunction with a federal holiday.

Besides, I'd rather do 80 percent of the something my boss and my other 'eight days a pay period' co-workers are doing each day.