-
Notifications
You must be signed in to change notification settings - Fork 28
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
Inconsistent Correlation Behaviour in Pro Mode #75
Comments
What were the assigned and actual used Codes by these two aircraft? |
Unknown in terms of their actually used codes. Their assigned codes were as specified in the departure list. |
As you have accept_pilot_squawk set true, according to the Wiki a code from the list do_not_autocorrelate_squawks is considered as a "correct" code, too. And the label is then displayed as a consequence. |
As far as I am aware, this is only the case if the aircraft has not been assigned a squawk already by ES. |
I understand it differently reading the wiki. Be also aware that the ES pro mode is not the same as the vSMR pro mode, hence different logics can apply. |
In this scenario, BAW189 (abeam A10W) is representing the correct pro-mode correlation behaviour as they are not squawking as assigned. However, BAW978J, abeam stand 522, is showing as correlated despite not squawking correctly.
vSMR_Profiles.json is as follows:
The text was updated successfully, but these errors were encountered: