265
edits
ATC-pie: Difference between revisions
Version update (v1.0.1)
Mickybadia (talk | contribs) m (v0.9.3) |
Mickybadia (talk | contribs) (Version update (v1.0.1)) |
||
| Line 10: | Line 10: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = February 1, 2015 | | initialrelease = February 1, 2015 | ||
| latestrelease = 0. | | latestrelease = 1.0.1 (Dec. 6, 2016) | ||
| writtenin = Python3 | | writtenin = Python3 | ||
| os = Any | | os = Any | ||
| Line 22: | Line 22: | ||
'''ATC-pie''' is an [[air traffic control]] simulation program allowing to play solo games, connect to [[FlightGear]] multi-player networks and set up tutorial sessions for teacher supervision of an ATC student. It features en-route centre control (CTR) as well as airport-based service (TWR, APP, GND...) where 3d tower viewing is possible. It is essentially designed for realism and simulates many tasks of real-life ATC such as strip rack and sequence management, transponder identification, handovers to/from neighbouring controllers, ATIS recording, flight plan editing, routing and conflict anticipation. | '''ATC-pie''' is an [[air traffic control]] simulation program allowing to play solo games, connect to [[FlightGear]] multi-player networks and set up tutorial sessions for teacher supervision of an ATC student. It features en-route centre control (CTR) as well as airport-based service (TWR, APP, GND...) where 3d tower viewing is possible. It is essentially designed for realism and simulates many tasks of real-life ATC such as strip rack and sequence management, transponder identification, handovers to/from neighbouring controllers, ATIS recording, flight plan editing, routing and conflict anticipation. | ||
The program is free and open source, and programmed in Python3 for Qt5 hence system-independant. Only Python3 and its Qt5 bindings must be installed. That done, it is meant to work straight away, with no make/compile command to run or external resource to install (except for | The program is free and open source, and programmed in Python3 for Qt5 hence system-independant. Only Python3 and its Qt5 bindings must be installed. That done, it is meant to work straight away, with no make/compile command to run or external resource to install (except for tower viewing, which requires a running FlightGear install and the appropriate scenery). | ||
== Program features == | == Program features == | ||
| Line 30: | Line 30: | ||
=== General features === | === General features === | ||
Available | Available games: | ||
* | * FlightGear multi-player server connection ([[FGMS]]) | ||
* For all types: en-route centre or airport control mode | * Solo games with AI IFR traffic | ||
* Teacher–student tutoring sessions | |||
* For all game types: en-route centre or airport control mode | |||
* For all airport games: tower view available (rendered by FlightGear) | |||
Common data sources: | Common data sources: | ||
| Line 40: | Line 43: | ||
* Real world declination lookup and true/magnetic distinction | * Real world declination lookup and true/magnetic distinction | ||
* Script to assist data import from .sct sector files (EuroScope/[http://www.vatsim.net VATSIM], IVAO) | * Script to assist data import from .sct sector files (EuroScope/[http://www.vatsim.net VATSIM], IVAO) | ||
* Custom background images (integrated [[OpenStreetMap]] retrieval helper) | |||
FlightGear multi-player games: | FlightGear multi-player games: | ||
* Weather: real world METAR retrieval | * Weather: real world METAR retrieval | ||
* ATC handovers: strip exchange with other ATC-pie and [[OpenRadar]] instances in range | * ATC handovers: strip exchange with other ATC-pie and [[OpenRadar]] instances in range | ||
* Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), incl. in-game retrieval, filing and editing (work on local copies and manage sync with online status), opening and closing | * Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), incl. in-game retrieval, filing and editing (work on local copies and manage sync with online status), opening and closing | ||
* In-app | * In-app announcement of ATC sessions on Lenny64's popular event page | ||
Solo games: | Solo games: | ||
* | * In airport mode, configurable combination of TWR, GND, APP and DEP positions | ||
* Randomised weather | |||
* Handovers to/from virtual ATCs | * Handovers to/from virtual ATCs | ||
* Airline choice and custom aircraft appearence | |||
* Airline choice | * Configurable runways in use, airspace and entry/exit/routing points | ||
* Configurable runways in use and entry/exit/routing points | |||
* Adjustable difficulty (traffic density) | * Adjustable difficulty (traffic density) | ||
* Departure–arrival and ILS–visual balance options | * Departure–arrival and ILS–visual balance options | ||
| Line 68: | Line 70: | ||
* Notification system combining selectable sounds, status bar messages and time-tagged history | * Notification system combining selectable sounds, status bar messages and time-tagged history | ||
* Notes, window state, general and location-specific settings saved on close and restored on restart | * Notes, window state, general and location-specific settings saved on close and restored on restart | ||
* Customisable colours | * Customisable colours | ||
* Instruct taxi, assign vectors and change routes with direct drag-and-drop mouse gestures | |||
* Multiple weather stations | |||
=== ATC surveillance === | === ATC surveillance === | ||
| Line 79: | Line 81: | ||
* Open multiple radar screens | * Open multiple radar screens | ||
* Configurable horizontal and vertical radar ranges and rotation speed | * Configurable horizontal and vertical radar ranges and rotation speed | ||
* Individual and general cheat modes | * Individual and general cheat modes | ||
* Ignore contacts | * Ignore contacts | ||
| Line 95: | Line 94: | ||
Strips, racks, flight plans: | Strips, racks, flight plans: | ||
* User-defined racks with configurable colours for linked radar contacts | * User-defined racks with configurable colours for linked radar contacts | ||
* | * Runway boxes with automatic WTC timers when freed | ||
* Loose strip bays with customisable backgrounds | |||
* Link strips | * Link strips, FPLs and radar contacts to merge details and inform radar display, tracking conflicts | ||
* | * Mouse drag to move strips along and across racks, runway boxes and loose strip bays | ||
* Handovers with neighbouring ATCs | |||
Routes, vectors, conflicts: | Routes, vectors, conflicts: | ||
| Line 104: | Line 104: | ||
* Route presets and quick retrieval between two end airports | * Route presets and quick retrieval between two end airports | ||
* Current leg and next waypoint display with geodesic calculations of headings and distances | * Current leg and next waypoint display with geodesic calculations of headings and distances | ||
* Anticipated path conflict warnings and separation incident alarm | * Anticipated path conflict warnings and separation incident alarm | ||
* Visible mismatches between assigned vectors and picked up positions (see [[:File:ATC-pie-screenshot-courseAndAssignmentsGraphics.png|all-in-one graphics]]) | * Visible mismatches between assigned vectors and picked up positions (see [[:File:ATC-pie-screenshot-courseAndAssignmentsGraphics.png|all-in-one graphics]]) | ||
Misc. tools: | |||
* Quick point-to-point heading and distance measuring tool and access to Earth coordinates | |||
* Direct text annotation of radar screen | |||
* Custom alarm clocks with quick two-key timer set-up | |||
* AD/nav point browser and indicator | |||
=== Communications === | === Communications === | ||
| Line 135: | Line 140: | ||
=== General === | === General === | ||
You are the air traffic controller, and | You are the air traffic controller, working with or without a tower window or radar scope, depending on your position and local facility. Players will connect to the network (multi-player), AI traffic be simulated (solo), or teacher traffic generated (tutorial session), with different types of aircraft and [[transponder]] equipment. | ||
* if a transponder is off | |||
As in real life, your main radar technology is [http://en.wikipedia.org/wiki/Secondary_surveillance_radar SSR], hence unless you cheat or activate the primary radar, will show you only what you pick up from on-board transponders in its range. This means: | |||
* if a transponder is off, you will not see the aircraft on your radar screen; | |||
* if a transponder is on, you will at least be able to see its position and read the transponder code, possibly its altitude and even its type and callsign, depending on the mode set by the pilot. | * if a transponder is on, you will at least be able to see its position and read the transponder code, possibly its altitude and even its type and callsign, depending on the mode set by the pilot. | ||
| Line 154: | Line 161: | ||
=== Radar identification === | === Radar identification === | ||
[[File:ATC-pie-screenshot-radarIdentification.png|thumbnail|Radar identification: both matched strip and radar contact marked in blue]] | [[File:ATC-pie-screenshot-radarIdentification.png|thumbnail|Radar identification: both matched strip and radar contact marked in blue]] | ||
To ''identify'' an aircraft and link the right radar contact to a strip, an ATC can rely on different things. He can read an aircraft's callsign straight away if its transponder has mode S turned on, tell from reported positions and altitudes, or use a transponder code. For instance, say a VFR traffic makes an initial radio contact giving his callsign and approximate position. ATC will typically pull out a new blank strip and give the pilot a unique transponder code to squawk, writing it on the strip alongside the announced callsign, then wait for it to appear on the radar. This allows for '''radar identification''' of aircraft–strip pairs such that: | To ''identify'' an aircraft and link the right radar contact to a strip, an ATC can rely on different things. He can read an aircraft's callsign straight away if its transponder has mode S turned on, tell from reported positions and altitudes, or use a transponder code. | ||
For instance, say a VFR traffic makes an initial radio contact giving his callsign and approximate position. ATC will typically pull out a new blank strip and give the pilot a unique transponder code to squawk, writing it on the strip alongside the announced callsign, then wait for it to appear on the radar. This allows for '''radar identification''' of aircraft–strip pairs such that: | |||
* the strip is assigned a transponder code; | * the strip is assigned a transponder code; | ||
* no other strip is assigned the same code; | * no other strip is assigned the same code; | ||
* the aircraft is the only | * the aircraft is the only unidentified traffic squawking that code in radar range. | ||
ATC-pie identifies such pairs automatically and reports them to you so you can properly link the two and get back to the pilot: "radar identified". | ATC-pie identifies such pairs automatically and reports them to you so you can properly link the two and get back to the pilot: "radar identified". | ||