Bike Fatigue & Peak Trends giving errors in console since v3.5 1804.

[Tim Sinclair]

I've been using GC for about 9 months and have previously been using the 'Fatigue Profile' trend, 'Peak' trend & 'Fatigue' trend. Since the latest release they stopped working
I was alerted to the fact that NP no longer exists and has been replaced replaced by IsoPower, so was able to get the 'Fatigue Profile' working again by correcting the entries in the R console.

I am now left with errors in the 'Peak' trend which says that 'function 'lm' cant be found': Has that also been renamed?
## linear regression

lm<-lm(yp~xp)

abline(lm, col="white")

text(x=100, y=400-count, col=color,

labels=paste(seasons$name[[index]],

" slope=",

round(lm$coefficients[[2]],3)))

 

## track slope to compute average

slopesum <- slopesum + lm$coefficients[[2]]

I'm also left with an error in the 'Bike Fatigue Profile' trend which says it can't open 'stats.dll' in the x64 folder  - saying the specified module could not be found (see screenshot of R console above) . The 'stats.dll' file does exist on my PC at that location - I've checked....

Any help in resolving the errors in 'Peaks' and 'Bike Fatigue Profile' would be very welcome :-)

GOLDEN CHEETAH ROCKS!

[Tim Sinclair]

For 'Bike Fatigue Profile' I have the latest version :
Bike Fatigue Profile

Last Edited At: 2018-04-25 - Creator: Edouard

Updated version of the Cyclist Fatigue Resistance Profile Based on Allen and Coggan (2010) Training and Racing with a Power Meter: 2nd Edition. This version will only work with GC v3.5-DEV1804. I would like to thank Manuel and Otokarz for their comments on this fatigue profile graph. The Normalized Power NP variable was replaced by the IsoPower variable in order for it to work in this version of GC. Indeed, TrainingPeak varaibles are not available anymore in GC due to copyright. This Fatigue Resitance Profile should complement the Cyclist Power Profile. For each metabolic level, powers of longer durations are expressed relative to a power of a shorter duration. Level 7 - Noromuscular power: 10s and 20s power relative to 5s. Level 6 - Anaerobic capacity: 1min and 2min power relative to 30s. Level 5 - VO2max: 5min and 8min power relative to 3min. Level 4 - Lactate threshold: 60min and 90min Normalized Power (now IsoPower in GC) relative to 20min power. The color scale represents the fatigue resistance levels according to Allen and Coggan (2010). There are five fatigue levels for Level 7 and 6 as power is highly variable for those levels: Well-Below-Average Fatigue Resistance, Below-Average Fatigue Resistance, Average Fatigue Resistance, Above Average Fatigue Resistance, Well-Above Average Fatigue Resistance. There are only three fatigue levels for Level 5 and 4 as power is less variable here: Below-Average Fatigue Resistance, Average Fatigue Resistance, Above Average Fatigue Resistance. For each metabolic level, the metabolic level and your fatigue resistance level will be indicated in yellow at the top of each graph. The reference power for each metabolique level will be indicated in white. When your fatigue resistance levels are located within Allen and Coggan's limits (2010), you will need to interprete by yourself the results in order for you to develop the best workout to inprove those results according to the characteristics of your next A priority race. When your fatigue resistance levels are located outside Allen and Coggan's limits (2010), indications on which power duration need to be retested will be provided in cyan.

[Ale Martinez]

El jueves, 3 de mayo de 2018, 13:35:28 (UTC-3), Tim Sinclair escribió:

I've been using GC for about 9 months and have previously been using the 'Fatigue Profile' trend, 'Peak' trend & 'Fatigue' trend. Since the latest release they stopped working
I was alerted to the fact that NP no longer exists and has been replaced replaced by IsoPower, so was able to get the 'Fatigue Profile' working again by correcting the entries in the R console.

I am now left with errors in the 'Peak' trend which says that 'function 'lm' cant be found': Has that also been renamed?

lm stands for linear model an is an R function, try a simple example outside GC to see if it working (s.t. http://www.r-tutor.com/elementary-statistics/simple-linear-regression/estimated-simple-regression-equation)

 

## linear regression

lm<-lm(yp~xp)

abline(lm, col="white")

text(x=100, y=400-count, col=color,

labels=paste(seasons$name[[index]],

" slope=",

round(lm$coefficients[[2]],3)))

 

## track slope to compute average

slopesum <- slopesum + lm$coefficients[[2]]

I'm also left with an error in the 'Bike Fatigue Profile' trend which says it can't open 'stats.dll' in the x64 folder  - saying the specified module could not be found (see screenshot of R console above) . The 'stats.dll' file does exist on my PC at that location - I've checked....

It looks like your R installation is broken. 

[Arnaud LECLÈRE]

To go in the same direction, I encounter exactly the same problems.

The stat.dll file exists in the right place on my disk despite the error returned.

And if I try to install "lmfit", the console answer that this module is already perfectly installed.

If I can help with my data,

Have a good day,

Arnaud

--
_______________________________________________
Golden-Cheetah-Users mailing list
golden-cheetah-users@googlegroups.com
http://groups.google.com/group/golden-cheetah-users?hl=en
---
You received this message because you are subscribed to the Google Groups "golden-cheetah-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golden-cheetah-users+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mark Liversedge]

If you open a command prompt and run R.exe does it work?

[Tim Sinclair]

Sorry for late response Mark - I've became a Granddad yesterday so it's been a bit hectic!

If I try R.exe at the command prompt from the route of C: I get:
 'R.exe' is not recognized as an internal or external command,
operable program or batch file.

If I type: C:\Program Files\R\R-3.4.3\bin>r.exe
then that run's the 64 bit version of R

[Tim Sinclair]

Cracked it!
See this from the R faq's: I added the correct path and everything now works
https://cran.r-project.org/bin/windows/base/rw-FAQ.html#Should-I-run-32_002dbit-or-64_002dbit-R_003f
Just wonder if there is anything that needs to be done for subsequent updates? Should we perhaps uninstall all previous versions of R when GC needs a newer version?

2.30 Rcmd is not found in my PATH!

This has often been reported after an upgrade.

The R installer does not put Rcmd.exe (nor any other R executable) on your PATH. What seems to have happened is that people did this for themselves in the past, upgraded R (which by default will install to a different location) and un-installed the old version of R. If you do that (or install R for the first time), you need to edit the PATH.

The element you want to add to the path is something like

c:\Program Files\R\R-3.1.0\bin\x64

for 64-bit Rcmd.exe, replacing x64 by i386 for 32-bit.

How you set the path depends on your OS version. Under recent versions, go to ‘User Accounts’ in the Control Panel, and select your account and then ‘Change my environment variables’. (System policies can prevent end users making changes.)

An alternative is to set the PATH in the shell you are running (Rcmd.exe is a command-line program). For those using the standard Windows ‘Command Prompt’ Duncan Murdoch suggested:

The simple way to do it just for the command prompt is to write a little batch file setpath.bat containing

set PATH=newstuff;%PATH%

and then run cmd with

CMD /K setpath.bat

On Friday, 4 May 2018 08:44:30 UTC+1, Mark Liversedge wrote:

[Mark Liversedge]

On Saturday, 5 May 2018 19:50:48 UTC+1, Tim Sinclair wrote:

Cracked it!

Nice. Might be a good thing to add to the GC FAQ - and link to the R one?

Mark

[Tim Sinclair]

Done - I hope it's what you meant me to do :-) https://github.com/GoldenCheetah/GoldenCheetah/wiki/Some-Trends-giving-errors-in-console-since-v3.5-1804-'R'-PATH-incorrect. I can edit it if you need me to!
I'm a bit new to the expected conventions and best ways of reporting things for GC!
Thanks Sooooooo much for the development work you all do and for the support you give so readily :-)
Do you ever get time to ride!!!! ;-)
Tim