As far as the FDM is concerned, there is an emerging AIAA standard for aircraft model exchange in XML (see daveml.nasa.gov). Bruce Jackson, author of LaRCSim, played a key role in the development of that standard. JSBSim also served as an inspiration as perhaps the first FDM to use XML to define an aircraft dynamic model (thanks to the urging of David Megginson and others).
JSBSim is moving towards compatibility with this emerging standard (which may soon come to be known as AeroML). As part of that, a key concept that AeroML embodies for an aircraft flight model is accountability (or trace-ability, if you prefer). That is, the aircraft flight model spec should include information about which version it is, who made it, if it is complete, revision history, where the data came from, which specific aircraft the model data represents, the date it was first created, contact information, how it can be distributed, etc. The new v2.0 specification for JSBSim aircraft includes several new features for tracking the kind of items mentioned above. Therefore, the user can know more about the flight model, what it can and cannot do, etc. Development continues on many fronts in FlightGear and JSBSim. Sometimes, development proceeds so quickly that the code and the flight models are not completely in step with each other. Jon -- Project Coordinator JSBSim Flight Dynamics Model http://www.jsbsim.org _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
