Issue with Conflict Detection

[04Jjromy]

Hi Bluesky Team,

I am currently working on a project where I am creating a GUI to display conflict pairs, vertical separation and horizontal separation, and time to conflict between aircraft pairs in conflict.

I have successfully created the simulation and the gui which is able to stream the data accurately. However, it is:

Firstly, only able to detect head on conflict.

Secondly, only able to detect conflicts with time to conflict below 5 mins. I need a minimum of 20 minutes.

May I know if you have any suggestions on how I can solve this please?

[04Jjromy]

@jooste @

[jooste]

Hi @04Jjromy,

The default lookahead time is indeed set to five minutes. You can select a different lookahead time with the DTLOOK command, either globally, or per aircraft. The built-in conflict detection method is state-based, so does not incorporate trajectory change points in its prediction. Perhaps this is why you are getting undetected conflicts? If not please provide a scenario where you know that there is a conflict within the lookahead time, but that is not detected by the built-in conflict detection algorithm.