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
First of all thank you for this project. As I am new to Garmin devices, I am very glad to have a tool running on my own server instead of Garmins servers.
I know that you are not working on fitplotter anymore, but I hope nevertheless to get some information from you: I am currently adapting fitplotter and fitalyser to my needs and stumbled upon "Median filter size" and "Average moving size". To be honest: I have no clue what both of them are doing. I did play around with the values but saw no differences in the plot area nor in the map. I did some superficial investigation in main.js, but this did not help me either, Can you please briefly explain what the two variables do? Thank you!
The text was updated successfully, but these errors were encountered:
If the inintial data are not noisy, these filters have no effects. Nowadays, it's the case because a smooth algorithm might already be implented into the watch hardware, howere, ten years ago, with the first Garmin watches, one typically had an issiue with noisy data
First of all thank you for this project. As I am new to Garmin devices, I am very glad to have a tool running on my own server instead of Garmins servers.
I know that you are not working on fitplotter anymore, but I hope nevertheless to get some information from you: I am currently adapting fitplotter and fitalyser to my needs and stumbled upon "Median filter size" and "Average moving size". To be honest: I have no clue what both of them are doing. I did play around with the values but saw no differences in the plot area nor in the map. I did some superficial investigation in main.js, but this did not help me either, Can you please briefly explain what the two variables do? Thank you!
The text was updated successfully, but these errors were encountered: