Gear review: Salomon Advanced Skin S-Lab Belt

June is bonus season at my workplace. And this year, I've worked damn hard and I'm going to spend a little of it on me instead of the boring 'mortgage' option.

And it just so happens that I was looking around for a hydration belt, because my 2 litre Camelbak Rogue is a bit over the top for some of the shorter trail runs I'm doing, and even my 26km Friday run to work now that winter's here, and carrying more than ~500ml of water isn't really necessary. 

Whilst there are plenty of good options out there (check out thisfishcanrun's review of one of UltrAspire's models), a non-negotiable for me was the ability to carry my Ay Up head torch for when my run will cross over from dark to light conditions. (The Ay Up was another 'bonus month' purchase. I'd review it but I don't know what else I'd say except that it's really frickin' bright and if you can afford one, get one.)

'Headtorch compatible' somewhat limited my options. Enter the Salomon Advanced Skin S-Lab Belt. Like the Ay Up, though, it's pricey. I got mine at Footpro in Malvern and it was $80 including one 237ml bottle, with another bottle costing $25. Subtract my 10% repeat customer discount and all up it cost $95.

The belt itself is made from the same lightweight material as the Advanced Skin packs everyone is raving about. It comes with six pockets in total: two larger ones at the 'back' (although the 'back' could easily be worn at the front), and two smaller zipped pockets plus two more pockets in front of them, at the front.

The 'back'

The 'front'

The inside

The back pockets are designed to take the 237ml bottles, which are the new 'soft flask' models made for Salomon by Hydrapack. The beauty of these bottles is they collapse as you drink from them making them (a) quite light and (b) small enough after a couple of sips to fit in the smaller front pockets, meaning my head torch can fit into the larger rear pocket when dawn breaks and I don't need it anymore.

With the first Salomon Trail Series race at Studley Park this Sunday, I switched my long run to this morning and tried out the belt. 

I loved it.

First, this is what it carried, with room to spare:

The feel was terrific. Once on, it settles into a tight fit, with no bounce. I didn't even register it being there, really. In fact, at one point, I reached behind me to make sure my head torch and bottle were still there because I couldn't feel them! Getting items in and out of pockets took a couple of tries, but I figured it out pretty quickly and after that it was a breeze accessing the water bottles. When it came time to take off my head torch I was able to quickly rotate the back to the front, stuff it in a pocket and rotate it back again, without breaking stride.

The only fault I can identify is the way the front and back attach to each other. There are these two loops and two clips which are a bit fiddly, especially with cold fingers. If you were in a race and needed to take it off and put it back on at a checkpoint, you could lose a bit of time.

The two clips (bottom) and two loops (top).

But really, that's a small complaint, because you wear a hydration belt to have it on, not to have it on, take it off, put it back on, etc.

Overall, I'm a big fan and I'm pleased I got it. Like the Ay Ups, if you can stand the price tag, I'd definitely recommend getting one.

Pros:

Light, 'don't know it's there' feel
Versatile front and back fit, and easy to switch between those two options on the run

Plenty of storage

Soft flasks

Cons:

Price tag

Clumsy attachment clips

Tan Time Trial

Yesterday's intervals result was staring me in the face. I averaged 3:52/km over the 5x1000, albeit with 250m recovery jogs between intervals.

But still, that kind of pace could see me tick off one of my running goals - a sub 15 min Tan time trial.

My PB to date was an agonisingly close 15:00.66, in May last year before my hip started playing up and I lost the best part of six months. Was I in that sort of form again? There was only one way to find out, but I knew what it meant: pain.

This. Was. Going. To. Hurt.

I looked up my splits from last year:
3:45
3:59 (through halfway in 7:25)
4:03
3:14 (for 0.86k)

Even though the official distance is 3.827km, last year my Garmin showed 3.86k, although I stupidly didn’t take the best racing line. Over 3.86k, I worked out I need to be averaging 3:53. Pretty much 'interval pace', with no recovery jogs in between kms!

I toe the line. Go.

First km down, 3:46. 1 second slower than last year. Already on the limit, but 7 seconds up against the average 3:53 pace required.

But now my watch is telling me I'm doing ~4:30 pace up Anderson Street. Doubts are starting to creep in. I'm losing too much time. 

I recover and I'm through half way in 7:26, again, one second slower than last year.

The 2^nd km is 4:00. My buffer over the goal pace is gone.

For a fleeting moment I actually consider stopping. "I can't do this. I'm already slower than last year and I feel like crap. I'll try another day." "No, you won't!" comes back the response, and I keep going.

The one positive is I know it’s almost all downhill from here, but last year’s 3^rd km was a shocker – a 4:03 despite the gradient.

No such problems this year. I pull out a 3:53 and I know I just need to beat that pace with the biggest downhill section ahead of me. Knowing I ran yesterday's fifth 1000m over pretty much the same section of the Tan, in 3:48, is a big boost.

I stick as tight as possible to the inside, any on-comers have to move over for me, I’m not moving for them. Meters could matter.

My watch is showing sub 3:50 pace with 500 to go, then sub 3:45 with 250 to go. I’ve got this. It’s weird but throughout the whole time trial, I don’t remember looking at the race time apart from halfway, it was all about the pace.

I cross, this time 3.84km showing, and more importantly, 14:42.16. I averaged 3:38 pace over the last 840m.

A sub 15 lap. Finally.

Tick.

[I'm not sure I could have done it without the strength I've built up as a result of the numerous training runs in the hills with the Dandy Trail Runners, so a big thanks to everyone from that group!]

Intervals

Intervals.

I hate you. 

I love you.

No other training session results in a war between Present Me and Future Me quite like intervals do.

Present Me is sitting at my desk, thinking "Am I really going to put my running gear on for the express purpose of inflicting pain on myself? Forget it."

Future Me is countering: "But I'll feel goooood after it's finished. I'll be proud and I'll be buzzing all afternoon. It's the most rewarding training run of the week."

And on it goes, until (usually, hopefully) Future Me prevails.

It happened this afternoon, of course. I didn't want to go out. I did want to go out. And I'm pleased to say, Future Me won the day. 

One of my goals is to run a sub 40 minute 10km. So my intervals are purposely hard (relatively speaking, of course): 5x1000m, aiming for less than 3:50 in the first and last, and less than 4:00 in the middle three, with a 250m jog recovery between intervals, at around 5:30 pace. My aim is therefore to have the session over (a total of 6km), in less than 25 minutes.

Today was a good day. I managed:

3:43 (my fastest ever 1000m)

3:53

3:57

3:57

3:48

And finished in 24:47 (a personal record).

And I was buzzing all afternoon.

Thanks, Future Me (who I suppose is now Historic Me).

Snapping out of it

I had a bad training week last week. One run - a solid 9k lunchtime run with a friend in 42 minutes something. 9k, when I aim to average at least 50 over the year.

I don't really know what happened. My ideal week at the moment looks something like this:

Mon or Tues: 5x1000m with 250 jog recovery between intervals. Aim to have the session over in 25 mins or less. If it's Monday, rest on Tuesday, and vice-versa

Wed: 7.5k tempo run. Aim for 4:15-4:20 pace

Thurs: 9k moderate pace, hopefully with a friend of mine if our diaries line up

Fri: 26km run in to work along the Gardiners Creek and Capital City Trails

Sat: rest

Sun: 1.5-2hr trail run. Lets say 17k, but could be more or less. 

That's about 65k. Sometimes I'll miss one or two of those runs for whatever reason, but last week I missed four out of five. Public holiday Monday, too busy at work Tuesday, blah blah blah. Not good enough, particularly with the first race of the Salomon Trail Series coming up in two weeks. (I'm doing the three Melbourne-based races in the mid-distance category.)

It's also not good enough if I want to achieve my list of running goals I have pinned up at my work:

1. Sub 15 min lap of the Tan

2. Sub 40 min 10k

3. Sub 55 min Puffing Billy

4. Sub 90 min half marathon

5. Sub 3:30 marathon

6. Sub 6:30 Two Bays 56km

7. Complete a 100km ultra.

Here's to getting back on track...

(Today ended up being a 'no run' day, so it's intervals tomorrow)

Welcome to Into The White

So on the advice of a friend I've decided to start this blog called Into The White. I'm not really sure what exactly, or how often, I'll be writing, but it'll mostly be about running. I say mostly, because there may be occasions when I'm taken by a whim and share my thoughts on matters outside the sphere of training runs, gear, races, etc.

Why 'Into The White'? I hear you ask ('you' that is, my currently non-existent dear reader). Well, fans of a certain band from Massachusetts might recognise the name of one of their songs and yes, I am a fan of that track, with its ambiguous meaning, and Kim's vocals in front of a wall of sound (seeing it played live was spellbinding).

But when I was thinking of a name, this song came to me because I think it's how I'd describe what I'm searching for sometimes on those runs, be it on the trails, roads or Tan. Into The White, where you block out whatever it is that you don't want to focus on, when you enter this state of mind and gain this sort of... clarity. Into The White, where it's just the beating of your heart, driving of your legs and your mind. Not every run is like that (in fact, most aren't), but when it is, I wish I could bottle it.

A little about myself. I'm a soon to be 34 year old guy with a beautiful wife and two boys (3yo and 1yo) who are the light of my life. I've been running since March 2010 and would like to consider myself a 'first half of the field' kind of guy for harder events (Roller Coaster 43k) , maybe top quartile for marathons and top 10% for more 'mass participation', events (Run for the Kids, Puffing Billy, etc), although each race is different. 

May 2012 was probably my peak, but then I had some hip problems and lost the better part of 6 months. Since then I've been working my way back and I'm probably where I was last May, maybe even a little ahead. I've got some goals (more on that in another post to come) which will hopefully drive me to bigger and better things.

But make no mistake, I'm largely a weekend (or lunchtime) warrior and I'm sure the more serious athletes would look on in horror (or pity) at the way I approach my training, nutrition, and race planning.

The last phantom question I'll respond to is 'why did you start this blog?' I guess I've always liked writing (but never been remotely good enough to be a writer), and a friend suggested that I might find writing about running to be fun. Hopefully he's right.

See you out there.

Nick