PySoar
PySoar copied to clipboard
GliderGeek
Gliding competition analysis
run analyses in batch-mode to establish how stable the programm is. this is only asserts that the program does not crash, it does not say that the outcomes are correct...
Apparently its possible for a competition day to have identical competition id's for different flights: http://www.soaringspot.com/en_gb/cae-nls-nederlandse-kampioenschappen-zweefvliegen-2012/results/club/task-1-on-2012-05-17/daily This currently results in only the first flight being analyzed
use optional input parameter utc_diff with default at zero.
this will only be a real issue when general turnpoints are allowed. following competition: http://www.soaringspot.com/en_gb/54th-australian-nationals-ozglide-benalla-gld-2016/results/18-meter/task-7-on-2016-01-12/daily 12 - YL is scored as finished, but SoaringSpot says he outlanded. update: PySoar does...
http://www.soaringspot.com/en_gb/jwgc2017/results/club/practice-1-on-2017-07-27/daily notice that there are a lot of different tasks outputted in console
http://www.soaringspot.com/en_gb/internationaler-hahnweide-segelflugwettbewerb-2017/results/standard/task-6-on-2017-05-27/daily - firstly there is the wrong task again (see #98) - secondly the DaeC keyhole (or similar shape) is incorrectly handled, leading to landouts in first waypoint (see #111...
http://www.soaringspot.com/en_gb/vch-povd-2017-day-3-hoogeveen-2017/results/lang/task-1-on-2017-06-04/daily from user: > Pysoar Showed weird start heights for multiple flights (1 m, -5 m, 0m). We did use a start cylinder. Some flights were also analysed incorrectly in...
now HC is not analyzed, because then the rank will not be an int, can be solved with string ranking edit: maybe better to use ints 0, -1, -2 etc...