search

weglide / bugtracker

WeGlide platform bug tracker.
https://www.weglide.org
11 stars 1 forks source link

Task valid, non-detected #174

Closed deltafox44 closed 7 months ago

deltafox44 commented 2 years ago

Describe the bug The task has been completed but "Task" tab is not present To Reproduce See flight 148258 Task is shown as declared on the logger. Start line, turnpoint sector and finish line seem OK. But the "Task" tab is not present as when the task was not completed. Perhaps due to the fact that the finish line was crossed on the ground (which is valid, at least as of IGC rules) Expected behavior When a task has been declared, the Task box (below the glider id) indicates the Distance and type (O/R, triangle, 3TN...) but that's all...There should be also either "Completed", or the distance missed on task to the goal, or the next turn point, when not completed) i.e. "finish missed for 30 km" or "100 m to 2nd TP", or any other reason for which the system decided it was not completed (for instance altitude difference greater than 1000 m, if required). It would help understand why Task tab is not present and what was wrong. Screenshots image

moldhouse commented 2 years ago

At the moment we only score tasks to the point where the landing is detected. We will look into that but will take some time. Showing more info why the task has not been completed is also in the works.

deltafox44 commented 1 year ago

Here is another case where task has been completed but not scored (Task tab not present) - flight 185021 on 13 July. I cannot see why Task tab does not appear, all waypoints were turned OK

The only particularity I see is that start line was crossed above 1000 m AGL (but less than 1000 m above finish line crossing) and at 260 km/h and that task was declared both via WeGlide - task 135985 and the logger (with a few meters difference in waypoints coordinates between the two, as often).

deltafox44 commented 8 months ago

In this flight also https://www.weglide.org/flight/299894 the task has been completed, TP sectors, lines, loss of height are OK, in the Netcoupe the same flight is scores "as declared"

But WeGlide consider the task is invalid (red dot)... Why ???

As commented here https://github.com/weglide/bugtracker/issues/213#issuecomment-1796999385 clicking on the red dot should show why the task cannot be scored...

deltafox44 commented 7 months ago

213 has now been solved and clicking on the red dot does show why the task is not scored (for new flights). To solve the mystery of the flights above, I re-loaded them and here are the results:

https://www.weglide.org/flight/148258 image

https://www.weglide.org/flight/185021 image In the original flight there has been a declaration through WeGlide adn the task is invalid. Re-loading the flight, it takes into account the logger declaration instead, and the task is validated !

The start altitude was 1301 m, the finish altitude was 1209 m (at 17:23:20). But at landing, the WeGlide finish line has been crossed again at 217m (at 17:51:26), and the task is apparently deemed invalid because the loss of height is greater than 1000 m ; the finish point declared in the logger is 100 m more to the south thus there is no second finish line crossing and in this case the task is validated.

The WeGlide task seems to be invalidated for a loss of height exceeding 1000 m.

https://www.weglide.org/flight/299894 image Same problem as above, with a confirmation by the error message (altitude difference too large). Start altitude was 1185m, finish 205m at 17:58:57 with a second crossing at 168m at 18:00:51

Conclusion :

moldhouse commented 7 months ago

We have converted this to multiple internal issues which have been solved (not deployed yet), so I'll close this for now. As always, thank you very much for your accurate reporting and for helping us improve WeGlide 👍