742
edits
Fr/High-Level Architecture: Difference between revisions
Jump to navigation
Jump to search
Traduction partielle
(Traduction partielle) |
(Traduction partielle) |
||
| Line 33: | Line 33: | ||
==Conception== | ==Conception== | ||
La conception globale entrevue est la suivante : | |||
* Intention d'utiliser OpenRTI comme RTI sous-jacent. Il s'agit d'un RTI standard IEEE 1516 open source, écrit par Mathias Fröhlich et disponible sur https://sourceforge.net/projects/openrti/. | |||
* Mathias a également développé une boîte à outils open source pour agir comme une bibliothèque d'interface, avec pour nom de code [[SimKit]]. Cela se trouve au-dessus du RTI et simplifie grandement l'interfaçage avec le RTI. L'intégration Python est également excellente , ce qui facilite l'écriture de scripts pour les modules fédérés. Simkit est disponible sur : https://sourceforge.net/projects/sim-kit/ | |||
==Federate Object Model== | En utilisant SimKit, le point d'intégration se trouve dans le code FlightGear au lieu de [[SimGear]]), en particulier le code se trouvant dans $FG_SRC/Network/HLA. | ||
==Federate Object Model (FOM)== | |||
A key part of the design is writing the Federation Object Model (FOM), which defines the objects and updates that are published by the RTI. While it might at first glance seem a good idea to use the FOM to share the internal property tree across multiple federates, this is probably the wrong way to use HLA as the granularity is too low <ref>https://sourceforge.net/p/flightgear/mailman/message/34795859/</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/34803436/</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/34794675/</ref> and it's likely to lead to synchonization issues. Instead, we'll need to make explicit decisions about the data models to communicate. | A key part of the design is writing the Federation Object Model (FOM), which defines the objects and updates that are published by the RTI. While it might at first glance seem a good idea to use the FOM to share the internal property tree across multiple federates, this is probably the wrong way to use HLA as the granularity is too low <ref>https://sourceforge.net/p/flightgear/mailman/message/34795859/</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/34803436/</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/34794675/</ref> and it's likely to lead to synchonization issues. Instead, we'll need to make explicit decisions about the data models to communicate. | ||
| Line 74: | Line 74: | ||
{{Appendix}} | {{Appendix}} | ||
== | ==Modules fédérés== | ||
Federates can be written in most languages, but SimKit provides very good hooks for writing them in C++ and Python. | Federates can be written in most languages, but SimKit provides very good hooks for writing them in C++ and Python. | ||
| Line 90: | Line 90: | ||
}}</ref> | }}</ref> | ||
== | ==Statut actuel == | ||
Last updated: (10/2022) | Last updated: (10/2022) | ||
| Line 144: | Line 144: | ||
<references/> | <references/> | ||
== | == A ce peopos == | ||
For additional information, please see: | For additional information, please see: | ||
* [[Technical_Reports#A_New_Architecture_for_FlightGear_Flight_Simulator]] | * [[Technical_Reports#A_New_Architecture_for_FlightGear_Flight_Simulator]] | ||
| Line 153: | Line 153: | ||
* [[Distributed Interactive Simulation]] (DIS specific review of the FlightGear multiplayer system/protocol and its limitations, which can be addressed via HLA) | * [[Distributed Interactive Simulation]] (DIS specific review of the FlightGear multiplayer system/protocol and its limitations, which can be addressed via HLA) | ||
== | == Liens externes == | ||
* {{wikipedia|High-level architecture (simulation)}} on Wikipedia | * {{wikipedia|High-level architecture (simulation)}} on Wikipedia | ||