Oliver Jowett
Oliver Jowett
It works for me, so there's something about your python install that you'll have to work out.
Ah, if you have the client software installed systemwide, that interferes with the server packages. Try uninstalling the client, or run the server under virtualenv.
Isn't the error message selfexplanatory?
The shebang line explictly invokes python3.4, so nope, it's not that. When you check that numpy is importable, are you running python3?
Show me exactly what you're running and what you get back.
``` #!/bin/sh D=`dirname $0` MLAT_CPU_PROFILE=1 $D/mlat-server \ --client-listen 40147:40147 \ --basestation-connect localhost:31003 \ --filtered-basestation-connect localhost:31004 \ --write-csv $D/positions.csv \ --work-dir $D \ --check-leaks \ >>$D/server.log 2>&1 & echo "$!" >$D/server.pid...
Coverage maps requires that you generate the tiles separately e.g. from cronjob. The sync page requires that you make sync.json (generated by the server) available in the same dir -...
There's no difference in input formats. The only real difference is that you might want different estimates of receiver clock stability/jitter depending on whether the receiver hardware is a rtlsdr...
Not currently. The main issue is that the current code uses the ICAO address to assign messages to a track. With Mode A/C you can't do that so reliably or...
I do have hardware, I'll have an experiment. (From looking through the library/firmware, I think that _maybe_ it's safe to call `airspy_set_samplerate` while streaming data; the firmware seems to have...