Skip to content

Python: drop the metres-versus-millimetres reason for skipping oarlock fields. #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sanderroosendaal merged 2 commits into from
Oct 10, 2026
Merged

Python: drop the metres-versus-millimetres reason for skipping oarlock fields. #30

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5435b1b
Python: drop the metres-versus-millimetres reason for skipping oarloc…
Oct 7, 2026
889c2d5
Merge main into python/effective-length-per-side-mm
Oct 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion python/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ so this library writes and reads ID 93.
**Not implemented** (Level 3–4, or blocked on draft defects):

- Oarlock summary fields 11–18
- Dual-oarlock 200–211 (210/211 have a metres vs millimetres conflict in the draft)
- Dual-oarlock 200–211
- In-stroke axis metadata 90–92, curve arrays, curve summaries, `.instroke.json`
- WorkoutState enumeration (the draft has no value table; ID 9 is an opaque UINT8)

Expand Down
Loading