AIAA S-119-2011 Flight Dynamics Model Exchange Standard《飞行动力学模型交换标准》.pdf

《AIAA S-119-2011 Flight Dynamics Model Exchange Standard《飞行动力学模型交换标准》.pdf》由会员分享，可在线阅读，更多相关《AIAA S-119-2011 Flight Dynamics Model Exchange Standard《飞行动力学模型交换标准》.pdf（129页珍藏版）》请在麦多课文档分享上搜索。

1、ANSI/AIAA S-119-2011 Standard Flight Dynamics Model Exchange Standard AIAA standards are copyrighted by the American Institute of Aeronautics and Astronautics (AIAA), 1801 Alexander Bell Drive, Reston, VA 20191-4344 USA. All rights reserved. AIAA grants you a license as follows: The right to downloa

2、d an electronic file of this AIAA standard for storage on one computer for purposes of viewing, and/or printing one copy of the AIAA standard for individual use. Neither the electronic file nor the hard copy print may be reproduced in any way. In addition, the electronic file may not be distributed

3、elsewhere over computer networks or otherwise. The hard copy print may only be distributed to other employees for their internal use within your organization. ANSI/AIAA S-119-2011 American National Standard Flight Dynamics Model Exchange Standard Sponsored by American Institute of Aeronautics and As

4、tronautics Approved 25 March 2011 American National Standards Institute Abstract This is a standard for the interchange of simulation modeling data between facilities. The initial objective is to allow easy, straightforward exchanges of simulation model information and data between facilities. The s

5、tandard applies to virtually any vehicle model (ground, air, or space), but most directly applies to aircraft and missiles. ANSI/AIAA S-119-2011 ii Approval of an American National Standard requires verification by ANSI that the requirements for due process, consensus, and other criteria have been m

6、et by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Cons

7、ensus requires that all views and objections be considered, and that a concerted effort be made toward their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufac

8、turing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the r

9、ight or authority to issue an interpretation of an American National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American

10、National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken to affirm, revise, or withdraw this standard no later than five years from the date of approval. Purchasers of American National Standards may receive c

11、urrent information on all standards by calling or writing the American National Standards Institute. LIBRARY OF CONGRESS CATALOGING DATA WILL BE ADDED HERE BY AIAA STAFF Published by American Institute of Aeronautics and Astronautics 1801 Alexander Bell Drive, Reston, VA 20191 Copyright 2011 America

12、n Institute of Aeronautics and Astronautics All rights reserved No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without prior written permission of the publisher. Printed in the United States of America American National Standard ANSI/AIAA S

13、-119-201X iii Contents Foreword v Introduction . vi Trademarks vii 1 Scope. 1 2 Tailoring . 2 2.1 Partial Use of the Standard 2 2.2 Implementing the Standard in a Nonflat or Nonscalar Namespace . 3 2.3 New and Reused Software Tailoring Guidance . 3 2.4 Creating New Variable Names and Coordinate Syst

14、ems. 3 3 Applicable Documents . 4 4 Vocabulary . 5 4.1 Acronyms and Abbreviated Terms . 5 4.2 Terms and Definitions 5 5 Standard Simulation Coordinate Systems . 10 5.1 Background / Philosophy . 10 5.2 Complete List of Coordinate Systems 11 5.3 Summary . 15 5.4 References 15 6 Standard Simulation Var

15、iables . 16 6.1 Background / Philosophy . 16 6.2 Variable Naming Convention . 16 6.3 Variable Name Methodologies . 16 6.4 Components Used to Create Variable Names . 24 6.5 Additional Discussion . 40 6.6 Standard Variable Name Table Example . 42 6.7 Summary . 43 6.8 References 43 7 Standard Simulatio

16、n Data Format and XML Implementation of the Standard: DAVE-ML 44 7.1 Purpose . 44 7.2 Philosophy . 44 7.3 Design Objective 44 7.4 Standard Function Table Data An Illustrative Example . 44 7.5 DAVE-ML Major Elements (Annex B) 46 7.6 Simple DAVE-ML Examples 47 7.7 Summary . 53 ANSI/AIAA S-119-2011 iv

17、8 Future Work . 55 8.1 Time History Information 55 8.2 Dynamic Element Specification . 55 9 Conclusion . 56 Annex A Standard Variable Names (Normative) 57 Annex B DAVE-ML Website (Informative) . 117 ANSI/AIAA S-119-201X v Foreword This standard was sponsored and developed by the AIAA Modeling and Si

18、mulation Committee on Standards. Mr. Bruce Jackson of NASA Langley conceived Dynamic Aerospace Vehicle Exchange Markup Language (DAVE-ML). DAVE-ML is the embodiment of the standard in XML. The DAVE-ML reference document, including examples of its use, and the document type definition for the XML imp

19、lementation are included in this standard (Annex B). This implementation was then tested by trial exchange of simulation models between NASA Langley Research Center (Mr. Bruce Jackson), NASA Ames Research Center (Mr. Thomas Alderete and Mr. Bill Cleveland), and the Naval Air Systems Command (Mr. Wil

20、liam McNamara and Mr. Brent York). Numerous improvements to the standard resulted from this testing. At the time of approval, the members of the AIAA Modeling and Simulation CoS were: Bruce Hildreth, Chair J. F. Taylor, Inc. Bruce Jackson, DAVE-ML Chair NASA Langley Research Center Bimal Aponso NASA

21、 Ames Research Center Jon Berndt Jacobs William Bezdek Boeing Phantom Works Geoff Brian Defence Science and Technology Organisation (DSTO) Victoria Chung NASA Langley Research Center R. Thomas Galloway University of Central Florida Peter Grant University of Toronto Michael Madden NASA Langley Resear

22、ch Center Michael Silvestro Charles Stark Draper Laboratory, Inc. Jean Slane Engineering Systems Inc. Brent York Indra Systems, Inc. The above consensus body approved this document in December 2011. The AIAA Standards Executive Council (VP-Standards Wilson Felder, Chairman) accepted the document for

23、 publication in February 2011. The AIAA Standards Procedures dictates that all approved Standards, Recommended Practices, and Guides are advisory only. Their use by anyone engaged in industry or trade is entirely voluntary. There is no agreement to adhere to any AIAA standards publication and no com

24、mitment to conform to or be guided by standards reports. In formulating, revising, and approving standards publications, the committees on standards will not consider patents that may apply to the subject matter. Prospective users of the publications are responsible for protecting themselves against

25、 liability for infringement of patents or copyright or both. ANSI/AIAA S-119-2011 vi Introduction The purpose of this standard is to clearly define the information and format required to exchange air vehicle simulation models between simulation facilities (see Figure 1). This standard simulation int

26、erchange format is implemented in XML and is described fully in Annex B of this document. Figure 1 Model exchange via a standardized format The standard interchange format includes: a) Standard variable name definitions to facilitate the transfer of information by using these standard variables as a

27、 “common language.” The interchange format can be used without using standard variable names. However, it will be more difficult because the exported model will have to include explicit definitions of all variables instead of just a subset unique to the particular model. b) Standard function table d

28、efinition to allow easy transfer of nonlinear function tables of arbitrary dimension. c) Standard coordinate system and reference frame definitions used by the variable names and function tables to clearly define the information being exchanged. d) Standard static math equation representation for de

29、finition of static equations forming part of aerodynamic, propulsive, or other models. A specialized grammar of XML provides a format for the exchange of this information, therefore each organization is required to design import/export tools that comply with the standard one time only. Use of this s

30、tandard will result in substantially reduced cost and time necessary to exchange aerospace simulations and model information. Test cases have indicated an order of magnitude reduction in an effort to exchange simple models when utilizing this standard. Even greater benefits could be attained for lar

31、ge or complicated models. ANSI/AIAA S-119-201X vii Trademarks The following commercial products that require trademark designation are mentioned in this document. This information is given for the convenience of users of this document and does not constitute an endorsement. Equivalent products may b

32、e used if they can be shown to lead to the same results. Simulink MATLAB ANSI/AIAA S-119-201X 1 1 Scope This standard establishes definitions of the information and format used to exchange air vehicle simulations and validation data between disparate simulation facilities. This standard is not meant

33、 to require facilities to change their internal formats or standards. With the concept of an exchange standard, facilities are free to retain their well-known and trusted simulation hardware and software infrastructures. The model is exchanged through the standard, so each facility only needs to cre

34、ate import/export tools to the standard once. These tools can then be used to exchange models with any facility at minimal effort, rather than creating unique import/export tools for every exchange. The standard includes a detailed convention for representing simulation variables. The purpose of thi

35、s is to unambiguously describe all variables within the model when it is exchanged between two simulation customers or facilities. The variable representation includes explicit specification of all coordinate systems, units, and sign conventions used. XML is used as the mechanism to facilitate autom

36、ation of the exchange of the information. Based on the definitions in the standard, a list of recommended but nonobligatory simulation variable names is included in Annex A. This list of standard variable names should further simplify the exchange of information, but is not required for use of the s

37、tandard. The standard includes capabilities for a model to be self-validating and self-documenting, with the provenance of a models components included within the model and transferred with it. Statistical descriptions of the quality of a model may also be included. ANSI/AIAA S-119-2011 2 2 Tailorin

38、g The requirements defined in this standard may be tailored to match the actual requirements of any particular program or project. Tailoring of requirements should be undertaken in consultation with the procuring authority where applicable. NOTE Tailoring is a process by which individual requirement

39、s or specifications, standards, and related documents are evaluated and made applicable to a specific program or project by selection, and in some exceptional cases, modification and addition of requirements in the standards. The following sections provide further guidance on specific tailoring situ

40、ations. 2.1 Partial Use of the Standard 2.1.1 General Not all aspects of this standard may be applicable to all models or simulation applications. The following guidelines are provided to encourage appropriate use of the standard in a number of example situations. 2.1.2 Creating a New Simulation Env

41、ironment This situation calls for use of the complete standard. It is hoped that the team developing the new simulation environment would, if necessary, add to the list of standard variables and coordinate systems. 2.1.3 Creating a New Simulation Model in an Existing Simulation Environment This situ

42、ation is defined as creating a new system model (aircraft dynamic model for example) that will run in an existing simulation environment. It is expected that this is the most commonly performed work that will see benefit by application of this standard. In this case the following tailoring guideline

43、s are applicable. a) Apply the standard to the new development aspects of the project and all the function tables. b) Assuming that most or all of the standard variable names and coordinate systems are applicable to the simulation, use them for the new code developed for the simulation. c) In the ex

44、isting simulation environment that is being reused, for example the equations of motion, there is no need to rewrite the code to use the standard variable names or coordinate systems. However, in most cases the coordinate systems used in existing simulation environments will be covered in the standa

45、rd coordinate system definitions herein (Section 5). Therefore the standard coordinate systems can easily be referenced when documenting the simulation and interfaces between the new simulation components and those reused. 2.1.4 Creating or Updating a Simulation with a Long Life Expectancy A pilot t

46、raining simulator is an excellent example of this type of simulation. This simulation may only be updated every 310 years, so at first glance the standard may seem to be less applicable. In fact the opposite is true. It is because of the infrequent maintenance that application of the standard is cri

47、tical. In this case, in each new software update, the original developers (or previous updaters) are probably no longer available, and the update is being performed by different personnel. Software developed using the standard should be easier for the new software team to understand. They are workin

48、g with clear variable definitions with which they are familiar. The function table format is understood and the functions themselves are better documented. The coordinate system definitions are clear. Changes are recorded for the benefit of any future software update. In simulations with a long expe

49、cted life, use of the state, state derivative control, and output conventions as part of the variable naming convention becomes critical as these variables form the core of the model ANSI/AIAA S-119-201X 3 and the significant inputs. It is important that the personnel modifying the simulation are able to easily identify the states, state derivatives, and controls. 2.2 Implementing the Standard in a Nonflat or Nonscalar Namespace The variable naming convention defined within the standard makes no assumption as to the hierarchy of data components, such as object-oriented model