You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following series are always kept in metric mode: "alt", "calt", "vosc", "pco" (maybe others?) so all the plots use metric values. See [1] for the meaning of these series.
Summary values (e.g lap average) are displayed as imperial when that system is selected.
Trouble is that summary data when detecting various intervals (intervals.rkt) is expecting them to be always in metric (as the summary values are actually converted for imperial for display). We need to do something similar to the way we handle distance and speed ("dst" -- always metric, "distance" -- metric or imperial; "spd" -- always metric, "speed" -- metric or imperial)
New "altitude" and "corrected-altitude" series now track altitude in the
selected measurement unit (meters or feet), the "alt" and "calt" series remain
in meters only, for other calculations. This makes the elevation plot use the
correct values when the user has the Imperial units selected.
The following series are always kept in metric mode: "alt", "calt", "vosc", "pco" (maybe others?) so all the plots use metric values. See [1] for the meaning of these series.
Summary values (e.g lap average) are displayed as imperial when that system is selected.
Trouble is that summary data when detecting various intervals (intervals.rkt) is expecting them to be always in metric (as the summary values are actually converted for imperial for display). We need to do something similar to the way we handle distance and speed ("dst" -- always metric, "distance" -- metric or imperial; "spd" -- always metric, "speed" -- metric or imperial)
[1] https://github.com/alex-hhh/ActivityLog2/blob/master/doc/session-df.md
The text was updated successfully, but these errors were encountered: