导弹DATCOM2011版用户手册：几何参数输入与气动力计算

5星 · 超过95%的资源需积分: 0 158 浏览量更新于2024-06-16 收藏 3.17MB PDF 举报

"MISSILE DATCOM User's Manual-2011 Revision" 是一份由美国陆军航空与导弹研究、发展和工程中心（U.S. Army Aviation & Missile Research, Development and Engineering Center）出版的用户手册，主要介绍了如何使用MISSILE DATCOM软件进行导弹设计中的气动分析。这份2011年的修订版取代了2008年的版本，由Christopher Rosema, Joshua Doyle, Lamar Auman, 和 Mark Underwood等人编写。 MISSILE DATCOM 是一个专门用于导弹气动特性计算的工具，它允许工程师输入导弹的各种几何参数，包括头部、弹身、翼面和舵面的尺寸和形状，然后根据这些输入数据计算出相应的气动力参数。在导弹设计中，这些参数至关重要，因为它们直接影响到导弹的飞行性能，如稳定性、操控性和飞行轨迹。用户手册详细阐述了以下几个关键知识点： 1. **几何参数输入**：用户需要准确提供导弹各部分的几何尺寸，如长度、直径、翼展、翼型、舵面尺寸等。这一步是气动分析的基础，不同的几何设计将导致不同的气动响应。 2. **气动力计算**：MISSILE DATCOM利用输入的几何参数，结合流体力学原理，计算出升力、阻力、侧向力和力矩等关键气动力系数。这些数据对理解导弹在不同飞行条件下的行为至关重要。 3. **飞行环境考虑**：手册可能包含如何考虑飞行速度、高度、攻角和马赫数等因素的指导，这些都会影响计算结果。 4. **输出报告**：用户可以导出详细的气动特性报告，包括图表和数值，帮助分析和优化设计。 5. **专利和使用权**：尽管政府提供了这些数据，但手册提醒用户，使用这些资料并不自动授予制造、使用或销售任何专利发明的权利，除非获得了相应授权。 "MISSILE DATCOM User's Manual-2011 Revision" 是导弹设计者和研究人员的重要参考资料，它提供了详细的步骤和指导，帮助他们进行精确的气动特性评估，从而优化导弹的设计性能。这份文档对于理解和使用MISSILE DATCOM软件进行导弹设计工作具有极高的实用价值。

Approved for public release; distribution unlimited.

3.1 NAMELIST INPUTS

The required program inputs use FORTRAN namelists. Missile Datcom is similar to

other codes which use the namelist input technique, but differs as follows:

• Namelist inputs are column independent, and can begin in any column

including the first. If a namelist is continued to a second card, the continued

card must leave column 1 blank. Also, the card before the continued card

must end with a comma. The last usable column is number 79 if column 1 is

used, and column 80 if column 1 is blank.

• The same namelist can be input multiple times for the same input case,

however this is NOT a recommended practice and should be avoided.

The three namelist inputs

$REFQ SREF=1.,$

$REFQ LREF=2.,$

$REFQ ROUGH=0.001,$

are equivalent to

$REFQ SREF=1.,LREF=2.,ROUGH=0.001,$

• If the SAVE card is used, the total number of namelists read, including repeat

occurrences of the same namelist name from all previous SAVEs, must not

exceed 300.

• The last occurrence of a namelist variable in a case is the value used for the

calculations.

The three namelist inputs

$REFQ SREF=1.,$

$FLTCON NMACH=2.,MACH=1.0,2.0,$

$REFQ SREF=2.,$

are equivalent to

$REFQ SREF=2.,$

$FLTCON NMACH=2., MACH=1.0, 2.0,$

• Certain variables may be input as arrays instead of single values, such as

ALPHA. If the array list is too long (80 columns) to fit on one line, it must be

continued on the following line. This can be done by repeating the variable

name with the array index of the first continued value, or continuing to the

next line with the next value. For example:

Approved for public release; distribution unlimited.

$FLTCON

NALPHA=20., ALPHA=0.,2.,4.,6.,8.,10.,12.,14.,16.,18.,20.,

ALPHA(12)=22.,24.,28.,32.,36.,40.,44.,48.,52.,

NMACH=5., MACH=0.2,0.8,1.5,2.0,3.0, ALT=0.,10000.,

ALT(3)=20000.,30000.,40000.,$

$FLTCON

NALPHA=20., ALPHA=0.,2.,4.,6.,8.,10.,12.,14.,16.,18.,20.,

22.,24.,28.,32.,36.,40.,44.,48.,52.,

NMACH=5., MACH=0.2,0.8,1.5,2.0,3.0, ALT=0.,10000.,

20000.,30000.,40000.,$

• The namelists can be input in any order.

• Only those namelists required to execute the case need be entered.

• Certain alphanumeric constants are permitted. They are summarized in

Table 2.

• Note the constant UNUSED can be used in the input deck, but it cannot be

guaranteed to reset the value truly to the value used within the code (i.e., the

read in value may not be truly .EQ. to UNUSED within the code due to round-

off error). It is therefore recommended that UNUSED be avoided. The

recommended way of resetting a variable within a namelist input is to

use the DELETE command on the namelist, then set the values as

desired.

All Missile Datcom namelist inputs are either real numbers or logical constants. Integer

constants will produce a nonfatal error message from the error checking routine and should be

avoided. ALL namelist and variable names must be input in CAPITAL LETTERS. This also

applies to numerical values input in “E” format, i.e. REN=6.0E06 is acceptable, while

REN=6.0e06 is not.

The namelist names have been selected to be mnemonically related to their physical

meaning. Each component of the configuration requires a separate namelist input.

$FLTCON to define the flight conditions

$AXIBOD or $ELLBOD to define the body

$FINSET1 to define the first fin set

$FINSET2 to define the second fin set

$FINSET3 to define the thirdfin set

$FINSET4 to define the fourth fin set

$FINSET5 to define the fifth fin set

$FINSET6 to define the sixth fin set

$FINSET7 to define the seventh fin set

$FINSET8 to define the eigth fin set

$FINSET9 to define the ninth fin set

$PROTUB to define protuberance option inputs

$INLET to define inlet geometry

Approved for public release; distribution unlimited.

The following sections describe each of the namelist inputs. Each section is

accompanied by a figure which summarizes the input variables, their definitions, and units.

Since the system of units can be optionally selected, the column "Units" specifies the generic

system of units as follows:

L Units of length; feet, inches, centimeters or meters

F Units of force; pounds or Newtons

deg Units of degrees; if angular, in angular degrees; if temperature,

either degrees Rankine or Kelvin

sec Units of time in seconds

Exponents are added to modify the above. For example, L

means units of length

squared, or area. Combinations of the above are also used to specify other units. For example,

F/L

means force divided by area, which is a pressure.

Since it is difficult to discern the difference between the number zero "0" and the

alphabetic letter "O", it should be noted that none of the namelist or namelist variable names

contain the number zero in them. In general, the number zero and the letter "O" are not

interchangeable unless so stated.

The program ascertains the configuration being modeled by the presence of each

component namelist, even if no data is entered. The following rules for namelist input apply:

• Do not include a namelist unless it is required. Once read, the presence of a

namelist (and, hence, a configuration component) can only be removed using

the DELETE control card in a subsequent case. Simply setting all variables

to their initialized values will not remove the configuration component.

• Do not include a variable within a namelist unless it is required. Program

actions are often determined from the number and types of input provided.

• Do not over-specify the geometry. In the 7/07 and subsequent releases,

over-specified geometry should always cause an error and STOP the code.

3.1.1 Namelist FLTCON - Flight Conditions

This namelist defines the flight conditions to be run for the case. The program is limited

to no more than 100 angles of attack and 20 Mach number/Altitude combinations per case at a

fixed sideslip angle, aerodynamic roll angle, and panel deflection angle. (Releases prior to 7/07

limit the angles of attack to 20.) Therefore, a "case" is defined as a fixed geometry with variable

Mach number/Altitude and angles of attack.

The inputs are given in Table 3. There are two ways in which the aerodynamic pitch

and yaw angles can be defined:

• Input ALPHA and BETA. If BETA is input and PHI is not, it is assumed that

the body axis angles of attack () and sideslip angles () are defined.

NOTE: The 7/07 and all prior releases defined BETA as

)u/v(tan

1



, which is

shown as





in Figure 1. The 8/08 and subsequent releases define BETA as

剩余114页未读，继续阅读

AImeha

粉丝: 0
资源: 1

导弹DATCOM2011版用户手册：几何参数输入与气动力计算

Missile DATCOM使用说明书

MissIe datcom用户使用说明中文版

USM3D.rar_ USM3D.f_MISSILE DATCOM_fluid fortran_结构力学_非结构

USAF Missile DATCOM.zip_MISSILE-DATCOM_USAF_matlab datcom_missil

MISSILE DATCOM 2011

missile datcom

MISSILE DATCOM 1997

Missile DATCOM Users Guide

MISSILE DATCOM使用教程

Missile-control-with-DQN

最新资源