Marathon Training – Week 1

This week I have run 8.31 miles over 4 runs. I'm fairly pleased with my progress as I hadn't intended to go over 2 miles for the first couple of weeks but was feeling good on Sunday when I got a mile from home so decided to go a little further. I thoroughly expected to be broken when I stopped but seem to be fine. Assuming this baby doesn't arrive next week I'll be aiming to do 3(ish) miles 4 times.

This weeks runs

1. Tuesday – 1.45 miles

2. Wednesday – 2.37 miles

3. Friday – 1.6 miles

4. Sunday – 2.89 miles

This weeks rides

None

Weight

Currently I weigh 14 stone 10.25 pounds which given my height of 5'9'' gives me a BMI of 30.45 which means I am still obese (but only just).

My weight is …

… more than it should be and I will be posting it here every week or so as an incentive to keep training and hopefully loose some (or lots if the NHS is to be believed) weight. I am training for the Great North Run in September 2011 and hopefully the London Marathon in April 2012 although I haven't got a confirmed place in the London Marathon yet. 

Currently I weigh 14 stone 12.25 pounds which given my height of 5'9'' gives me a BMI of 30.75 which means I am obese (but only just).

According to the BMI thing my BMI should be between 18.5 and 24.9 meaning I should roughly weigh between 8 stone 13.25 pounds and 12 stone 0.75 pounds. So my 'ideal weight' is the middle of that range which is 10 stone 7.25 pounds. This means to hit my 'ideal weight' I need to loose 4 stone 5 pounds. So there is a goal for me! 

I am using 'Map My Fitness' to record my training if you are at all interested you can see my profile here but you'll have to sign up and add me as a friend to see anything useful. 

Drowning Doesn’t Look Like Drowning

This article was written by Mario Vittone I have re-posted it here because everyone should read it. Especially parents and especially parents of kayakers, and other watersports participants, where there is a (hopefully) high chance that their child will follow their passion for being in the water. The original article can be seen here

The Incident – The new captain jumped from the cockpit, fully dressed, and sprinted through the water. A former lifeguard, he kept his eyes on his victim as he headed straight for the owners who were swimming between their anchored sportfisher and the beach. “I think he thinks you’re drowning,” the husband said to his wife. They had been splashing each other and she had screamed but now they were just standing, neck-deep on the sand bar. “We’re fine, what is he doing?” she asked, a little annoyed. “We’re fine!” the husband yelled, waving him off, but his captain kept swimming hard. ”Move!” he barked as he sprinted between the stunned owners. Directly behind them, not ten feet away, their nine-year-old daughter was drowning. Safely above the surface in the arms of the captain, she burst into tears, “Daddy!”

How did this captain know? – from fifty feet away – what the father couldn’t recognize from just ten? Drowning is not the violent, splashing, call for help that most people expect. The captain was trained to recognize drowning by experts and years of experience. The father, on the other hand, had learned what drowning looks like by watching television. If you spend time on or near the water (hint: that’s all of us) then you should make sure that you and your crew knows what to look for whenever people enter the water. Until she cried a tearful, “Daddy,” she hadn’t made a sound. As a former Coast Guard rescue swimmer, I wasn’t surprised at all by this story. Drowning is almost always a deceptively quiet event. The waving, splashing, and yelling that dramatic conditioning prepares us to look for, is rarely seen in real life.

The Instinctive Drowning Response (IDR) – so named by Francesco A. Pia, Ph.D., is what people do to avoid actual or perceived suffocation in the water. And it does not look like most people expect. There is very little splashing, no waving, and no yelling or calls for help of any kind. To get an idea of just how quiet and undramatic from the surface drowning can be, consider this: It is the number two cause of accidental death in children, age 15 and under (just behind vehicle accidents) – of the approximately 750 children who will drown next year, about 375 of them will do so within 25 yards of a parent or other adult. In ten percent of those drownings, the adult will actually watch them do it, having no idea it is happening (source: CDC). Drowning does not look like drowning – Dr. Pia, in an article in the Coast Guard’s On Scene Magazine, described the instinctive drowning response like this:

"Except in rare circumstances, drowning people are physiologically unable to call out for help. The respiratory system was designed for breathing. Speech is the secondary or overlaid function. Breathing must be fulfilled, before speech occurs.

Drowning people’s mouths alternately sink below and reappear above the surface of the water. The mouths of drowning people are not above the surface long enough for them to exhale, inhale, and call out for help. When drowning people’s mouths are above the surface, they exhale and inhale quickly before their mouths start to sink below the surface again.

Drowning people cannot wave for help. Nature instinctively forces them to extend their arms laterally and press down on the water’s surface. Doing this permits drowning people to leverage their bodies so they can lift their mouths out of the water to breathe.

Throughout the IDR, drowning people cannot voluntarily control their arm movements. Physiologically, drowning people who are struggling on the surface of the water cannot stop drowning and perform voluntary movements such as waving for help, moving toward a rescuer, or reaching out for a piece of rescue equipment.

From beginning to end of the IDR people’s bodies remain upright in the water, with no evidence of a supporting kick. Unless rescued by a trained lifeguard, these drowning people can only struggle on the surface of the water from 20 to 60 seconds before submersion occurs". Source: On Scene Magazine: Fall 2006: 14

This doesn’t mean that a person that is yelling for help and thrashing isn’t in real trouble – they are experiencing aquatic distress. Not always present before the instinctive drowning response, aquatic distress doesn’t last long – but unlike true drowning, these victims can still assist in their own rescue. They can grab lifelines, throw rings, etc.

Other signs of drowning on the water:

  • Head low in the water, mouth at water level
  • Head tilted back with mouth open
  • Eyes glassy and empty, unable to focus
  • Eyes closed
  • Hair over forehead or eyes
  • Not using legs – Vertical
  • Hyperventilating or gasping
  • Trying to swim in a particular direction but not making headway
  • Trying to roll over on the back
  • Ladder climb, rarely out of the water.

So if a crew member falls overboard and everything looks OK – don’t be too sure. Sometimes the most common indication that someone is drowning is that they don’t look like they’re drowning. They may just look like they are treading water and looking up at the deck. One way to be sure? Ask them, “Are you alright?” If they can answer at all – they probably are. If they return a blank stare, you may have less than 30 seconds to get to them. And parents – children playing in the water make noise. When they get quiet, you get to them and find out why.

You can also follow Mario on Facebook and Twitter

JavaScript parseInt() Octal Mode

I spent a good deal of time today trying to work out why some maths in a script I was writing was not working. The script in question doesn't do anything particularly complicated but kept going screwy whenever an 8 or 9 was entered into one of the numeric fields. Turns out this was due to a peculiarity in the use of the parseInt function of JavaScript. It should be noted that it isn't a bug … parseInt performs this way by design.

I was using parseInt to convert form fields read using JQuery into proper integers. As the integers in question are part of a time I was zero padding them … so 8 is 08 and 9 is 09. Turns out that the parseInt function used in it's simplest form:

parseInt("08");

thinks the leading zero indicates that the number is an octal integer and as octal using the digits 1 – 7. 8 & 9 are invalid so are interpreted as 0. This issue can be easily avoided by using parseInt fully and specifying a radix:

parseInt("08", 10); // Force use of base 10

You could of course use Number instead. I am not sure of the performance advantages / disadvantages of each method but historically have always used parseInt or parseFloat rather than Number. This feature isn't present in parseFloat. In this case I converted the script to use Number and all seems well now.

Update: So I have completely refactored the script for a couple of reasons but it is now uploaded here. I have gone back to using parseInt and parseFloat but to ensure no issues am specifying a radix for each use of parseInt.