Hi,
>> >
>> > https://sites.google.com/site/compendiumofphysicalactivities/Activity-Categories/bicycling
>> >
>> > However, the MET value is not per training session but per sport, which
>> > is problematic.
>>
>> > I have set the MET of bicykling to 9.0 after considering
>> That's right. To be honest it looks pretty complex to change MET's
>> value according how hard sessions are, not really sure which way to go
>> in order to overcome the issue...
>>
>> > Another problem is that the calorie counter function seems to use the
>> > total time, not excluding pauses recorded by Forerunner 305.
>>
>> For tracking purposes, following link leads to how Calories (kcal) are
>> currently calculated in pytrainer:
>>
>> http://sourceforge.net/apps/trac/pytrainer/browser/pytrainer/trunk/pytrainer/gui/windowrecord.py#L647
>>
>> > When I compare the calorie counts of two training sessions, I got weird
>> > results:
>> >
>> > Case 1. bicykling, duration 1:42, 44 km, average pulse rate 144 => 594
>> > Cal
>> > Case 2. bicykling, duration 2:32, 39 km, average pulse rate 130 => 1188
>> > Cal
>> >
>> > Case 2 had a reported total time of 1:55 according to Forerunner 305.
>> >
>> > 1. Is the duration problem due to my use of garmin-forerunner-tools as
>> > import plugin? Should I use something else instead?
>>
>> I would say the issue is not on your side, but on pytrainer's one. As
>> far as I understand the way Calories are being calculated (see link
>> above), it takes the complete activity duration and this is not
>> correct.
>>
>> Newer versions do show workout's status in register tab
>> ("active/paused" I guess, not sure since I have it ES localized) so it
>> shouldn't be too difficult to retrieve those values and compute more
>> accurated energy value.
>>
>> > 2. It seems as if the average pulse rate is not taken into account
>> > when the Calories are calculated, but why is that?
>>
>> To be honest, I don't know. I guess somehow pulse should be included
>> in MET when calculating energy using basic formula, but as we have
>> just one MET per sport so far, then it would be congruent to have
>> another variable to stress intensity. Any ideas or written literature
>> about how to tune MET based in average heartbeat? I think it would be
>> the simplest approach here.
>
> It is an interesting topic. I found the following document:
>
> http://www.myfitnesspal.com/blog/Azdak/view/calories-burned-during-exercise-it-s-the-intensity-not-the-heart-rate-that-counts-26524
>
> There it is stated that the MET does NOT depend on the heartrate. But as far
> as I understand it should depend on the type of exercise. In the case of
> running and cycling on a flat ground, I guess it should be mainly a function
> of the speed. But in general it should also depend on the change of
> elevation.
What I understand from it is MET (objective/fixed intensity) remains
the same for everyone (same slopes, etc.) and the only variable that
influence energy consumed is weight. He plays with the relative
intensity concept (measured with Heartrate and VO2 max) that can
change through training.
> I propose the following:
> 1) Confirm the correctness of this article.
To be honest it is beyond my knowledge to confirm if this article it's
correct or not.
> 2) In the cases of cycling and running: Try to find a formula to express MET
> in terms of GPS data and the type of sport (it should depend on speed and
> incline). So MET it time-dependent. When resting (more precisely: lying),
> MET should be 1. Therefore one may possibly use a fixed value for the
> resting times, probably close to 1. Then one can calculate the energy
> (calories) burned using these "local" METs, which involves basically summing
> up the METs.
I find your proposal very interesting, but pretty complex to
implement. I would go for a simpler one: each sport has one default
MET and interested users would be able to change it (based on their
own criteria) on per session ('Advanced' tab when editing entry) in
order to achieve more accurated figure for his/her training session.
What do you think?
BTW, looking at some documents from the American College of Sports
Medicine, they use another formula for Calories burned:
Calories/min = 3.5 x MET x Weight (kg) / 200
Another topic I want to highlight is that currently there is no
support in Activity class for "active" duration, although it impacts
also paces computations (see
http://sourceforge.net/apps/trac/pytrainer/ticket/103). What I have
seen so far is that figures shown in "Register" tab are calculated "on
the fly" (see
http://sourceforge.net/apps/trac/pytrainer/browser/pytrainer/trunk/pytrainer/gui/windowmain.py#L356)
but not saved, so can not be retrieved (but again calculated) if
needed somewhere else. In addition, we would need to recalculate paces
already present in database taking only active time into account.
Not sure how to approach last issue the best way, but if we store new
data in database, it means changes in database schema, migration
scripts, new field in Activity... bufff... time for a beer! ;)
Regards,
David
------------------------------------------------------------------------------
FREE DOWNLOAD - uberSVN with Social Coding for Subversion.
Subversion made easy with a complete admin console. Easy
to use, easy to manage, easy to install, easy to extend.
Get a Free download of the new open ALM Subversion platform now.
http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Pytrainer-devel mailing list
Pytrainer-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
