Small changes to README_coach.md
This commit is contained in:
parent
c577db4a51
commit
dcf745a0f1
|
|
@ -112,7 +112,8 @@
|
|||
|
||||
### Engine
|
||||
|
||||
* WorkoutRecorder.js - This Module captures the metrics of a rowing session and persists them.
|
||||
* WorkoutRecorder.js
|
||||
This Module captures the metrics of a rowing session and persists them.
|
||||
* recordStroke,
|
||||
recordRotationImpulse,
|
||||
handlePause,
|
||||
|
|
@ -142,18 +143,23 @@
|
|||
heartrate,
|
||||
heartrateBatteryLevel
|
||||
|
||||
* RowingEngine.js - The Rowing Engine models the physics of a real rowing boat.
|
||||
* RowingEngine.js
|
||||
The Rowing Engine models the physics of a real rowing boat.
|
||||
[Physics of Rowing by Anu Dudhia](http://eodg.atm.ox.ac.uk/user/dudhia/rowing/physics)
|
||||
* averager - moving, interval and weighted
|
||||
* MovingFlankDetector.js - A Detector used to test for up-going and down-going flanks
|
||||
* Timer.js - Stopwatch used to measure multiple time intervals
|
||||
* WorkoutUploader.js - Handles uploading workout data to different cloud providers
|
||||
* averager
|
||||
moving, interval and weighted
|
||||
* MovingFlankDetector.js
|
||||
A Detector used to test for up-going and down-going flanks
|
||||
* Timer.js
|
||||
Stopwatch used to measure multiple time intervals
|
||||
* WorkoutUploader.js
|
||||
Handles uploading workout data to different cloud providers
|
||||
|
||||
### Client
|
||||
|
||||
* server.js - entry point
|
||||
* app/client/index.js
|
||||
Main Initialization Component of the Web Component App
|
||||
Main Initialization Component of the Web Component App.
|
||||
renders a performance-dashboard component, defines a custom element called
|
||||
web-app using LitElement.
|
||||
* app/client/components/AppElement.js
|
||||
|
|
@ -171,14 +177,19 @@
|
|||
|
||||
### tools
|
||||
|
||||
* RowingRecorder.js - A utility to record and replay flywheel measurements for
|
||||
* RowingRecorder.js
|
||||
A utility to record and replay flywheel measurements for
|
||||
development purposes.
|
||||
* ConfigManager.js - Merges the different config files and presents the
|
||||
* ConfigManager.js
|
||||
Merges the different config files and presents the
|
||||
configuration to the application
|
||||
* StravaAPI.js - Implements required parts of the [Strava API](https://developers.strava.com/)
|
||||
* AuthorizedStravaConnection.js - Creates an OAuth authorized connection to
|
||||
* StravaAPI.js
|
||||
Implements required parts of the [Strava API](https://developers.strava.com/)
|
||||
* AuthorizedStravaConnection.js
|
||||
Creates an OAuth authorized connection to
|
||||
[Strava](https://developers.strava.com/) Running, Cycling & Hiking App
|
||||
* Helper.js - Helper functions
|
||||
* Helper.js
|
||||
Helper functions
|
||||
|
||||
```html
|
||||
https://stackblitz.com/edit/lit-element
|
||||
|
|
@ -205,7 +216,7 @@ https://www.chartjs.org/docs/latest/samples/line/line.html
|
|||
* Stroke detection
|
||||
* Power (watts)
|
||||
* Split time (/500m)
|
||||
- Strokes per Minute
|
||||
* Strokes per Minute
|
||||
* Calories used (kcal)
|
||||
* Training Duration
|
||||
* Heart Rate (supports BLE and ANT+ heart rate monitors, ANT+ requires an ANT+
|
||||
|
|
@ -265,13 +276,16 @@ program in relation to improvements over time.
|
|||
|
||||
* Provide warning over excess heart rate while exercising:
|
||||
Heart rate should remain below upper limit of "expected zone".
|
||||
Advise that heart rate above upper limit by >1 bpm means user must reduce effort.
|
||||
Advise that heart rate above upper limit by >1 bpm means user must reduce
|
||||
effort.
|
||||
|
||||
* Instruction on when to take rest days.
|
||||
* Recording of heart rate after work-outs too, to identify pending illness.
|
||||
* Coach warns of overtraining when performance declines steadily over, say 4 or more, days.
|
||||
* Coach warns of overtraining when performance declines steadily over, say 4 or
|
||||
more, days.
|
||||
* When overtraining is indicated, Coach suggests: skip a day or two; eat more;
|
||||
Coach also warns of overtraining when, after a skip, performance has not returned to before.
|
||||
Coach also warns of overtraining when, after a skip, performance has not
|
||||
returned to before.
|
||||
* Coach suggests work rates based on recent past performance.
|
||||
* Perhaps present this as a choice for the user, perhaps between:
|
||||
(Coach's default, perhaps based on yesterday's performance), and (user choice).
|
||||
|
|
@ -333,9 +347,14 @@ tempo from time to time.
|
|||
|
||||
#### Fitness Dashboard
|
||||
|
||||
Fitness_Dashboard captures Ant+ and BLE data from power meters, heart rate monitors, fitness trainers and various other [devices](https://www.fitnesshrv.com/2024/01/11/devices.html).
|
||||
Fitness_Dashboard captures Ant+ and BLE data from power meters, heart rate
|
||||
monitors, fitness trainers and various other [devices](https://www.fitnesshrv.com/2024/01/11/devices.html).
|
||||
|
||||
The data is displayed in two ways. First is a set of graphs showing various statistics. Second a large display of the current values for the statistics from each device being monitored. The intent is to provide the equivalent of of a cycling computer with a much larger and easier to read interface suitable for using when training indoors.
|
||||
The data is displayed in two ways. First is a set of graphs showing various
|
||||
statistics. Second a large display of the current values for the statistics
|
||||
from each device being monitored. The intent is to provide the equivalent of
|
||||
a cycling computer with a much larger and easier to read interface suitable
|
||||
for using when training indoors.
|
||||
|
||||
Currently supported:
|
||||
|
||||
|
|
@ -348,7 +367,8 @@ Currently supported:
|
|||
|
||||
#### Fitness_ECG
|
||||
|
||||
Captures heart rate and ECG data from a Polar H10 heart rate monitor (proprietary BLE service). This is displayed as an ECG trace and heart rate graph over time.
|
||||
Captures heart rate and ECG data from a Polar H10 heart rate monitor (proprietary
|
||||
BLE service). This is displayed as an ECG trace and heart rate graph over time.
|
||||
|
||||
### Android
|
||||
|
||||
|
|
@ -359,15 +379,19 @@ EXR | Row together Virtually Subscription: € 7,95/month
|
|||
### [Coxwain](https://github.com/svenmeier/coxswain) [Android](https://play.google.com/store/apps/details?id=svenmeier.coxswain)
|
||||
|
||||
waterrower workout tracker,
|
||||
* [Coxwain2fit](https://github.com/inonoob/Coxswain2Fit) Convert garmin TCX export file from Coxswain android app (Waterrower) to a garmin FIT file.
|
||||
|
||||
* [Coxwain2fit](https://github.com/inonoob/Coxswain2Fit) Convert garmin TCX
|
||||
export file from Coxswain android app (Waterrower) to a garmin FIT file.
|
||||
|
||||
## Requests
|
||||
|
||||
An "unlocked" PM would be such an amazing training tool.
|
||||
|
||||
* Everything that ErgData does, without crashing.
|
||||
* Also average stroke rating could help a lot, especially on pieces where my coach gives us punishments for not hitting our goal average stroke rate exactly.
|
||||
* My only complaint with PM5 is that if you sync your HRM to it, you get your HR from the end of the split not the average across it. Sort that and I'm all set.
|
||||
* Also average stroke rating could help a lot, especially on pieces where my
|
||||
coach gives us punishments for not hitting our goal average stroke rate exactly.
|
||||
* My only complaint with PM5 is that if you sync your HRM to it, you get your HR
|
||||
from the end of the split not the average across it. Sort that and I'm all set.
|
||||
|
||||
The PM6 Super Plus:
|
||||
|
||||
|
|
@ -379,15 +403,36 @@ The PM6 Super Plus:
|
|||
* stroke length,
|
||||
* average stroke rate data to the tenth of a stroke,
|
||||
* current split to the tenth of a split
|
||||
* Accurate average heart rate data - right now the resulting heart rate for a piece seems closer to the final heart rate measured than the average for the piece
|
||||
* Ability to add a split distance by the push of a button (so if you do 1500m, with 250m splits, you push a button and it adds that distance to your piece)
|
||||
* Results graph that shows heart rate, stroke rate, split over the course of the piece
|
||||
* Accurate average heart rate data - right now the resulting heart rate for a
|
||||
piece seems closer to the final heart rate measured than the average for the
|
||||
piece
|
||||
* Ability to add a split distance by the push of a button (so if you do 1500m,
|
||||
with 250m splits, you push a button and it adds that distance to your piece)
|
||||
* Results graph that shows heart rate, stroke rate, split over the course of the
|
||||
piece
|
||||
* Front facing speakers
|
||||
* Netflix + spotify
|
||||
* LED backlit screen
|
||||
* Full colour display
|
||||
* Picture-in-picture or overlay (so you can have erg data plus another feed, perhaps a TV stream or something nice to watch). A headphone jack / bluetooth audio connection would be awesome too, with input either from streams or a radio/TV receiver. It would also give the option of something I've always wanted for training/coaching rate work - timing pips. Seriously, like a metronome, but for rowing, would be absolutely incredible for keeping focus / improving consistency.
|
||||
* Picture-in-picture or overlay (so you can have erg data plus another feed,
|
||||
perhaps a TV stream or something nice to watch). A headphone jack/
|
||||
bluetooth audio connection would be awesome too, with input either from
|
||||
streams or a radio/TV receiver. It would also give the option of something
|
||||
I've always wanted for training/coaching rate work - timing pips. Seriously,
|
||||
like a metronome, but for rowing, would be absolutely incredible for keeping
|
||||
focus / improving consistency.
|
||||
* Touch screen, and a good one at that. Buttons are nice but this is 2018.
|
||||
* WiFi / Mobile Data. Cables are also something which should be optional in all but the most critical situation. Obviously, for stability sensitive things like indoor rowing competitions in real-time, the Ethernet connection is absolutely irreplaceable, but additional connectivity for more general use would be an excellent feature.
|
||||
* Use of the data connection to allow me to store my data on a cloud based profile, great for shared ergs in clubs/gyms, just sign in and save/recall all your metrics, bonus points if you can access it from other platforms too for analysis. So much smoother and cleaner than a USB stick, much better UX too.
|
||||
* Buttons on the handle that control the PM6 and/or my music via bluetooth, because sometimes I'm just not feeling a track. Hate myself for adding this one but it would be cool as hell, plus great to be able to make changes (e.g. add 1000m to a steady state piece) mid-row without breaking rhythm.
|
||||
* WiFi / Mobile Data. Cables are also something which should be optional in all
|
||||
but the most critical situation. Obviously, for stability sensitive things
|
||||
like indoor rowing competitions in real-time, the Ethernet connection is
|
||||
absolutely irreplaceable, but additional connectivity for more general use
|
||||
would be an excellent feature.
|
||||
* Use of the data connection to allow me to store my data on a cloud based
|
||||
profile, great for shared ergs in clubs/gyms, just sign in and save/recall
|
||||
all your metrics, bonus points if you can access it from other platforms
|
||||
too for analysis. So much smoother and cleaner than a USB stick, much better
|
||||
UX too.
|
||||
* Buttons on the handle that control the PM6 and/or my music via bluetooth,
|
||||
because sometimes I'm just not feeling a track. Hate myself for adding this
|
||||
one but it would be cool as hell, plus great to be able to make changes
|
||||
(e.g. add 1000m to a steady state piece) mid-row without breaking rhythm.
|
||||
|
|
|
|||
Loading…
Reference in New Issue