Compare commits
60 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
cc215a1e5c | ||
|
|
9ae1102467 | ||
|
|
2908f01196 | ||
|
|
526e459071 | ||
|
|
67991077f7 | ||
|
|
677fc9079d | ||
|
|
e500bfcfa9 | ||
|
|
ace540a572 | ||
|
|
ac2a809106 | ||
|
|
bc0cba5f46 | ||
|
|
7dba1d204f | ||
|
|
14578f7398 | ||
|
|
dda1597a8d | ||
|
|
8200066d68 | ||
|
|
b976905e68 | ||
|
|
ce5bd9f9d1 | ||
|
|
997c432167 | ||
|
|
9f0b61e642 | ||
|
|
9871100259 | ||
|
|
684970ef0f | ||
|
|
13bbfb876e | ||
|
|
9286d4f2fd | ||
|
|
cde54eba51 | ||
|
|
e4ed56bb8f | ||
|
|
1cb483654e | ||
|
|
7e3d8dcaaf | ||
|
|
b470523cd3 | ||
|
|
abea23dc9c | ||
|
|
9bdda8ebc5 | ||
|
|
250d9d1abe | ||
|
|
8917556ad0 | ||
|
|
5fe3e9bddf | ||
|
|
c8a438039e | ||
|
|
a4044191fa | ||
|
|
74e3591193 | ||
|
|
68beddd1b7 | ||
|
|
ecb674756b | ||
|
|
25b21819bd | ||
|
|
fd204a65e6 | ||
|
|
6bf0c2334b | ||
|
|
52c023d5c3 | ||
|
|
ffeec636c5 | ||
|
|
a4b2990b51 | ||
|
|
c6b2394a33 | ||
|
|
7c01f18202 | ||
|
|
c89fa2812f | ||
|
|
be83533509 | ||
|
|
0572680b2c | ||
|
|
27ab0b89d1 | ||
|
|
7e1483d47b | ||
|
|
2ad8e4c4e6 | ||
|
|
b2df92cbc6 | ||
|
|
4bea06f150 | ||
|
|
fdc4be16e6 | ||
|
|
539672b18b | ||
|
|
38076efc74 | ||
|
|
92b586b691 | ||
|
|
df9c72c822 | ||
|
|
c7c8e77197 | ||
|
|
c7ec57ba6c |
BIN
doc/contrib/WASP Packet Protocol.pdf
Normal file
@@ -1,7 +1,7 @@
|
||||
This is GC3-FAQ.info, produced by makeinfo version 4.13 from
|
||||
This is GC3-FAQ.info, produced by makeinfo version 5.2 from
|
||||
GC3-FAQ.texinfo.
|
||||
|
||||
This manual is for Golden Cheetah, version 3.0.
|
||||
This manual is for Golden Cheetah, version 3.1.
|
||||
|
||||
Copyright (C) 2013 Mark Liversedge
|
||||
|
||||
@@ -11,7 +11,7 @@ File: GC3-FAQ.info, Node: Top, Next: Top, Prev: Top
|
||||
title
|
||||
*****
|
||||
|
||||
This manual is for GoldenCheetah, version 3.0.
|
||||
This manual is for GoldenCheetah, version 3.1.
|
||||
|
||||
* Menu:
|
||||
|
||||
@@ -33,29 +33,30 @@ File: GC3-FAQ.info, Node: MOST COMMON QUESTIONS OF ALL, Next: GENERAL, Prev:
|
||||
1.1 How do I override / manually enter TSS for a ride?
|
||||
======================================================
|
||||
|
||||
The details chart on the analysis view allows you to override metrics
|
||||
on the metrics tab. By default the most common metrics are listed,
|
||||
including average HR, distance and so on. From v3.0 the default setup
|
||||
The details chart on the analysis view allows you to override metrics on
|
||||
the metrics tab. By default the most common metrics are listed,
|
||||
including average HR, distance and so on. From v3.1 the default setup
|
||||
will also include TSS as a metric you can override here.
|
||||
|
||||
If the metric is not there you will need to configure GoldenCheetah to
|
||||
allow it to be shown. This is simple to do and described in 3.9 below.
|
||||
The 3.1 upgrade process should have added it to the Metric tab if it was
|
||||
not already there.
|
||||
|
||||
1.2 How do I add or remove a chart?
|
||||
===================================
|
||||
|
||||
To add a new chart to the view you can select from the + menu on the
|
||||
right hand side of the scope bar (the scope bar is underneath the
|
||||
toolbar and lets you select from Home, Analysis, Train etc).
|
||||
To add a new chart to the view you can select from the hamburger menu on
|
||||
the right hand side of the chart bar.
|
||||
|
||||
Depending upon which view you are on the charts available will differ.
|
||||
For example realtime plots only appear on the Train view, whilst charts
|
||||
that work with individual rides will only appear on the analysis view.
|
||||
|
||||
To remove a chart, when you mouse over a chart (in tabbed or tiled
|
||||
mode) a small triangle will appear in the top left of the chart. This
|
||||
is a menu drop down, if you click on it you will see a `Close' option.
|
||||
This is the option to remove (close) the chart.
|
||||
To remove a chart, when you mouse over a chart (in tabbed or tiled mode)
|
||||
the word 'More...' will appear in the top left of the chart. This is a
|
||||
menu drop down, if you click on it you will see a 'Close' option. This
|
||||
is the option to remove (close) the chart.
|
||||
|
||||
1.3 Can I enter my weight and track/plot it?
|
||||
============================================
|
||||
@@ -63,16 +64,16 @@ This is the option to remove (close) the chart.
|
||||
Weight can be maintained in 3 ways;
|
||||
|
||||
* Every athlete is setup with a weight value - this is the fallback
|
||||
value should no other weight measure be available. It can be
|
||||
found under preferences and athlete.
|
||||
value should no other weight measure be available. It can be found
|
||||
under preferences and athlete.
|
||||
|
||||
* The 'Weight' field can be maintained in the details screen. This
|
||||
is found on the 'Workout' tab in the details screen by
|
||||
default. Any entry here will be used for this ride ONLY.
|
||||
* The 'Weight' field can be maintained in the details screen. This
|
||||
is found on the 'Workout' tab in the details screen by default.
|
||||
Any entry here will be used for this ride ONLY.
|
||||
|
||||
* You can download weight from a withings scale. This is performed
|
||||
manually via the menu option Tools->Get Withings Data. This is
|
||||
then used to update the local measures database.
|
||||
* You can download weight from a withings scale. This is performed
|
||||
manually via the menu option Tools->Get Withings Data. This is
|
||||
then used to update the local measures database.
|
||||
|
||||
When calculating W/KG the Activity value is used if present, if not we
|
||||
then fall back to the last Withing measure that was collected, and if
|
||||
@@ -85,20 +86,25 @@ plotted separately in the LTM plots.
|
||||
1.4 How do I plot x sec power best?
|
||||
===================================
|
||||
|
||||
As of v3.0 it is still not possible to plot custom durations for power
|
||||
bests. We are looking to add this in version 3.1, but for now you can
|
||||
only plot 1s, 5s, 10s, 15s, 20s, 30s, 1min, 2min, 5min, 10min, 20min,
|
||||
30min and 60min bests.
|
||||
In v3.1 it is now possible to plot custom durations for any data series
|
||||
on a metric trends chart in the Trends view. You will need to add a
|
||||
curve for the data series and select 'Best' instead of 'Metric' or
|
||||
'Estimate' on the curve settings.
|
||||
|
||||
For v3.0 or earlier it is still not possible to plot custom durations
|
||||
for power bests. We are looking to add this in version 3.1, but for now
|
||||
you can only plot 1s, 5s, 10s, 15s, 20s, 30s, 1min, 2min, 5min, 10min,
|
||||
20min, 30min and 60min bests.
|
||||
|
||||
1.5 I can't find Aerolab / Performance Manager?
|
||||
===============================================
|
||||
|
||||
By default we do not add these charts to the layout. Aerolab can be
|
||||
added to the Analysis view via the '+' menu found to the right hand
|
||||
side of the GoldenCheetah scope bar.
|
||||
By default we do not add these charts to the layout. Aerolab can be
|
||||
added to the Analysis view via the '+' menu found to the right hand side
|
||||
of the GoldenCheetah scope bar.
|
||||
|
||||
Similarly, the Performance manager can be added to the Home layout via
|
||||
the '+' menu. We may deprecate this chart in the near future since the
|
||||
the '+' menu. We may deprecate this chart in the near future since the
|
||||
LTM charts can be used to plot a PMC and we expect to implement an
|
||||
interactive PMC for planning in v3.1.
|
||||
|
||||
@@ -107,31 +113,31 @@ interactive PMC for planning in v3.1.
|
||||
|
||||
It has been deprecated since the Diary view allows you to summarise by
|
||||
day, week and month and add charts to the view that summarise for the
|
||||
selection. As the weekly summary was fixed on specific charts and did
|
||||
not handle other selections (e.g. monthly) it has been deprecated in
|
||||
selection. As the weekly summary was fixed on specific charts and did
|
||||
not handle other selections (e.g. monthly) it has been deprecated in
|
||||
view of the diary view.
|
||||
|
||||
At present you can treat the Diary view as you would have the weekly
|
||||
summary - they offer the same functionality. We expect the diary view
|
||||
summary - they offer the same functionality. We expect the diary view
|
||||
to extend to planned workouts when we implement planning functionality
|
||||
in v3.1.
|
||||
|
||||
1.7 Where are all the chart settings?
|
||||
=====================================
|
||||
|
||||
All chart settings can be found under the drop down menu that appears
|
||||
in the top left hand corner of a chart when you mouse over it. They
|
||||
will appear as a popup dialog box.
|
||||
All chart settings can be found under the drop down menu that appears in
|
||||
the top left hand corner of a chart when you mouse over it, titled
|
||||
'More...'. They will appear as a popup dialog box.
|
||||
|
||||
Additionally, when you move the cursor towards the title of a chart in
|
||||
a view that is tabbed (not tiled) then a small selection of the most
|
||||
Additionally, when you move the cursor towards the title of a chart in a
|
||||
view that is tabbed (not tiled) then a small selection of the most
|
||||
important settings for the chart will appear for convenience.
|
||||
|
||||
1.8 Where is the preferences / options panel?
|
||||
=============================================
|
||||
|
||||
On a Mac the configurations page can be found under 'GoldenCheetah ->
|
||||
Preferences' on the main menu. Whilst on all other platforms it is
|
||||
Preferences' on the main menu. Whilst on all other platforms it is
|
||||
found via 'Tools -> Options'.
|
||||
|
||||
We do this to match the general guidelines for the operating system.
|
||||
@@ -142,15 +148,35 @@ We do this to match the general guidelines for the operating system.
|
||||
Activities are coloured according to keywords embedded in their details
|
||||
(metadata) you can configure the field that is used and the values that
|
||||
are matched and the colours they are shown in from the preferences pane
|
||||
via the 'Data Fields' toolbar option then select Notes Processing. The
|
||||
via the 'Data Fields' toolbar option then select Notes Processing. The
|
||||
keywords and related words are scanned for to determine if the
|
||||
associated colour should be used for this ride.
|
||||
|
||||
They are processed in the order they are defined with the first match
|
||||
being returned. Take care when using values such as 'TT' and 'race'
|
||||
since these can also be part of an English word (e.g. ATTEMPT contains
|
||||
being returned. Take care when using values such as 'TT' and 'race'
|
||||
since these can also be part of an English word (e.g. ATTEMPT contains
|
||||
'TT' and graceful contains 'race'.
|
||||
|
||||
1.10 GoldenCheetah doesn't find my PowerTap on Ubuntu Linux.
|
||||
============================================================
|
||||
|
||||
If you're using the USB cradle (as opposed to the older, serial one),
|
||||
the FTDI driver sometimes conflicts with the braille terminal in the
|
||||
default Ubuntu installation. Try unplugging the PT cradle from the
|
||||
computer and uninstalling brltty: sudo apt-get remove brltty Then plug
|
||||
the device back in and it should work.
|
||||
|
||||
1.11 GoldenCheetah.dmg installation didn't seem to work.
|
||||
========================================================
|
||||
|
||||
Are you running OS X Snow Leopard (10.6) or later? You need to be. If
|
||||
you are, and you're still having this problem, open Terminal (in
|
||||
Applications -> Utilities) and type this at the prompt:
|
||||
|
||||
/Applications/GoldenCheetah.app/Contents/MacOS/GoldenCheetah then press
|
||||
<return> and send an email to the mailing list with whatever it prints
|
||||
out. We'll help you debug it.
|
||||
|
||||
|
||||
File: GC3-FAQ.info, Node: GENERAL, Next: METRICS, Prev: MOST COMMON QUESTIONS OF ALL, Up: Top
|
||||
|
||||
@@ -161,31 +187,31 @@ File: GC3-FAQ.info, Node: GENERAL, Next: METRICS, Prev: MOST COMMON QUESTIONS
|
||||
==========================
|
||||
|
||||
GoldenCheetah is primarily a program for cyclists that own a power
|
||||
meter. It allows them to record, track and review their performance
|
||||
against recorded data. It also allows you to ride your turbo and
|
||||
meter. It allows them to record, track and review their performance
|
||||
against recorded data. It also allows you to ride your turbo and
|
||||
collect data as you ride.
|
||||
|
||||
If you do not have a power meter then some of the functionality will
|
||||
not be of use to you as a cyclist. But you can still record and track
|
||||
progress. We support HR based TRIMP metrics for a HR based PMC for
|
||||
If you do not have a power meter then some of the functionality will not
|
||||
be of use to you as a cyclist. But you can still record and track
|
||||
progress. We support HR based TRIMP metrics for a HR based PMC for
|
||||
example.
|
||||
|
||||
2.2 What is a good book or resource on training with power?
|
||||
===========================================================
|
||||
|
||||
Unquestionably the bible for working with a power meter is Training and
|
||||
Racing with a Power Meter by Hunter Allan and Andy Coggan. Make sure
|
||||
Racing with a Power Meter by Hunter Allan and Andy Coggan. Make sure
|
||||
you look at the 2nd edition since it is revised quite dramatically.
|
||||
Whilst it is heavily biased towards WKO+ as a software package most of
|
||||
Whilst it is heavily biased towards WKO+ as a software package most of
|
||||
the functions of note are also available in GoldenCheetah.
|
||||
|
||||
2.3 Where can I download the installer for GoldenCheetah ?
|
||||
==========================================================
|
||||
|
||||
Stable releases are available from `http://www.goldencheetah.org'
|
||||
whilst the latest and greatest code build is available from
|
||||
`http://goldencheetah.stand2surf.net'. Development builds are for the
|
||||
brave, since they may contain bugs. In reality the development builds
|
||||
Stable releases are available from <http://www.goldencheetah.org> whilst
|
||||
the latest and greatest code build is available from
|
||||
<http://goldencheetah.stand2surf.net>. Development builds are for the
|
||||
brave, since they may contain bugs. In reality the development builds
|
||||
are a changing feast and often contain latest fixes too.
|
||||
|
||||
2.4 Where can I get the source code?
|
||||
@@ -193,23 +219,23 @@ are a changing feast and often contain latest fixes too.
|
||||
|
||||
The GoldenCheetah source code is hosted on github and can be cloned
|
||||
using the following url;
|
||||
`git://github.com/GoldenCheetah/GoldenCheetah.git'
|
||||
'git://github.com/GoldenCheetah/GoldenCheetah.git'
|
||||
|
||||
2.5 I am a triathlete is GoldenCheetah appropriate for me?
|
||||
==========================================================
|
||||
|
||||
GoldenCheetah is not a multi-sport program. For tracking cycling
|
||||
performance it is a good choice. But if you are looking for running and
|
||||
GoldenCheetah is not a multi-sport program. For tracking cycling
|
||||
performance it is a good choice. But if you are looking for running and
|
||||
swimming metrics and tracking then these features are not available at
|
||||
present. It is an excellent choice for analysing cycling aspects of
|
||||
present. It is an excellent choice for analysing cycling aspects of
|
||||
triathlon, or working on the trainer.
|
||||
|
||||
2.6 Is there a mailing list?
|
||||
============================
|
||||
|
||||
The mailing list for GoldenCheetah users is maintained via Google
|
||||
Groups at
|
||||
`http://groups.google.com/forum/?fromgroups=#forum/golden-cheetah-users'
|
||||
The mailing list for GoldenCheetah users is maintained via Google Groups
|
||||
at
|
||||
<http://groups.google.com/forum/?fromgroups=#forum/golden-cheetah-users>
|
||||
the first post you make is moderated and may take a while to appear.
|
||||
Once your first post is made you can make future posts without
|
||||
moderation.
|
||||
@@ -217,16 +243,16 @@ moderation.
|
||||
2.7 How do I report a bug or request a new feature?
|
||||
===================================================
|
||||
|
||||
We use Github issues to record bugs and feature requests. You will need
|
||||
We use Github issues to record bugs and feature requests. You will need
|
||||
to create an account on github and then post a new request or bug at
|
||||
`http://www.github.com/GoldenCheetah/GoldenCheetah/issues'
|
||||
<http://www.github.com/GoldenCheetah/GoldenCheetah/issues>
|
||||
|
||||
2.8 How can I contribute?
|
||||
=========================
|
||||
|
||||
Patches are most welcome via the mailing list or a pull request in
|
||||
github. Of equal importance is the timely reporting of bugs and help in
|
||||
testing fixes. We also desperately need volunteers to translate into
|
||||
github. Of equal importance is the timely reporting of bugs and help in
|
||||
testing fixes. We also desperately need volunteers to translate into
|
||||
non-English languages and help with writing documentation including the
|
||||
maintenance of this FAQ.
|
||||
|
||||
@@ -236,8 +262,8 @@ list.
|
||||
2.9 Can I donate to the project?
|
||||
================================
|
||||
|
||||
We are an open source project. Our software is developed by a
|
||||
community. We do not have any facility to collect funding or spend it!
|
||||
We are an open source project. Our software is developed by a
|
||||
community. We do not have any facility to collect funding or spend it!
|
||||
We would rather you spread the word if you think our software is good,
|
||||
and maybe help out with documentation, tutorials or translations if you
|
||||
can.
|
||||
@@ -251,70 +277,70 @@ File: GC3-FAQ.info, Node: METRICS, Next: DATA, Prev: GENERAL, Up: Top
|
||||
3.1 What is the difference between xPower, NP and Daniels EqP?
|
||||
==============================================================
|
||||
|
||||
They all serve the same purpose - to express the variable power you
|
||||
have generated over a given period of time as a single value. This is
|
||||
so you can quantify the intensity of the ride and therefore the
|
||||
training stress of the ride.
|
||||
They all serve the same purpose - to express the variable power you have
|
||||
generated over a given period of time as a single value. This is so you
|
||||
can quantify the intensity of the ride and therefore the training stress
|
||||
of the ride.
|
||||
|
||||
In practice, NP and xPower are largely the same, whilst Daniels EqP
|
||||
place much higher emphasise on upper intensity work. For more info on
|
||||
place much higher emphasise on upper intensity work. For more info on
|
||||
xPower see Dr Skiba's paper on BikeScore
|
||||
`http://www.physfarm.com/bikescore.pdf'
|
||||
<http://www.physfarm.com/bikescore.pdf>
|
||||
|
||||
3.2 What is the difference between CP and FTP?
|
||||
==============================================
|
||||
|
||||
CP is a shorthand for CP60 in GoldenCheetah, and is computed using the
|
||||
Scherer/Monod protocol using 3 and 20 minutes. Functional Threshold
|
||||
Power (FTP) is an actual measure of the power an athlete sustains for
|
||||
60 minutes.
|
||||
Scherer/Monod protocol using 3 and 20 minutes. Functional Threshold
|
||||
Power (FTP) is an actual measure of the power an athlete sustains for 60
|
||||
minutes.
|
||||
|
||||
Since it is very difficult for an athlete to maintain the desired
|
||||
intensity FTP 'reality' tends to result in a number that is much lower
|
||||
than CP 'theory'. Often users will consider the two as the same.
|
||||
than CP 'theory'. Often users will consider the two as the same.
|
||||
|
||||
In GC we compute TSS and BikeScore using your 'CP' value. If you set it
|
||||
to your FTP value TSS will be accurate, BikeScore is likely to be
|
||||
lower. And if you set it to your CP value BikeScore will be accurate,
|
||||
but TSS will be overstated.
|
||||
In GC we compute TSS and BikeScore using your 'CP' value. If you set it
|
||||
to your FTP value TSS will be accurate, BikeScore is likely to be lower.
|
||||
And if you set it to your CP value BikeScore will be accurate, but TSS
|
||||
will be overstated.
|
||||
|
||||
3.3 Why does my CP chart show higher watts for a longer duration?
|
||||
=================================================================
|
||||
|
||||
A higher power average for a longer time is possible if an effort has
|
||||
been "book ended". If, for example, you did a massive 30 second
|
||||
effort, followed by freewheeling for 29:30 then another massive 30
|
||||
second effort, then your best average for a continuous 30 minutes would
|
||||
in fact be lower that your best average for a continuous 30minutes and
|
||||
30 seconds. (Thanks for Jon Hill from the Golden Cheetah Users mailing
|
||||
been "book ended". If, for example, you did a massive 30 second effort,
|
||||
followed by freewheeling for 29:30 then another massive 30 second
|
||||
effort, then your best average for a continuous 30 minutes would in fact
|
||||
be lower that your best average for a continuous 30minutes and 30
|
||||
seconds. (Thanks for Jon Hill from the Golden Cheetah Users mailing
|
||||
list for this example).
|
||||
|
||||
3.4 Can I set a different CP/FTP for different reasons e.g. CP/FTP on a trainer?
|
||||
================================================================================
|
||||
|
||||
We allow you to override the CP value for a specific ride by setting
|
||||
the "CP" field to the value you wish to use for the ride in question.
|
||||
We do not have a concept of 'separate' Cps for different purposes - you
|
||||
will need to specify the CP when the data is imported into GC. But this
|
||||
We allow you to override the CP value for a specific ride by setting the
|
||||
"CP" field to the value you wish to use for the ride in question. We do
|
||||
not have a concept of 'separate' Cps for different purposes - you will
|
||||
need to specify the CP when the data is imported into GC. But this
|
||||
allows you to make manual adjustments.
|
||||
|
||||
We provide this functionality at user request - we do not endorse the
|
||||
concept of multiple CP values. But we do recognise the ongoing debate
|
||||
concept of multiple CP values. But we do recognise the ongoing debate
|
||||
regarding physiological stress from working on a trainer vs on the road.
|
||||
|
||||
3.5 How do I seed the CTL for my PMC?
|
||||
=====================================
|
||||
|
||||
You can seed the starting CTL (we call it LTS, for long term stress)
|
||||
when you define a season. That way it is re-usable in a number of
|
||||
places. To do this you edit the season (date range) in the Home View
|
||||
when you define a season. That way it is re-usable in a number of
|
||||
places. To do this you edit the season (date range) in the Home View
|
||||
and can set the Starting LTS.
|
||||
|
||||
3.6 Why is elevation different in GoldenCheetah to my other training software / website?
|
||||
========================================================================================
|
||||
|
||||
Different programs will use different hysteresis values to smooth the
|
||||
small changes in altitude. In GC we use a hysteresis value of 3m.
|
||||
small changes in altitude. In GC we use a hysteresis value of 3m.
|
||||
|
||||
If this is of great concern you can adjust the hysteresis value in
|
||||
preferences under the general tab.
|
||||
@@ -322,70 +348,70 @@ preferences under the general tab.
|
||||
3.7 Why is a metric e.g. TSS or average power different in GoldenCheetah to Garmin Connect?
|
||||
===========================================================================================
|
||||
|
||||
The algorithms for calculating TSS, AP etc are static. They are
|
||||
The algorithms for calculating TSS, AP etc are static. They are
|
||||
implemented exactly the same way in GoldenCheetah, Garmin Connect,
|
||||
TrainingPeaks etc. The algorithms are extremely simple and not prone to
|
||||
TrainingPeaks etc. The algorithms are extremely simple and not prone to
|
||||
difficulty in implementation.
|
||||
|
||||
However, how each application treats pauses and stops or loss of data
|
||||
accounts for most differences. In GoldenCheetah we always calculate
|
||||
AP,TSS etc including stop time. Other applications choose to ignore or
|
||||
accounts for most differences. In GoldenCheetah we always calculate
|
||||
AP,TSS etc including stop time. Other applications choose to ignore or
|
||||
smooth segments of short duration.
|
||||
|
||||
In addition, if there are anomalies in your data, with large gaps or
|
||||
even time going backwards, this will drastically affect GoldenCheetah's
|
||||
calculations.
|
||||
|
||||
We NEVER attempt to interpret data anomalies - if the results are not
|
||||
as you would expect you will need to correct the data. We do not
|
||||
'silently' fix the data for you. There is no secret sauce in
|
||||
We NEVER attempt to interpret data anomalies - if the results are not as
|
||||
you would expect you will need to correct the data. We do not
|
||||
'silently' fix the data for you. There is no secret sauce in
|
||||
GoldenCheetah, we are open and transparent with your data.
|
||||
|
||||
3.8 How do I set the metrics shown for intervals in the various summaries?
|
||||
==========================================================================
|
||||
|
||||
In the GoldenCheetah preference pane under the Metrics tab you can
|
||||
choose the metrics that will be shown in the ride summary charts and
|
||||
the metrics that will be shown in the interval summary in the analysis
|
||||
choose the metrics that will be shown in the ride summary charts and the
|
||||
metrics that will be shown in the interval summary in the analysis
|
||||
sidebar.
|
||||
|
||||
3.9 How do I add a metric to the details screen (so I can override it) ?
|
||||
========================================================================
|
||||
|
||||
If the metric you want (e.g. TSS) is not shown then you will need to
|
||||
add it via the GoldenCheetah preferences pane. On Mac this is from the
|
||||
menu option GoldenCheetah->Preferences whilst on Windows and Linux it
|
||||
is under Tools->Options.
|
||||
If the metric you want (e.g. TSS) is not shown then you will need to
|
||||
add it via the GoldenCheetah preferences pane. On Mac this is from the
|
||||
menu option GoldenCheetah->Preferences whilst on Windows and Linux it is
|
||||
under Tools->Options.
|
||||
|
||||
You will need to select 'Data Fields' option from preferences toolbar
|
||||
and then the 'fields' tab. You will see a list of fields that are
|
||||
associated with a particular screen tab. If you scroll down you should
|
||||
and then the 'fields' tab. You will see a list of fields that are
|
||||
associated with a particular screen tab. If you scroll down you should
|
||||
find entries for the 'Metrics' screen tab, you can insert a new entry
|
||||
here with the '+' button. You should make sure the new entry is called
|
||||
here with the '+' button. You should make sure the new entry is called
|
||||
exactly the same thing as the metric in question.
|
||||
|
||||
For 'TSS' this is relatively straight forward. For others, e.g.
|
||||
For 'TSS' this is relatively straight forward. For others, e.g.
|
||||
'Average Heart Rate' you must make sure that the name includes spaces
|
||||
etc. Once your metric has been added to the configuration you should
|
||||
etc. Once your metric has been added to the configuration you should
|
||||
save that and return to the details screen where you can now maintain
|
||||
it.
|
||||
|
||||
If you are creating a manual entry then there is no 'details' tab in
|
||||
the dialog. Once you have created the entry (and again in this case TSS
|
||||
can be entered in the dialog) you should go to the details tab to
|
||||
maintain any other specific fields. The manual entry dialog is designed
|
||||
to be simple and accept only the most common of entries.
|
||||
If you are creating a manual entry then there is no 'details' tab in the
|
||||
dialog. Once you have created the entry (and again in this case TSS can
|
||||
be entered in the dialog) you should go to the details tab to maintain
|
||||
any other specific fields. The manual entry dialog is designed to be
|
||||
simple and accept only the most common of entries.
|
||||
|
||||
3.10 Can you calculate gradient, virtual power or other derived series from the ride data?
|
||||
==========================================================================================
|
||||
|
||||
Not in 3.0. We may introduce derived data series in the future.
|
||||
Not in 3.1. We plan to extend this functionality in v3.2.
|
||||
|
||||
3.11 Can I export metrics or access the metric database GC uses?
|
||||
================================================================
|
||||
|
||||
The metrics are stored within a Sqlite 3 Database called 'metricDBv3'
|
||||
that can be found in the athlete directory. You can use any Sqlite 3
|
||||
that can be found in the athlete directory. You can use any Sqlite 3
|
||||
tools to query and work with the db.
|
||||
|
||||
Alternatively you can export the db in its entirety using the
|
||||
@@ -408,19 +434,19 @@ To join two rides together (making one longer ride from two rides) you
|
||||
can copy rows in the activity editor and paste special in the ride
|
||||
editor (right click) and then select append mode.
|
||||
|
||||
If you wish to merge rides, that is much harder and would need to be
|
||||
performed outside of GC or by cutting and pasting columns in the
|
||||
activity editor.
|
||||
If you wish to merge rides, in v3.1 there is a new Activity->Merge
|
||||
wizard that will walk you through merging ride files and also provide
|
||||
the ability to synchronise timestamps.
|
||||
|
||||
4.2 How can I find 'spikes' or specific values in activity data?
|
||||
================================================================
|
||||
|
||||
The activity editor has a function to find data on its toolbar. You can
|
||||
The activity editor has a function to find data on its toolbar. You can
|
||||
specify a range or upper or lower limit and find values less than,
|
||||
greater than or between a range of values.
|
||||
|
||||
Additionally, the editor will scan the file looking for anomalies -
|
||||
where the data appears to be out of normal ranges. These are shown with
|
||||
where the data appears to be out of normal ranges. These are shown with
|
||||
a wiggly red line in the editor and can also be listed by clicking on
|
||||
the anomalies icon on the editor toolbar.
|
||||
|
||||
@@ -430,24 +456,24 @@ anomalies in the currently selected ride.
|
||||
4.3 How can I fix 'spikes' or 'anomalies' in activity data?
|
||||
===========================================================
|
||||
|
||||
You can either manually edit the values in the activity editor (there
|
||||
is full undo and redo in the editor). Or you can use the fix tools that
|
||||
You can either manually edit the values in the activity editor (there is
|
||||
full undo and redo in the editor). Or you can use the fix tools that
|
||||
are listed under the tool menu option (fix power spikes, fix gaps in
|
||||
recording, fix gps errors, fix torque.
|
||||
|
||||
Each of the fix tools opens a dialog that displays texts to explain
|
||||
what the fix tool does.
|
||||
Each of the fix tools opens a dialog that displays texts to explain what
|
||||
the fix tool does.
|
||||
|
||||
4.4 How can I add/remove a field to edit on the details screen?
|
||||
===============================================================
|
||||
|
||||
The fields (metadata) that is editable can be configured in the
|
||||
preferences pane under the data fields tab. Where no screen is
|
||||
preferences pane under the data fields tab. Where no screen is
|
||||
specified (its left blank) it will not be made available.
|
||||
|
||||
GoldenCheetah ships with a number of fields defined in the config but
|
||||
with no screen set. If you wish to use them simply set the screen tab
|
||||
to the tab you would like it to be shown on. To remove a field set the
|
||||
to the tab you would like it to be shown on. To remove a field set the
|
||||
field tab to blank.
|
||||
|
||||
4.5 What are 'special fields' ?
|
||||
@@ -459,10 +485,9 @@ purposes.
|
||||
|
||||
Some examples include;
|
||||
|
||||
Weight - used in W/KG calculations, Sport and Workout code are used
|
||||
when exporting to other file formats, Identifier is used to assign a
|
||||
UUID to the activity when it is uploaded to online services and so
|
||||
on.
|
||||
Weight - used in W/KG calculations, Sport and Workout code are used when
|
||||
exporting to other file formats, Identifier is used to assign a UUID to
|
||||
the activity when it is uploaded to online services and so on.
|
||||
|
||||
There is a full list of special fields and their meaning in the Golden
|
||||
Cheetah user guide appendices.
|
||||
@@ -470,8 +495,8 @@ Cheetah user guide appendices.
|
||||
4.6 How do I find/add/sort/delete/edit intervals ?
|
||||
==================================================
|
||||
|
||||
The context menu (on the right hand side of the splitter handle) for
|
||||
the interval sidebar in Analysis view contains a number of options for
|
||||
The context menu (on the right hand side of the splitter handle) for the
|
||||
interval sidebar in Analysis view contains a number of options for
|
||||
working with intervals.
|
||||
|
||||
Additionally, you can click and drag on the performance (aka ride) plot
|
||||
@@ -486,13 +511,13 @@ Activity->Export allows you to export the activity to csv, fitlog, gc
|
||||
4.8 Can I use GC to convert data from one format to another on the command line?
|
||||
================================================================================
|
||||
|
||||
No. It is something we may add in v3.1
|
||||
No. It is something we may add in v3.2
|
||||
|
||||
4.9 Can I delete an athlete and all his/her data?
|
||||
=================================================
|
||||
|
||||
No. It must be done manually by removing the athlete directory via the
|
||||
operating system. Please ensure you do this when GoldenCheetah is not
|
||||
No. It must be done manually by removing the athlete directory via the
|
||||
operating system. Please ensure you do this when GoldenCheetah is not
|
||||
running.
|
||||
|
||||
|
||||
@@ -505,7 +530,7 @@ File: GC3-FAQ.info, Node: UPLOADING AND DOWNLOADING, Next: SEASONS AND EVENTS,
|
||||
==================================================
|
||||
|
||||
The Sport field in TrainingPeaks must have very specific values,
|
||||
although this is not documented in the XML Schema. We recommend using a
|
||||
although this is not documented in the XML Schema. We recommend using a
|
||||
sport of "Bike" if you plan on uploading rides to training peaks.
|
||||
|
||||
5.2 Why does download from TrainingPeaks say I need a premium account?
|
||||
@@ -514,48 +539,32 @@ sport of "Bike" if you plan on uploading rides to training peaks.
|
||||
Training Peaks only allow paid up members to get access to their data.
|
||||
If you are using a free service they do not let you retrieve your data.
|
||||
|
||||
5.3 Upload/Download with Strava fails?
|
||||
======================================
|
||||
|
||||
Strava have switched off their v1 and v2 APIs before providing access
|
||||
to their v3 APIs. We have requested access to the new v3 API but it has
|
||||
not been granted. In the meantime to upload to Strava you can send an
|
||||
email to <upload@strava.com> from you registered email account
|
||||
attaching the ride in a format Strava supports.
|
||||
|
||||
We remain committed to helping cyclists download their power data to
|
||||
the computer of their choice, analyze it in whatever way they see fit,
|
||||
and share their methods of analysis with others.
|
||||
|
||||
We will be deprecating support for Strava upload/download in v3 SP1 and
|
||||
have no immediate plans to provide support for it in the future.
|
||||
|
||||
5.4 What settings do I need to get GoldenCheetah to upload to my Google Calendar?
|
||||
5.3 What settings do I need to get GoldenCheetah to upload to my Google Calendar?
|
||||
=================================================================================
|
||||
|
||||
The upload to Google Calendar uses their CalDAV API, and as such needs
|
||||
to specify a collection. This means when entering the details in the
|
||||
to specify a collection. This means when entering the details in the
|
||||
passwords pane of preferences you should use the following for the
|
||||
caldav url:
|
||||
|
||||
`https://www.google.com/calendar/dav/xxxx@gmail.com/events/'
|
||||
<https://www.google.com/calendar/dav/xxxx@gmail.com/events/>
|
||||
|
||||
Where xxxx is your username. The username will need to be repeated in
|
||||
Where xxxx is your username. The username will need to be repeated in
|
||||
the username field and obviously set the password too.
|
||||
|
||||
5.5 When setting up my Withings wifi scales where do I get the userid and key ?
|
||||
5.4 When setting up my Withings wifi scales where do I get the userid and key ?
|
||||
===============================================================================
|
||||
|
||||
You will need to login to your Withings account
|
||||
(`http://my.withings.com') and click on the `share' button at the top
|
||||
of the dashboard. From there you will get a popup box with lots of
|
||||
(<http://my.withings.com>) and click on the 'share' button at the top of
|
||||
the dashboard. From there you will get a popup box with lots of
|
||||
options.
|
||||
|
||||
If you click on `share on my website' you will be greeted with a number
|
||||
of code snippets you can embed in a web page. If you look closely in
|
||||
the top right hand corner there will be a box containing the user id
|
||||
and public key. These are the two values you need to enter into the
|
||||
options dialog.
|
||||
If you click on 'share on my website' you will be greeted with a number
|
||||
of code snippets you can embed in a web page. If you look closely in
|
||||
the top right hand corner there will be a box containing the user id and
|
||||
public key. These are the two values you need to enter into the options
|
||||
dialog.
|
||||
|
||||
You will now be able to retrieve withings data via the tools menu.
|
||||
|
||||
@@ -568,31 +577,31 @@ File: GC3-FAQ.info, Node: SEASONS AND EVENTS, Next: CHARTS, Prev: UPLOADING A
|
||||
6.1 Why are there different types of seasons?
|
||||
=============================================
|
||||
|
||||
This is to help with planning functions. As of v3 there is no real
|
||||
This is to help with planning functions. As of v3 there is no real
|
||||
distinction made. Adhoc seasons are expected to be used solely as date
|
||||
ranges and have no associated plan. Whilst other season types may
|
||||
contain plans. This is only relevant for planning functions that are
|
||||
contain plans. This is only relevant for planning functions that are
|
||||
not available yet.
|
||||
|
||||
6.2 What is event used for?
|
||||
===========================
|
||||
|
||||
It is only used to annotate a LTM chart - so you can show an 'event'
|
||||
that happened at a particular date. There are no rules about what
|
||||
constitutes and event. It could be a race, a training camp or just a
|
||||
day that was particularly meaningful e.g. illness, crash.
|
||||
that happened at a particular date. There are no rules about what
|
||||
constitutes and event. It could be a race, a training camp or just a
|
||||
day that was particularly meaningful e.g. illness, crash.
|
||||
|
||||
6.3 How do create/edit/delete seasons and events?
|
||||
=================================================
|
||||
|
||||
Seasons and Events are created and edited in the sidebar for the Home
|
||||
view. Seasons are listed under date ranges, whilst events are listed
|
||||
under the events sidebar item. In both cases they can be created and
|
||||
view. Seasons are listed under date ranges, whilst events are listed
|
||||
under the events sidebar item. In both cases they can be created and
|
||||
deleted from the sidebar item's drop down menu.
|
||||
|
||||
Please note that in v3.0 events can only be created when a user season
|
||||
is selected, since events are associated with a particular season. This
|
||||
constraint will be removed in v3.1.
|
||||
Please note that in v3.1 events can only be created when a user season
|
||||
is selected, since events are associated with a particular season. This
|
||||
constraint will be removed in v3.2.
|
||||
|
||||
|
||||
File: GC3-FAQ.info, Node: CHARTS, Next: INDEX, Prev: SEASONS AND EVENTS, Up: Top
|
||||
@@ -610,85 +619,70 @@ similarly 'This' 'month' and prior '2' is a month 2 months ago, whilst
|
||||
|
||||
'This' 'month' prior and 0 is just this month.
|
||||
|
||||
7.2 How does the mean max chart calculate CP when showing power?
|
||||
================================================================
|
||||
|
||||
The CP algorithm searches your best power for two durations; for
|
||||
anaerobic efforts it looks between 15s and 1min, for aerobic it looks
|
||||
for best efforts between 10mins and an hour.
|
||||
|
||||
Once it has found these two best values it will curve fit the two to
|
||||
enable the 60min value to be extracted. Bear in mind this is a
|
||||
theoretical number and as described above is applicable to the
|
||||
BikeScore algorithm. The value for FTP that the TSS algorithm requires
|
||||
is simply the highest value for 60mins for the time period, assuming
|
||||
you have performed a 60minute test recently.
|
||||
|
||||
7.3 How should I use Aerolab?
|
||||
7.2 How should I use Aerolab?
|
||||
=============================
|
||||
|
||||
The following is a brief piece of advice from Robert Chung, from a
|
||||
discussion on the Golden Cheetah Users mailing list:
|
||||
|
||||
Ideally, you'll want calm conditions (both in terms of wind and
|
||||
traffic) but here's a quickie test you can do just to get a handle
|
||||
on what to do. Try to find a loop without stop signs, or an
|
||||
out-and-back with maybe a little dip or something in the middle. Make
|
||||
sure you won't get hit by a car and have good sight lines. I just go
|
||||
around my block a few times. Do a loop in the drops, then another
|
||||
loop faster, then a loop slower; then repeat with your hands on the
|
||||
hoods.
|
||||
Ideally, you'll want calm conditions (both in terms of wind and traffic)
|
||||
but here's a quickie test you can do just to get a handle on what to do.
|
||||
Try to find a loop without stop signs, or an out-and-back with maybe a
|
||||
little dip or something in the middle. Make sure you won't get hit by a
|
||||
car and have good sight lines. I just go around my block a few times.
|
||||
Do a loop in the drops, then another loop faster, then a loop slower;
|
||||
then repeat with your hands on the hoods.
|
||||
|
||||
Weigh yourself and the bike and ballpark the air density.
|
||||
|
||||
See whether you can come close to modeling the "true" elevation profile
|
||||
by sliding the CdA slider around. Even with this informal test, as
|
||||
long as the wind isn't blowing too hard, you ought to be able to
|
||||
see a difference between the loops where you were in the drops and
|
||||
the loops where you on the hoods, and to spot little bumps and dips in
|
||||
the road.
|
||||
by sliding the CdA slider around. Even with this informal test, as long
|
||||
as the wind isn't blowing too hard, you ought to be able to see a
|
||||
difference between the loops where you were in the drops and the loops
|
||||
where you on the hoods, and to spot little bumps and dips in the road.
|
||||
|
||||
There is also an overview of Virtual Elevation to measure aerodynamics
|
||||
in this YouTube video from the power seminar at Interbike 2011 given by
|
||||
Jim Meyer the founder of Quarq:
|
||||
|
||||
`http://www.youtube.com/watch?v=b8tJnFE_BFg&feature=youtu.be&t=27m58s'
|
||||
<http://www.youtube.com/watch?v=b8tJnFE_BFg&feature=youtu.be&t=27m58s>
|
||||
|
||||
Finally, Robert Chung's original paper is included in the docs section
|
||||
of the GoldenCheetah repository, you can it up here (click on 'View
|
||||
Raw' to download):
|
||||
of the GoldenCheetah repository, you can it up here (click on 'View Raw'
|
||||
to download):
|
||||
|
||||
`https://github.com/GoldenCheetah/GoldenCheetah/blob/master/doc/contrib/ChungVE.pdf'
|
||||
<https://github.com/GoldenCheetah/GoldenCheetah/blob/master/doc/contrib/ChungVE.pdf>
|
||||
|
||||
7.4 My map doesn't show?
|
||||
7.3 My map doesn't show?
|
||||
========================
|
||||
|
||||
This is most likely because you have a proxy that requires
|
||||
authentication or session details. We do not have sophisticated support
|
||||
for internet proxy servers. We will re-use the operating system
|
||||
authentication or session details. We do not have sophisticated support
|
||||
for internet proxy servers. We will re-use the operating system
|
||||
settings where they are configured.
|
||||
|
||||
7.5 What is the treemap plot used for?
|
||||
7.4 What is the treemap plot used for?
|
||||
======================================
|
||||
|
||||
Typically it is used to visualise where you spend your time or where
|
||||
you get best results. It is not particularly useful if you do not
|
||||
maintain details for each ride e.g. workout code, sport et al.
|
||||
Typically it is used to visualise where you spend your time or where you
|
||||
get best results. It is not particularly useful if you do not maintain
|
||||
details for each ride e.g. workout code, sport et al.
|
||||
|
||||
7.6 Can I change the colors in plot x ?
|
||||
7.5 Can I change the colors in plot x ?
|
||||
=======================================
|
||||
|
||||
With the exception of the Long Term Metric plots the colours on the
|
||||
charts are configured in the GoldenCheetah preferences pane.
|
||||
charts are configured in the GoldenCheetah preferences pane. It is
|
||||
possible to apply a theme or change each individual color.
|
||||
|
||||
We want to use the same colours to plot each data series across the
|
||||
charts, so you can change them globally.
|
||||
|
||||
The only colours you cannot change are the colours assigned to
|
||||
intervals when plotting them on scatterplot or PfPv. These colours are
|
||||
assigned according to their sequence.
|
||||
The only colours you cannot change are the colours assigned to intervals
|
||||
when plotting them on scatterplot or PfPv. These colours are assigned
|
||||
according to their sequence.
|
||||
|
||||
7.7 How do you zoom in on a chart?
|
||||
7.6 How do you zoom in on a chart?
|
||||
==================================
|
||||
|
||||
You can zoom in on the distribution, scatterplot and PfPv charts by
|
||||
@@ -699,17 +693,17 @@ bottom of the chart (if you select the full plot in the chart settings).
|
||||
|
||||
There are no other zoom options for the other charts.
|
||||
|
||||
7.8 I zoomed in but can't zoom out?
|
||||
7.7 I zoomed in but can't zoom out?
|
||||
===================================
|
||||
|
||||
Right click will zoom back out to the previous zoom level (in the case
|
||||
of zooming multiple times). If you select another activity the chart
|
||||
will return to fully zoomed out.
|
||||
|
||||
7.9 GoldenCheetah is saying there is no data for a chart, but I'm sure there is?
|
||||
7.8 GoldenCheetah is saying there is no data for a chart, but I'm sure there is?
|
||||
================================================================================
|
||||
|
||||
You should check in the editor if the data series is present. if the
|
||||
You should check in the editor if the data series is present. if the
|
||||
activity is a manual activity entry it will contain no data.
|
||||
|
||||
|
||||
@@ -722,106 +716,118 @@ Index
|
||||
* Menu:
|
||||
|
||||
* add: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 20)
|
||||
(line 22)
|
||||
* adhoc: SEASONS AND EVENTS. (line 9)
|
||||
* Aerolab <1>: CHARTS. (line 33)
|
||||
* Aerolab: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 69)
|
||||
* algorithm: CHARTS. (line 19)
|
||||
(line 75)
|
||||
* Aerolab <1>: CHARTS. (line 19)
|
||||
* anomalies: DATA. (line 23)
|
||||
* anomalies <1>: DATA. (line 38)
|
||||
* AP: METRICS. (line 80)
|
||||
* best: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 61)
|
||||
(line 62)
|
||||
* bug: GENERAL. (line 66)
|
||||
* Chung: CHARTS. (line 33)
|
||||
* cervo: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 136)
|
||||
* Chung: CHARTS. (line 19)
|
||||
* clone: GENERAL. (line 40)
|
||||
* colour <1>: CHARTS. (line 84)
|
||||
* colour: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 115)
|
||||
(line 121)
|
||||
* colour <1>: CHARTS. (line 68)
|
||||
* contribute: GENERAL. (line 73)
|
||||
* CP <1>: CHARTS. (line 19)
|
||||
* CP: METRICS. (line 22)
|
||||
* CSV: DATA. (line 88)
|
||||
* CP <1>: METRICS. (line 39)
|
||||
* CP <2>: METRICS. (line 50)
|
||||
* CSV: DATA. (line 87)
|
||||
* CTL: METRICS. (line 63)
|
||||
* cycle: SEASONS AND EVENTS. (line 9)
|
||||
* Daniels: METRICS. (line 9)
|
||||
* donate: GENERAL. (line 85)
|
||||
* download: GENERAL. (line 31)
|
||||
* download <1>: UPLOADING AND DOWNLOADING.
|
||||
(line 16)
|
||||
* download: GENERAL. (line 31)
|
||||
* elevation: METRICS. (line 71)
|
||||
* EqP: METRICS. (line 9)
|
||||
* event: SEASONS AND EVENTS. (line 18)
|
||||
* event <1>: SEASONS AND EVENTS. (line 26)
|
||||
* feature: GENERAL. (line 66)
|
||||
* FITLOG: DATA. (line 88)
|
||||
* FITLOG: DATA. (line 87)
|
||||
* FTP: METRICS. (line 22)
|
||||
* FTP <1>: METRICS. (line 50)
|
||||
* Garmin Connect: METRICS. (line 80)
|
||||
* github: GENERAL. (line 40)
|
||||
* Google: UPLOADING AND DOWNLOADING.
|
||||
(line 38)
|
||||
(line 22)
|
||||
* install: GENERAL. (line 31)
|
||||
* join: DATA. (line 9)
|
||||
* JSON: DATA. (line 88)
|
||||
* JSON: DATA. (line 87)
|
||||
* LTS: METRICS. (line 63)
|
||||
* mail: GENERAL. (line 56)
|
||||
* map: CHARTS. (line 69)
|
||||
* map: CHARTS. (line 53)
|
||||
* merge: DATA. (line 9)
|
||||
* month: CHARTS. (line 9)
|
||||
* NP: METRICS. (line 9)
|
||||
* options: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 106)
|
||||
(line 112)
|
||||
* override: METRICS. (line 110)
|
||||
* PMC <1>: METRICS. (line 63)
|
||||
* PMC: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 69)
|
||||
(line 75)
|
||||
* PMC <1>: METRICS. (line 63)
|
||||
* powertap: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 136)
|
||||
* preferences: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 106)
|
||||
(line 112)
|
||||
* prior: CHARTS. (line 9)
|
||||
* PWX: DATA. (line 88)
|
||||
* PWX: DATA. (line 87)
|
||||
* remove: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 20)
|
||||
(line 22)
|
||||
* report: GENERAL. (line 66)
|
||||
* season: SEASONS AND EVENTS. (line 9)
|
||||
* season <1>: SEASONS AND EVENTS. (line 26)
|
||||
* settings: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 95)
|
||||
(line 101)
|
||||
* source: GENERAL. (line 40)
|
||||
* spikes: DATA. (line 23)
|
||||
* spikes <1>: DATA. (line 38)
|
||||
* split: DATA. (line 9)
|
||||
* Strava: UPLOADING AND DOWNLOADING.
|
||||
(line 22)
|
||||
* TCX: DATA. (line 88)
|
||||
* TCX: DATA. (line 87)
|
||||
* trainer: METRICS. (line 50)
|
||||
* TrainingPeaks: UPLOADING AND DOWNLOADING.
|
||||
(line 9)
|
||||
* treemap: CHARTS. (line 77)
|
||||
* TrainingPeaks <1>: UPLOADING AND DOWNLOADING.
|
||||
(line 16)
|
||||
* treemap: CHARTS. (line 61)
|
||||
* triathlete: GENERAL. (line 47)
|
||||
* TSS <1>: METRICS. (line 80)
|
||||
* TSS: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 9)
|
||||
* unzoom: CHARTS. (line 108)
|
||||
* TSS <1>: METRICS. (line 80)
|
||||
* unzoom: CHARTS. (line 93)
|
||||
* upload: UPLOADING AND DOWNLOADING.
|
||||
(line 9)
|
||||
* VE: CHARTS. (line 33)
|
||||
* usb: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 136)
|
||||
* VE: CHARTS. (line 19)
|
||||
* weekly summary: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 81)
|
||||
(line 87)
|
||||
* weight: MOST COMMON QUESTIONS OF ALL.
|
||||
(line 36)
|
||||
(line 37)
|
||||
* Withings: UPLOADING AND DOWNLOADING.
|
||||
(line 51)
|
||||
(line 35)
|
||||
* xPower: METRICS. (line 9)
|
||||
* zoom: CHARTS. (line 97)
|
||||
* zoom: CHARTS. (line 82)
|
||||
* zoom <1>: CHARTS. (line 93)
|
||||
|
||||
|
||||
|
||||
Tag Table:
|
||||
Node: Top164
|
||||
Node: MOST COMMON QUESTIONS OF ALL609
|
||||
Node: GENERAL6062
|
||||
Node: METRICS9684
|
||||
Node: DATA16676
|
||||
Node: UPLOADING AND DOWNLOADING20606
|
||||
Node: SEASONS AND EVENTS23387
|
||||
Node: CHARTS24784
|
||||
Node: INDEX29585
|
||||
Node: Top163
|
||||
Node: MOST COMMON QUESTIONS OF ALL608
|
||||
Node: GENERAL7263
|
||||
Node: METRICS10899
|
||||
Node: DATA17912
|
||||
Node: UPLOADING AND DOWNLOADING21867
|
||||
Node: SEASONS AND EVENTS23922
|
||||
Node: CHARTS25327
|
||||
Node: INDEX29480
|
||||
|
||||
End Tag Table
|
||||
|
||||
@@ -9,7 +9,7 @@
|
||||
@paragraphindent 0
|
||||
|
||||
@copying
|
||||
This manual is for Golden Cheetah, version 3.0.
|
||||
This manual is for Golden Cheetah, version 3.1.
|
||||
|
||||
Copyright @copyright{} 2013 Mark Liversedge
|
||||
@end copying
|
||||
@@ -35,7 +35,7 @@ Copyright @copyright{} 2013 Mark Liversedge
|
||||
@node Top,Top,Top,
|
||||
@top title
|
||||
|
||||
This manual is for GoldenCheetah, version 3.0.
|
||||
This manual is for GoldenCheetah, version 3.1.
|
||||
@end ifnottex
|
||||
|
||||
@menu
|
||||
@@ -58,24 +58,24 @@ This manual is for GoldenCheetah, version 3.0.
|
||||
|
||||
The details chart on the analysis view allows you to override metrics on the metrics tab.
|
||||
By default the most common metrics are listed, including average HR, distance and so on.
|
||||
From v3.0 the default setup will also include TSS as a metric you can override here.
|
||||
From v3.1 the default setup will also include TSS as a metric you can override here.
|
||||
|
||||
If the metric is not there you will need to configure GoldenCheetah to allow it to be shown.
|
||||
This is simple to do and described in 3.9 below.
|
||||
This is simple to do and described in 3.9 below. The 3.1 upgrade process should have added it
|
||||
to the Metric tab if it was not already there.
|
||||
|
||||
@section How do I add or remove a chart?
|
||||
@cindex add
|
||||
@cindex remove
|
||||
|
||||
To add a new chart to the view you can select from the + menu on the right hand side of
|
||||
the scope bar (the scope bar is underneath the toolbar and lets you select from Home,
|
||||
Analysis, Train etc).
|
||||
To add a new chart to the view you can select from the hamburger menu on the right hand side of
|
||||
the chart bar.
|
||||
|
||||
Depending upon which view you are on the charts available will differ. For example realtime
|
||||
plots only appear on the Train view, whilst charts that work with individual rides will only
|
||||
appear on the analysis view.
|
||||
|
||||
To remove a chart, when you mouse over a chart (in tabbed or tiled mode) a small triangle
|
||||
To remove a chart, when you mouse over a chart (in tabbed or tiled mode) the word 'More...'
|
||||
will appear in the top left of the chart. This is a menu drop down, if you click on it
|
||||
you will see a `Close' option. This is the option to remove (close) the chart.
|
||||
|
||||
@@ -110,7 +110,11 @@ the LTM plots.
|
||||
@section How do I plot x sec power best?
|
||||
@cindex best
|
||||
|
||||
As of v3.0 it is still not possible to plot custom durations for power bests. We are
|
||||
In v3.1 it is now possible to plot custom durations for any data series on a metric
|
||||
trends chart in the Trends view. You will need to add a curve for the data series
|
||||
and select `Best' instead of `Metric' or `Estimate' on the curve settings.
|
||||
|
||||
For v3.0 or earlier it is still not possible to plot custom durations for power bests. We are
|
||||
looking to add this in version 3.1, but for now you can only plot 1s, 5s, 10s, 15s, 20s,
|
||||
30s, 1min, 2min, 5min, 10min, 20min, 30min and 60min bests.
|
||||
|
||||
@@ -147,7 +151,7 @@ implement planning functionality in v3.1.
|
||||
@cindex settings
|
||||
|
||||
All chart settings can be found under the drop down menu that appears in the top left hand
|
||||
corner of a chart when you mouse over it. They will appear as a popup dialog box.
|
||||
corner of a chart when you mouse over it, titled `More...'. They will appear as a popup dialog box.
|
||||
|
||||
Additionally, when you move the cursor towards the title of a chart in a view that is tabbed
|
||||
(not tiled) then a small selection of the most important settings for the chart will appear
|
||||
@@ -175,7 +179,23 @@ They are processed in the order they are defined with the first match being retu
|
||||
care when using values such as 'TT' and 'race' since these can also be part of an English
|
||||
word (e.g. ATTEMPT contains 'TT' and graceful contains 'race'.
|
||||
|
||||
@section GoldenCheetah doesn't find my PowerTap on Ubuntu Linux.
|
||||
@cindex powertap
|
||||
@cindex cervo
|
||||
@cindex usb
|
||||
|
||||
If you're using the USB cradle (as opposed to the older, serial one), the FTDI driver sometimes
|
||||
conflicts with the braille terminal in the default Ubuntu installation. Try unplugging the PT cradle
|
||||
from the computer and uninstalling brltty: sudo apt-get remove brltty
|
||||
Then plug the device back in and it should work.
|
||||
|
||||
@section GoldenCheetah.dmg installation didn't seem to work.
|
||||
|
||||
Are you running OS X Snow Leopard (10.6) or later? You need to be. If you are, and you're still
|
||||
having this problem, open Terminal (in Applications -> Utilities) and type this at the prompt:
|
||||
|
||||
/Applications/GoldenCheetah.app/Contents/MacOS/GoldenCheetah then press <return>
|
||||
and send an email to the mailing list with whatever it prints out. We'll help you debug it.
|
||||
|
||||
@node GENERAL,METRICS,MOST COMMON QUESTIONS OF ALL,Top
|
||||
@chapter GENERAL
|
||||
@@ -417,7 +437,7 @@ dialog is designed to be simple and accept only the most common of entries.
|
||||
|
||||
@section Can you calculate gradient, virtual power or other derived series from the ride data?
|
||||
|
||||
Not in 3.0. We may introduce derived data series in the future.
|
||||
Not in 3.1. We plan to extend this functionality in v3.2.
|
||||
|
||||
|
||||
|
||||
@@ -447,8 +467,8 @@ To join two rides together (making one longer ride from two rides) you can copy
|
||||
in the activity editor and paste special in the ride editor (right click) and then select
|
||||
append mode.
|
||||
|
||||
If you wish to merge rides, that is much harder and would need to be performed outside
|
||||
of GC or by cutting and pasting columns in the activity editor.
|
||||
If you wish to merge rides, in v3.1 there is a new Activity->Merge wizard that will walk
|
||||
you through merging ride files and also provide the ability to synchronise timestamps.
|
||||
|
||||
|
||||
|
||||
@@ -532,7 +552,7 @@ Training Peaks PWX or Garmin TCX format.
|
||||
|
||||
@section Can I use GC to convert data from one format to another on the command line?
|
||||
|
||||
No. It is something we may add in v3.1
|
||||
No. It is something we may add in v3.2
|
||||
|
||||
|
||||
|
||||
@@ -567,22 +587,6 @@ using a free service they do not let you retrieve your data.
|
||||
|
||||
|
||||
|
||||
@section Upload/Download with Strava fails?
|
||||
@cindex Strava
|
||||
|
||||
Strava have switched off their v1 and v2 APIs before providing access to their
|
||||
v3 APIs. We have requested access to the new v3 API but it has not been granted.
|
||||
In the meantime to upload to Strava you can send an email to @email{upload@@strava.com}
|
||||
from you registered email account attaching the ride in a format Strava supports.
|
||||
|
||||
We remain committed to helping cyclists download their power data
|
||||
to the computer of their choice, analyze it in whatever way they see fit, and
|
||||
share their methods of analysis with others.
|
||||
|
||||
We will be deprecating support for Strava upload/download in v3 SP1 and have no
|
||||
immediate plans to provide support for it in the future.
|
||||
|
||||
|
||||
@section What settings do I need to get GoldenCheetah to upload to my Google Calendar?
|
||||
@cindex Google
|
||||
|
||||
@@ -643,8 +647,8 @@ Seasons and Events are created and edited in the sidebar for the Home view. Seas
|
||||
listed under date ranges, whilst events are listed under the events sidebar item. In
|
||||
both cases they can be created and deleted from the sidebar item's drop down menu.
|
||||
|
||||
Please note that in v3.0 events can only be created when a user season is selected, since
|
||||
events are associated with a particular season. This constraint will be removed in v3.1.
|
||||
Please note that in v3.1 events can only be created when a user season is selected, since
|
||||
events are associated with a particular season. This constraint will be removed in v3.2.
|
||||
|
||||
@node CHARTS,INDEX,SEASONS AND EVENTS,Top
|
||||
@chapter CHARTS
|
||||
@@ -663,22 +667,6 @@ prior '2' is a month 2 months ago, whilst 'This' 'month' and prior '1' is last m
|
||||
|
||||
|
||||
|
||||
@section How does the mean max chart calculate CP when showing power?
|
||||
@cindex CP
|
||||
@cindex algorithm
|
||||
|
||||
The CP algorithm searches your best power for two durations; for anaerobic efforts it
|
||||
looks between 15s and 1min, for aerobic it looks for best efforts between 10mins and
|
||||
an hour.
|
||||
|
||||
Once it has found these two best values it will curve fit the two to enable the
|
||||
60min value to be extracted. Bear in mind this is a theoretical number and as described
|
||||
above is applicable to the BikeScore algorithm. The value for FTP that the TSS algorithm
|
||||
requires is simply the highest value for 60mins for the time period, assuming you have
|
||||
performed a 60minute test recently.
|
||||
|
||||
|
||||
|
||||
@section How should I use Aerolab?
|
||||
@cindex Aerolab
|
||||
@cindex Chung
|
||||
@@ -736,7 +724,8 @@ e.g. workout code, sport et al.
|
||||
@cindex colour
|
||||
|
||||
With the exception of the Long Term Metric plots the colours on the charts are
|
||||
configured in the GoldenCheetah preferences pane.
|
||||
configured in the GoldenCheetah preferences pane. It is possible to apply a theme
|
||||
or change each individual color.
|
||||
|
||||
We want to use the same colours to plot each data series across the charts, so you
|
||||
can change them globally.
|
||||
|
||||
270
doc/user/GC31-Release.info
Normal file
@@ -0,0 +1,270 @@
|
||||
This is GC31-Release.info, produced by makeinfo version 5.2 from
|
||||
GC31-Release.texinfo.
|
||||
|
||||
|
||||
File: GC31-Release.info, Node: Top, Next: Top, Prev: Top
|
||||
|
||||
title
|
||||
*****
|
||||
|
||||
These release notes are for GoldenCheetah, version 3.1.
|
||||
|
||||
* Menu:
|
||||
|
||||
* WHATS NEW:: What's new in V3.1
|
||||
* CONTRIBUTORS:: List of Contributors to V3.1
|
||||
|
||||
|
||||
File: GC31-Release.info, Node: WHATS NEW, Next: CONTRIBUTORS, Prev: CONTRIBUTORS, Up: Top
|
||||
|
||||
1 Whats New
|
||||
***********
|
||||
|
||||
1.1 Major new features; Compare, Share and Merge
|
||||
================================================
|
||||
|
||||
We have added a new feature to enable comparing rides and intervals
|
||||
across all the charts where it is sensible to try; performance plot, cp
|
||||
chart, histogram and QA charts all support compare. Additionally it is
|
||||
possible to compare trends across different seasons as well as
|
||||
histograms. And of course, these are also possible across athletes; so
|
||||
you can compare one athletes season or ride with another athletes season
|
||||
or ride.
|
||||
|
||||
Wherever it is sensible to compare things, we think it is now possible
|
||||
to compare things.
|
||||
|
||||
We have also unified upload to "cloud" across Strava, RideWithGPS and
|
||||
Cycling Analytics. With a single click you can upload to all services.
|
||||
We do not currently support Garmin Connect as they have closed their
|
||||
system and only work with commercial partners - for this reason we
|
||||
recommend storing data outside for future data security.
|
||||
|
||||
Lastly, it is now possible to merge data from different sources into a
|
||||
single ridefile. This is particularly useful when working with
|
||||
multipled devices or integrating data from devices like the Moxy SM02
|
||||
monitor.
|
||||
|
||||
1.2 General Enhancements
|
||||
========================
|
||||
|
||||
We have made the following general / UI enhancements:
|
||||
|
||||
* Open Athletes in Tabs - it is possible to open up all your athletes
|
||||
within a single window and switch tabs.
|
||||
|
||||
* ChartBar - the chartbar has become a toolbar item and is
|
||||
scrollable. This dramatically increases the screen estate
|
||||
available for displaying charts and data but also makes the UI less
|
||||
'quirky' and align more to typical desktop application styles.
|
||||
|
||||
* Themes and better support for color customisation - we now have
|
||||
much more sophisticated support for color customisation and support
|
||||
across all the charts. Themes allow you to switch between light on
|
||||
dark and dark on light setups quickly and easily.
|
||||
|
||||
* Improved Interactivity - mouse over interactivity has been extended
|
||||
over the ride list and most charts for faster exploration of data
|
||||
and to provide a more fluid and dynamic user experience. This
|
||||
extendes to isolating curves within a chart by hovering over the
|
||||
axis labels and automatically selecting intervals as you hover over
|
||||
their data in the QA and ride charts.
|
||||
|
||||
* Autofilter in Trends view - as well as advance data filtering
|
||||
within chart setup and the toolbar search box we have now added
|
||||
autofilters in the trends sidebar to make it simple to filter data
|
||||
based upon metadata e.g. all running files or rides on your TT
|
||||
bike.
|
||||
|
||||
* Specify athlete library location - You can now specify where data
|
||||
is stored to make it easier to integrate with backup or other
|
||||
synchronisation tools.
|
||||
|
||||
* Improved Dropbox support (CRC) - We will check the data within a
|
||||
ride has changed (as opposed to its timestamp) before refreshing
|
||||
metrics. This is to remove unneccessary metric refreshes when
|
||||
copying data between computers or synchronising using tools like
|
||||
Dropbox.
|
||||
|
||||
* Find intervals via matches, hills etc - The find intervals dialog
|
||||
will now find hills as well as sustained efforts using W'
|
||||
consumption (see support for W'bal).
|
||||
|
||||
1.3 Enhanced Device Support
|
||||
===========================
|
||||
|
||||
We have fixed or enhanced device support for:
|
||||
|
||||
* Fixed up Tacx Fortius Support - Dave Waterworth has updated the
|
||||
original beta code for Fortius support to now make the Fortius and
|
||||
fully supported device in train view.
|
||||
|
||||
* Joule GPS updates - the latest firmware is now supported and no
|
||||
longer crashes GC (!).
|
||||
|
||||
* FIT ride file updates - better support for custom FIT sections that
|
||||
are being used by vendors to suport localised data.
|
||||
|
||||
* Pedal Smoothness / Torque Effectiveness support - the Rotor and
|
||||
Vector data series are now extracted and stored in ridefiles and
|
||||
can be plotted alongside all the other ride data series on
|
||||
performance, scatter and histogram plots.
|
||||
|
||||
* Moxy support - we have added support for the Moxy SM02 monitor and
|
||||
can be imported and merged with ride data using the new merge
|
||||
dialog.
|
||||
|
||||
1.4 New Metrics Implemented
|
||||
===========================
|
||||
|
||||
We have implemented a lot of new science in 3.1 and along with that
|
||||
there are a lot of associated metrics:
|
||||
|
||||
* Plot bests - It is now possible to plot user-defined durations for
|
||||
power bests. For example it is now possible to plot 13s power
|
||||
best, but we have extended this to cover all ride data series, so
|
||||
you can plot best durations for heartrate, speed, cadence and so on
|
||||
within a metric trends chart. This feature has been the most
|
||||
requested feature since LTM was implemeted in 2010, so we've
|
||||
finally got there.
|
||||
|
||||
* Plot Model Estimates - With the new PD models we also derive
|
||||
estimates for W', CP et al using each of the models. These can
|
||||
then be plotted; an example 'CP History' plot in the trends view is
|
||||
provide as an example.
|
||||
|
||||
* W'bal implemented with metrics - The W'bal data series is derived
|
||||
from power data and can be plotted alongside all other ride data.
|
||||
It has also been implemented within the erg plot to assess ERG
|
||||
workouts before attempting them.
|
||||
|
||||
* TISS implemented - An an Ae TISS have been implemented and can be
|
||||
plotted as data series within a ride but also as inputs into a PMC
|
||||
chart. An example 'Stress' chart is provided to plot these in the
|
||||
Trends and Rides view.
|
||||
|
||||
* aPower - We have implemented Altitude Power to adjust recorded
|
||||
power to take into account the effect of altitude on vo2max and
|
||||
thus power output. This can be plotted alongside all other ride
|
||||
data series.
|
||||
|
||||
* Polarised Zones - Histogram chart will now plot power histograms in
|
||||
Polarised Zones as well as the more familar Coggan 7 levels.
|
||||
|
||||
* Pacing Index / Fatigue Index - Experimentally added to help review
|
||||
interval efforts.
|
||||
|
||||
* W' work - To compliment W'bal and Work metrics we now isolate and
|
||||
can track how much W' energy is being expended. This is closely
|
||||
related to tracking Anaerobic training.
|
||||
|
||||
* Average Pedal Smoothness / Torque Efficiency - the Rotor/Vector
|
||||
metrics can be plotted alongside ride data but also as average
|
||||
metrics to track across weeks, months and seasons.
|
||||
|
||||
1.5 Chart Enhancements
|
||||
======================
|
||||
|
||||
We have made significant changes across all the charts in 3.1. These
|
||||
have been added to support the new models and science and also to try
|
||||
and enhance the utility and user experience.
|
||||
|
||||
* LTM Chart - It is now possible to select charts via a Chart
|
||||
selection sidebar thus reducing the number of charts needed to be
|
||||
pre-configured on the chart bar. We have also tidied up the LTM
|
||||
settings dialog and improved the UX for setting up charts in the
|
||||
first place. To support the new compare mode we have also added a
|
||||
Stack mode and a Data table mode to look at series in isolation or
|
||||
just review the numbers. It is also now possible to export the
|
||||
chart data to manipulate or analyse in other tools. Lastly, we
|
||||
have also added Labels and Quadratic trend lines to create charts
|
||||
that are more readable without resorting to tooltips and guess
|
||||
work.
|
||||
|
||||
* CP Chart - The critical power chart has seen a lot of new features
|
||||
added both to support the new PD models but also to provide the
|
||||
possibility to plot and compare intervals. The key new features
|
||||
include User selectable CP models and the ability to fine tune the
|
||||
search intervals used by each of the 4 models. It is also now
|
||||
possible to plot rates of change for power, heartrate etc and also
|
||||
to plot heat and heat by age. You can also plot a ride as
|
||||
percentge of best or as a centile. And as with the LTM charts it
|
||||
is also possible to export the PD data and model to review and
|
||||
assess in other tools.
|
||||
|
||||
* Ride Chart - It is now possible to plot lots of derived series; NP,
|
||||
W'bal, xPower, Delta etc and also to plot each series in its own
|
||||
chart with all series shown as a 'stack'. We have also finally
|
||||
added the ability to create and edit reference lines for power and
|
||||
have added an overlay to display interval data as you hover or
|
||||
select them in the plot.
|
||||
|
||||
* Summary Chart - It is mostly unchanged but will now also support
|
||||
displaying user defined metrics for Athlete Bests for the date
|
||||
range selected. It will also show model estimates that apply to
|
||||
the ride or for the date range being summarised.
|
||||
|
||||
1.6 Code refactoring and 300 issues fixed
|
||||
=========================================
|
||||
|
||||
Since we release 3.0 in June 2013 we've been busily updating the code to
|
||||
fix lots and lots of nits and errors, but also slowly adjusting the code
|
||||
to provide a better platform for new features.
|
||||
|
||||
We have deferred almost all features related to indoor training to a
|
||||
release 3.11 that is planned for the beginning of 2015 with development
|
||||
starting in August 2014.
|
||||
|
||||
However, some of the (boring, tehcnical) foundational things that
|
||||
changed in 3.1 include:
|
||||
|
||||
* QT 5.3 is now supported; so QT video support, QML, Qt Json, faster
|
||||
webkit and for the future, possible support for IOS and Android
|
||||
devices.
|
||||
|
||||
* QWT 6.1 with multiaxis is now supported; lots of bug fixes and
|
||||
better rendering on retina and high resolution displays.
|
||||
|
||||
* CP chart and AllPlot chart refactored to make it possible to extend
|
||||
functionality e.g. for new PD models and derived data series.
|
||||
|
||||
Some of the functionality that has been fixed include reinstated support
|
||||
for Strava and Twitter. We also have better native support for
|
||||
look-and-feel differences across the three platforms we currently
|
||||
support (Mac, Linux, Windows).
|
||||
|
||||
We have also adjusted the startup mechanism to make it possible to
|
||||
select a different athlete or create a new one if recovering from a
|
||||
fatal crash.
|
||||
|
||||
|
||||
File: GC31-Release.info, Node: CONTRIBUTORS, Next: WHATS NEW, Prev: WHATS NEW, Up: Top
|
||||
|
||||
2 Contributors
|
||||
**************
|
||||
|
||||
2.1 Credits and Contributors
|
||||
============================
|
||||
|
||||
The main contributors continue to be Mark, Damien and Gareth, but a few
|
||||
new contributors have joined the team in the last year and the future
|
||||
looks promising. A particular shout out is deserved for Joern
|
||||
Rischmuller who has updated the GC Wiki to cover all functionality - so
|
||||
for the first time we have comprehensive user documentation.
|
||||
|
||||
The following have all made a contribution to 3.1:
|
||||
|
||||
Alejandro Martinez, Bruno Fernandez-Ruiz, Christian Stade-Schuldt,
|
||||
Damien Grauser, Dave Waterworth, Eric Johnson, Gareth Coco, Ilja Booij,
|
||||
Jaime Jofre, Joern Rischmuller, Jon Beverley, Jon Escombe, KURASHIKI
|
||||
Satoru, Mark Liversedge, Rainer Clasen, Ralf Spenneberg, Simon Egli,
|
||||
Stig B. Dørmænen, Tom Weichmann, Walter Bürki and Alex Delli.
|
||||
|
||||
|
||||
|
||||
Tag Table:
|
||||
Node: Top88
|
||||
Node: WHATS NEW312
|
||||
Node: CONTRIBUTORS10389
|
||||
|
||||
End Tag Table
|
||||
BIN
doc/user/GC31-Release.pdf
Normal file
245
doc/user/GC31-Release.texinfo
Normal file
@@ -0,0 +1,245 @@
|
||||
\input texinfo @c -*-texinfo-*-
|
||||
@ifnotinfo
|
||||
@input palatino
|
||||
@end ifnotinfo
|
||||
@c %**start of header
|
||||
@setfilename Release Notes.texinfo
|
||||
@settitle Golden Cheetah v3.1 Release Notes
|
||||
@c %**end of header
|
||||
@paragraphindent 0
|
||||
|
||||
@titlepage
|
||||
@title Golden Cheetah v3.1 Release Notes
|
||||
@c @subtitle subtitle-if-any
|
||||
@c @subtitle second-subtitle
|
||||
@author Mark Liversedge
|
||||
|
||||
@end titlepage
|
||||
|
||||
@c So the toc is printed at the start.
|
||||
@contents
|
||||
|
||||
@ifnottex
|
||||
@node Top,Top,Top,
|
||||
@top title
|
||||
|
||||
These release notes are for GoldenCheetah, version 3.1.
|
||||
@end ifnottex
|
||||
|
||||
@menu
|
||||
* WHATS NEW:: What's new in V3.1
|
||||
* CONTRIBUTORS:: List of Contributors to V3.1
|
||||
@end menu
|
||||
|
||||
@node WHATS NEW,CONTRIBUTORS,CONTRIBUTORS,Top
|
||||
@chapter Whats New
|
||||
|
||||
@section Major new features; Compare, Share and Merge
|
||||
|
||||
We have added a new feature to enable comparing rides and intervals across all
|
||||
the charts where it is sensible to try; performance plot, cp chart, histogram
|
||||
and QA charts all support compare. Additionally it is possible to compare
|
||||
trends across different seasons as well as histograms. And of course, these are
|
||||
also possible across athletes; so you can compare one athletes season or ride
|
||||
with another athletes season or ride.
|
||||
|
||||
Wherever it is sensible to compare things, we think it is now possible to compare things.
|
||||
|
||||
We have also unified upload to "cloud" across Strava, RideWithGPS and Cycling
|
||||
Analytics. With a single click you can upload to all services. We do not currently
|
||||
support Garmin Connect as they have closed their system and only work with commercial
|
||||
partners - for this reason we recommend storing data outside for future data security.
|
||||
|
||||
Lastly, it is now possible to merge data from different sources into a single ridefile.
|
||||
This is particularly useful when working with multipled devices or integrating data
|
||||
from devices like the Moxy SM02 monitor.
|
||||
|
||||
@section General Enhancements
|
||||
|
||||
We have made the following general / UI enhancements:
|
||||
|
||||
@itemize @bullet
|
||||
@item Open Athletes in Tabs - it is possible to open up all your athletes within a
|
||||
single window and switch tabs.
|
||||
|
||||
@item ChartBar - the chartbar has become a toolbar item and is scrollable. This
|
||||
dramatically increases the screen estate available for displaying charts and data
|
||||
but also makes the UI less `quirky' and align more to typical desktop application
|
||||
styles.
|
||||
|
||||
@item Themes and better support for color customisation - we now have much more sophisticated
|
||||
support for color customisation and support across all the charts. Themes allow you
|
||||
to switch between light on dark and dark on light setups quickly and easily.
|
||||
|
||||
@item Improved Interactivity - mouse over interactivity has been extended over the ride
|
||||
list and most charts for faster exploration of data and to provide a more fluid and
|
||||
dynamic user experience. This extendes to isolating curves within a chart by hovering
|
||||
over the axis labels and automatically selecting intervals as you hover over their data
|
||||
in the QA and ride charts.
|
||||
|
||||
@item Autofilter in Trends view - as well as advance data filtering within chart setup and
|
||||
the toolbar search box we have now added autofilters in the trends sidebar to make it
|
||||
simple to filter data based upon metadata e.g. all running files or rides on your TT bike.
|
||||
|
||||
@item Specify athlete library location - You can now specify where data is stored to make
|
||||
it easier to integrate with backup or other synchronisation tools.
|
||||
|
||||
@item Improved Dropbox support (CRC) - We will check the data within a ride has changed
|
||||
(as opposed to its timestamp) before refreshing metrics. This is to remove unneccessary
|
||||
metric refreshes when copying data between computers or synchronising using tools like
|
||||
Dropbox.
|
||||
|
||||
@item Find intervals via matches, hills etc - The find intervals dialog will now find
|
||||
hills as well as sustained efforts using W' consumption (see support for W'bal).
|
||||
|
||||
@end itemize
|
||||
|
||||
@section Enhanced Device Support
|
||||
|
||||
We have fixed or enhanced device support for:
|
||||
|
||||
@itemize @bullet
|
||||
|
||||
@item Fixed up Tacx Fortius Support - Dave Waterworth has updated the original beta code
|
||||
for Fortius support to now make the Fortius and fully supported device in train view.
|
||||
|
||||
@item Joule GPS updates - the latest firmware is now supported and no longer crashes GC (!).
|
||||
|
||||
@item FIT ride file updates - better support for custom FIT sections that are being used
|
||||
by vendors to suport localised data.
|
||||
|
||||
@item Pedal Smoothness / Torque Effectiveness support - the Rotor and Vector data series
|
||||
are now extracted and stored in ridefiles and can be plotted alongside all the other ride
|
||||
data series on performance, scatter and histogram plots.
|
||||
|
||||
@item Moxy support - we have added support for the Moxy SM02 monitor and can be imported
|
||||
and merged with ride data using the new merge dialog.
|
||||
|
||||
@end itemize
|
||||
|
||||
@section New Metrics Implemented
|
||||
|
||||
We have implemented a lot of new science in 3.1 and along with that
|
||||
there are a lot of associated metrics:
|
||||
|
||||
@itemize @bullet
|
||||
|
||||
@item Plot bests - It is now possible to plot user-defined durations for power bests.
|
||||
For example it is now possible to plot 13s power best, but we have extended this to
|
||||
cover all ride data series, so you can plot best durations for heartrate, speed, cadence
|
||||
and so on within a metric trends chart. This feature has been the most requested feature
|
||||
since LTM was implemeted in 2010, so we've finally got there.
|
||||
|
||||
@item Plot Model Estimates - With the new PD models we also derive estimates for W', CP et al using
|
||||
each of the models. These can then be plotted; an example `CP History' plot in the trends view
|
||||
is provide as an example.
|
||||
|
||||
@item W'bal implemented with metrics - The W'bal data series is derived from power data and
|
||||
can be plotted alongside all other ride data. It has also been implemented within the erg
|
||||
plot to assess ERG workouts before attempting them.
|
||||
|
||||
@item TISS implemented - An an Ae TISS have been implemented and can be plotted as data series
|
||||
within a ride but also as inputs into a PMC chart. An example `Stress' chart is provided to
|
||||
plot these in the Trends and Rides view.
|
||||
|
||||
@item aPower - We have implemented Altitude Power to adjust recorded power to take into
|
||||
account the effect of altitude on vo2max and thus power output. This can be plotted alongside
|
||||
all other ride data series.
|
||||
|
||||
@item Polarised Zones - Histogram chart will now plot power histograms in Polarised Zones as well
|
||||
as the more familar Coggan 7 levels.
|
||||
|
||||
@item Pacing Index / Fatigue Index - Experimentally added to help review interval efforts.
|
||||
|
||||
@item W' work - To compliment W'bal and Work metrics we now isolate and can track how much
|
||||
W' energy is being expended. This is closely related to tracking Anaerobic training.
|
||||
|
||||
@item Average Pedal Smoothness / Torque Efficiency - the Rotor/Vector metrics can be plotted
|
||||
alongside ride data but also as average metrics to track across weeks, months and seasons.
|
||||
|
||||
@end itemize
|
||||
|
||||
@section Chart Enhancements
|
||||
|
||||
We have made significant changes across all the charts in 3.1. These have been added
|
||||
to support the new models and science and also to try and enhance the utility and
|
||||
user experience.
|
||||
|
||||
@itemize @bullet
|
||||
|
||||
@item LTM Chart - It is now possible to select charts via a Chart selection sidebar thus
|
||||
reducing the number of charts needed to be pre-configured on the chart bar. We have also
|
||||
tidied up the LTM settings dialog and improved the UX for setting up charts in the first place.
|
||||
To support the new compare mode we have also added a Stack mode and a Data table mode to
|
||||
look at series in isolation or just review the numbers. It is also now possible to export
|
||||
the chart data to manipulate or analyse in other tools. Lastly, we have also added Labels
|
||||
and Quadratic trend lines to create charts that are more readable without resorting to
|
||||
tooltips and guess work.
|
||||
|
||||
@item CP Chart - The critical power chart has seen a lot of new features added both to
|
||||
support the new PD models but also to provide the possibility to plot and compare intervals.
|
||||
The key new features include User selectable CP models and the ability to fine tune the
|
||||
search intervals used by each of the 4 models. It is also now possible to plot rates of change
|
||||
for power, heartrate etc and also to plot heat and heat by age. You can also plot a ride as
|
||||
percentge of best or as a centile. And as with the LTM charts it is also possible to export
|
||||
the PD data and model to review and assess in other tools.
|
||||
|
||||
@item Ride Chart - It is now possible to plot lots of derived series; NP, W'bal, xPower, Delta etc
|
||||
and also to plot each series in its own chart with all series shown as a 'stack'. We have also
|
||||
finally added the ability to create and edit reference lines for power and have added an overlay
|
||||
to display interval data as you hover or select them in the plot.
|
||||
|
||||
@item Summary Chart - It is mostly unchanged but will now also support displaying user
|
||||
defined metrics for Athlete Bests for the date range selected. It will also show model
|
||||
estimates that apply to the ride or for the date range being summarised.
|
||||
|
||||
@end itemize
|
||||
|
||||
@section Code refactoring and 300 issues fixed
|
||||
|
||||
Since we release 3.0 in June 2013 we've been busily updating the
|
||||
code to fix lots and lots of nits and errors, but also slowly adjusting
|
||||
the code to provide a better platform for new features.
|
||||
|
||||
We have deferred almost all features related to indoor training to a
|
||||
release 3.11 that is planned for the beginning of 2015 with development
|
||||
starting in August 2014.
|
||||
|
||||
However, some of the (boring, tehcnical) foundational things that changed in 3.1 include:
|
||||
|
||||
@itemize @bullet
|
||||
@item QT 5.3 is now supported; so QT video support, QML, Qt Json, faster
|
||||
webkit and for the future, possible support for IOS and Android devices.
|
||||
|
||||
@item QWT 6.1 with multiaxis is now supported; lots of bug fixes and better
|
||||
rendering on retina and high resolution displays.
|
||||
|
||||
@item CP chart and AllPlot chart refactored to make it possible to extend
|
||||
functionality e.g. for new PD models and derived data series.
|
||||
|
||||
@end itemize
|
||||
|
||||
Some of the functionality that has been fixed include reinstated support
|
||||
for Strava and Twitter. We also have better native support for look-and-feel
|
||||
differences across the three platforms we currently support (Mac, Linux, Windows).
|
||||
|
||||
We have also adjusted the startup mechanism to make it possible to select a
|
||||
different athlete or create a new one if recovering from a fatal crash.
|
||||
|
||||
@node CONTRIBUTORS,WHATS NEW,WHATS NEW,Top
|
||||
@chapter Contributors
|
||||
|
||||
@section Credits and Contributors
|
||||
|
||||
The main contributors continue to be Mark, Damien and Gareth, but a few new contributors
|
||||
have joined the team in the last year and the future looks promising. A particular shout
|
||||
out is deserved for Joern Rischmuller who has updated the GC Wiki to cover all functionality --
|
||||
so for the first time we have comprehensive user documentation.
|
||||
|
||||
The following have all made a contribution to 3.1:
|
||||
|
||||
Alejandro Martinez, Bruno Fernandez-Ruiz, Christian Stade-Schuldt, Damien Grauser, Dave Waterworth, Eric Johnson,
|
||||
Gareth Coco, Ilja Booij, Jaime Jofre, Joern Rischmuller, Jon Beverley, Jon Escombe, KURASHIKI Satoru, Mark Liversedge,
|
||||
Rainer Clasen, Ralf Spenneberg, Simon Egli, Stig B. Dørmænen, Tom Weichmann, Walter Bürki and Alex Delli.
|
||||
|
||||
@bye
|
||||
@@ -12,7 +12,7 @@ clean:
|
||||
|
||||
MANUAL: GC3-Manual.pdf
|
||||
FAQ: GC3-FAQ.pdf GC3-FAQ.info
|
||||
RELEASE: GC3-Release.pdf GC3-Release.info
|
||||
RELEASE: GC3-Release.pdf GC3-Release.info GC31-Release.pdf GC31-Release.info
|
||||
|
||||
## The basic commands, good on Linux/Mac
|
||||
## need mingw on Windows
|
||||
|
||||
BIN
doc/wiki/2d_Plot.jpg
Normal file
|
After Width: | Height: | Size: 115 KiB |
BIN
doc/wiki/3d_Plot.jpg
Normal file
|
After Width: | Height: | Size: 162 KiB |
BIN
doc/wiki/AddChart_NewChart_Name.jpg
Normal file
|
After Width: | Height: | Size: 60 KiB |
BIN
doc/wiki/Aerolab.jpg
Normal file
|
After Width: | Height: | Size: 152 KiB |
BIN
doc/wiki/ChartsBar_Rides.jpg
Normal file
|
After Width: | Height: | Size: 30 KiB |
BIN
doc/wiki/ChartsBar_Rides_More.GIF
Normal file
|
After Width: | Height: | Size: 3.9 MiB |
BIN
doc/wiki/ChartsBar_Rides_More.jpg
Normal file
|
After Width: | Height: | Size: 154 KiB |
BIN
doc/wiki/ChartsGeneral_DateRange.jpg
Normal file
|
After Width: | Height: | Size: 39 KiB |
BIN
doc/wiki/CollectionTree_First.jpg
Normal file
|
After Width: | Height: | Size: 140 KiB |
BIN
doc/wiki/CollectionTree_RidePopup.jpg
Normal file
|
After Width: | Height: | Size: 165 KiB |
BIN
doc/wiki/CollectionTree_Second.jpg
Normal file
|
After Width: | Height: | Size: 155 KiB |
BIN
doc/wiki/ComparePane_DragDrop.gif
Normal file
|
After Width: | Height: | Size: 224 KiB |
BIN
doc/wiki/ComparePane_Pane.jpg
Normal file
|
After Width: | Height: | Size: 80 KiB |
BIN
doc/wiki/CriticalMeanMaximal_Basic.jpg
Normal file
|
After Width: | Height: | Size: 244 KiB |
BIN
doc/wiki/CriticalMeanMaximal_CP_Model_Extended.jpg
Normal file
|
After Width: | Height: | Size: 42 KiB |
BIN
doc/wiki/CriticalMeanMaximal_Speed.jpg
Normal file
|
After Width: | Height: | Size: 212 KiB |
BIN
doc/wiki/Date_Range-Add_Season1.jpg
Normal file
|
After Width: | Height: | Size: 43 KiB |
BIN
doc/wiki/Date_Range-Add_Season2.jpg
Normal file
|
After Width: | Height: | Size: 32 KiB |
BIN
doc/wiki/Date_Range-Add_Season3.jpg
Normal file
|
After Width: | Height: | Size: 40 KiB |
BIN
doc/wiki/Date_Range-Add_Season_Details.jpg
Normal file
|
After Width: | Height: | Size: 42 KiB |
BIN
doc/wiki/Distribution - Ride Data Samples.jpg
Normal file
|
After Width: | Height: | Size: 155 KiB |
BIN
doc/wiki/Distribution - Ride Metrics.jpg
Normal file
|
After Width: | Height: | Size: 181 KiB |
BIN
doc/wiki/Event-Add.jpg
Normal file
|
After Width: | Height: | Size: 48 KiB |
BIN
doc/wiki/Event-Menu.jpg
Normal file
|
After Width: | Height: | Size: 40 KiB |
BIN
doc/wiki/Event_Details.jpg
Normal file
|
After Width: | Height: | Size: 23 KiB |
BIN
doc/wiki/Filters_Manage.jpg
Normal file
|
After Width: | Height: | Size: 53 KiB |
BIN
doc/wiki/Filters_Settings.jpg
Normal file
|
After Width: | Height: | Size: 50 KiB |
BIN
doc/wiki/FirstSteps_DownloadDialog.JPG
Normal file
|
After Width: | Height: | Size: 35 KiB |
BIN
doc/wiki/FirstSteps_ImportFilesDialog.JPG
Normal file
|
After Width: | Height: | Size: 45 KiB |
BIN
doc/wiki/FirstSteps_YourFirstAthlete_ChooseAnAthlete.JPG
Normal file
|
After Width: | Height: | Size: 18 KiB |
BIN
doc/wiki/FirstSteps_YourFirstAthlete_NewAthlete.JPG
Normal file
|
After Width: | Height: | Size: 38 KiB |
BIN
doc/wiki/FirstSteps_YourFirstAthlete_RidesViewSplashScreen.JPG
Normal file
|
After Width: | Height: | Size: 67 KiB |
BIN
doc/wiki/GC_logo.png
Normal file
|
After Width: | Height: | Size: 236 KiB |
BIN
doc/wiki/GC_logo_small.png
Normal file
|
After Width: | Height: | Size: 4.0 KiB |
BIN
doc/wiki/HR_vs_Power.jpg
Normal file
|
After Width: | Height: | Size: 150 KiB |
BIN
doc/wiki/HR_vs_Power_Colors.jpg
Normal file
|
After Width: | Height: | Size: 50 KiB |
BIN
doc/wiki/MenuBar_Activity.jpg
Normal file
|
After Width: | Height: | Size: 73 KiB |
BIN
doc/wiki/MenuBar_Athlete.jpg
Normal file
|
After Width: | Height: | Size: 39 KiB |
BIN
doc/wiki/MenuBar_Help.jpg
Normal file
|
After Width: | Height: | Size: 31 KiB |
BIN
doc/wiki/MenuBar_Tools.jpg
Normal file
|
After Width: | Height: | Size: 98 KiB |
BIN
doc/wiki/MenuBar_View_TrendsCharts.jpg
Normal file
|
After Width: | Height: | Size: 90 KiB |
BIN
doc/wiki/MetricTrends_New_Basic.jpg
Normal file
|
After Width: | Height: | Size: 133 KiB |
BIN
doc/wiki/MetricTrends_New_Curve.jpg
Normal file
|
After Width: | Height: | Size: 133 KiB |
BIN
doc/wiki/MetricTrends_New_Curve_Details.jpg
Normal file
|
After Width: | Height: | Size: 59 KiB |
BIN
doc/wiki/MetricTrends_New_Curve_Edit.jpg
Normal file
|
After Width: | Height: | Size: 60 KiB |
BIN
doc/wiki/MetricTrends_New_Curve_Edit_Best.jpg
Normal file
|
After Width: | Height: | Size: 34 KiB |
BIN
doc/wiki/MetricTrends_New_Curve_Edit_Estimates.jpg
Normal file
|
After Width: | Height: | Size: 44 KiB |
BIN
doc/wiki/MetricTrends_New_Preset.jpg
Normal file
|
After Width: | Height: | Size: 188 KiB |
BIN
doc/wiki/PedalForce_vs_Velocity.jpg
Normal file
|
After Width: | Height: | Size: 164 KiB |
BIN
doc/wiki/Performance-Overview.jpg
Normal file
|
After Width: | Height: | Size: 251 KiB |
BIN
doc/wiki/Performance_Create_Ref_Line.gif
Normal file
|
After Width: | Height: | Size: 159 KiB |
BIN
doc/wiki/Performance_Edit_Ref_Line.gif
Normal file
|
After Width: | Height: | Size: 729 KiB |
BIN
doc/wiki/Performance_Isolate_Series.gif
Normal file
|
After Width: | Height: | Size: 204 KiB |
BIN
doc/wiki/Performance_Scale_Y-Axis.gif
Normal file
|
After Width: | Height: | Size: 193 KiB |
BIN
doc/wiki/Performance_Select_Interval.gif
Normal file
|
After Width: | Height: | Size: 274 KiB |
BIN
doc/wiki/Performance_ZoomInOut.gif
Normal file
|
After Width: | Height: | Size: 253 KiB |
BIN
doc/wiki/PreferencesAppearance_Colors.jpg
Normal file
|
After Width: | Height: | Size: 181 KiB |
BIN
doc/wiki/PreferencesAppearance_Overview.jpg
Normal file
|
After Width: | Height: | Size: 159 KiB |
BIN
doc/wiki/PreferencesAthlete.jpg
Normal file
|
After Width: | Height: | Size: 106 KiB |
BIN
doc/wiki/PreferencesAthleteCP.jpg
Normal file
|
After Width: | Height: | Size: 144 KiB |
BIN
doc/wiki/PreferencesAthleteCP_Default.jpg
Normal file
|
After Width: | Height: | Size: 127 KiB |
BIN
doc/wiki/PreferencesAthlete_HR_Overview.jpg
Normal file
|
After Width: | Height: | Size: 167 KiB |
BIN
doc/wiki/PreferencesAthlete_Power_Def.jpg
Normal file
|
After Width: | Height: | Size: 162 KiB |
BIN
doc/wiki/PreferencesAthlete_Power_Default.jpg
Normal file
|
After Width: | Height: | Size: 126 KiB |
BIN
doc/wiki/PreferencesAthlete_Power_Overview.jpg
Normal file
|
After Width: | Height: | Size: 178 KiB |
BIN
doc/wiki/PreferencesBar.jpg
Normal file
|
After Width: | Height: | Size: 32 KiB |
BIN
doc/wiki/PreferencesDataFields_Fields.jpg
Normal file
|
After Width: | Height: | Size: 214 KiB |
BIN
doc/wiki/PreferencesDataFields_NotesKeywords.jpg
Normal file
|
After Width: | Height: | Size: 99 KiB |
BIN
doc/wiki/PreferencesDataFields_Processing.jpg
Normal file
|
After Width: | Height: | Size: 129 KiB |
BIN
doc/wiki/PreferencesGeneral.jpg
Normal file
|
After Width: | Height: | Size: 130 KiB |
BIN
doc/wiki/PreferencesMetrics_Overview.jpg
Normal file
|
After Width: | Height: | Size: 182 KiB |
BIN
doc/wiki/PreferencesPasswords_1.jpg
Normal file
|
After Width: | Height: | Size: 133 KiB |
BIN
doc/wiki/PreferencesPasswords_2.jpg
Normal file
|
After Width: | Height: | Size: 134 KiB |
BIN
doc/wiki/PreferencesTrain_Overview.jpg
Normal file
|
After Width: | Height: | Size: 74 KiB |
BIN
doc/wiki/Ride_3d-analyis-layer.gif
Normal file
|
After Width: | Height: | Size: 578 KiB |
BIN
doc/wiki/Ride_3d-rotate.gif
Normal file
|
After Width: | Height: | Size: 2.7 MiB |
BIN
doc/wiki/Ride_Details-Extra.jpg
Normal file
|
After Width: | Height: | Size: 87 KiB |
BIN
doc/wiki/Ride_Details-Metric.jpg
Normal file
|
After Width: | Height: | Size: 82 KiB |
BIN
doc/wiki/Ride_Details-Workout-Config.jpg
Normal file
|
After Width: | Height: | Size: 88 KiB |
BIN
doc/wiki/Ride_Details-Workout.jpg
Normal file
|
After Width: | Height: | Size: 50 KiB |
BIN
doc/wiki/Ride_Editor-Context_1st_Column.jpg
Normal file
|
After Width: | Height: | Size: 60 KiB |
BIN
doc/wiki/Ride_Editor-Context_Data.jpg
Normal file
|
After Width: | Height: | Size: 127 KiB |
BIN
doc/wiki/Ride_Editor-Context_Header_Row.jpg
Normal file
|
After Width: | Height: | Size: 110 KiB |
BIN
doc/wiki/Ride_Editor-Icons.jpg
Normal file
|
After Width: | Height: | Size: 8.1 KiB |
BIN
doc/wiki/Ride_Editor-View.jpg
Normal file
|
After Width: | Height: | Size: 344 KiB |
BIN
doc/wiki/Ride_Histogram.jpg
Normal file
|
After Width: | Height: | Size: 124 KiB |
BIN
doc/wiki/ScopeBar_Views.jpg
Normal file
|
After Width: | Height: | Size: 4.8 KiB |
BIN
doc/wiki/Search_Filter_Apply_Remove.gif
Normal file
|
After Width: | Height: | Size: 72 KiB |
BIN
doc/wiki/Search_Filter_ManageFilters.jpg
Normal file
|
After Width: | Height: | Size: 55 KiB |
BIN
doc/wiki/Search_Filter_UI.gif
Normal file
|
After Width: | Height: | Size: 120 KiB |