May 20, 2010
Raw STS-132 Launch Audio
During the #NASATweetup and launch of Space Shuttle Atlantis for STS-132, I left my netbook recording audio in the twent (about 3 miles from Pad 39A). Here's the raw, unedited audio from the launch including the hum of the big A/C units and the PA audio commentating on the launch proceedings. Zero time is right around 17:25 File type is .ogg. File size is 22.3 MB: right-click to save file: Launch.ogg.
Enjoy. MUCH more to come.
May 06, 2010
2010 Illinois Marathon
Note, if you'd like to comment, and you're a member, you can comment over at Daily Mile.The 2010 Illinois Marathon from My Perspective in Excruciating Detail
The Nitty Gritty:
(These numbers have been fluctuating - results are not official at time of writing.)General:
Number registered: ~2420Number of Females: 635
Number of Males: 1,173
Average Time: 4:31:35
My Stats:
(Pretty sure these placements, though not the times, all represent Personal Bests)
Overall place: 538 out of 1813 29.62%Division place: 73 out of 171 42.69%
Gender place: 430 out of 1176 36.56%
Chip Time: 4:06:07
Average Pace: 9:24
Official Splits:
10K: 56:23:00
13.1M: 2:00:06
20M: 3:05:58
The Good:
No injury.
The Bad:
Couldn't sub-4 despite overwhelming training and confidence.
The Ugly:
22 ER trips during the event (luckily no one from our group).
Pre-race:
Mile By Mile:
(For a given mile, the text and pace describes the events leading up to that number mile marker. It gets confusing in my head around the middle of the race, so I might be off one way or the other, but I think I've got it sorted. Also note that paces were tweaked in a few cases were I was late to press the Lap button at a mile marker so numbers might not strictly add up.)Mile 0
Mile 1 - 9:01/0:09:01
Mile 2 - 9:01/0:18:02
Mile 3 - 9:02/0:27:11
Mile 4 - 9:03/0:36:15
Mile 5 - 9:05/0:45:21
Mile 6 - 9:10/0:54:31
Mile 7 - 9:30/1:04:02
Mile 8 - 9:00/1:13:02
Mile 9 - 9:02/1:22:04
Mile 10 - 9:34/1:31:38
Mile 11 - 9:05/1:40:44
Mile 12 - 9:16/1:50:03
Mile 13 - 9:07/1:59:10
Mile 13.1 - 9:02/2:00:06
Mile 14 - 9:21/2:08:32
I distracted myself from this grim potential by realizing, "Around here is where I High-5'ed Elvis last year. I wish he was here." Not only had I slapped skin with an Elvis at Illinois last year, but in the Chicago Marathon as well at the Fleet Feet water station. I NEEDED an Elvis 5 if I was going to get out of this race alive, right? Where was Elvis? Just as that thought cleared my head, I heard the tunes. I can't tell you which song was on, but it was Elvis, and it was ending, and there I saw The King, walking away from the course to go futz with his P.A./music player. I yelled across the wide street, "Elvis, come back!" but a High-5 from Elvis was not in my cards on that day. One of the course workers said, "Elvis has NOT left the building, he'll be back." I replied, dejected, "Yeah, but I won't." As I crested the next slight rise which put that corner behind me, I could hear the next song starting up, but it was too late. Love me tender, indeed. My pace was slipping again.
Mile 15 - 9:17/2:17:49
Mile 16 - 9:24/2:27:14
In talking about the number of marathons we'd each run, I mentioned that my wife was also running, her first, hopefully just a few short miles behind us. Though I'd thought about her earlier, this was the first time it really sunk in what an awful first marathon experience this was for her. I wanted nothing more at the moment than to have some way to communicate to her that, no, this was NOT normal, and that her time goals for the race should be projected downward a bit, and NOT to beat herself up about slipping paces. I wanted so much to be able to run with her at that moment. I gave a half a thought to stopping and waiting for her, but I instantly knew that would do nothing but piss her off. She's a fiercely independent person. And she's smart, too. I realized she'd figure it out on her own, but I still wanted to be able to support her.
In my continuing conversation with #9, I suddenly made a foolish statement - much like the "WTF?!?" gasp I'd let out in the car on the way to the race. I glanced at my watch and I confidently said, "Yeah, it's been way tougher going than I expected, but luckily I'm at a heart rate that I can run pretty much all day." Talk about opening your mouth to insert your foot . . .. A minute later, if that, I suddenly became aware that the 'pound of pollen' feeling in my chest from earlier had joined with my upset stomach to form a new, very disconcerting pain in my torso region. I'm being VERY careful not to call it a "chest pain," but I was suddenly quite concerned about my overall condition and quickly weighing my options. In all honesty, had there been a medical tent or mobile medic RIGHT THERE, I may have pulled the plug and stopped running. I may have sat right down and DNF'd. In the previous 15 minutes, it seemed, things had just started falling apart again. I regained my composure and remembered that if I was fearing heart problems, it might be wise to use the technology on my wrist and take a look at what my heart rate was doing right at that moment. I checked my Garmin, and it was still at the same or similar rate it had been a few minutes earlier - nothing notably high NOR low. So I decided to back my pace down and see if things cleared up. The "nuisance" in my chest subsided a bit. I sped up and slowed down a few times and it came and went with no real pattern. I don't know if it was heart burn, irritation in my lungs, or god knows what, but I was soon convinced I was not having a heart attack. Not long after that, I got a much-needed distraction when I met Josh at a water station. Again, it was good to see a buddy. I completely forgot about the episode for the rest of the race, only recalling it afterward. With all of that going on, I remembered my next Shot Bloks a little late. They, of course, did nothing to help my stomach settle.
Mile 17 9:36/2:36:50
Now, I want to be clear on something. Finish times are highly personal and no matter who you are, YOUR slow is another runner's fast, and your fast is another runner's warm-up pace. By many standards, a 4:10 marathon is nothing to be ashamed of. But let's face it - I didn't train for 16 solid weeks, harder, more consistently, and at faster paces than ever so I could run slower. I had run in 9 degree weather. Not 9 degree wind chills, 9 degree raw temps. I didn't even bother to look at the wind chills that day because every bit of skin was covered, and I ran. I completed a 15-miler on an ankle I had twisted in the first mile as I ran in the dark so that I could get the run in before going to Easter Mass with my family, and I didn't miss a workout as I recovered from it. I had literally run in rain, sleet, and snow since January to get my miles in. I had done long runs the day before snowboarding for 6-8 hours straight. I had run and then shoveled, by hand, at least a hundred driveways at work. All tolled, I had missed a minute handful of miles on my 16 week plan and I can pretty well justify each of those missed runs with illness, cross-training, or in rare cases, just running out of time. Hell, I'd even run on the dreadmill once or twice, which I HATE. I had come to town to, at best, PR and bump up a corral for Chicago, at worst, pace a friend or two to a 3:59:59. Yet here I was facing the very likely possibility of a 4:10 finish for a 2 minute personal worst, or even a DNF.
Even after doing the math, I wasn't ready to accept reality and I kept checking my time against my pace card. Just as I wrapped up a SLOW Mile 17, I dropped the card trying to put it back in my pocket. I stopped and doubled back a few steps to pick it up and apologized to two runners who had to avoid me. The girl said, "No problem. What was that, anyway?" I said, "My pace card." She said, "Oh, that's important." I said, "Yeah, I need it so I know exactly how fast I'm NOT going." I said it as a joke, but there as definitely some bitterness to it. I marched on. 9:36. In training, I had to FORCE myself to run this slow on long runs.
Mile 18 - 9:25/2:46:16
Mile 19 - 9:36/2:55:52
Mile 20 - 10:10/3:06:03
Mile 21 - 10:13/3:16:16
Mile 22 - 9:47/3:26:04
Mile 23 - 10:09/3:36:13
Mile 24 - 10:17/3:46:30
Late this mile, I saw something I didn't think I'd see until the finish line - Sarah's light blue running top and red hair bobbing along ahead of me. She had been running so strong, it bummed me out to see I was gaining on her. I eventually caught up to her and tapped her on the shoulder. She paused her iPod, we both slowed to a walk and she asked something like "Is it just me or does this suck?" I told her it was brutal. Brutal was the word that had come into my head earlier and it was the word which most seemed to fit the conditions and the looks on peoples faces. I told her that everyone I saw was having a hard time. That good, strong runners, people with 3:30 goals pinned to their backs, were crashing and burning. This was oddly consoling to her (I found out later) and may have been the first time I, myself, fully appreciated that I wasn't in this alone as far as missing goals. I told her that this next stretch - the Country Club Hill - was my nemesis, and that I was going to beat it, if nothing else. Or maybe I just said that in my head and expected my nod to convey that. But we exchanged something of an 'alright, gotta go,' and I set to running again. I expected her to pick up and run with me since she had been running so strong all day (I had referred to her as a running machine a few times), but I don't know if she did. This was my slowest mile. The long dark teatime of the soul.
Mile 25 - 9:08/3:55:38
At that point, I was finally starting to see some light at the end of the tunnel. Part of it was that I saw that, after 10 miles of him being out of sight, I was catching up to good ol' #9. He seemed a good, strong, even runner and the fact that I was catching him encouraged me. I don't know if he made his goal of not stopping, but all the times I saw him, he was running steady, so I hope he did. The other part of it was that my foggy brain was able to work out some math and I figured out that if I could keep up what I was doing, IF I could kick a little at the end, then I could actually salvage a course PR out of the day. 4:10 was well in hand, finally, and matching or bettering last year's 4:08 was a distinct possibility. 3:59 was out the window, but at least this was something. From that point on, things started happening really fast. Soon after I made the turn from Armory to Prospect, I caught #9. As I pulled up next to him, I said, "How's it going?" or something like that. He said, "Hey!" as he recognized me and then as I sailed past followed up with an enthusiastic, "Go get it!" I was on my way. I don't think I did it any justice, but it was a great exchange between two brief but close friends.
Just after I passed him, I came upon a house blasting "Daylight," by Matt and Kim. I've always liked that song, but on that day, at that moment, it was a lightning bolt of adrenaline directly from the base of my brain down my spine into my nether regions. As I ran by, I threw up rock horns, and bobbed my hand to the music. The college-age kids playing cornhole in the front yard started cheering for me and GAME WAS ON!
My time at this mile post (3:55) was pretty much when I'd dreamed of crossing the finish line. I came up exactly 1.2 miles short. But that wasn't on my mind at the time. At the time, my 'win' was beating 4:08. 9:08 pace? Where had you been?!?!?
Mile 26 - 8:45/4:04:24
I was running pretty hard for the last full mile, but I still had some reserve to interact with the crowd and other runners. In the penultimate stretch, on Stadium Drive, I came across a 20-something guy who slowed into a walk just in front of me. I tried to encourage him on the way by, "Come on, you've GOT THIS! You're SO CLOSE!" He grunted and stepped back into a jog - I don't know for how long, but I'm glad if I motivated him a little. On the ACTUAL home stretch, down 1st Street, I saw a woman who looked to be in her 50s, Linda, according to her pace tag, slow up to a walk as well. A guy who had been running with her tried to encourage her along. She told him to go on, she'd be right behind. I gave her a "Come on, Linda, you got it!" and she smiled back at me. Just beyond her, right at the Mile 26 stick with about a block and a half to the stadium entrance, I saw an older man go down on the parkway. When I got up to him, he was clutching a calf cramp, but otherwise seemed OK. I waved to the marshal at the next corner and she mobilized some bicycle medics. As they rode past, I let them know he was cramping. Poor dude - so close. I hope he was able to get up and finish. An 8:45 mile - whoa. Didn't think I'd see one of those that day.
Mile 26.2 - 7:40/4:06:07
Though not my strongest .2 miles ever, I made my way into the stadium and heard the cheering. I made the final dash down to the 50-yard finish line on the edge of my oxygen capacity, my whole back on the verge of completely knotting up, and my legs trying their hardest to out-kick the frat-boy relay team who had just mobbed past me. I couldn't quite do it, but I gave it everything at the end. 7:40 pace in the last .2 of a tough marathon? Respectable. Damned respectable. As I crossed the finish line I saw "4:09" on the clock. We had started 3 minutes behind the gun, so I knew I had around a 4:06 finish - 2 minutes better than last year. I was gasping like a fish out of water as a girl put a medal around my neck. I walked over to one of the scaffolds they had set up for the photographers, still gasping, and leaned against it to stretch my back out and keep a full-on cramp at bay. As I was cooling down, I pieced together from the PA announcer a bit of what a lot of the cheering was about as I crossed the finish line. Not surprisingly, it wasn't for me. A guy had proposed to his girlfriend after they both finished the race. Perhaps I'm in some of their engagement photos, with my shirt half off like some Fame reject. ;) I slowed my breathing down a bit and finally remembered to stop my watch.
I walked back across the finisher's chute, grabbed a bottle of water, then went to go stand and wait for my fellow runners at the finish line. Despite my thoughts while in the throes of the race, I did NOT have a breakdown at the end. I was NOT disappointed with my finish. As I would later say about it, it was ugly, but I was proud.
Note, if you'd like to comment, and you're a member, you can comment over at Daily Mile.
March 17, 2010
Get yer Yassos off!
INTRO
As usual, I'm no expert, but I've done a few sets of these Yasso800s now, so here's what I've learned from experience and these links. If you don't know anything about Yasso800s or why you'd want to subject yourself to them, visit those links. This is not intended as a primer on Yasso800s. This is just one guy with a Garmin Forerunner GPS watch explaining to another guy with a Gamin Forerunner GPS watch how he goes about running these.My take on a Garmin Forerunner/Training Center workout is here (right-click and save-as): Oblivs_Yasso800_workout.tcx
If you'd like to see what the splits of this workout look like, here is an example on RunSaturday.
PREMISE:
Your 800m target = your marathon goal as minutes. For a 4 hour marathon, you get 4 minutes to run 800m and 4 minutes to recover (more detail below, but in my experience about 400m). Build up until you can do 10 sets at a certain pace, and theoretically you can run a marathon in that time.GOTCHA
Since the 800 is roughly a half mile, the PACE is going to be double that - or in this case 8:00/mi. I KNOW that's stupidly obvious, but it's easy to get confused going between race hours, interval minutes and pace per mile. The sanity check on the 800m PACE is that at our speeds, it's going to be around 1 minute per mile FASTER than marathon pace. MP ~ 9:00/mi., 800 Pace ~ 8:00/mi. NOT 4:00/mi. :DMY TRAINING CENTER FILE:
The Warm-up and Recoveries are open-ended so you hit the Lap button to complete them. I did this so I'm sure I'm in a good spot on my road to kick off the next set since I don't do them on a track. You could optionally automate the starts.Goals (WarmUp/CoolDown distance, target pace) are in the "Custom Name" for each leg. They are only guidelines, of course, and do not affect the execution of the workout.
Take a look at the "Targets" for the steps. Setting HR zones for the WU/CD/Recoveries sounds like a good idea to me, but in practice is pretty useless. For the actual 800s (well, half miles), I have a Speed Zone defined as "Yasso800." You can set this in your user profile, or you can remove the "Specific Target" for this step. All it really does is chirp at you if you're too fast or too slow - which neither of us can hear anyway. FYI, I have a 10 second cushion on both sides of my target, so that speed zone is 7:40-7:20 (for a 3:45 marathon goal).
THE WATCH:
I think my IDEAL screen setup would be:
LAP AVG
lap dist | inst. pace
That said, my current is:
LAP AVG
lap time | lap dist.
It's workable, but knowing my instant pace (to know if I was WAY too fast or
flagging) would be better for me. You kind of get to know the pace, but
fatigue makes all cloudy by the 5th or 6th one. The lap time IS useful
on the recovery lap, so I may stick with this layout after all. I don't
want to be switching screens per leg. Let me know what works for you.If you use the 'workout screen' and you have set the pace target, that might be good enough, but 'In desired Zone' is too vague for me.
REMEMBER to press Lap when you kick off for your sets. Again, the 800 is auto-lapped, but the warm-up and recoveries are manually advanced.
THE 800 (or Half Mile):
Don't get lulled into a false sense of security. The first 2-3 won't seem so bad, in fact you may be tempted to push your recovery cycle a little short. You can do that if you're stupid. ;) It doesn't matter much, actually, because even with full recoveries, it won't take but a few sets to get into oxygen debt. THAT is where the workout really starts and you'll have to keep a close eye on your pace to make sure you hit it. I get into full-on huff and chuff mode to finish each 800 after the first couple. If you don't want to puke, you're doing it wrong and may need to adjust your marathon goal pace.Pace will yo-yo a bit - again, especially if not on a track. Over such a short distance, it might not be so bad to go out a little quick and bank some time for when you start sucking wind. I've played these both ways, and I've got to say THAT way is a touch easier than trying to dig out of debt at the end. No negative splits here! That's how I missed #5 today - I started conservative, got behind and could not catch up.
THE RECOVERY:
Strictly speaking (The Word According to Yasso), you have as much time as the interval took. E.g. A 3:45 interval at 7:30/mi pace means you also get 3:45 for your recovery jog. Some have refined that to allow a max of 2-3 minutes recovery arguing that any longer is too much rest. _I_ think THOSE people are full of shit. :D Whichever school of masochism you choose to follow, take all of the recovery time it allows (see above re: sucking wind).THE COOL DOWN:
The Runners World marathon plan I use calls for 2 miles each, warm-up and cool-down. I think this is the first time I've stuck to that (or very close), and though I had to walk a few times on the way home (I mostly jogged (10:00/mi +/- :15)) my legs are feeling GREAT now, so I believe there's real benefit in those miles. I don't know if they squeeze out the lactic acid or what, but I'm a believer.ENJOY:
If I know you, you'll learn to love to hate these. Remember, they're not so much intended as a workout themselves, but more of a 'test' of where you are and what you're capable of. Given that, it's OK to 'fail.' Up until the last set of 10, anyway. :DHTH. Ask questions: oblivion at ratula dot net.
March 12, 2010
Green Day
This has been circulating the internet seasonally for several years. It seems to be getting harder to find with each passing year (copyright take-downs?), so I captured it and shall reproduce it here until I can't. I don't know if it's actually from Denis Leary, but it's damned funny. Enjoy.
"Green Day" by Denis Leary:
First things first: There are many Irish-Americans in this country who celebrate St. Patrick's Day in a quiet and sober manner, perhaps heading off to work with a muted-olive tie or a small emerald pin as their nod to the day's events. There are also those who go to the 7 a.m. mass at St. Patrick's Cathedral and consider the day a prayerful tribute to the patron saint of all things green. There are still others who awaken the morning of March 17 and carry on as if it were just another 24 hours— no drinking, no fighting, no puking.
I don't know any of these people.
Therefore, this piece will be about the red-blooded, hard-boiled, hammerheaded souls who patrol the St. Patrick's Day arena as if it were life's last call.
If you consider the image of a working-class Mick named Fitzy caterwauling down Fifth Avenue wearing a kelly-green plastic derby, well oiled on whiskey and slurring his words, an offensive and demeaning stereotype, then call the Irish Anti-Defamation League (IDLE) right now. I think the number is 1-800-NO-FITZY.
I've spent several hundred official and unofficial St. Patrick's Day celebrations in New York City over the years, and the calm, bespectacled intellectual Irishman clutching his copy of
Finnegan's Wake
is a rare sight indeed. Unless he's passed out around 3:15 a.m. in the back booth at McQuigan's Pub.
No, March 17 is not for the squeamish. It's for the thirsty masses. Those young rebels willing to shout and scream about their Irish blood, the chosen few who will toss raw eggs into open cab windows, the banshees who only want (as House of Pain so eloquently put it) to "get off their feet and jump around." That's what St. Patrick's Day is all about. Doing incredibly stupid things while under the influence of alcohol and wearing neon-green clothing.
Herewith, a guide to spending the day in the Big Apple. This is what I'll probably be doing this year.
9:00 a.m.
Meet best friend Sully at Greek diner for traditional Irish-American breakfast of wet toast, runny eggs, cold home fries, bitter black coffee, three cigarettes, and the sports page. Curse the Knicks. Marvel at Pat Riley's hair.
9:30 a.m.
Corner of Ninth and 39th. Ring Fitzy's buzzer 23 times. On the twenty-fourth try, he buzzes us up. Find him naked on the living-room floor surrounded by empty Bud Tall Boys and an open can of paint. His entire body, including his hair, is green.
10:00 a.m.
Arrive at the corner of 51st and Fifth and take our places for the parade. Sully steals three cans of Molson out of some Italian guy's cooler. Fitzy tosses a half-eaten green hot dog into the middle of the Staten Island Marching Men's Choir.
10:14 a.m.
Fitzy gives Mayor Giuliani the finger. Mayor waves back. "****in' typical," Sully says. Fitzy steals three more beers from the Italian guy.
11:05 a.m.
The Francis Mulcahy School of Irish Step Dancing pauses right in front of us and runs through a rigamarole of jigs and reels. Fitzy bops out into the street and joins them by doing a variation on the twist. Two cops promptly escort him back to the curb. Ends up one of them (Blaney) is Sully's second cousin. All charges dropped. I steal a few more beers out of the cooler. We toast the NYPD.
12:02 p.m.
The Italian guy accuses us of raiding his stash. Waves his fists in the air. Sully punches him on the neck. Fitzy pulls out a lighter and starts to melt the cooler. Two more cops show up. So happens, one of them (O'Keefe) is Fitzy's dad's old neighbor from Brooklyn. Tells the Italian guy to "Move it along, pal, this ain't Columbus Day." Brawl breaks out between Irish and Italian bystanders. We throw several punches, grab the cooler, and split.
12:06 p.m.
Drop into St. Patrick's Cathedral for a quick gander at the Lord. Crack
open a couple of beers. Sully and I debate the merits of a short confession. Sully's argument -- "In a half hour, at the bar at Paddy Reilly's it's gonna be standin'-room only" -- wins out over mine, which involves Eternal Damnation. We opt for a fast Our Father, five bucks in the poor box, and a brief round of candle-lighting. Fitzy, meanwhile, steals a sip of Holy Water.
12:17 p.m.
In the cab downtown, our driver, one Adjid Sakeel, expresses his opinion that the Irish Lesbian and Gay Organization should be allowed to march in the parade. Fitzy -- his large green mug plugged right into the pay slot -- begs to differ: "They awready got their own parade downtown inna Village. We don't go down there, so why should they come uptown ta ours?" Adjid says, "Because this is America."
"No it ain't," counters Fitzy. "This is New York City. It's a whole different ball game." The argument ends with Fitzy barking like a dog and Adjid veering all over Second Avenue. We get out at 29th Street. I give Adjid a $3 tip and the cooler.
12:22 p.m.
Stop in at Paddy Reilly's for a few pops. Several rounds of green beer and whiskey. Rogues March -- a local band made up of guys who used to know members of the Pogues -- bash through a loud, boisterous show. The lead singer -- Joe Hurley -- stretches his voice to the point of aneurysm. We toast the IRA. We toast the cease-fire. We toast the pope. Fitzy pukes.
4:27 p.m.
Stop in at Molly Malone's Pub for a few more pops. Eat several slices of green pizza made by Sweeney the bartender's wife. She's Italian. We drink green champagne and vodka. Sweeney calls JFK the greatest man who ever lived. Fitzy calls Mario Cuomo a fag. Mrs. Sweeney kicks Fitzy. Sully pukes.
About a Quarter Past Eight
Over at the Emerald Inn, we drink green Guinness and recite dialogue from The Quiet Man verbatim. The Stogues -- a local band made up of guys who used to know the mother of one of the guys in the Pogues -- play "Danny Boy," and Fitzy starts to cry, green tears streaming down his puffy green cheeks. As Sully and I pat Fitzy on the back, the lead singer passes out.
Sometime After Ten
Head over to a Blarney Stone, where we order a drink called the Shane
MacGowan -- three ounces of vodka, four ounces of gin, six ounces of Irish whiskey, a teaspoon of something that smells like turpentine, and half a beer. You gotta down it in two slugs. Makes you spout poetic musings with a tongue so thick only Shane could understand. The problem is -- he ain't here. Fitzy stuffs an entire green bagel in his mouth, swallows it almost whole, downs his MacGowan, and says, "Now this is the life!"
That Same Night
Stop in at Siné. Place holds only 75 people, 72 of whom look like they just stepped off the boat. People without green cards drinking green beer. We're in time to see another local band (really local, since they live in the cellar) take the stage. Call themselves the Fogues. Made up of guys who used to be friends with guys who once bought a round for the guys who used to roadie for the Stogues. During "Thousands Are Sailing," the guitar player leaps up into the air and stays there. For what seems like a long time. His head is stuck in the ceiling; he gets a standing ovation. The lead singer asks if there's a carpenter in the house. There is. Thirty-three of them, to be exact.
Later
The fact that we're in the Dublin House is news to all three of us. But it's printed right there on the matches. And the wall. And the back of the bouncer's T-shirt. As my old man used to say: "Wherever the hell you go, there you ****in' are."
Later Still
The thing about painting yourself green is this: It's a great symbolic way to show your support of the Old Country and your family tree, but it's a terrible way to go out drinking. Mostly because your friends can't tell when you're about to puke. The point is, we didn't see it coming when Fitzy leaned over an Englishman named Trevor -- who was explaining his support of the peace process in Ireland -- and let blow. The hot dog, the pizza, the bagel -- they made a comeback even Travolta woulda been proud of. And set off a brawl the likes of which we may never see again. Seventeen Englishmen, 27 Micks, and a side order of Hispanic, African-American, and Polish guys. When the cops show up (Carelli, Tiveiros, Jackson, etc.) none of them is related to Fitzy or Sully, so they just pack the whole melting pot in the back of a couple of paddy wagons (just for the sake of historical irony, I guess) and drop us off downtown. I share a cell with Fitzy and a Puerto Rican plumber named Bob
. He says the cell gives him "déjà-vu" because he had the same one after the Puerto Rican Day Parade last year.
The Next Morning
I wake up to the sound of Mickey Mantle repeatedly pounding a Louisville Slugger across the side of my face. I make a count of my few remaining brain cells -- eight and holding. Bob's droning on about pipe wrenches and putty knives when they come to take us to court. Ends up the judge (McSwiggin) is not only a fifth cousin of Fitzy's mom but also happened to be in Dublin House last night when the hot dog hit the fan. He thinks the Englishman, the queen, and the United Kingdom had it coming. All charges dropped. (That should be the motto above the entrance to the Irish Embassy.) We tell the judge about Sully, and fifteen minutes later, me, Sully, Fitzy, and Bob are sitting in P.J. Clarke's chugging Bloody Marys and discussing the merits of indoor plumbing -- copper pipe vs. plastic. Fitzy says he likes plastic: "It's more modern. And it don't look shiny." Sully and I make up our minds. Bob -- turning a light shade of burnt sienna -- pukes.
GPX to CRS - Setting a Course in your Forerunner
A plan was hatched to meet up with a fellow runner who needs to pound out 18 miles this weekend, like myself. The idea came up to preview the Wisconsin Marathon course in Kenosha, since he'll be running it as his first marathon in a few weeks (5/1 - go cheer! I'll be down in Champaign). It turned out that the marathon route was nicely posted on MapMyRun.com. It's a complicated route neither of us have run before. Since we both have Garmin Forerunner GPS running watches, we figured we'd let them be our guide, and rather than try to re-map it by hand whittled down to 18 miles, I decided to try futzing with the downloads available. They provide the option to download as a Garmin .crs file, but since I wanted to edit the route, I opted for the more universal .gpx file.
One note on Garmin Forerunner Courses, I have NOT used Courses a lot. About a year ago, I built a Course similarly for a 20-or-so-miler once, and the watch got VERY picky about hitting the points, going off-course, and not advancing properly through the points. I BELIEVE this was a flaw in my source Course - I'd made it too sloppily (not following slight bends in mostly straight roads, not putting in enough points around arcs, etc. Keep this in mind when editing/building a source track, and don't use it for life-or-death navigation until you test it out and see how it works FOR YOU.
Continuing on, I opened the .gpx in a handy old program I have called ExpertGPS from TopoGrafix. It's not the prettiest program out there, but if you look at my old flying tracklogs, it's a workhorse when it comes to GPS data. Other than address-based routing, I've always preferred it for to the Garmin-specific software for working with Waypoints and Tracks.
As I said, the marathon route itself is very complex. It turns back on itself several times, so cutting out that redundancy (with the zoom and scissor tools) got me down to about 20 miles. One thing ExpertGPS wonderfully is that it easily reverses tracks and joins two together. So I cut out the repeat areas, deleted as needed, and then re-joined the resultant fragments into one track. To lose the the extra two miles, I busted out the scissors again and just started snipping off bits of the northern out-and-back section until I was near 18 miles - re-joining the main parts again when done.
One final tweak I did was to adjust the start and finish location to be less ceremonial (on a loop out by Lake Michigan) and closer to a parking lot. The 'Draw Track" tool has a nice feature which lets you extend an existing track, so that was trivial.
Once all of the edits were done, I saved the file back to a new .gpx file.
Garmin's Training Center Software (used with Forerunner GPS watches and the like) lets you import Courses which can guide you through a workout, but amazingly, it doesn't import the nearly universal GPX format. So a translator is needed to get the .gpx file into a .crs file Garmin Training Center can use. There are a few options to do this.
One option is the handy website GPSies. The upload form will take a local file, data directly off a Garmin GPS, or the URL to a file anywhere on the public web. There are many options as far as what to convert the data to, but for the Forerunner you want to select, from the Track pull-down, "Garmin Course CRS." If you click "Show Options," you can reduce the number of points in the track (to make a smaller, less-detailed file), give the track a name (this will be handy when you import it to the Training Center and watch), speed (if you like dot-racing the dude on your watch), reversing the track, using a special algorithm for reducing the track further, or Add / replace elevation. I'm not totally up on that option, but it sounds good to me (to get an elevation profile on the watch as opposed to the Course just showing flat), but it's not critical. Once you click convert, the browser will churn a bit and eventually spit out a File dialog and likely ask you if you want to open or save the resultant file. Save it (make sure it gets a .crs extension).
Another other option is to use a stand-alone converter program. There are several out there and Google can guide you, but I found/used (right-click/ Save-As) gpx2crs.exe (a href="http://www.niniu.com/Garmin/release%20notes.txt">Release Notes) I don't know anything about the author, hosting site, or anything. I smelled it and it didn't smell rotten, but use it (as all software randomly downloaded from the internet) at your own peril. The interface is pretty simple. Stay on the first tab "Convert GPX to Course," browse to the source .gpx file, put a target pace and make sure "Simulate an average speed of" is selected (default), add extra points or reverse the track if that's your thing, and click convert. At that point, you'll get prompted for a filename/location. Again, ensure the .crs file extension is added. I noticed that when the conversion is done, the progress bar is still colorized like it might be doing something. It's likely not. The 18 mile track I was working with only took a second or two to process on an old laptop.
Once you have your .crs file, you can open the Garmin Training Center software. Click File, Import, Courses. Browse to your newly created .crs file. and you should see the new course listed when you press the "Courses" button at the top of the Training Center. You might have to expand one or more folders to find it. gpx2crs gives the course a non-unique name, so it's a good idea to right-click the new course, select Edit, and give it a good name - in this case, "Kenosha 18."
The next time you sync to your watch, the new Course(s) should go along for the ride. To use a Course on your run, cycle through the Modes on the watch, select Workouts, then Courses (this is from memory - might not be exact). When you select a Course, you can edit it (just the name), delete, or "Do Course." Once you select that, the watch will guide you to the start point, and you're off.
If you're interested, my edited .gpx file is here: (right-click / Save-as) Kenosha18.gpx
and the resultant .crs file is here: (right-click / Save-as) Kenosha18.crs
BTW, I'm NOT going to get to test this out this weekend, as timing didn't work out, but we might do similar with a 20-miler in a couple weeks. I'll try to remember to post back with results.
Yeah, I should have included some screenshots in this. Oh well.
Edits/comments/suggestions are welcome @ eblo @ ratula dot net.
YMMV.
Etc.
Happy running/navigating!

