-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ghost hex #7
Comments
Sounds like bad input data. What is your receiver configuration? If you use --aggressive, turn it off. |
I have connected about 100 receivers and do not know what is the configuration of the other receivers. |
What mlat-client version are you using?
|
0.2.5 dev |
That is a wide range of code. What's the commit hash you're on? I am particularly interested in whether you have this commit included: mutability/mlat-client@7f25d8e |
I have a version of 2 March |
OK, so mlat-client isn't contributing to the problem, it's just that you have bad data from your receivers. |
I noticed another relationship, these empty hexes they appear behind him true hex |
When connected about 100 receivers how to verify that the receiver sends bad data? |
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.
The text was updated successfully, but these errors were encountered: