;-*- ahsdb -*-
# Leave that first line alone.
#
# This is AHSDB Template v. 1.00
# Questions? email docs@vtol.org
#
# This is a template for submitting a single AHS document database entry.
# Copy it into a working file, then edit it using your favorite text editor.
# If you use emacs, see below.
#
# When you're done preparing your entry, email it to:
#
#        docs@vtol.org
#
# Give us a week or two to process your information, then verify
# by searching on the AHS document search page,
#
#        http://www.vtol.org/dbsearch
#
# An easy search query is just    author:yourname
#
# IF YOU USE EMACS:
#
# ahsdb-mode provides syntax-colorization.
# 1) put ahsdb.el in your load path
# 2) put this in your ~/.emacs:
#
#  (autoload 'ahsdb-mode "ahsdb" "Mode for editing AHS bibliographic data files" )
#
# HOW TO FILL OUT FORM:
#
# In this file, any text starting with "#" through to the end of the
# line is assumed to be a comment and is ignored during processing.
# Feel free to include explanatory comments as you see fit.
#
# Blank lines are ignored.
#
#
# Each section begins with a line containing  only a keyword beginning
# with a "@". The sections can appear in any order.
#
#
# =============== Form Begins Here =======================================

# SUBMITTED: Your contact info. This information will NOT be placed
# in the public database.

@SUBMITTED
AHS Docs Manager <docs@vtol.org> (703) 684-6777

#  Full title of document

@TITLE
Dynamics Workshop On Rotor Vibratory Loads

# Abstract: the entire abstract. For mathematical symbols, you'll have
# to wing it. One possibility would be to use LaTeX representations.
# Don't worry about formatting paragraphs - this is taken care of automatically
# by AHS when your entry is processed.

@ABSTRACT
This paper reviews the results of a Dynamics Workshop focusing on the
correlation of vibratory hub load predictions from 8 advanced
aeroelastic codes, in comparison with Lynx flight test
measurements. Simple `Baseline Models' are first established with near
uniform characteristics for all codes, to enable vibration prediction
improvements to be illustrated for various changes in analytical
models including; free wakes, fuselage upwash, unsteady aerodynamics
and finite element vs Modal methods. Incorporating some of these
analytical modelling improvements upgraded the `Current Technology'
codes to `Improved Technology Models' which are subsequently
re-evaluated with flight test loads to identify rotor modelling
deficiencies. On average, codes are not able to predict vibratory loads
to an accuracy any greater than 50% of the Lynx measured loads.

#  DOCKEY is a unique key assigned by AHS. Leave it blank.
#  Eventually this may be used to create a BiBTeX database.

@DOCKEY
(none yet)

#  Enter authors using BiBTeX syntax
#  Example:
#  Lastname, A. B. and Othername, C. D. Jr. and Thirdname Jr., E. F. and others.
#  You can use full given names rather than initials.

@AUTHOR
Hansford, Robert E. and Vorwald, John

#  If you don't submit keywords, AHS will attempt to put some in
#  for you. But it's better if you do it. Use as many as you see fit.
#  Case-insensitive.

@KEYWORDS
dynamics, loads prediction, comprehensive analysis, lynx, aeroelastic
code, 2gchas, flight lab, crfm, umarc, camrad, rdyne, r150

#     DATE, MONTH, YEAR, SOURCE, VOLUME, NUMBER, ADDRESS:
#     For Journal, Vertiflite, and Proceedings, this information
#     is entered by AHS. But you can enter it if you want.

#  DATE is the full date. Better to leave blank and use
#  MONTH and YEAR instead.

@DATE

#  Full name of month:

@MONTH
June

#  Four-digit year:

@YEAR
1996

#  SOURCE is one of: JAHS, Journal, Forum, Vertiflite, or Conference
#  (or leave blank)

@SOURCE
Forum

#  VOLUME - for periodicals. Forum Proceedings  too - sometimes
#  they're split into multiple volumes.

@VOLUME
1
  
#  NUMBER - number within volume. For Forum proceedings, NUMBER is
#  the proceedings number, i.e. 1996 = Forum 52.

@NUMBER
52

#  ADDRESS - where the conference took place, or where item is published
#  (usually: Washington DC).

@ADDRESS
Washington, DC

#  Enter pages in this format:  18--27   i.e. with a double-hyphen.

@PAGES
93--110

#  NOTES is for any additional information you feel is useful.
#  NOTES appears in the database. If you want to add notes for
#  yourself or explanations to any item, use "#" comments instead -
#  these may appear  anywhere in the file.

@NOTES