Register | Login
Attackpoint - performance and training tools for orienteering athletes

Training Log Archive: iansmith

In the 7 days ending Jun 16:

activity # timemileskm+mload
  Biking7 11:19:19 160.9(14.2/h) 258.94(22.9/h) 236298.8
  Running1 21:49 2.7(8:04) 4.35(5:01)2.2
  Total8 11:41:08 163.6(4:17) 263.29(2:40) 2362100.9

«»
4:57
0:00
» now
MoTuWeThFrSaSu

Saturday Jun 15 #

7 AM

Biking 4:57:36 [1] 111.6 km (22.5 kph) +1533m
shoes: Canyon Endurace

Today, I set out for my first metric century in the Bay area. That it has taken me this long is inexcusable, though I didn't get my bike until mid February. A metric century is a convenient threshold for a "long" ride. Rides of more than 150 km can rightly be considered ultradistance, and 200 km is probably the threshold for epic rides. The climb and conditions of a ride might adjust these thresholds, but they are useful guidelines.

I carried sub-ultra gear: two 750 mL bottles (one water, one electrolyte); a Shot Blox; a 1200 kCal bag of M&Ms; spare, pump, tire levers; phone, ID and credit card. My bike performed admirably, with its new 1.9L frame bag. Shifting and braking were crisp and responsive. However, I ran into the trifecta of slowness of climb (planned), traffic lights (suck), and wind (meh). I set the Marin headlands as my objective.

I left home at 7:50a, later than my 7:15 planned departure. The best time to ride is probably 5-10a, because it is mostly light and calm with reduced sun. I planned my route the day before on Komoot, and some parts were delightful. I had done the section north of the Golden Gate before, and the upper great highway along the beach near Golden Gate Park is closed to cars. However, getting to Lake Merced is surprisingly non-trivial from Burlingame, and returning through the city was a miserable path of stoplights and stop signs. Going forward, it might be expeditious to first do the 200m climb up to Skyline, then ride along Skyline Blvd up the west coast to Golden Gate Park.

My objective - the Marin headlands - was tame compared to my neighborhood climbs of Ralston and Crestview. According to Strava, Hawk Hill is 2.7 km at 5.8% average (158m). For comparison, Crestview is 2.2 km at over 12% average (278m). There are two sections on Conzelman Road around 10%, but these are trivial with my mighty 34 tooth gear. I stopped at the top of Hawk Hill to take a photo, stopped my Wahoo GPS tracker, then forgot to resume it until I had cycled to the tunnel via Bunker Road. My track is missing roughly 10 km and perhaps 25 minutes. This is a bit of a shame, because the descent west from Hawk Hill on Conzelman Rd is terrifying, with a peak grade of 18% according to a sign and some blind corners. I liberally used my brakes and generally stayed below 35 kph.

I was puzzled when my computer said 93 km when I got home, as the route I had planned was a shade above 100. To hit the arbitrary target, I did an extra loop. Today's ride including climbing by design, but I was still surprised how long it took, even with a long stop to meet a friend for coffee. My standard 120 km ride in Toronto only had 300m of climb from small undulations. If I can find ways to avoid traffic lights and stop signs, I believe average speeds of 25+ kph are possible, even with the occasional 100m+ climb.

Other notes:
  1. Currently, the east side of the Golden Gate Bridge is reserved for pedestrians, west side for cyclists (I rode the east side going north).
  2. Gough Street and Broadway is a monster, with sustained sections over 10% and one block over 25% (according to Strava).
  3. Valencia St in the Mission has a median bike lane, which is nice albeit still susceptible to traffic lights.


Friday Jun 14 #

7 PM

Biking 1:32:20 [2] 34.76 km (22.6 kph) +696m
shoes: Canyon Endurace

Building character on SpeedyBike. I repeated the Crestview loop that I also rode last Friday, June 7 - Ralston, Skyline, Cañada, Crestview, Crystal Springs, Woodridge loop. While this was not controlled, I rode the same loop 8:47 faster today on SpeedyBike. I lost about 90s last week when I dropped my chain on a climb, and this comparison doesn't control for traffic light delays or wind, but SpeedyBike was nonetheless obviously faster. Some comparative splits:

Split - S11, Canyon
Ralston Climb (184m): 18:18, 16:34
Hayne to Edgewood (flatish): 25:58, 24:06
Crestview Climb (203m): 15:59, 14:39

I very much appreciated the extra big rings at the back, as Crestview is a 203m climb in 2.31 km. Crestview is savage, with a peak gradient on Strava of 19.6%, and the first half averaging 11.2%. Ralston, my neighborhood hill, has 184m of climb in 4.3 km, with stretches over 10%. I also took SpeedyBike above 60 kph on some descents, where I used my MVP 11 tooth cassette gear. Having a 12 speed cassette makes going from the highest to lowest gear a bit absurd.

Thursday Jun 13 #

7 PM

Biking 1:15:29 [1] 30.03 km (23.9 kph) +113m
shoes: Canyon Endurace

The debut of SpeedyBike™. After equipping my new Canyon Endurace with pedals and a bottle cage and inflating the tires, I set out for a ride to get acquainted with my new wheels. The bike itself is magnificent - carbon frame, electronic shifting, and a responsive feel. The seat needs adjustment, as its angle was uncomfortable. In general, the bike needs some fine tuning - repositioning of my seat in particular.

My first impressions are favorable, though any new bike with this level of groupset would feel fantastic compared to my ten year old 105 S11. The electronic shifting is definitely more responsive, effortless, and easier than mechanical, though the shifter struggled to shift to the big ring once or twice. The cassette is a 12-speed 11-34, which feels absolutely massive compared to my 11-28. I didn't know what to do with all the gears I had, and climbing was a breeze. I don't think I used my dinnerplate-sized granny gear. The geometry feels too relaxed, though that may change once I get accustomed to the bike, when I shift my seat backwards, and when I add my aerobars.

The bike is equipped with a 32 mm back tire and a 30 mm front tire, both of which are much larger than the 25 mm tires on my commuter bike. I ran them at the maximum listed pressure to minimize rolling resistance, but they felt quite comfortable. I didn't specifically notice that I was riding a carbon frame compared to aluminium, but the advantages may be more apparent after a longer ride. SpeedyBike ostensibly weighs 8.5 kg compared to 9.7 kg on my old bike, but this was hardly noticeable.

Overall, I'm quite pleased with SpeedyBike, and I look forward to many adventures with it.

Wednesday Jun 12 #

2 PM

Biking 33:34 [1] 13.37 km (23.9 kph) +5m

7 PM

Biking 1:53:10 [2] 42.95 km (22.8 kph) +3m

On my commute home, I decided to stop by REI to pick up some pedals for SpeedyBike. I left work with 80 minutes to travel about 31 km, and made it in 70 mins, including traffic lights. I then rode home at a more leisurely clip and stopped for a burrito.

Tuesday Jun 11 #

9 PM

Running 21:49 [1] 4.35 km (5:01 / km)

Monday Jun 10 #

10 AM

Biking 33:54 [1] 13.41 km (23.7 kph) +6m

Chain is skipping a bit under high torque loads from the big ring, probably because the drive train was cleaned and lubricated. I hope to get a month or so out of the sparkly clean drive train before I replace the cassette, chain, and chainset.
6 PM

Biking 33:16 [1] 12.83 km (23.1 kph) +6m

« Earlier | Later »