Today I am a (slow) TRIATHLETE: my first triathlon

Phew. What a race!

First, the setup. My sister Julie and her family live in Vermont. I was idly poking around trifind.com (yay for the “sort by date” option) and saw that there was a triathlon over the July 4th weekend in Shelburne, not far from her home in Montpelier. I had originally thought about running Tri for Old Glory in Huntsville, but the mountain biking portion of the course put me off a little bit. A Vermont triathlon sounded like a great excuse for a visit, so I registered and started making plans, which included buying a wetsuit, flying, and so on. The organizer’s pre-race mail described the course as “rolling and challenging – Vermont isn’t flat!” That worried me more than a little, since this particular race had a long bike leg and a 500m swim (longer than I’m used to) and it was my first wetsuit swim and my first open-water swim. Oh, and it was my first triathlon, period. So I was a little disconcerted by that message. Julie was kind enough to drive me over to Shelburne to take a look at the course. We found the swim entrance easily enough, but the race map provided by the course organizer didn’t seem to match what we were seeing on Julie’s in-dash GPS. As it turns out, what we drove was not the course, but I didn’t know that at the time, so I went to bed last night thinking “hey, those hills aren’t too bad.”

Pregame

Last night I ate a normal meal: steak salad (plus some extra steak), some guac, a Fourth of July-themed cupcake, and a Heady Topper. I went to bed at a reasonable time and woke up, for no good reason, at 3am. I managed to get back to sleep until about 330am, but after that it was game over. I finally got up at 445, showered, put on my tri suit, and hopped in the car with Julie. We got to the race staging site half an hour early (who knew there wouldn’t be any traffic?) so we headed back into Shelburne for a Dunkin’ Donuts coffee stop. Registration was quick and easy, and I got a good spot on the rack with plenty of time to set everything up.

WP 20140705 008

My setup in transition; note camera on handlebar mount

WP 20140705 013

Julie, acting as my pit crew (she was super helpful— thank you very much, J!)

The weather was cool and windy, as you could see from the video I shot if my balky computer would upload it. However, the scenery on the beach was gorgeous— mountains in the background, a nice variety of low clouds, and the water itself, complete with whitecaps.

WP 20140705 07 11 10 Panorama

a panorama of the lakeside pre-race

After posing for a few pre-race pictures, I got my wetsuit on and got ready for the warmup swim. Several of my TRI101 peeps had recommended taking a warmup swim before any open-water action, and I’m glad I did. The water wasn’t as cold as I expected, thanks to my wetsuit and earplugs. It was, however, choppy, but the course was set so that the longest leg was parallel to the shoreline, so we were swimming parallel to the waves too. The race marshal herded everyone out of the water and gave us a quick safety brief, during which he described the bike course thusly: “You’ll go under the railroad overpass, then get to the first big hill…”

Uh oh, I thought. We didn’t see a railroad overpass yesterday. Maybe we went on the wrong bike course… But at that point there was nothing I could do about it, so I joined the single-file line for the swim and marched down the boat ramp into Lake Champlain.

The swim

The swim started in a single wave. The water was no more than about 2’ deep where we started, so it was easy to wade out to the starting point. I deliberately hung back because I knew if I got in front, I’d get run over by faster swimmers. Laura, Rachel, and a bunch of my other TRI101 peeps had all advised me to just treat the swim as a fun outing, so I did.This proved to be a good decision. At the starting gun, we all started swimming: 100m out to the first buoy, a sharp right turn followed by a 300m leg parallel to the shore, another turn, and 100m back to the boat ramp. I was surprised at how good I felt during the swim, though I got a couple of snorts of lake water from poorly timed breathing. I didn’t have much of a sighting technique, in large part because I hadn’t practiced; shame on me. (I hope Lisi isn’t reading this!) The only negative to the swim was that the inbound leg got shallow really quickly so I had to wade in because it was too shallow for me to swim. This made my legs get wobbly in transition, but I still felt pretty fresh overall. I exited the water, dropped off my provided swim cap, unzipped my wetsuit on the run, and got into the chute.

DSC 2424

As far as you know, I’m up in the front

T1

Coach Rick was right: it’s hard to put socks on wet feet. It’s also hard to remove a wetsuit without a) looking like a stork or b) falling over. I chose option a). The TRI101 transition training was really helpful here, as I had already neatly laid out shoes, socks, helmet, and sunglasses so I could get everything together. However, my transition time was longer than I wanted. It didn’t help that the camera fell off the mount that Paul and I had attempted to repair the night before, so I had to pick it up, adding a little bit of time. Then I stupidly forgot to push the right button on my watch, so my transition time and bike leg measurements are a bit jacked up.

DSC 2442

Luckily I didn’t fall over

The bike

ACK. The course was indeed “challenging”.

Sure enough, after the initial outbound leg, I went under the railroad overpass and… damn, that’s a long hill. And double damn… there was another one after it. The course also featured a long downhill stretch where I set a new speed record on the bike (29.8 mph), plus a stretch with an epic crosswind, plus beach scenery. The whole thing was rough, mostly because I had been riding exclusively on the flats in Alabama. It didn’t help that I stopped a couple of times: on the outbound leg I noticed that my watch wasn’t giving me speed data, so I stopped to adjust the speed sensor, which had gotten knocked out of position. (The cadence sensor, which Paul helped me fix yesterday, performed flawlessly, so yay.) A few miles later I stopped to move my watch to my Cajun handlebar mount, and then later still a cyclist passing me said “your back wheel looks loose!” as he passed. Or maybe he said “That’s a big heel goose.” He was going faster than me so anything’s possible. To be on the safe side, I stopped and checked it too. For the record, it was not loose and there were no geese evident.

I went back later (in the car, of course) and took a video of the course that I hoped would illustrate the hills, but it doesn’t; it looks like driving in the car, so you can’t really see the badness. The route is on MapMyRide, if you use it. Here’s an elevation map that helps tell the tale. That big knuckle around the 3.16mi mark is the first big hill, and the one before the 9.47mi mark is the second one. I had to walk up the first hill on the second course loop, as my legs were just gassed. As I found out when the official results were posted, I finished last on the bike— a little embarrassing, but I finished the ride and that’s what counts. (Plus, since this race didn’t have any professional photographers there is no record of my facial expression on the hills, for which I am grateful!)

NewImage

T2

T2 was slick as maple syrup: I got in, parked the bike, put on my running shoes, strapped on my belt, and took off. It could have gone faster; I think my time was around 1:50, but I didn’t drop anything, fall over, swear audibly, or drop dead, so I consider it a success.

The run

The run was a simple out-and-back, with a little bit of elevation on the first leg (the same road as the first 1/2 mile of the bike course, in fact). I took an easy pace, with several walking breaks, but still managed to turn in a respectable time: just under 30 min for 3.0 miles. I drained both of the bottles in my race belt, though, because I had very little water on the bike. I froze my water bottle overnight because I figured that way I’d have plenty of cold water to drink. Sadly, the 3 hours between taking the bottle out of the freezer and trying to get my first drink was not enough to melt the ice, so I got periodic trickles of melted water on the bike but that was it.

Results: “Who you gonna believe, me or your lyin’ eyes?”

78th overall (out of 80). My goals for the race were a) finish and b) not be last.  These might not seem super ambitious, but I expected both the bike and swim to be harder than anything I had done to date. And I was right, so yay me! I ran the race at close to my normal training pace, which I thought was pretty good after the abusive bike ride, and I’m pleased with my performance in the swim.

Event Official result Paul’s watch
Openwater swim 14m20s 292yd, 10m53s
T1  — 3m49s
Cycling 1h13m 13.83mi, 1h11m
T2 1m50s
Run 32m49s 3.0mi, 29m49s

My struggle with the Ambit 2S continues. The results it gives me don’t always agree with what I expect, particularly in pool swims, but today represented a new low. I was careful to make sure that I had “triathlon” loaded as one of the two multisport activities, and I gave it plenty of time to get a GPS lock before the race. The race organizers claimed the swim distance was 500 yards, and the watch credited me with 292. It’s possible that the course buoys were, accidentally or on purpose, sited to make the course shorter, but it’s also possible that the watch just gets confused by swim distances. Once I can plug it in (I didn’t bring the sync cable, oops), I can look at the track it recorded and figure out where things went amiss.

Interestingly, they didn’t time transition separately. The swim was a gun start, and we didn’t have individual chips, but the bike had a chip tag and so did my run bib, so it seems like they should’ve been able to calculate the T2 time at least.

Important things I learned during and after the race

  1. Before you register for a triathlon, look carefully at the course map. This is the most important tip I can possibly give you.
  2. If you freeze your bike water bottle the night before, it might not thaw before the race starts and you will have nothing to drink on the bike.
  3. If you leave your glasses on your transition mat, the very nice lady next to you might stomp on them; if you are very lucky, your brother-in-law will fix them for you.
  4. The salted-caramel flavor of Gu is pretty decent, at least as energy gels go.
  5. The water in Lake Champlain tastes way better than the water in the Madison Wellness Center pool. It’s probably because of all the zebra mussels.

Executive summary

I am a triathlete. Suck it, Blerch!

DSC 2539

3 Comments

Filed under Fitness

Huntsville to Vermont

As some of you may have noticed, I am planning to run a triathlon in a couple of days. This of course requires me to get to where the triathlon is, which in this case happens to be Vermont— several hundred nautical miles away from where I live. Luckily I had a solution for that problem. I took off from Decatur, stopped briefly at Winchester to fuel up, and headed north. Why Winchester? Fuel there is about $1/gal cheaper than it is at Decatur, and that makes a big difference when you’re buying 50+ gallons. Plus the staff there are super friendly and their facility is nearly brand-new: great, well-marked runway with a nice building. I saw an AgCat there filling his spray tanks and met Zachary, who just bought a Piper Lance a couple of months ago. We had a nice visit while I waited for my starter to cool down; I am still getting the hang of hot-starting the engine in this plane. The best technique seems to be to prime it just a tiny bit, then open the throttle full, set mixture to idle, and crank. You just have to be aggressive about enriching the mixture and closing the throttle when it does catch.

My flight northwards could not have gone better. I set up the autopilot, climbed to 7500’, and spent an hour or so dodging built-up clouds before settling on a steady course. During that time, I learned that the floor air vents can be opened or closed; when you open them, they work great at cooling down the cabin. This was handy because it was super hot on the ground— hot enough to melt my stash of protein bars inside my flight bag. I brought a cooler along so I could enjoy diet Coke on demand, which was a wonderful bonus.

On the first leg, I spent some of my time in flight reading the manual for my ancient panel-mounted GPS, which was installed in 2001, and I was surprised to find how capable it actually is; it just isn’t very user-friendly, so I still have a lot to learn, but I did get the time zone set, figure out how the altitude alerting function works, and learn how to set up complex flight plans instead of just using the “direct to” button. Originally I’d planned to stop at Rostraver (just outside Monongahela; try saying “Rostraver Monongahela” five times fast) but I noticed in flight that they close before I would have gotten there, so I decided to divert to Allegheny County instead. Fuel is a little more expensive, but that was offset by the fact that the airport was still open when I arrived. I parked the plane, hopped across the street to the Holiday Inn, and enjoyed a delicious calzone delivery from Mama Pepino’s. Then I hit the sack, intending to leave early this morning. The weather was not great when I awoke, so I did a bit of work and headed to the airport about 0900.

WP 20140703 001

706 on the ground at Allegheny County on Thursday morning

You can’t see it in the picture above, but the keys are on the dashboard, as shown below. This serves the extremely useful purpose of making it easy for everyone around to visually confirm that the keys aren’t in the ignition and that the airplane is therefore not startable. No one wants to tangle with an 84” propeller. This keychain has sentimental value, too; it came from Custer State Park on our 2005 trip to Sturgis. It was a Christmas present for Matt that year and he gave it back to me for the plane. The attached buffalo is named Pappy, after Pappy Boyington, not to mention Grandfather Buffalo, a family favorite book. Pappy is not quite as famous as The Lego Pilot but maybe he’ll get there someday.

Buffalo keychain

Corporate Air had taken good care of the plane overnight, so after a thorough preflight I launched with the intent to go direct to Montpelier, with Rome as an intermediate stop if the weather further north was still iffy. Pittsburgh limited me to 3000’ until I got further to the east, then I got 5500’, which was comfortably above the tops of the scattered clouds in that area. I went up to 7500’ about 50nm to the northeast and even then ended up having to dodge some higher buildups, but the clouds were gorgeous and by the time I got to Ticonderoga (see below) they were widely scattered.

Ticonderoga

Overhead Ticonderoga, NY; that’s Lake George 

 

My flight into Montpelier was completely uneventful (except that I got to talk to Boston Center, which was kinda cool). Julie and her boys were waiting for me, and I had a great time giving them a tour of the plane while we unloaded. Then it was back to her house for a nap, the Montpelier Mile, and the town’s fireworks.

Interestingly, I had a ton of different female air traffic controllers along my route. I’ve never had that happen before; I’m not sure why, but Nashville approach, Indianapolis Center, Pittsburgh Approach, and a couple of smaller approach control centers en route all had women working the tower cab.

Bonus picture: I saw this crop-dusting plane (an AirTractor AT802) when I refueled at Winchester. That might be my ideal job…

DSC 2394

2 Comments

Filed under aviation

Training Tuesday: and so it begins

Well, “begins” isn’t quite the right word; I’m 9 weeks into my 16-week training plan, but this week has a special milestone: my first triathlon is this coming Saturday. I am about equal parts nervous and excited. It’s my first-ever triathlon, my first open-water swim, and my first wetsuit swim. I have really low expectations, though: my goal is to finish, and, as long as I’m not last, the rest is gravy. I know I can do the swim distance, and the wetsuit should make it a little easier thanks to the added buoyancy. The bike distance isn’t a problem but the course is hilly. (Here’s the bike route, though you may not be able to see it if you’re not a MapMyRide member).

I have all the supplies and gear I’ll need, including a spiffy triathlon bag, although I want to get road tires today or tomorrow. Then it’s a matter of packing, for which I’ll carefully follow the checklist I made. I have TRI101 class tonight, and I’d like to get my long Thursday run in before I leave for Vermont, but I’ll wait and see how I feel; I definitely don’t want to overdo it. Perhaps a swim tomorrow would be nice, too. Tom is letting me borrow his Contour sports camera, so I hope to have some fun video from the trip (and, most importantly, the bike!)

Workouts this week:

  • Tuesday was transition training, which I already wrote about— lots of fun.
  • Wednesday I didn’t do anything.
  • Thursday I ran my first 5-miler! (well, 4.98 miles, but who’s counting?) Took me just over 51 minutes. If you look at the route map, you can see where we ran the HudsonAlpha helix— just look for the squiggly lines.
  • Friday I didn’t do anything.
  • Saturday we had our last group swim of the training season, featuring a drill known as “the washing machine”— you swim laps in two adjacent lanes, in a big swirl. Think of seeing people running laps around a track and you get the idea. Over 45 min or so I swam just over 900m, which is a new record for me. Some of that time was spent taking short breaks, though.
  • Sunday I didn’t do anything except eat.
  • Monday I rode with the Athens-Limestone posse— 26km in 1:11. That’s right, I voluntarily rode a bike in 91° heat for more than an hour. What the hell was I thinking?

Expect a Flying Friday post about the trip up to Vermont; that should be a fun adventure in and of itself. Now, I have to go put my USTA sticker on my car…

Leave a comment

Filed under Fitness

Training Tuesday: Transition Trouble edition

So tonight’s TRI101 class deserves its own post. Coach Rick had us practicing transitions; the coaching staff brought out the bike racks and we set up our bikes, shoes, etc. as we would in a race. When called, we were to run, barefoot, to our rack to simulate exiting the water for T1, put on shoes (and socks, if desired) and helmet, then move the bike to the mount line and ride 2 laps around a ~1mi loop. Then we were supposed to bring the bike back into transition, switch to our run gear (hello, T2!), and run the loop again. The goal was to do 3 complete circuits within 45 minutes. I didn’t quite make it— I got 3 bike laps and 2 runs before time expired. I did, however, learn several things I didn’t know, presented here for the edification of all:

  1. No one will stop you from exiting T2 for the run with your helmet on. You might want to remove it before running, though.
  2. Despite their cleats, bike shoes have little traction. If you get a good head of steam going downhill to the mount line, you may have difficulty stopping without falling on your butt.
  3. There’s only one way to hang your bike on the rack so that it doesn’t fall over.
  4. You (or at least I) can’t just jam your feet into your bike shoes because the heel area isn’t stiff; it’ll just mash down.

Despite these errors, I felt like I got the transition mechanics down OK, and both the ride and run felt pretty good (I averaged ~14mph on the bike and 6.5mph on the run). Oh, and my Cajun-rigged cadence sensor fix failed again, darn it. Onwards!

Leave a comment

Filed under Fitness

Training Tuesday: halfway through TRI101

So last week marked the halfway point in the Fleet Feet TRI101 program. I can definitely see a big difference in my overall fitness level, although (as I learned on Sunday in the gym) I am not nearly as strong as I was when I was lifting regularly. This is in part due to the garbage diet I’ve been following; too many carbs, not enough protein, and probably too much fat to boot. That’s one of the things I want to focus on in the upcoming weeks as I start reintegrating lifting into my workouts. The bricks we’ve been doing at TRI101 class have been really helpful, too, along with the many small tips and tricks that the more experienced athletes and coaches have been sharing.

I continue to be tempted by signing up for more races, but at the same time I’m growing more nervous: my first real tri is in less than two weeks, and it’s hard to judge whether I’m ready for it or not. On the other hand, my friend Dana just ran her first sprint tri and finished 2nd in her age group— so it proves that even your first race can go well. My goals for the Shelburne tri are to not burn up all my energy in the swim. The bike ride is a longer distance than any I’ve done so far, so I’d like to finish that at my same ~15mph pace, and then get the run done in under 35 minutes. We’ll see how that goes.

The past week’s workouts:

  • Tuesday we bricked as part of our weekly class: 34:46 for 8.45mi on the bike plus a weak, slow 15:01 to run 1.41mi. As a bonus, I split my forehead open in transition and had to go get stitches, so I couldn’t swim for a little while.
    WP 20140617 003Like my old man always said: it’s not a project until blood has been shed
  • Wednesday I met up with a group of triathletes for a brick south of the airport. Damn, it was hot. 55:01 for 12 miles on the bike plus a super short 8:15 run of 0.8 miles. For some reason I didn’t get any cadence data from this ride. The reason turned out to be simple: the magnet that the cadence sensor senses fell off somewhere. I replaced it with several Buckyballs, which I stuffed into the pedal hole on the crank; a piece of electrical tape holds them securely in place and now I get cadence data again.
  • Thursday I skipped my normal morning run— after a race last Saturday, a long ride Monday, and bricks Tuesday and Wednesday I was ready for a break. I took Friday off too.
  • Saturday I volunteered at the Monster Tri. It was great fun; I saw a bunch of my tri friends and got a close-up look at how transition is supposed to work. I also took a bunch of pictures, some of which were better than others.
  • Sunday I dragged myself to the pool and swam ~ 500yd. I still don’t think my watch is counting swim laps right. Then I carried my tired self over to the weight room and got a lift in for the first time in about two months. I felt weak but good when done, and the DOMS I had yesterday and today is a small price to pay (especially since my glutes and hams were already sore before I even got there.)
  • Monday I geared up and went to downtown Athens for the 15-mile beginner ride that a group of local cyclists holds… but the weather wasn’t cooperating.WP 20140623 002

    Not acceptable weather for instrument flight or VFR bicycling

    Rather than get hit by lightning, I elected to go home. I didn’t even get to test the sweet handlebar mount I made for my watch so I can see cadence and speed data on the go: a trip to Home Depot yielded a piece of pipe insulation that was just right for holding it. However, I am confident that it will work.

     WP 20140624 004Nothing like a little Cajun engineering

     

Right now I’m hoping that the weather will clear so I can go on to TRI101, where we have a workout cleverly named “Rick’s Special” after our lead coach– it’s a 2 mi bike + 1 mi run brick, repeated as many times as possible. Should be fun!

Leave a comment

Filed under Fitness

Thursday trivia #108

First, my thoughts and condolences are with the families of the pilots killed in the Westwind II crash at Huntsville yesterday. 
  • I don’t normally post on political topics here… but if you believe that six key IRS employees just happened to lose all of their email, at the same time, in a manner that’s not recoverable, then I have some hope and change I’d like to sell you. Government agencies and large companies pay large sums of money to prevent exactly that type of occurrence.
  • This looks pretty interesting: “Loss of Signal: Aeromedical Lessons Learned from STS-107
  • Yesterday was the 100th anniversary of the first successful demonstration of an autopilot. We’ve come a long way since then.
  • Having two teenage sons both driving has reacquainted me with all the reasons I don’t like auto insurance companies. Every six months, when I write that check, my dislike for them peaks.
  • I’m loving the World Cup, but oddly I don’t care much about soccer in general. Go figure. I must be an American.

3 Comments

Filed under General Stuff

Training Tuesday: gearing up

It’s amazing how much crap you can buy for triathlon training. I already had running shoes and a bike; since then I’ve bought a watch, a cadence sensor, a wetsuit, goggles, a race hydration belt, and an assortment of other odds and ends. Yesterday I finally broke down and bought swim fins, a kick board, and a swim pacing timer— not because I need those for the race but because I need them for the drills my swim coach is giving me, and if I actually spend money on the gear I will feel obligated to do the drills. Commitment device FTW! In the same vein, since it was about 25% more expensive to buy a wetsuit than rent one, I bought one for my upcoming triathlon in Vermont… but now, having bought one, I feel like I need at least one more open-water tri to justify it. Candidates include the Lone Star Sprint in Galveston (which seems to have a permanently broken web site), the Frantic Frog in Scottsboro, the Tri-Rock in Austin, the Tawas Festival of Races, or maybe one of these.

I think I am done buying stuff for this tri season, unless I break or lose something— certainly not out of the question. I think I’d like a heart rate monitor but that’s just because I like looking at pretty graphs, not because I think it would help my training. At this point I need to stick to the plan, be a little more careful about what I eat, and start getting some actual races under my belt. More experienced cyclists have suggested changing the big semi-knobby hybrid tires on my bike for thinner road tires, and I might do that, but we’ll see how my first race or two goes. I figure I can always buy more crap later, but having more stuff isn’t going to make me go any faster or train any harder.

This week’s workouts:

  • Tuesday and Wednesday I was out of town and didn’t do anything.
  • Thursday I went back to Bridge Street for another group run. I felt really slow starting off, but in the end I ran 4.67 miles in about 47:25— a new distance record for me. (In fact it was a bit longer because my watch didn’t start timing when I thought it did). This was a real confidence boost, because if I can run that distance well that puts me in good position to complete a 10K. I’ll do better this week, too; at once point I stopped to walk because the group in front of me had run out of sight and I didn’t know where the planned route was, so I waited for the group behind me to catch up.
  • Friday I swam. Maybe 475m, maybe 500m, maybe 600m. It depends on which set of data from my watch you believe, as I wasn’t manually counting laps.
  • Saturday I ran the Alabama A&M Cross-Country 5K. I ran it in 31:59, which is certainly not great. The course features a good-sized hill, though, so that’s my excuse. I saw a ton of folks from my TRI101 class, which was cool, and it was a good workout. Plus each finisher got a hand-painted souvenir rock instead of Yet Another T-Shirt, so that was cool.
  • Sunday, I celebrated Fathers’ Day by not doing anything exercise-related. I did eat a steak, though, and I think that should count.
  • Monday I joined the local Kreme Delite group (so called because that’s where we ride from) and did 12.51 mi in 55:29. I got to the ride site a few minutes late, and the group had already left, so I blundered around trying to find the correct street for the route, then encountered another late rider along the way— so he and I rode the route, only to find a big group at the finish line. Note to self: be on time for next time.

On to the next!

1 Comment

Filed under Fitness

Does Azure Machine Learning open the door for on-premises Office Graph?

Microsoft continues to expand the reach of its Azure services by introducing new capabilities, seemingly on a daily basis. Today I was surprised to see an announcement for the new Azure Machine Learning service (more background in this NY Times article). The link for the service apparently isn’t live yet, though.

The availability of this service raises some interesting questions around Office Graph, the set of nifty social-ish features that Microsoft introduced at SPC and reiterated at MEC and TechEd. We recently learned that, at least for now, there are no plans to offer Office Graph, and its associated features, to on-premises customers in the next release of Exchange Server. Carefully parse that statement; it could mean anything from “there will never be Office Graph features in on-prem Exchange” to “we can change our plans and include them at any time.”

It’s fair to say that Office Graph is designed to leverage the high scale of Office 365, and that because it is a resource-intesive group of processes and services, that there’s likely to be a lot of infrastructure for management, monitoring, and tuning of its components— not necessarily something that could trivially be unleashed on the existing base of on-premises customers. I’d bet that these services have a lot of interconnections, too. However, if Microsoft is adopting the Amazon approach of  “everything is a service”, as they seem to be, you’d think that having some parts of Office Graph running on Azure ML is not only possible but probable. And the Azure folks are clearly comfortable with hybrid environments, as witness the fact that the Forza 5 and Titanfall video games on Xbox One both make extensive use of Azure-based resources.

So, if Office Graph is (or could be) consuming Azure ML as a service, it would seem to lower the barrier for getting Office Graph-related services into on-prem Exchange. I’ll be watching closely to see what Microsoft announces, and even more closely to see what they do, around this issue— it seems like the best possible world would be one where on-prem customers can harness the scale of Azure to get access to Office Graph features and where Microsoft doesn’t have to engineer a complete support system around on-prem variants of the Office Graph components. Stay tuned…

Leave a comment

Filed under Office 365, UC&C

Thursday trivia #107

  • “Learned helplessness” is totally a thing, but perhaps some people are more prone to it than others
  • If I were critically injured, I would be totally OK with having my blood replaced with freezing salt water to “pause” my metabolism long enough for the ED docs to fix me up. 
  • In the past two weeks I’ve started watching 3 new shows: Longmire, Orange is the New Black (thoroughly enjoying it so far), and Halt and Catch Fire (atmospheric, but they muff a lot of technical details and the MacMillan character seems a straight ripoff of Don Draper). However, that’s all about to go by the wayside for two reasons: my “pre-order” list at Amazon is about to blow up with new books, and the World Cup is starting today.
  • Hopefully the airplane will be fixed in time for our scheduled trip to Perrysburg. If not, second prize  is the Fathers’ Day Weekend Inferno at Anaheim Chili.

Leave a comment

Filed under General Stuff

Training Tuesday: more of the same

[ I know this is a day late but the draft was sitting on my computer at home and I couldn’t post it yesterday. C’est la vie. ]

My weightlifting training should have been pretty easy: I had a daily eating plan and a scheduled list of workouts. All I had to do was stick with that schedule. The effort involved, of course, came from actually lifting the weights (and, sometimes, getting my lazy ass off the sofa and going to the gym). That is one of the key aspects of the Fleet Feet TRI101 program for me: the training schedule is laid out, day by day. In theory, all you have to do is follow it and you will, almost inevitably, get better at the individual events. But what if you deviate from it… for example, by mixing in races? I guess I’m going to find out. My first multisport event was on Saturday: the brand-new Mountain Deux aquathlon (a rather stupid name; it’s a ~5K trail run followed by a 200m swim).

I signed up for two more sprints, too: the Tarpon Tri in Houma (200m swim, 10mi bike, 5K run; super flat course but August in Louisiana, yikes!) and the RaceVermont Sprint in Shelburne, Vermont (where I’ll get to see Julie and her family, and for which I had to rent a wetsuit— Lake Champlain is cold!) I am a little nervous about the Vermont race because it’s a longer bike distance than I’m used to, and the swim portion is 500m of open water. It’ll be a fun challenge though.

Workouts since my last post:

  • Tuesday: in TRI101 class, we had a 40-minute group run scheduled. It was 88° when we took off, but I still managed 4.0 miles in 40:04. I’ll take it, but maaaaan, I was sweaty when we finished. I also had a swimming lesson, which went poorly— I am still having a hard time getting my stroke and breathing coordinated, and the drills Lisi taught me mostly just made me frustrated that I wasn’t doing them well.
  • Wednesday: I took a short ride to test my new cadence/speed sensor. Just under 7 mi in about 31 minutes.
  • Thursday: I had a root canal around noon, so I wanted to get a run in early. A local group of runners meets at Bridge Street for a 4.5 mile run, so I dragged out of bed at 0515 to join them. There were storm clouds building when we stepped off, then we started getting a really impressive lightning display about 1.5 mi into the run, so we cut it really short. 2.67mi in 23:14, which felt great— that’s very close to my “good” 5K race pace. The threat of getting zapped by lightning obviously helped, given my pace on the last part of the race. I love it that the watch gathers enough pace data to show the two (short) intervals when I took a walk/water break— those sharp downwards spikes.
    NewImage
  • Friday I swam 600m: in 3 sets:100, 400, and 100 again. I haven’t been doing the drills that Lisi prescribed, which means she’s been fussing at me.
  • Saturday was the Mountain Deux. See my full report here.
  • Sunday I had planned to do a brick, but wasn’t feeling well so I punked out. The schedule had a programmed day off anyway so I didn’t feel too badly about it.
  • Monday I had another swim lesson with Lisi. She introduced me to the notion of holding a steady stroke count, as well as giving me a whole bunch of drills. I swam about 450m, plus at least another 300m or so of drills. Then for fun, I took a bike ride through part of Limestone County— beautiful country scenery, followed by a big rainstorm once I was safely at home with the gear put away. This was the farthest distance I’ve ridden so far, just over 12 miles, and after finishing it I feel better about the Vermont distance.

This week I need to focus on getting in the pool!

Leave a comment

Filed under Fitness, General Stuff

My first multisport event: Mountain Deux

Like every other endeavor, endurance sports have their own lexicons. Most people know what a triathlon is, but it’s a little unclear what to call a two-event competition. Turns out, it depends on which two events are involved: a bike/run combo is usually known as a duathlon, and a swim/run combo is apparently known as an aquathlon. I found this out more or less by accident; one of my TRI101 training teammates said he had signed up for Mountain Deux, an aquathlon here in Huntsville. It looked like fun so I signed up too, then ran it yesterday. The course was a hilly trail totaling just over 2 miles, followed by a 200m swim in a very nice, and nearly brand-new, saltwater pool. Sounds like fun, right? Turns out that it was!

Friday night I packed my gear: two towels (one to wrap my wet, muddy clothes in), swim cap and goggles, a change of clothes, and my race belt. Then, bright and early Saturday morning, I headed over to the race area, the Three Caves trail system. The race was small, so there wasn’t much in the way of check-in or registration; I found the transition area, staged my gear, and chatted with friends (including borrowing some bug spray and getting my race number inscribed on my arm) until it was time to start. We actually started from the Three Caves themselves, which means the first leg of the race was all uphill. This was not my favorite. After that initial climb, I settled into a slow and fairly steady pace, terrain permitting.

NewImage

The race course

Thursday and Friday the whole Huntsville area got hammered with rain and thunderstorms, so I was expecting a wet trail, and I wasn’t disappointed. I was surprised by how rocky the trail was. Big rocks, little rocks, flat rocks, pointy rocks: I didn’t feel like I was running so much as I was dodging, stepping over, or hurdling rocks. The last time I ran a trail race, in 2010, I turned an ankle while fording a creek when I stepped on a rock, so I’ve avoided trails since then.Where the trail was not rocky, it was slick and muddy. This definitely made it more challenging than my typical flat-surface runs. I ended up walking about a third of the trail overall, which hurt my time. The last leg of the race was all downhill, which was even more challenging because of the slippery ground. I nearly face planted a couple of times, but survived uninjured.

Transition was super easy: off came the long pants, shirt, shoes, and socks; on went the goggles and cap, and splash! Into the pool.

The swim was easy. I wasn’t trying to swim particularly fast, and I didn’t (although my watch mysteriously didn’t capture a time for the swim, and the event didn’t provide split times). I felt smooth in the water though, which is a big improvement. It was only 200m, so the short distance certainly helped make it feel easier.

My finishing time was 36:59, which more or less agrees with my watch time if you add in the missing swim. I didn’t have any particular expectations since this was so different than my normal race fare; I’m happy to have finished, uninjured, and I learned a few things: I can run just fine without music, it’s a bad idea to accidentally spray bug spray on your water bottle’s mouth unless you like numb lips, and trail running actually can be fun.

Leave a comment

Filed under Fitness

Does getting a root canal hurt?

tl;dr: not as much as the tooth hurt before the root canal

For years I had one tooth that would, very occasionally, make a popping or clicking sound— very faint, but since it was inside my mouth I could feel it. I couldn’t figure out why so, as one does, I ignored it. Then last July, it abruptly became very sensitive to heat and cold: Toothmageddon. I went to my dentist, who referred me to an endodontist, Matthew Friedt, who told me “keep an eye on it.” It seemed to get better, so I left it alone. Then came “Toothmageddon II: The Revenge.” A couple of weeks ago, the heat sensitivity returned with a vengeance, along with the popping sound; eating anything above mouth temperature would make the tooth throb for hours. I immediately made another endodontist appointment, and yesterday was the big day.

I found a lot of contradictory and confusing information online about root canals, so I thought I’d summarize the process, at least the way my endo did it.

First, he took a couple of X-rays and confirmed, by using both heat and cold tests, which tooth was afflicted. Interestingly, the nerves that sense cold tend to be the first ones to die off, which is why I lost the cold sensitivity. The tooth was definitely heat-sensitive, and Matthew used an optical microscope to examine the tooth surface and saw a few small cracks. Once he had verified that he had the right tooth, he shot me up with plenty of lidocaine (or whatever the cool kids use for face numbing), let it percolate, and then started working.

The work phase was simple: he clamped a little metal ring on my back molar and used it to hold a dental dam and frame, which was a new experience for me. Then he drilled a hole in the top of the tooth and used a series of super-fine probes and drills to clean all the tooth-guts (that’s a technical term) out. Once he finished this phase, I got another X-ray so he could verify that everything was out. Then using the same series of probes, he filled the nerve channels in with some sort of rubber or epoxy or something, then added a cone-shaped plug that sealed the hole in the tooth and tamped the material down. That was it; I didn’t have anything stronger than topical anesthesia, and he didn’t prescribe any antibiotics or pain pills.

After I left I noticed that the entire right side of my face— all the way up to my right temple— was as numb as a steak; my jaw was super stiff from holding it open, and my neck and shoulders were tense from me tensing them. I went home, had a protein shake, took an Advil and a leftover pain pill from Toothmageddon I, and napped for a couple of hours, followed by a light dinner and some Netflix. Now I’m back to normal.

While I wouldn’t say it was fun it wasn’t as bad as I had feared, and it is nice to be able to enjoy non-room-temperature food without pain. I very highly recommend Dr. Friedt; he explained very clearly what he was going to do, then he did it efficiently and quickly (the whole process from arrival to departure took a little over 2 hours).

The More You Know™…

1 Comment

Filed under General Stuff

The difference between Suunto cadence and bike pods

I spent way too much time trying to figure this out today, so I’m blogging it in hopes that the intertubez will make it easy for future generations to find the answer to this question: what’s the difference between a cadence pod and a bike pod according to Suunto?

See, the Suunto Ambit series of watches can pair with a wide range of sensors that use the ANT+ standard. You can mix and match ANT+ devices from different manufacturers, so a Garmin sensor will work with a Suunto watch, or a Wahoo heart-rate belt will work with a Specialized bike computer. I wanted to get a speed and cadence sensor for my bike. These sensors measure two parameters: how fast you’re going and how rapidly you’re pedaling. (This is a great explanation of what these sensors really measure and how they work.) Ideally you want a nice, steady cadence of 75-90 rpm. I knew I had a variable cadence, and I wanted to measure it to get a sense for where I was at.

I ordered a Wahoo combined cadence/speed sensor from Amazon and installed it on the bike, which was pretty straightforward. Then I paired it with the watch using the “bike POD” option. (Suunto, for some reason, calls sensors “PODs”). That seemed to work fine, except that I wasn’t getting any cadence or speed data. But I knew the sensor was working because the watch paired with it. I tried changing the sensor battery, moving the sensor and its magnets around, and creating a new tracking activity that didn’t use GPS to see if I got speed data from the sensor. Then I thought “maybe it’s because I didn’t pair a cadence pod”, so I tried that, but no matter what I did, the watch refused to see the Wahoo sensor as a cadence sensor.

Here’s why: to Suunto, a “bike POD” is a combined speed/cadence sensor. A “cadence pod” is for cadence only. Like Bluetooth devices, each ANT+ device emits a profile that tells the host device what it is. That’s why the watch wouldn’t see the sensor, which reported itself as a combined cadence/speed unit, when I tried to pair a cadence pod. After I figured that out, I quit trying to pair the cadence pod… but I still didn’t get speed or cadence data.

The solution turned out to be simple. For some reason, in the cycling sport activity, the “Bike POD” sensor was unchecked, so the watch wasn’t reading its data stream during the activity. I don’t remember unchecking the box, but maybe I did. In any event, once I checked the “Bike POD” box and updated the watch, I immediately started getting cadence and speed data, so I set out for a ride.

NewImage

Hint: if you uncheck any of these boxes the watch will never, ever pay attention to that sensor

I thought it was a pretty good ride from a speed perspective, even though I took a new route that had a number of hills– I had some trouble with that. But look at my cadence… you can see that it definitely needs work. Sigh. One of the nifty things about Suunto’s web site is that it shows vertical speed when you point at cadence data, so I could see where I was struggling to get up hills (meaning I needed to change gears) or loafing when going downhill. Just one more thing to put on my to-fix list…

NewImage

37 Comments

Filed under Fitness, General Tech Stuff, HOWTO

Creating an Office 365 demo tenant

One of the big advantage of software as a service (SaaS) is supposed to be reduced overhead: there are no servers to install or configure, so provisioning services is supposed to be much easier. That might be true for customers, but it isn’t necessarily true for us as administrators and consultants. Learning about Office 365 really requires hands-on experience. You can only get so far from reading the (voluminous) documentation and watching the (many and excellent) training videos that Microsoft has produced. However, there’s a problem: Office 365 costs money.

There are a few routes to get free access to Office 365. If you’re an MVP, you can get a free subscription, limited (I think) to 25 users. If you’re an MSDN subscriber, you can get a tenant with a single user license, which is fine for playtime but not terribly useful if you need a bigger lab. Microsoft also has a 30-day trial program (for some plans: Small Business Premium, Midsize Business, and Enterprise) that allows you to set up a tenant and use it, but at the end of that 30-day period the tenant goes away if you don’t pay for it. That means you can potentially waste a lot of effort customizing a tenant, creating users, and so on only to have it vanish unless you whip out the credit card.

I was a little surprised to find out recently that there’s another alternative: Microsoft has a tool that will create a new demo tenant on demand for you. You can customize many aspects of the tenant behavior, and you can use the provided user accounts (which include contact photos and real-looking sample emails and documents) or create your own. There are even vertical-specific packs that customize the environment for particular customer types. And it’s all free; no payment information is required. However, you do have to have a Windows Live ID that is associated with a Microsoft Partner Network (MPN) account. If you don’t have one, you can join MPN fairly easily.
All this goodness is available from www.microsoftofficedemos.com. Here’s what you need to do to use it.
  1. Go to http://www.microsoftofficedemos.com/ and log in.
  2. Click the “Get Demo” link in the top nav bar, or the “Create Demo” link on the page, or just go to https://www.microsoftofficedemos.com/Provision_step1.aspx. That will display the page below. Note that you can download VHDs that provide an on-prem version of the demo environment if you want those instead.
    Tenant01
  3. Make sure you’ve selected “Office 365 tenant” from the pulldown, then click “Next”. That will display a new page with four choices, all of which are pretty much self-explanatory. If you want an empty tenant to play around with, choose the “Create an empty Office 365 tenant”. If you want one that has users, email, documents, and so on, choose “Create new demo environment” instead.
    tenant02
  4. On the next page, you can choose whether you want the standard demo content or a vertical-specific demo pack. This will be a really useful option once Microsoft adds more vertical packs, but for now the only semi-interesting one is retail, and the provided demo guides (IMHO) are more useful for the standard set, so that’s what I’d pick. After you choose a data set, click “Create Your Demo”.
  5. The next page is where you name the tenant, and where Microsoft asks you to prove you’re not a bot by entering a code that they send to your mobile phone. (Bonus points if you know why I picked this particular tenant name!) The optional “Personalize Your Environment” button lets you change the user names (both aliases and full names) and contact pictures, so if you’re doing a demo for a particular customer you can put in the names of the people who will attend the demo to add a little spice. The simple option is to customize a single user; there’s one main user for each of the demos (which I’ll get to in a minute), but you can customize any or all of the 25 default users.
    Tenant04
  6. Once you click “Create My Account”, the demo engine will start creating your tenant  and provisioning it. This takes a while; for example, yesterday it took about 12 hours from start to finish. Provisioning demos is just about last on Microsoft’s priority list, so if you need a tenant in a hurry use the “create a blank tenant” option I mentioned earlier. You’ll see a progress page like the one below, but you’ll also get a notification email to the address you provided in step 5 when everything’s finished, so there’s no need to sit and watch it.
    Tenant06
Once the tenant is provisioned, you can log into it using any of the test users, or the default “admin” user. How do you know which users are configured (presuming you didn’t customize them, that is)? Excellent question. The demo guides provide a complete step-by-step script both for setting up the demo environment and executing the demo itself. For example, the Office 365 Enterprise “hero demo” is an exhaustive set of steps that covers all the setup you need to do on the tenant and whatever client machines you’re planning on using.
Once the tenant is provisioned, it’s good for 90 days. You can’t renew it, but at any time during the 90 days you can refresh the demo content so that emails, document modification times, and so on are fresh. And on the 91st day, you can just recreate the tenant; there doesn’t seem to be any explicit limit to the number of tenants you can create or the number of times you can create a tenant with a given name.
While the demo data set is quite rich, and the provided demo scripts give you a great walkthrough to show off Office 365, you don’t have to use them. If you just want a play area that you can test with, this environment is pretty much ideal. It has full SMTP connectivity, although I haven’t tested to verify that every federation and sharing feature works properly (so, for example, you might not be able to set up free/busy sharing with your on-prem accounts). I also don’t know whether there are any admin functions that have been RBAC’d to be off limits. (If you see anything like that, please post a comment here.)
Enjoy!

11 Comments

Filed under Office 365, UC&C

Training Tuesday: slow progress is still progress

One of my fellow TRI101 participants shared this excellent article about building on your strengths in one event to bolster your weaknesses in another. I don’t really feel like I have any special strengths in running or cycling, other than “can complete required sprint distance.” But on reflection… that counts too. I definitely feel like my swimming is improving, though, and cycling the 10-15Km routes we use for training has been getting easier: an excellent sign that I need to go either farther or faster. The TRI101 program is scaled for participants who start at a low fitness level, but we are now at the beginning of week 6. If I stopped right now, I’m confident that I could finish a sprint triathlon, which is great news— now I just need to work on doing it faster.

The week’s training:

  • Thursday: 250m swim + swim drills. Slow, but better than nothing. I just wasn’t feeling it that day. As Karen, one of our coaches, pointed out, some days are better than others, and sometimes the best thing to do on a bad swim day is cut the distance short.
  • Friday: I swam 100m without stopping— a big deal for me, since I hadn’t been able to do that before— then 5 x 50m intervals, then another 100m. The intervals are 25m slow and 25m as fast as possible. It was a good workout, and I felt much better than I did after Thursday’s swim.
  • Saturday I did a short run/bike brick with a couple of classmates: 8.5 mi on the bike in 44:26 and 1.1mi running in 11:34. On the bike I spent a while riding slow circles waiting for all our party to catch up, so I didn’t take that time too out of sorts. I also went to the pre-race brief for the Mountain Deux aquathalon, which is this coming Saturday: a ~5Km trail run, followed by a 200m swim. Should be fun, except for the “trail run” part.
  • Sunday I swam with two TRI101 peeps: 100m warmup without stopping, 400m with minimal rest, then another 100m (which I did as 2×50, with the same 25m slow/25m fast). This was the first workout I logged with my new Suunto Ambit 2s triathlon watch.
  • Monday I had a bike fitting. That’s a topic for a post all on its own; look for it next week.

So, the watch. Anyone who knows me knows what a gadget nerd I am. I saw a mention on Facebook of a big watch sale mentioned at the DC Rainmaker blog, so I started poking around and was fascinated by the idea of a GPS-powered watch that could track my workouts for me— something I’d been using my phone for, with varying degrees of success. After reading his über-review, I decided to get an Ambit 2S. As much fun as it would be to have the barometric altimeter in the Ambit 2, it wasn’t worth the extra money. It arrived Saturday, and first thing Sunday morning I strapped it on and headed to the pool. Here was my reward: a more-or-less accurate record of my swim activity. I say “more or less” because I think it miscounted laps a couple of times, and the “total distance” column in the laps table doesn’t match the “distance” field at the top. I will be using it for cycling and running in the next couple of days and can get a better idea of how it works but I am most interested in the “multisport” mode for triathlons. I’ll be using that at Mountain Deux next week. The watch can pair with heart rate monitors, cycle sensors, and all sorts of other goodies that I will eventually add.

First swim

The upcoming week’s training should be good stuff— running tonight and Thursday, swimming Friday, and a bike/run brick Saturday. There’s a group that meets Thursday mornings to run a 4.5mi road course; I might join them to get a little distance in on the theory that if I can run 4.5 miles, it’s not that much of a stretch to run 6 miles, which means that I’d be in striking distance of running a 10K once triathlon season calms down some. On the down side, I also have a root canal Thursday (after running), so that may slow me down a bit. Hopefully I’ll bounce back in time for Mountain Deux on Saturday!

 

Leave a comment

Filed under Fitness, General Stuff