20,741
edits
High-Level Architecture: Difference between revisions
→Federates
m (→Current Status) |
|||
| Line 76: | Line 76: | ||
For some Subsystems split off from the existing FlightGear source, it's fairly easy to create an executable with its own property tree<ref>https://sourceforge.net/p/flightgear/mailman/message/34632142/</ref> and have shared C++ code to map FOM objects to property values. However, this is an implementation detail - the whole point of HLA and the FOM is that it makes no assumptions about what Federates do with the data. | For some Subsystems split off from the existing FlightGear source, it's fairly easy to create an executable with its own property tree<ref>https://sourceforge.net/p/flightgear/mailman/message/34632142/</ref> and have shared C++ code to map FOM objects to property values. However, this is an implementation detail - the whole point of HLA and the FOM is that it makes no assumptions about what Federates do with the data. | ||
Regarding weather, in a HLA/RTI context the way to do this would be to have a weather engine as an RTI Federate. This would run any required weather simulation, and pass (very) local weather conditions to each of the aircraft/tower/windsock in the simulation, plus publish position information on clouds for use by visualiation engines.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35595300/ | |||
|title = <nowiki> Re: [Flightgear-devel] Traffic 2020: Towards a new Development | |||
Model for FlightGear AI Traffic </nowiki> | |||
|author = <nowiki> Stuart Buchanan </nowiki> | |||
|date = Jan 10th, 2017 | |||
|added = Jan 10th, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
==Current Status == | ==Current Status == | ||