#
#  This file contains information about Advanced Acoustical Model (AAM) 
#  aircraft that are available for use in BaseOps.  
#
#  BaseOps fully supports AAM.  You can create BaseOps cases that 
#  include AAM aircraft, then create AAM input files and run AAM 
#  from within BaseOps. 
#
#  In order to support AAM, BaseOps must know which AAM aircraft are
#  available.  When BaseOps first starts up, it searches the 
#  "Noisemap\AAM" directory for files whose names end with the text 
#  "AAM Aircraft.txt".  BaseOps then reads each of these files that it 
#  finds.  These files contain information about the available AAM 
#  aircraft.  
#
#  If you add hemisphere files (*.NC files) for new aircraft to 
#  your AAM installation, you must also add the new aircraft to an 
#  "AAM Aircraft.txt" file.  The easiest way is to make a copy of
#  this file, rename it to something like "My Local AAM Aircraft.txt",
#  then edit it to reflect the new aircraft.
#
#  *** IMPORTANT ***  You should not edit the "Default AAM Aircraft.txt" 
#  file, since it will be overwritten when new versions of BaseOps 
#  are installed.
#
#  The "AAM Aircraft.txt" files provide all of the information BaseOps
#  needs in order to view and edit BaseOps cases and create AAM input 
#  files --- the AAM model and the sphere files do not need to be 
#  installed to view and edit a case.  But obviously, to actually run 
#  such a case, the AAM model and sphere files must be installed.
#
#
#
#  About This File's Format
#
#  This file is a simple text file that can be edited by a text editor.
#  Any blank lines are ignored.  Any text following a pound sign # is 
#  taken as comments and ignored.
#
#  The available AAM aircraft are listed, one aircraft to a line.  
#  The following information must be provided for each aircraft.
#
#    - The aircraft's name, surrounded by double-quotes.  For example, 
#      "F-35A".  This is the aircraft name as displayed by BaseOps and
#      stored in the BaseOps case file.
#
#      Note that each aircraft known to BaseOps must have a unique 
#      name.  A given AAM aircraft can only be defined in one 
#      "AAM Aircraft.txt" file.  In addition, there cannot be an aircraft 
#      with the same name listed in either the NMap NOISEFILE or the 
#      RNM aircraft list.
#
#    - The 5-character sphere id for the aircraft, surrounded by 
#      double-quotes.  The noise data for an AAM aircraft is stored 
#      in a series of sphere files with file names of the form 
#      XXXXX###.NC, where...
#
#        XXXXX is the 5-character sphere id of the aircraft.
#
#        ### is a three-digit sphere number.  There are typically 
#            several sphere files for a given aircraft, each with 
#            a different sphere number.
#
#      BaseOps does not require that the sphere id be unique.  If
#      you define multiple aircraft names with the same sphere id,
#      then the aircraft names will appear as distinct in BaseOps, but
#      will act as synonyms for the same noise data.
#
#    - The category of AAM aircraft.  It must be one of the following 
#      keywords (with no quotes):
#
#        Helicopter
#        TiltRotor
#        FixedWing
#        FixedWingVectoredThrust
#
#      The description of the categories is as follows:
#
#      Helicopter - A rotary-wing aircraft with a fixed nacelle 
#      angle; for example, the CH-53.  When editing a Helicopter 
#      profile, the following aircraft parameters are available: 
#      airspeed, yaw angle, angle of attack, and roll angle.  For 
#      helicopters, the nacelle is assumed to be fixed at 90 degrees.
#
#      TiltRotor -  A rotary-wing aircraft with a variable nacelle 
#      angle; for example, the MV-22B Osprey.  When editing a TiltRotor 
#      profile, the following aircraft parameters are available: 
#      airspeed, yaw angle, angle of attack, roll angle, and nacelle 
#      tilt angle. 
#
#      FixedWing - A fixed-wing aircraft with a fixed thrust vector 
#      angle.  When editing a FixedWing profile, the following aircraft 
#      parameters are available: airspeed, engine power setting, aircraft 
#      configuration (flaps and gear up, flaps down, etc.), yaw angle, 
#      angle of attack, and roll angle.
#
#      FixedWingVectoredThrust - A fixed-wing aircraft with a variable
#      thrust vector angle; for example, the F-35B Joint Strike Fighter.
#      When editing a FixedWingVectoredThrust profile, the following 
#      aircraft parameters are available: airspeed, engine power 
#      setting, aircraft configuration (flaps and gear up, flaps down, 
#      etc.), yaw angle, angle of attack, roll angle, and thrust vector 
#      angle.
#
#    - The engine power setting units that the sphere files use for 
#      this aircraft, surrounded by double-quotes.  For example, "ETR".  
#      The power units are used only for fixed-wing aircraft.  For 
#      rotary-wing aircraft, just list "n/a" for the units.
#
#
#  Below are sample entries, one for each of the four aircraft categories.
#  These entries begin with # characters, so are taken as comments by
#  BaseOps and therefore ignored.  However, if you delete the # characters 
#  at the start of each of these four entries, the entries would be live, 
#  and you would see AAM aircraft named FW1, FWVT1, etc., available 
#  for selection in BaseOps.
#
#                      AAM                               Engine
#    Aircraft         Sphere         Aircraft            Power
#      Name            Id            Category            Units
#---------------------------------------------------------------
#   "FW1"            "FAKEX"   FixedWing                 "EPR"
#   "FWVT1"          "FAKEX"   FixedWingVectoredThrust   "EPR"
#   "TR1"            "ch146"   TiltRotor                 "n/a"
#   "HC1"            "ch146"   Helicopter                "n/a"

