[skip ci]
This PMC chart is an example of #4652, it uses Expected
PMC curves so it looks like a regular PMC until today,
but it uses Planned activities for the future forecasting
training load according to them.
[skip ci]
This PMC chart is an example of #4652, it uses Expected
PMC curves so it looks like a regular PMC until today,
but it uses Planned activities for the future forecasting
training load according to them.
* Support generic reading and writing FIT developer fields
* Move coretemp to generic DEVELOPER fields
* Add additional type info for fit dev fields
* Add example fit roundtrips
* Clean up CIQ format
* Switch to embedded json for ciq field
* Format json string and reduce tab width on extra tab text box
* Store type name as string rather than index
* Add scale, offset and message metadata to ciq developer fields
Fixes#2553
This patch adds ANT+ support for CoreTemp body sensors.
If there is core temperature XData then it uses that for "tcore" data instead of using the estimated calculation.
All activity functions working with data series,
both standard and xdata, now include an optional
compareindex=-1 parameter.
When compare mode is enabled compareindex parameter
is used as an index to get data for the corresponding
compare item, be an activity or an interval.
Sample chart contributed by Marcen at the users forum
Fixes#4346
Updating the python chart to render via a Qt Chart in addition
to the existing web page rendering.
Five aspects are planned:
1. Add QT chart option, basic rendering of Line+Scatter (this commit)
2. Add legend and axes, support for Pie and Bar charts
3. Add interactivity / hover etc
4. Add options for annotations and markers
5. Add more advanced charts and chart objects
There is an example in the tests folder, but at this point the
chart is very basic, but the main plumbing is in place.
- Performances are computed independently for Rides and Runs in Estimator
- Running Performances are shown in LTM Charts When all selected activities
are runs for a Performance curve
- Banister models uses Performances from activities were score > 0
and for the same date with matching sport, so a Banister model based
on BikeScore/BikeStress will include only rides while one based on
GOVSS will include only runs
- Banister (Run) chart based on GOVSS metric added for testing
.. completes the updates to RTool.cpp
.. as predicted by forming the pmc data.frame via an S3
list instead of a pair list the merge() function works
properly and column names are retained.
