Good training after age 40! ~ Don't do training too much!

Good Training after age 40!

I usually run a few times a week last a few years and it might be a good for me.

I resumed running when I was 40 years old.
Originally, my goal was sub-3, which is less than 3 hours for full marathon.
I run about 200 miles a month to achieve the goal.
Unfortunately, I have not achieved the goal after 40 years old due to injuries.

I guess it was probably all right the first a few years.

However, I was getting old and my body cannot recover well in a short time.
That was the primary reason I kept injured.

The problem was once I got injured, I had to stop running for a while.
After resume the training, it took longer time to recover the original fitness level for a long time.

Key is to avoid injury 

Especially after 50 years old, it is very difficult to recover the fitness level before the injury.

Therefore, to keep a similar fitness level, I need to continuously train regular basis.

That is really the key.

Probably, it might be too much to run long distance every day for most of people who is over 50!

There might be some exceptions, but it might be true in general.

Tip for training after age 50!

Here is some tip based on my experience!

• Follow a training plan - There are many free training plans in the internet!
• Using some measurable index for training
• Having one or two resting days

Training Plan 

I am using a training plan in "Garmin Connect".  You need to register the web site, but there are many training plans and they are good to avoid over training.

Measurable index

Some model of Garmin Running device, such as Forerunners / Fenix, has a feature to show a recovery time based on the strength of training.  I guess it might be a conservative side, but it is probably good indication to have the next training for people who is over 50!

Based on the data, the typical frequency of training for me is somewhere around every 2 days or 3 days.

Resting days

Other than recovery time, I set at least one resting days once a week.

Good to have monitor your activities!

It is always good to have a way to monitor your activities!

I am using a Garmin Running device to monitor my activities.

A bit expensive, but there are many nice features!

It is a reasonable price.

This device is one generation older, but it is good enough and the price is very good deal!

Heart Rate Monitor ~ chest strap v.s. wrist sensor??

What heart rate monitor is good for hiking?

Chest-strap heart rate sensor

Embedded wrist heart rate sensor

There are a lot of devices which have heart rate sensors!!

Running devices, activity tracker, Apple watch and so on!

A several years ago, most of heart rate sensor for running was chest strap type.

Now, it is getting popular to use embedded heart rate sensor in a device.

I had a comparison about the accuracy!

Offset of measured heart rate between a chest-strap sensor and embedded wrist sensor

Offset of measured heart rate

I collected heart rate data based on my regular running exercise for a month.  I was wearing the both type of heart rate sensors, a chest-strap type and an embedded wrist sensor when I ran.

The chart above is the offset of the both measurements.  More than 90% of samples are within 4 (bpm).    This shows the embedded sensor is probably accurate enough for running and hiking.

Here is an example which has larger offset:

An example of larger offset 

The orange color is a data captured by a chest-strap sensor (with Garmin Forerunner 910XT).
In the middle of chart, there are some portion where the offset is bigger.  However the reading is more than 180 (bpm) which is probably way bigger for mild jog.  Therefore, I assume this data captured by a chest-strap sensor might be something wrong.

Another example is the the following:

Another bad example with larger offset

The blue color is captured by an embedded writ sensor (Garmin Vivosmart HR).  The early part, there are some spikes.  This data captured by an exercise using StarMaster in a gym.  It is hard to believe there is such spike during the exercise since the type of exercise won't introduce such narrow heart rate spikes.  Therefore, I assume this would be wrong reading by the embedded sensors.

Conclusion:The both sensors might have some wrong reading!

The both example shows there might be some wrong reading for the both sensors.  It is hard to identify the reason why the reading gets some offset.  Overall reading is matched well.   I think as long as contact between the sensor and body is good, the reading can be accurate.
My best guess is that if the contact is getting loose or dislocate a proper position to the body, the reading might be offsetting.

When people using a chest-strap sensor, it is probably easy to dislocate position due to a backpack.  I think that would be one of issue when I use the chest-strap type sensor during hiking.
Therefore, I would recommend embedded wrist sensor for hiking!

 

This device is with GPS function and it can track where you hike.

 

This device has pulse oximeter function, but no GPS.
It might be good to see your oxygen saturation which might be a good index for your body reaction of elevation!

Garmin Vivosmart 4 with pulse oximeter!

Garmin Vivosmart 4

I posted about Garmin fenix 5X Plus a few weeks ago.  I also found out that Vivosmart 4 was announced as well which has pulse oximeter function.  It seems that it will take a several weeks to get it based on information on Garmin web site.

The reason I am interested in this device is pulse oximeter function.  It seems that it is possible to measure SPO2 value during sleeping and  the price is USD $129.99 which is much lower than fenix 5 plus.  I saw some early reviews are posted on the internet.  However it is not very clear how often the device samples SPO2 value during sleeping.   I will try to get it and test it.

Garmin fenix 5X Plus ~ After some internet search ...

I mentioned I was interested in a new product from Garmin, which is fenix 5X Plus.  I did some search on the internet to look into review by some other people.

Here is the summary:
The pulse oximeter feature is supported in only "5X" model.  The other models are not supported.  I also found out Japanese edition does not support it at all. I am not sure why.....

The other things I found out is to look at SPO2 data on Garmin connect is not supported, either.  This product was announced some time the end of June this year.  It's been some time and it may supported now.  However, reports / reviews I checked mentioned it says the feature is not available.  I know Lactate threshold feature is not supported on the mobile application.  So I guess some special features which are supported a few specific model might not be supported.  This is probably in such category.  (Lactate threshold can be seen on the regular web site for Garmin Connect).

It also consumes a large power.  If people measure SPO2 value so often, then the total time to use the device with one charge would be shorter.  If people using this feature and GPS during hiking, the duration would be impact, especially this device also support embedded music player feature which also eats more power..... 
Based on a data I took from hiking on Mt. Whitney Trail a few weeks ago, the range SPO2 without  acclimatization is big.  Thus, it might be hard to find out a reasonable measured value if the sample size is small.  I think we probably need to sample more data to get average to evaluate the data in higher elevation without acclimatization.

Usage for Sleep apnea, it is also better to sample often to detect event of stopping breathing during sleeping.  For such purpose, it might be better to use a traditional pulse oximeter to collect data.

I concluded I would wait ./ watch how this feature would be supported.   For now, I have everything I need and I will continue to look into reviews by other people......

Garmin fenix 5 Plus (5XPlus) ~ This is really cool!

Garmin fenix 5X Plus (from Garmin.com)

I just wrapped reports for hiking to Mt. Whitney this year.   I was looking into some new product on the internet.  I found another new product from Garmin, "fenix 5 Plus" series.  This is really cool.  What I own is fenix 3 HR.  When fenix 5 was introduced, I did not really want to get it since not much new features were added and it was not really attractive for me.  However, this one "fenix 5 Plus" is really attractive for me.

The big one is they added Pulse oximeter function.  This means the device can capture all data I really want during hiking.  I do not have to carry a pulse oximeter to hiking anymore.  Also, it is easy to collect SPO2 value when I walk.  It is really helpful to collect more useful data for "smart hiking" I am writing in this blog.  This is really good one for hiking in higher elevation.

The price is a bit expensive, the low end model which is "fenix 5S" the price is starting from about $800 however, the pulse oximeter function is not supported.  It seems that the function is available for the high-end model 5X, which is starting from USD $850.  The model also includes map function, although the display might be too small to use the map function.  But it might be better than nothing.

So I am considering to get it some time in the future.  It might be hard to get it any time soon, but I really want to get it!  In a mean while, I will collect more information and review in the internet.
I think it is really good one for serious hikers who is looking for a GPS tracking device.

Smart Hiking (8) ~ Strength of activity for hiking

Example of heart rate trend

(Whitney Portal ~ Trail Camp in 2015) 

Impact of elevation

The above chart is an example of heart rate trend in higher elevation.   As you can see, the heart rate except resting above 9,000 feet (3,000 m) is more than 150 bpm.  This is a sort of high side.  Here is another data as a reference.

 Heart Rate during long run

This is a data when I ran for 3 hours.  The pace is not very fast, but the average heart rate is somewhere around 150 bpm.  To compare those two activity is not really easy.  During hiking, I had a backpack with all camping gears, however, the walking pace was really slow.  The strength is probably higher than the long run.   The heart rate is close to 160 bpm in some part.

What I try to say here is the impact of elevation, or lower oxygen environment, is probably much higher than people think.  The key is we need to understand this impact of elevation and manage the heart rate (pace) is really helping for better experience during hiking.

Also, the running example shows that I can run longer if I can maintain the heart rate somewhere around 150 bpm.

(To be continue)

Smart Hiking (5) ~ Heart rate base training

Running Watch (device) with GPS and Heart Rate Monitor

I wrote about relationship between elevation and heart rate in the previous post.   Today, I am talking about heart rate base training in running world.  This is slightly different topic from hiking, but it is better to know the concept of heart rate training.

Running device

Many runners use a running device which has GPS, heart rate monitor and other nice function nowadays.  It is really convenient to track all activities with a lot of data during the activities such as where they ran, distance of running, pace, heart rate and etc.  It also help to tell actual pace when they run in real time.

Since such device is getting very popular in running world, many people using the device to manage running pace and training.  There are so many training menu using heart rate since depending on what performance people try to improve, the intensity of the training is different.   For example to burn fat in the body, the intensity should not be high.  Low intensity with longer time of running would be much more efficient to burn body fat.  However to improve speed and lactate threshold, it usually require high intensity like interval training.  To set a target, "pace" was used in old days, something like 6 minutes per mile x 5.  However, it is hard to set a right pace for many people who is not really serious athletes.  Then the strength / intensity might be too high and it is due to an injury.  Or it is too easy to improve the performance old days.
Now many training many using "target heart rate" instead of "target pace".   It is much easier for many people to set a reasonable goal based on heart rate.

Heart rate zone
To set a target heart rate, there is a definition called "heart rate zone" which is a range of heart rates based on the maximum heart rate, sometime maximum heart rate with the resting (minimum) heart rate.  As long as people knows the maximum (and resting ) heart rate, it is easy to tell which heart rate range people need to maintain for each training.

One of simple example is based on ratio of the maximum heart rate:
- Zone 5 - 90% of the maximum heart rate ~ maximum heart rate
- Zone 4 - 80% ~ 70%
- Zone 3 - 70% ~ 60%
- Zone 2 - 60% ~ 50%
- Zone 1 - 50% ~ or less

Then to burn the body fat, zone 2 would be a good zone.  Typical marathon pace for many people is probably zone 3 or zone 2.   Many interval training can be zone 4 something like that.

The maximum heart rate can be find in a real high intensity activities or using an equation to estimate the maximum heart rate by age.  (A popular formula is "220 - age" [bpm])

Based on such heart rate zone definition, it is hard to maintain zone 4 for a long time.   Even zone 3, it is probably possible to maintain the range longer than zone 4.  But it is probably not easy to maintain zone 3 very long time.  To continue to maintain for very long time, it is probably better to stay in zone 2.   That is the idea.

Based on my experience, it is similar in hiking.  If the heart rate reaches zone 4, it is obviously impossible to maintain such high heart rate for long time.  Therefore, if we can maintain a pace in hiking based on this heart rate zone.  I think we can find a better pace for hiking.

This is the concept for "smart hiking" in higher elevation with heart rate.

(To be continue)

Garmin Forerunner 645

Forerunner 645

Forerunner645 is available!

I have not checked Garmin web site for a while and I found out Forerunner 645 is available. The price is USD $399.99.  The feature is probably between Forerunner 935 and 735.  Battery life is shorter than Forerunner 935.  Forerunner 645 is up to 7 days as a smart watch,  14 hours with GPS.

Overall, it is probably good enough for regular running and hiking purpose.   Major difference between 935 and 645 is "Training Stauts" and "Training Load" features that fenix 5 also has.

I have fenix 3 HR which does not have those features, but I do not believe they are really important features.  It is probably "nice to have" features.

Based on the price, price for Forerunner 735 is reduce to USD $349.99.  So 735 is attractive for price point of view. 

The other feature I found is this has "Garmin Pay".  It seems that it is a similar feature like "Apple Pay".  Garmin watch really becomes "smart watch" now.  For most of people, Apple watch might have more "nice feature", however for runners / hikers, I guess Garmin watch is probably better due to longer battery life.

For now, fenix 3 HR is probably good enough for me and I do not plan to replace any new product.  However, people who look for a GPS watch, it is probably worth to look around the new products.

Pace management with heart rate (4) ~ Heart rate during hiking

   The previous post was talking about required endurance for hiking.   Without enough endurance, it might be hard to achieve some hard hiking just managing the pace.   Today, I assume a person has enough endurance for a hiking, then how he / she can manage the pace for hiking.

   First of all, a target heart rate which is the upper limit of heart rate during hiking needs to be set.  As the previous posts are talking about heart rate zones to define a target heart rate zone.   Of course, the idea is to maintain the heart rate below the target, however there are some tips.  It is probably better to set an actual target 5 ~ 10 bpm lower than the upper limit since it is typically increasing the heart rate slowly even if a person walking with a similar pace.  In many cases, the intensity of hiking is typically high and it is probably hard to maintain a similar heart rate even if he / she walk a similar case.  Also, the trail slope can be vary and it is hard to maintain the heart rate in some steep sections.  It is probably better to have some extra margin not to reach the upper limit based on my past experience.
   It is also better to slow down significantly or stop if the heart rate reaches close to the upper limit or beyond the limit.  Once it is not immediately lower the heart rate with slowing down / stopped, then it is a time to take a rest with completely stop walking.  You may need to take a rest till the heart rate is get lower than "zone 1".  If it is not getting into "zone 1" in a short period of resting, it is probably better to lower the elevation if you hike higher elevation more than 12,000 feet in general.  If you want to walk without taking reset for a long time, you might need to set the actual threshold to adjust the heart rate much lower.  If your target zone is "zone 2", you might need to close to be lower threshold of zone 2 or zone 1.
   Another tip is to try keeping a constant heart rate as well as you can for easy hiking.   If your heart rate range during hiking is big, it is typically really high intensity when the heart rate in upper side.  In this case, you might feel hard in many cases.

(This is a summary for pace management with heart rate)

For detail, I will be almost ready to publish a Kindle Book about this topic very soon.  It is under review now.   I try to complete this this months and I will be announce it when it is ready.

Pace management with heart rate for hiking (2) ~ Heart Rate Zone definition

Heart rate sensor for running

   Regarding a method to define a target heart rate for hiking, I think one of good methods is probably based on heart rate zone.   However, there are a few different way to define heart rate zones and the range of the heart rate zone is vary depending on how it is defined.  For detail, I will plan to publish a kindle book to talk about a method to manage hiking pace with heart rate soon!

   As an example using my data, I am 51 years old now (as of December / 2017).   A typical formula to estimate the maximum heart rate is "220 - age".  Based on this formula estimated maximum heart rate for myself is 169 bpm.   However, based on the past training data, actual maximum heart rate for myself is 178 bpm.

Maximum Heart rate the past 6 months

(Based on the training data)

   If I use this value and calculate the heart rate zone, the value will be different.   To be safe, I assume the target heart rate is "zone 2" which is 60~70%.

• Based on the formula: 101 ~ 118 bpm
• Based on the actual value: 107 ~ 125 bpm

   Thus there is some gap around a several bpm between the two different maximum heart rate value.  Also, there is another method with reserved heart rate range which is using actual range of the heart rate.  The formula will be "(maximum HR - resting HR) * xx% + resting HR".   xx% would be 60~70% for zone 2.  We need a resting heart rate value and based on the training data in the past 6 months, my number is 59 bpm.

Resting heart rate in the past 6 months

   The calculated value for zone 2 would be:

• 130 ~ 142 bpm

   The last method is based on lactate threshold.   The variation is huge depending on how we define the heart rate zone.   Lactate threshold could be estimated the latest running device like Garmin fenix 3 HR.   My number is 165 bpm and zone 2 would be 134 ~ 146 bpm.  (The formula I use is from a web site which is 81% ~ 89% of lactate threshold heart rate)

• 134 ~ 146 bpm

   This method is higher side result.   If people do a training based on the heart rate, this range needs to be reasonably accurate.   Since the strength of training depends on the heart rate, therefore this value is really key for the training menu.   However, it is not really key to define hiking pace and I believe using lower side might be safer.

   Based on my training experience, 134~147 bpm which is calculated based on lactated threshold value, might be reasonable range for myself.  It is also reasonable result for my past Mt. Whitney hiking.  This is just my opinion and less than 120 bpm for myself is probably too low.  I think we must adjust based on the training / hiking data.

   There might be a couple things to apply this method in general.  One is people who are doing training regular bases and the other is people who are NOT doing training regular bases.   For the next post I will try to write my opinion how we need to think about the target value with the heart rate zones.

(To be continue ....)

VO2max Estimation by Garmin device

Garmin fenix 3 HR

which has VO2max estimation feature

VO2max

VO2max is one of performance factor for athletes.  Traditional way to estimate the number without special lab equipment is "Cooper Testing".   It is so called "12 minutes running".  Based on distance people can run in 12 minutes, VO2max can be estimated.
This number is also used for estimated marathon time.

Garmin Device can estimate VO2max

As I introduce a couple times in my blog before, the recent Garmin Running devices have a feature to estimate this VO2max number based on activities.   I think this is very good factor to see the progress of your training.

Actually, I have never measure my VO2max in lab before.  Therefore, I do not know the estimation by Garmin device is accurate or not.  But it seems that the number is close to the cooper test result based on my past data.  At least the absolute value of VO2max is probably not very important for most of people.   I think just having a relative comparison would be very useful.  As long as people using that way, the feature is really useful.  Even if we have some gap between the estimated value and the real value.

Benefit of the estimation by a device

For Cooper testing, people need to run really push to their limit, basically it should be "all-out".  This really high intensity training is probably really tough for many people except some serious athlete.   A good thing estimate by Garmin device does not requires really high intensity activity to get the number.  It requires to see the maximum heart rate and some accumulated activity data to get a reasonable numbers.  However after accumulating some activity data including some high intensity activities, even if an easy activities, we still can get some estimated number and it seems to be a reasonable.   I think this is a good benefit to get the number for each activities and understand the fitness situation.

This is one of features I really like in Garmin fenix 3 HR.

Heart Rate base pacing ~ Update

Switch back in early summer

in Mt. Whitney trail

This year, I did not go hiking to Mt. Whitney.  I do not have much update.  However, I found out some additional thoughts based on recent date for my running activities.   Today, I just share what I found recently.

A good heart rate number for hiking?

As I mentioned before hear rate zone around zone 2 and zone 3 would be a good range for hiking based on my past hiking records.  Depending on how we define the heart rate zone, a good range would be 60 ~ 80% of the heart range, which is really wide range  In a reality below middle of zone 3 which is around 75% of the range would be a reasonable.  In my case, the maximum heart rate is about 180 bpm and my resting heart rate is around 60 bpm.  With those data, 75% of the range is is around 150 bpm.   Based on the past experience, this is really reasonable value for me.

Recent Running training
Here is my recent update for my training, due to a large wild fire around Napa / Santa Rosa area, the air condition is getting really  bad last a few weeks.   Schools started no PE outside and I also did not run outside last a few weeks.   I only did station bike indoor to maintain my fitness level.

Due to my age, which is over 50 years old, I realized the fitness level is easily getting worse if I do not do training a several days.   This is obvious my past training records this year with stopping training due to injury and vacation.

This time I have not run outside for 2 weeks and then my estimated VO2max and lactate threshold by Germin running device was getting worst a little even if I was doing station bike a few times a week.
Muscle for running is different from station bike and load to my body for station bike is much lower than running.  I found out that my heart rate is really easy to get high within a short period.  The estimated lactate threshold is around 165 bpm by a Garmin device.  However, I probably need to keep it below 155 bpm if I need to run more than 1 hour.  In my case, there is no problem since I set my running pace based on the lactate threshold and 155 bpm is in zone 2 with lactate threshold heart rate.  (155 bpm is zone 3 with reserved heart rate zone and zone 4 with a ration of maximum heart rate.

This weekend, the scheduled menu was 3 times of 55 minutes running with 5 minutes resting (walking) .  I could not have enough time for 3 times and I just did 2.5 times with total time 2 hours 20 minutes.  I maintained my heart rate between 140 and 155 bpm.  The average speed was 8:45/km and the average heart rate was 149 bpm.  This is very slow but this is what I can do now.  This value including 5 minutes working in the activities.  Therefore actual running speed and heart rate could be a little better.  (I did not have a separate lap data this time)

A generic target

In my case, I already have a good target heart rate based on my past data.  I have no problem to manage my pace with that number.  On the other hand, it might be heard to define a generic guide line for other people since 150~155 bpm in my case is could be zone 2 ~ zone 4 depending how I define the heart rate zone.
The key point is where the lactate threshold heart late is in.  If you have high end running device which can estimate a lactate threshold, then the number would be a good reference for the target.  People just need to know how much lower they can set as a target.  If people has less training, then it could be better to set 6~10% lower than the lactate threshold.  If people are in a good shape, then it could be enough to set a few percent lower than the lactate threshold based on my past data.

If you do not have any idea where the lactate threshold is, this could apply based on the training activities.   A rough guide line could be using zone 2 if people do not have much training  and using zone 3 if people has a regular base aerobic training (at least more than 1 hour once a week).
Anyway, zone 2 could be a good range for "easy hiking" in general in my opinion.   The definition of heart rate zone could be good using a ratio of the maximum heart rate (220 - age) I think.  In any cases, important things is to collect more data during your training / hiking to understand your heart rate reaction during activities.

I published a Japanese version of book about the heart rate based pacing method for hiking.  I am still working on an English edition.  It will take some time to translate to English and it is not easy job for me....... 

Resting heart rate - Usage of Garmin fenix 3 HR

Heart rate trend on Sep 26

   Today's topic is a resting heart rate.  Previously, before I got a Garmin device which can monitor my heart rate 24/7, I used to check my heart rate right after I wake up.  Recently my Garmin device can monitor my heart rate 24/7 and it is easy to tell my resting heart rate.

   Based on the data, my resting heart rate is roughly 50~60 bpm.  This is also depending on a training progress.  If I stopped the training for a while, the number was going up.  On the other hand, when my training progress was getting good, then the number was going down.  The training I am talking here is an aerobic training.

   The other thing I found out recently is the number after a hard training or when I felt tired, then the resting heart rate is relatively higher.  The data I showed in the beginning is a heart rate trend on September 26 this year.   The resting heart rate right before waking up is about 52 bpm.   I also did an interval training after work.  That is why the heart rate in the evening is getting higher.

Heart rate trend on Sep 27

   The next day, the resting heart rate before waking up is 58 bpm.  The difference is small, but I can see a similar trend in the past.  The resting heart rate is usually higher if I have a hard training a day before.  Probably it is due to my age, I usually feel tired if I do a hard training a day before.  I guess the data for younger people might be different from what I see myself.   However, for my age, I guess it is probably better to take a reasonable resting to recover after a hard training.

   I expected to get a similar data on high altitude during a hiking like 14,000 feet elevation.  However, as I posted I could not go hiking this year and collecting / analyzing the data will be after next year.....   This would be an interesting data to understand my body reaction in high altitude!

Garmin fenix HR feature ~ Estimating Lactate Threshold / VO2max

Lactate Threshold Pace (Last 6 months)

Lactate Threshold HR (Last 6 months)

VO2max (Last 6 months)

Lactate Threshold Estimation on Garmin High-End Running device

   The last posting was talking about VO2 max for a factor of training progress.  Garmin started supporting this estimating feature most of running devices (above Forerunner 35).   My device, fenix 3 HR, supports to estimate Lactate Threshold (LT) as well.

   The devices shows LT with LT Heart rate and LT pace.   I did not have very good idea how I use the both data.  I did not have enough data to talk about my analysis before.  Now I have probably enough data to talk about LT feature.  As I explained my training activities last 6 months in my previous posting:

• April: Just finished "Full marathon level 2" training -- Good fitness condition
• May:  Due to injury late in April, I stopped running about 4 weeks
• June:  Resumed training, but stopped again due to FRU for 3 weeks
• July:   Resumed training, every other days 5km - 10km, rested for 1 week in the last week
• August - September: Started "Full marathon level 1", 3 times a week
• September -- my health condition is not very well last a several days

   Since last a several days in September, my health condition has not been very well, but I did not take a rest.  Therefore, my performance was not very well.  That is why I do see most of factors are dropped in September.

LT Heart Rate

   The range of LT Heart rate last 6 months is 163-167 [bpm].  The delta between the minimum and the maximum is only 4 [bpm].   My opinion, this is not much difference, but I think slightly improved due to the training a little.  Even if I stopped training, it was not really getting worse.  As long as I tried to do something regular basis, this might not change a lot.  Maybe people who does not have training for a long time, it may be improved with some regular based training.

LT Pace

   The range of LT pace last 6 months is 5:31 ~ 6:23 [MM:SS].   The delta is close to 1 minute.  If I stopped the training, the number was getting worse and once I resumed running, it was getting better slowly.  The trend is very similar as VO2max.

My analysis

   I think LT HR is probably not much change as long as people continue to training for long time　and LT Pace and VO2max could be a good factor to see the progress.  Either one could be used to measure the progress of the training.  Many models support VO2max estimation, but LT estimation is limited only some high-end model.   The high-end models have more nice features and the prices is much higher than other low-mid class models.   So if you just need a basic features, I think Forerunner 35/235 would be good.   Also 735 price is getting lower due to some other new models.

   The other factors, VO2max estimates works with the embedded heart rate sensor.  However for LT estimation, chest-strap heart rate sensor is requires.   Also, to estimate LT, people need to do relatively hard workout than VO2max estimation.  VO2 max estimation can be done with a light workout.  I am not sure how it is accurate.  But even I ran slowly, the value is a similar number as I did heard work out.   So with those factors, I would think VO2 max is probably more convenient in my opinion.

Good time for hiking ~ Minimize impact of high altitude sickness during hiking

Yosemite National Park (July/2016)

   It is mid July and this is a good time for hiking.   Kids started summer vacation in the United States.  I think many people plans to go hiking this summer.
   I keep posting about a method to manage hiking pace based on heart rate with a running watch, activity trackers.   Finally, I published a kindle book last April in Japanese.  I have been working on its English edition now.  This book is based on my past data for Mt. Whitney hiking.  Mt. Whitney is very popular destination for hiking in California.  (Japanese Edition -- High Tech pace management)
  There are some mountains over 12,000 feet, that many people easily hike, such as Mt. Whitney, White mountain, Mt. Dana (which is in the photo in this posting.  If you have a GPS tracking data with heart rate, please share your data for my further study.

   As I mentioned, I am working on the English edition, but it will take some time.  Therefore, I introduce a simple method in this positing.  Please try this if you hike high elevation.

1. Estimate your maximum heart rate from your age
   A popular formula to estimate the maximum heart rate by age is "220 - (age)".  As an example, I am 50 years old and my estimated value is "220 - 50 = 170".  So that my value is 170 (bpm).  This value may not be very accurate.  Since the maximum heart rate depends on each person depending on the fitness and regular training situation.  However, this value could be a good enough as a placeholder or starting point.  (This is not a generic,  this is based on my past data)

 2. Calculate heart rate zone
   The next step is to calculate heart rate zone with a spreadsheet software like MS-Excel.   The calculation is to get heart rate number in 50% ~ 100% of the maximum heart rate by 10% step, which is 50%, 60%, 70%, 80%, 90% and 100%.  They are used to define each heart rate zone, the zone 1 is 50~60% range and zone 5 is 90 _ 100%.   The following is an example of my case.

Example of heart rate zones

3. A guide line of walking pace during hiking.
   Based on my experience, we need to stay in zone 3 which is 70~80% of the maximum heart rate or lower.  In my case, 119 (bpm) ~ 136 (bpm) or lower.

4. Heart rate monitor
   People can use an activity tracker, running watch with GPS, Apple watch to monitor your heart rate during hiking.   One for running, it usually has a feature to notify with alarm or vibration if the heart rate is out of a range people set.  This is really convenient feature to manage the walking pace during hiking.

5. When the heart rate is out of range, it is getting higher than the maximum limit.  Then, people need to slow down or stop to lower the heart rate.  If the duration over the limit is getting higher or the heart rate stays higher, I think it is time to take a rest to lower the heart rate.   If the heart rate is not getting lower with a rest, I think it is a sign to consider to stop hiking.  Especially, people feel some headache, nausea and etc, it is safe to stop hiking at that point.  Even people do not feel anything wrong, but the heart rate is staying high is probably a sign to stop hiking in many cases.


  In many article to minimize the impact of high altitude sickness, it is better to walk slowly.  However it is not very clear how slow.  This is a good method to define the pace with clear guide line.  I think this pace might be too easy especially in the beginning of hiking.   However, there is some gap between your feeling and actual situation of your body.   Therefore, it is better to see your heart rate is one of clear factor to understand your condition / situation.

   Please share your experience and data if you try this method.  It will help my further study on this topics.

   Enjoy your hiking this summer!

An example of usatg for Garmin fenix 3 HR ~ Estimation of Lactate Threshold

Lactate Threshold on Garmin Connect

   The previous posting was beginning of June, so that it's been for a while.   After the injury was getting better, I just resumed running, however, I got really bad flu and I stopped running for 3 weeks due to the flu.
   I am not fully recoverd, but I resumed running last Saturday.  I ran for 90 minutes, but the pace was really slow and I only ran 11 km.   Then, I was pointing about function of Garmin fenix 3 HR, I keep my eyes on the VO2max and Lactate threshold estimated by the device.  For VO2max, as I reported, the number was dropped to 36 [ml/kg/min] and a little recovered to 39[ml/kg/min] after I resumed running late last month.  After 3 weeks of resting, it was dropped to 38[ml/kg/min].  Probably, the ratio of dropping was slowing down and even if I rested for 3 weeks, the actual dropping is very minimum.
   However, the lactate threshold is a bit different.  The Garmin device provides 2 numbers, one is heart rate and the other is pace.  I am not really sure what the relationship for those 2 numbers.  Based on my recent data, the heart rate value is almost the same which is around 164[bpm], however the pace is slowly dropping.   It was 5:40/km in March, but now it is dropped to 6:28/km.  It is about 1 minute dropping.  Actually, I felt my breath is getting higher than before even with slower pace.  The number is probably indicates that situation.   To see my training progress, it is probably good to monitor those 2 numbers, VO2max and Lactate threshold especially the pace.  I will post how those numbers get improved.

   Before the injury, I had done a level 2 of full marathon menu.  But I guess it is better to back to level 1 after a few weeks of slow jog.   I am thinking to run every other days since I just resumed running after flu.

Mt. Whitney Hiking 2017 (9) ~ Training using Garmin fenix 3 HR

VO2max value is recovering

   As I mentioned in a different topic, I got injured my right leg and I just resumed running about two weeks ago.  This is a training not only for a marathon, but also for hiking to Mt. Whitney as well.  Running is one of a good training to improve my aerobic performance for hiking.

   Due to the injury, I stopped running for a month and my VO2max value is down from 43 to 36 [ml/kg/min].  This drop is significant performance down.   After 2 weeks of running, the number is getting better and it is 39 [ml/kg/min].   The first 5 days, I only ran 2 miles, then increased to 3 miles and this week is about 4.5 miles.   The average pace is also getting improved.

   Since I just resumed running, I tried not to run fast.   I tried to stay "slow pace", but the course selection, I tried to include some hilly sections.  This will helps to train muscle for ascending.   I think this VO2max is one of good factor to monitor my training progress.  At least I can tell my training is on track to recover from the injury.

Lactate Threshold

   On the other hand, the lactate threshold is not improved like VO2max.   However, I tried not to run faster.  Therefore, once my body is adopted for the pace.  I might not reach a point fenix 3 HR cannot detect "lactate threshold"  because the pace is not fast enough to hit the threshold.   This is probably true.  Because right after resumed running, my heart rate jumped close to my maximum heart rate value.   However the heart rate is getting stable with the current slow running pace after 1 week.

  I will monitor those two factors as index of my training progress.

Resting

   Another factor, I do care now is resting.  Since I just resumed running and I am not young any more.   I try to take more rest day than usual to avoid another injury.   So my current training schedule is 2 day running and 1 day resting.   Then I try to increase total running time slowly.   I think this is a key to avoid injury, especially people who have not been training for a while.  My first goal is try to recover my VO2max to more than 40 [ml/kg/min] first.  Then I will resume more speed (threshold running) to improve my fitness performance.

Pace management for Hiking with Heart rate ~ looking for more data

Mt. Whitney

   As I mentioned a couple times about a method to manage hiking pace based on heart rate.  I had published a Japanese edition a few months ago.   I have been working on the English edition now.  The book is based on just my experience.   I am looking for data from others, not only myself.

   Today, I am writing to ask people who read this blog to share other hiking data with GPS, especially Mt. Whitney and Mt. Shasta.  The both mountains are very popular destination for hiking in California.   Please let me know if somebody willing to share the data.   For people who have a Garmin device, I prefer to get "*.tcx" format.  For people who have a device from other vendors, I prefer to get "*.gpx" data.

   Based on my experience, I can see a significant pace down around 10,000 feet elevation.  I want to understand what the generic trend is.   This helps to understand what I am writing is really reasonable to apply to everybody.

Garmin Forerunner 935 was announced on the web

Garmin Forerunner 935from Garmin US web site

   A several days ago, I checked Garmin US web site and I found a new model "Garmin Forerunner 935" was announced.   I am not really interested in the new model since I just got "Garmin Fenix 3 HR" late last year and I did not plan to get any new model any time soon.   However within a several months, fenix 5 was announced and it is available now and now Forerunner 935 is announced.   I am just interested in what's new.   The price is from USD $499.99 to 649.99.  The price difference is if heart rate monitor(s) are bundle or not.

   One of big improvements is a battery life.  For Forerunner 735XT is up to 14 hours in the GPS mode, now Forerunner 935 is up to 24 hours which is the same as Fenix 5 series.  It is a big pulse for hikers.  It is also longer than Fenix 3 HR which is up to 16 hours.   The water registrant is 5 ATM, on the other hand, Fenix series is 10 ATM.   However it is probably not a big deal for using not in water.  The price of Fenix 3 HR was adjusted to USD $549.99, however 935 is USD $50 lower, which is very attractive with some other new features.   I guess it would be one of good selection people who are thinking to buy a new GPS watches.

   It is usual facts that newer product introduce every several months.  It might be hard to decide when would be a good time to buy a new product.   One think I can tell is if people who use the previous generation of the products which does not have a feature to pair with a smart phone, I guess it is a good time to replace it to the current generation even if the current one is functional.  I am pretty happen to replace my old Forerunner 910XT to Fenix 3 HR.  I think it is very convenient especially with an embedded hard rate monitor.