Re-hosting of an aerodynamic model (as well as other model data that are presented in tabular table-lookup form) from one simulation platform to another can be a time-consuming process. It typically involves the conversion of data stored in a format compatible with the source
simulator to a format used by the destination simulation environment. Additionally, due to the differences in variable naming conventions ("AOA" in one simulation versus "Alpha" in another) code-level changes for the mechanization of the data sets are usually required and often need
extensive verification and validation efforts to confirm the accuracy of the re-hosted model.
process is greatly simplified with the availability of the AeroPort
tool. Aeroport provides a gateway for many simulation formats into D-Six,
but because it also allows the user to export their data to another
target format, it can serve as a "universal translator" for any simulation
user. Thus it can operate as a D-Six support tool, or as a stand alone
tool for any simulation user/developer that has to import and export
simulation data different from their host environment format.
Aeroport currently supports over ten different simulation formats, including a MATLAB .mat format that allows users to import or export their tables between their host format and MATLAB. This powerful capability allows the entire model database (or subsets of the database) to be
exported to MATLAB to be plotted, evaluated, manipulated, etc. using the powerful MATLAB toolset, and then imported back into D-Six or one of the other target formats. The D-Six Developer package includes an Aeroport filter "Wizard" for users who wish to build their own custom data
import/export filter, or Bihrle can also provide an import filter for your format if needed.
Aeroport was developed to provide model database conversion capabilities for any type of tabular function, but can also be extended to take D-Six simulation tables and code and process the entire model into a code and table compatible output for another simulation environment. This
approach was successfully used in the support of a full flight training simulation that was operating on a Wind Rivers real time simulation host. D-Six was used as the model development platform, and the entire simulation database and model code was processed through Aeroport to provide
the customer with model updates that could be immediately compiled and linked in their system.
The Aeroport tool provides the user with a number of automated operational features that greatly expedite the model database conversion process. The following is a listing of some of the key features:
- Variable names (for both the lookup variables and the dependent variables) can be graphically remapped before the converted data tables are generated. Additionally, the name changes for the dependent variables can be applied globally to all tables or to only the selected data
- All or only the selected tables are converted. This feature is particularly useful if the user wishes to convert only a portion of a large data file, such as in the case of a periodic data base update.
- All variables from an existing D-Six project can be loaded and displayed for reference and use on the variable or table renaming process.
- The order of the independent variables can be manipulated. For example, the Bihrle 2.0 aerodynamic data format is easier to read and manipulate when the two dependent variables with the highest number of break points are assigned to the first and second independent variable
positions, since this requires the least number of data files. The user may choose to manually sort each lookup term or use the auto-sort feature to alter the order of the independent variables.
- The workspace can be saved so that the conversion of a large data base file can be performed over several sessions.
- In addition to generating data table files in Bihrle 2.0 format, a conversion log file, "import.txt," is generated. This text file can be read directly into D-Six's InfoFile interface so that the time-consuming process of mechanizing a database is significantly automated and
- The ability to globally apply table suffix and prefix names to distinguish between the different sets of table data.
- Scripting language for automating repetitive conversion processes.
- Output of data in any supported formats. This tool may be used as a format translator to convert data to and from two dissimilar formats.