Skip to content

Introduction of the Calories workout type, various improvements#158

Open
JaapvanEkris wants to merge 225 commits intomainfrom
0.9.7-(under-construction)
Open

Introduction of the Calories workout type, various improvements#158
JaapvanEkris wants to merge 225 commits intomainfrom
0.9.7-(under-construction)

Conversation

@JaapvanEkris
Copy link
Owner

New functionality in 0.9.7

  • Addition of the 'Calories' workout type. You can now program Intervals and splits based on calories to be burned
  • Introduction of splits in the fit-file. The fit-file now also has splits, which makes the fit-file closer to a native Garmin recording of the same session

Bugfixes and robustness improvements in 0.9.7

  • Improvement of the Moving Least Squares regressor:
    • Code refactoring to isolate this function from Flywheel.js, allowing a more thorough testing of its behaviour
    • Introduced the 'Local Goodness of Fit' function to improve the robustness against noise. This reduces the effect of outliers on stroke detection, the Force curve, Power curve and Handle speed curve
    • Introduction of a 'Gaussian Weight' filter to reduce the effects of flanks on the regression in a specific datapoint
    • Added documentation about the mathematical foundations of the algorithms used
  • Upgrade of the flywheel position pre-filter, which now can handle systematic errors of flywheel positioning. This is more effective at reducing measurement noise and allows a reduction of the code complexity in Flyhweel.js as all dependent algorithms can use the same datastream again.
  • Fixed a bug in the initialisation of the Flywheel.js
  • Improved logging in the Strava uploader for better troubleshooting (see issue 145)
  • Increased the test coverage of key algorithms

JaapvanEkris and others added 30 commits January 18, 2026 23:02
A stray point causing havoc
* First Pass: Refactor settings and controls into separate toolbar component
* Fix layout padding calculation to prevent vertical overflow scrolling
* Added migration logic to remove 'actions' from saved dashboardMetrics in localStorage.
* Cleaned up Dashboard CSS.
* Refine and make explicit the layout for PerformanceDashboard.
* Make chart font sizes responsive using em-based calculations.
* Refactor DashboardForceCurve, removed any/all labels from ForceCurve.
* Standardized bottom padding to all tiles
* Maximize chart height in forceCurve
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants