Opened 13 years ago
Closed 13 years ago
#104 closed task (worksforme)
Review algorithm for landings
| Reported by: | smoser | Owned by: | smoser |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: |
Description (last modified by )
Today (2013-04-01), I have seen several landings that were not recorded correctly. Especially tow-planes that lost connectivity on the runway make troubles. Investigate in that.
Change History (2)
comment:1 Changed 13 years ago by
| Status: | new → accepted |
|---|---|
| Version: | 1.1.0 (Startlist release) |
comment:2 Changed 13 years ago by
| Description: | modified (diff) |
|---|---|
| Resolution: | → worksforme |
| Status: | accepted → closed |
As a workaround: The visible devices are removed after a long time (default 16h). If we loose connection before the landing is recorded, the landing will be recorded as soon as the device re-appears. At least the book-keeping is correct, even if we cannot determine the flight time exactly.
Note: See
TracTickets for help on using
tickets.
![(please configure the [header_logo] section in trac.ini)](/trac/flarmradar/chrome/site/your_project_logo.png)
There is currently not much we can do about that. The landing is not recorded if transition AIRBORNE -> TAXI,PARKED is not recorded. That can happen e.g. in the following scenario:
Once that we introduce the concept of a "Flight" this will become better.