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
i am aware that the circling algorithm is one of the crucial parts of the analysis and that it might be sensitive to different logger interval settings.
to isolate things, i have started OpenSoar, another repo which you have already found i see ;)
i plan to improve the circling algorithm there, because it is a lot easier to isolate parts, write test etc. feel free to open a new issue there
Started testing this brilliant package and looks like logger interval is influencing the performance calculations (understandably when looking e.g. at thermal detection code).
E.g. check flight PB on https://www.soaringspot.com/en_gb/62th-hungarian-national-gliding-hajduszoboszlo-airport-2017/results/unknown/task-8-on-2017-07-14/daily
I think the logger interval is set to 1s in that flight.
Can you suggest a simple/quick way to tackle this?
The text was updated successfully, but these errors were encountered: