20,741
edits
Implementing VNAV support in FlightGear: Difference between revisions
Jump to navigation
Jump to search
m
Implementing VNAV support in FlightGear (view source)
Revision as of 04:19, 1 December 2013
, 1 December 2013→Methods for implementing VNAV
| Line 89: | Line 89: | ||
== Methods for implementing VNAV == | == Methods for implementing VNAV == | ||
#<big>(virtual flight-testing database)</big>: | #<big>(virtual flight-testing database)</big>: | ||
Instead of doing all this "live" inside the FDM via a reverse solver, another method would be doing virtual test flights and gathering the required flight data to come up with a virtual PerfDB, i.e. actually write test data to some form of database (eg. SQLite) so that this could be queried at runtime in FG. | Instead of doing all this "live" inside the FDM via a reverse solver, another method would be doing virtual test flights and gathering the required flight data to come up with a virtual PerfDB, i.e. actually write test data to some form of database (eg. SQLite) so that this could be queried at runtime in FG. | ||
'''What is required to apply this method?''' | '''What is required to apply this method?''' | ||
* data analysis to determine the scope of fields, and the domain of values for the gathered data | * data analysis to determine the scope of fields, and the domain of values for the gathered data (weight & balance, fuel, weather, temperatures, aircraft configurations) | ||
* an agreed standard of tests applied to all airplanes (climb/descend profiles with different configurations) | |||
* an agreed standard of tests applied to all airplanes | |||
* an agreed format(data file structure) in which this data is formated, or using an improved database approach and provide mapping via a DBMS for a changing file structure | * an agreed format(data file structure) in which this data is formated, or using an improved database approach and provide mapping via a DBMS for a changing file structure | ||
* an agreed property inside flightgear to hold this data (a single property won't suffice) | |||
* an agreed property inside flightgear to hold this data | * an interface for flightgear to query the data file through the DBMS (FlightGear's scripting language Nasal does have SQLite bindings, another option would be a flat text/XML file) | ||
* an interface for flightgear to query the data file through the DBMS | |||
* a way of implementing this data into the aircraft's model(usually xml file) | * a way of implementing this data into the aircraft's model(usually xml file) | ||
== Resources == | == Resources == | ||