mutability / mlat-server Goto Github PK

i have installed all the pre-reqs, but when i attempt to run mlat-server --help
i get: "mlat-server: command not found"

any guidance would be greatly appreciated

An actual beast, set to --input-type beast, will never show sync stats towards receivers of type radarcape. If set to dump1090, it will show sync.

The log file indicates that the receiver pair is used for solutions, so it actually has sync, but not shown in the sync stats table.

If 2 dump1090 system are both set to --input-type beast (for testing this issue, or by mistake), they will also not show sync with radarcapes, not with real beast systems, and not with each other, but with normal dump1090 systems....

(The client will auto-detect the correct format but has already informed the server of the manually set format, and as discussed, the on-the-fly format change is not implemented in mlat-server. )

What is the difference between beast and dump input formats?

Is there a mailing list or anywhere else to discuss mlat-client and mlat-server (and maybe your dump1090 variants)? Specifically I'm looking for experience reports: What's the current status, does it work, how well does it work, etc.?

Why shows the wrong altitude?
http://screenshot.sh/ovTH2kNjqVui4

Hi.
I'm trying to run mlat-server, but I'm getting some errors with new and old version of pygraph. I've tried with new pygraph library (new repo, link in old one). Got this error (a lot!) and no tracking at all:

AttributeError: module 'pygraph.algorithms.minmax' has no attribute 'minimal_spanning_tree'
20181210 10:55:01.056  ERROR    asyncio              Exception in callback MlatTracker._resolve(<mlat.server....x7f30f2c904a8>)
handle: <TimerHandle when=1080929.026755315 MlatTracker._resolve(<mlat.server....x7f30f2c904a8>)>
Traceback (most recent call last):
  File "/usr/lib64/python3.6/asyncio/events.py", line 145, in _run
    self._callback(*self._args)
  File "/home/satradar/mlat-server/mlat/server/mlattrack.py", line 174, in _resolve
    timestamp_map=timestamp_map)
  File "/home/satradar/mlat-server/mlat/server/clocknorm.py", line 186, in normalize
    mst_forest = pygraph.algorithms.minmax.minimal_spanning_tree(g)

Now, using old pygraph repository (link in mlat-server README), I can get it running and tracking some aircrafts, but still wth errors in log:

Dec 10 11:12:42 skynet4 python3.6[12654]: future: <Task finished coro=<JsonClient.handle_connection() done, defined at /home/satradar/mlat-server/mlat/server/jsonclient.py:262> exception=CancelledError()>
Dec 10 11:12:42 skynet4 python3.6[12654]: concurrent.futures._base.CancelledError
Dec 10 11:12:42 skynet4 python3.6[12654]: 20181210 11:12:42.656  ERROR    asyncio              Task exception was never retrieved
Dec 10 11:12:42 skynet4 python3.6[12654]: future: <Task finished coro=<JsonClient.handle_connection() done, defined at /home/satradar/mlat-server/mlat/server/jsonclient.py:262> exception=CancelledError()>
Dec 10 11:12:42 skynet4 python3.6[12654]: concurrent.futures._base.CancelledError
Dec 10 11:12:42 skynet4 python3.6[12654]: 20181210 11:12:42.656  ERROR    asyncio              Task exception was never retrieved
Dec 10 11:12:42 skynet4 python3.6[12654]: future: <Task finished coro=<JsonClient.handle_connection() done, defined at /home/satradar/mlat-server/mlat/server/jsonclient.py:262> exception=CancelledError()>
Dec 10 11:12:42 skynet4 python3.6[12654]: concurrent.futures._base.CancelledError
Dec 10 11:13:16 skynet4 python3.6[12654]: 20181210 11:13:16.893  INFO     kalman               E48994 acquiring.
Dec 10 11:15:51 skynet4 python3.6[12654]: 20181210 11:15:51.559  INFO     kalman               E47EC0 acquiring.

any tips how to solve it?!

Hi
When I use my mlat-server is tracking is jagged with jumps http://screenshot.sh/m1CmWCqce1Lac
Such jagged is not in results from FA.

In working to load balance MLAT, I noticed that the mlat-server code includes partitioning support. Is there a corresponding piece of infrastructure that you've used to route MLAT data or aggregate single clients to multiple MLAT instances?

Output altitude should be decoded altitude (ac.altitude ? ) if available, otherwise multilaterated altitude?

Today we get relatively big errors in altitude even when aircraft xmits its own altitude.

I tried everything I thing. Installed via pip, pip3, conda.. Without effect. What's going on?

Hi, I have noticed the server sends results in beast format and to port 30104, it is like piaware does.
I do not know if it is a problem when running Piaware and mlat-client at the same time and if it is related with the problem to get mlat results from mlat-client.

Hi
A lot appears hexes ghost. I always position shown side by side.
The following screenshot of the case:
http://screenshot.sh/mKBhtdz6m6NOY
And it appears in the results of the mlat-server.

Is the server can manage the Mode A/C?

For most aircraft displays the wrong callsign (aircraft sends valid) or it is not there.
Knowing one letter or number is incorrect.

Py2cairo is as someone on the web said "notoriusly hard to install".

For coverage generation cairocffi bind works perfectly and it is a lot easier to install (works with just pip install + necessary dev libs)

Example:
tmuic@024a52d

It would be nice with a beast-format output with MLAT timestamp so that VRS and other display softwares understand that it is an mlat position. Just like mlat-results in mlat-client.