Annotated Turbine A Input File

Annotated Input File for Turbine A

Comments in the input file

#
!
PAUSE # pause the program Any lines that start with these characters are ignored. Text following these characters is ignored.

Parameters similar to those used in the PROP code

MODE 1.0
Mode of operation of the machine as a wind turbine.

LTIP 1.0
Use the Prandtl tip loss model.

LHUB 1.0
Use the Prandtl hub loss model.

IBR 1.0
Use the advanced brake model.

ISTL 1.0
Use the Viterna stall model in the post stall region.

USEAP 1.0
Include the swirl effects.

WEXP 0.0000
The exponent to be used in the boundary layer profile of the wind.

HH 3.372
Normalized tower height w.r.t. rotor radius

NS_NSEC 10.0 1.0
Number of blade elements/number of sectors

IS1 1.0
First segment used in analysis

IS2 10.0
Last segment used in analysis

BE_DATA 0.0
Do not print out blade element data

INCV 0.0
Use Tip Speed Ratio

SH 0.0
Ignore shaft tilt effects on cross flow

BN 3.0
Number of blades in the rotor

CONE 3.42
Cone angle of rotor

RHO 0.001987
Density(slugs/ft^3)

HUB 0.04
Normalized hub radius (hub radius/rotor radius)

RD 16.50
Rotor radius (ft)

Blade Geometry Specification

CHORD_BASE 0.0909
The blade geometry can be specified using either a relative distribution or the a more conventional (but sometime less useful) approach that follows.
These three lines indicate the method of specifying the relative blade geometry. The CHORD_BASE line indicates a base chord and the CHORD_RELATIVE line indicates the relative chord at a particular radial station w.r.t. the base chord. At least two relative chords are required when using this mode of specification. In this case, the relative chords are 0. Hence, the blade is of constant chord, the offset is 0.0905. Thus, the blade chord is 0 + 0.0905 (normalized based on the radius). This approach is useful when the number of blade segements is changed from, say, 10 to 20. This change only requires changing NSEC and IS2 from 10 to 20.

The TWIST_RELATIVE line describes the twist of the blade. Again, two points or more are required. Unlike this setup, the usually approach is to set the blade twist to 0 deg at the 75% station. Thus, the "offset" (in this case the blade pitch prescribed later) gets added, and the blade pitch is referenced to the 75% station where the twist is zero.

CHORD_RELATIVE 2 .5 .000 1. .000

TWIST_RELATIVE 18 0.14 47.67 0.17 42.39 0.22 35.29 0.27 29.56 0.32 24.95 0.37 21.19 0.42 18.10 0.47 15.52 0.52 13.35 0.57 11.50 0.62 9.91 0.67 8.52 0.72 7.32 0.77 6.25 0.82 5.30 0.87 4.45 0.92 3.69 0.97 3.00

#CH_TW # 0.0625 6.3 # 0.0792 6.3 # 0.0959 6.3 # 0.1064 5.93 # 0.0984 4.45 # 0.0903 2.96 # 0.0823 1.48 # 0.0743 0.00 # 0.0663 -1.48 # 0.0583 -2.96
This line indicates the method of specifying the normalized blade geometry. The normalized chord distribution and twist angle along span are given here. The number of points at which the distributions are given should be equal to the number of segments the blade is divided into in the NS_NSEC line. In this annotated input file, this line is not being used because the blade geometry is specified using the relative description above.

Stall delay models

DU_MODEL 1.0 1.0 1.0 22.5
Stall delay models to be used are indicated by these 2 lines. The UIUC model line, DU_MODEL, is followed by 4 inputs. The first 3 are the empirical constants in the model. Their best value is 1. The last value is the wind speed to be used in generating 3D data when using the model in the fixed-wind mode (described with the AirfoilFileNames line).

The CORRIGAN_EXPN line indicates that the Corrigan model is to be used for stall delay. The value input in the line line is exponent to be used in the expression for the Corrigan model.

Note that the specification of the post stall models has to occur before the airfoil data is read in to the program by the AIRFOIL_MODE line. If neither model is used, then the program uses the stall delay angle specified in the AIRFOIL_MODE line and keeps the C_lmax fixed for this angle range before starting post stall models.

#CORRIGAN_EXPN 1

Lines related to obtaining airfoil data from the code (fixed-wind mode)

OUTPROP turba-prop.in
Files are written out in these three lines that are used as input files to PROP, AERODYN and WTPLOT programs. The lines are followed by the name of the file desired.

The OUTPROP line writes out a file that can be usedas input to the PROP93 program. This option can be used only with the AirfoilFileNames and the StationRe lines.

The OUTAERODYN feature will write out an input file to AeroDyn/Yawdyn for ADAMS. The file is generated based on the input file described in Table 6.1 in the User's Guide for AeroDyn/YawDyn developed by Dr. Craig Hansen at the University of Utah for NREL. It should be noted that the user should provide a lot of information for use in YawDyn after the ADAMS input ends in the file. This line in the WTPREP input file just generates the file format. A lot of information like the rotor moment of inertia is not availble to WTPREP and hence is to be entered by the user once the input file is generated.

The OUTGRAPH feature writes out data to a file that can be used for plotting with the WTPLOT software.
These input files are generated in the fixed-wind mode only. Fixed-wind mode means that the airfoil data is generated at one wind speed, and there is an angle of attack sweep, similar to the wind tunnel situation.
Variable-wind mode (next section) is similar to what happens in an experiment on a wind turbine. The airfoil data output from the code is generated "on the fly" during the PROP subroutine analysis. For instance, to compare the UIUC-stall-delay-model predictions with the CER experiment, it is necessary to compare the data for the variable-wind mode because the lift and drag increments predicted by the model depend on the wind speed and tip speed ratio. For each angle of attack at each station on the blade, there is a certian corresponding wind speed and tip speed ratio, which are most easily obtained during a PROP analysis.

OUTAERODYN turba-aerodyn.in

OUTGRAPH turba-wtplot.in

Lines related to obtaining airfoil data from the code (variable-wind mode)

PROPFileNames 10 uiucseg1.dat turbine A at station 1 uiucseg2.dat turbine A at station 2 uiucseg3.dat turbine A at station 3 uiucseg4.dat turbine A at station 4 uiucseg5.dat turbine A at station 5 uiucseg6.dat turbine A at station 6 uiucseg7.dat turbine A at station 7 uiucseg8.dat turbine A at station 8 uiucseg9.dat turbine A at station 9 uiucseg10.dat turbine A at station 10
This line is used to read in the filenames and titles (first line of data files) which are used when writing out the airfoil data "on the fly" during the analysis. This approach is refered to as the "variable-wind mode." More specifically, variable-wind mode means that the angles of attack are generated by using a wind sweep specified by the user in the analysis mode.
As opposed to the variable-wind mode, data can also be obtained from the code in a fixed-wind mode, which is described with the AirfoilFileNames-line.
For this input file, the UIUC model is on. The names of the data files are indicative of this. Note that when this line is used, the user must specify a file name and a title for each of the segments. In this input file, the blade is divided into 10 segments. Hence, 10 file names and titles are input. Since the data written to these files comes out of the analysis, this line must appear before the analysis lines in the input file.
Data written to this file is wind speed, angle of attack, lift coefficient, drag coefficient and lift increment due to the UIUC model if it is on together with the "potential lift coefficient" (2 × pi × angle of attack which is used in the UIUC model).
The files generated by the PROPFileNames line can be downloaded here.

Airfoil specifications

AIRFOIL_MODE 3 5 ../polardata/airfoil1ext 0.21 10 0 1.1 4 00 27 ../polardata/airfoil1ext 0.21 15 0 1.1 4 00 18 ../polardata/airfoil1ext 0.21 10 0 1.1 4 00 15 ../polardata/CYLINDER.TXT 0.24 0.10 3 0.1 4 00 30 ../polardata/CYLINDER.TXT 0.24 0.10 3 0.1 4 00 30
The mode 3 indicates that the airfoil data that follows is in the format of C_l, C_d and angle of attack. Mode 4 would indicate angle of attack, C_l and C_d. The number of airfoils which follow is being read in is indicated in the next line. The location of the airfoil is input in the next line. The airfoil parameters, viz, t/c ratio, stall angle, stall delay angle, C_lmax, insert angle for the Corrigan model, the start and end angles for the UIUC model are input for each airfoil. The line must occur after the stall delay models are specified.

AIRFOIL_FAMILY 5 0.00 4 1.0 0.02 5 0.955 0.26 1 0.40 0.60 2 0.80 0.95 3 0.20
This line indicates the distribution of airfoils along the blade span. The first column is the span wise location and the second column is the airfoil to be used from the AIRFOIL_MODE line. The airfoil properties at each segment along the blade are interpolated by using these airfoil distributions and the blending functions in the third column.

USE_AIRFOIL_FAMILY 1
The USE_AIRFOIL_FAMILY-line indicates which set of airfoils are used in the analysis. In this case, only one set of airfoils is used in the design file and the index is therefore "1". In general many AIRFOIL_FAMILY-lines can be used to prescribe many airfoil families.

Analysis lines

TIPON
Force the tip loss model to always on, even into the post-stall model region (Viterna region).

DP 1 72 0 999 2 Specifies a design point. The parameters input are the design point number, the rpm, pitch, wind speed and the units for the wind speed. In this case, the wind speed is not used in any of the lines to follow. To make this clear, "999" is used to indicate to the user that the wind speed in this design point line is just a place holder. The number "999" is not used in any special way in the code.

IDES Starts the design process. But for this file, there are no "design" steps. Still this line is needed to indicate the end of the rotor input parameters, and the start of the analysis. IDES stands for "initiate design".

RPM_DP 1 PITCH_DP 1 WIND_SWEEP 7 50.0 1 2.0 2D_SWEEP WRITE_FILES 40 45 55 95 100 50 RPM_DP 1 PITCH_DP 1 WIND_SWEEP 7 15 2 1 1D_SWEEP WRITE_FILES 35 75 85 90 80 95 99 32
This is the analysis mode to determine the rotor performance. Briefly, the rpm is taken from the first design point as is the blade pitch. The wind speed is swept over the range from 7 mph to 50 mph in increments of 1 mph (and the units are mph "2.0"). The 2D_SWEEP-line performs the analysis, and all the data is saved in arrays in the process. The WRITE_FILES line writes out the data.
The files generated by the WRITE_FILES line can be downloaded here.

More lines related to obtaining airfoil data from the code (fixed-wind mode)

StationRe 1 10 1 2 3 4 5 6 7 8 9 10
Airfoil data at particular blade segments with Re taken from the most previous analysis run. The number input after the StationRe line must be the same as that input after the AirfoilFileNames line. This is for data output for the fixed-wind mode. The data can be obtained for any or all of the segments in this case, unlike the PROPFileNames line.

AirfoilFileNames 10 wfix3duiuc1.dat turbine A at station 1 wfix3duiuc2.dat turbine A at station 2 wfix3duiuc3.dat turbine A at station 3 wfix3duiuc4.dat turbine A at station 4 wfix3duiuc5.dat turbine A at station 5 wfix3duiuc6.dat turbine A at station 6 wfix3duiuc7.dat turbine A at station 7 wfix3duiuc8.dat turbine A at station 8 wfix3duiuc9.dat turbine A at station 9 wfix3duiuc10.dat turbine A at station 10
These are the names of the output files and their titles for the fixed-wind mode. These lines must necessarily come before the MakePROPAirfoilData line because that line creates the data files and the file names have to be input before that line occurs in the input file.
The angle of attack and the lift coefficient is written to the file first, followed by the angle of attack and the drag coefficient. The angle of attack values are the sweep described in the AlfaMinMaxInc line.
The files generated by the AirfoilFileNames line can be downloaded here.

AlfaMinMaxInc 1 -10 50 2
This line gives the angle of attack sweep for generating data for the fixed-wind mode. If 1 is used, then the next line contains the minimum, maximum and increment angles for the sweep. If 2 is used, then the actual angles are specified.

PrintHeaders This line causes the code to write to the screen the airfoil data for each station selected.

Itype 3 This line indicates screen output mode for the PrintHeaders line. Mode 3 (this example) indicates that the airfoil data is output in the format: angle of attack, Cl and Cd. Mode 4 outputs data as Cl, Cd and angle of attack.

MakePROPAirfoilData This line generates the output data for the fixed-wind mode

Generate the PROP93 and PROPID output files (features not fully documented)

DUMP_PROP93 1 9
These two lines write out files which can be used for a PROP93 run and a PROPID input file respectively.

DUMP_PROPID 21

Stop reading in input data and stop execution.

* This is the character that indicates the end of file. Everything after this character in the input file will be ignored by the program.

Annotated Input File for Turbine A
Comments in the input file
# ! `PAUSE` # pause the program	Any lines that start with these characters are ignored. Text following these characters is ignored.




Parameters similar to those used in the PROP code
MODE 1.0	Mode of operation of the machine as a wind turbine.
LTIP 1.0	Use the Prandtl tip loss model.
LHUB 1.0	Use the Prandtl hub loss model.
IBR 1.0	Use the advanced brake model.
ISTL 1.0	Use the Viterna stall model in the post stall region.
USEAP 1.0	Include the swirl effects.
WEXP 0.0000	The exponent to be used in the boundary layer profile of the wind.
HH 3.372	Normalized tower height w.r.t. rotor radius
NS_NSEC 10.0 1.0	Number of blade elements/number of sectors
IS1 1.0	First segment used in analysis
IS2 10.0	Last segment used in analysis
BE_DATA 0.0	Do not print out blade element data
INCV 0.0	Use Tip Speed Ratio
SH 0.0	Ignore shaft tilt effects on cross flow
BN 3.0	Number of blades in the rotor
CONE 3.42	Cone angle of rotor
RHO 0.001987	Density(slugs/ft^3)
HUB 0.04	Normalized hub radius (hub radius/rotor radius)
RD 16.50	Rotor radius (ft)




Blade Geometry Specification
CHORD_BASE 0.0909	The blade geometry can be specified using either a relative distribution or the a more conventional (but sometime less useful) approach that follows. These three lines indicate the method of specifying the relative blade geometry. The `CHORD_BASE` line indicates a base chord and the `CHORD_RELATIVE` line indicates the relative chord at a particular radial station w.r.t. the base chord. At least two relative chords are required when using this mode of specification. In this case, the relative chords are 0. Hence, the blade is of constant chord, the offset is 0.0905. Thus, the blade chord is 0 + 0.0905 (normalized based on the radius). This approach is useful when the number of blade segements is changed from, say, 10 to 20. This change only requires changing `NSEC` and `IS2` from 10 to 20. The `TWIST_RELATIVE` line describes the twist of the blade. Again, two points or more are required. Unlike this setup, the usually approach is to set the blade twist to 0 deg at the 75% station. Thus, the "offset" (in this case the blade pitch prescribed later) gets added, and the blade pitch is referenced to the 75% station where the twist is zero.
CHORD_RELATIVE 2 .5 .000 1. .000
TWIST_RELATIVE 18 0.14 47.67 0.17 42.39 0.22 35.29 0.27 29.56 0.32 24.95 0.37 21.19 0.42 18.10 0.47 15.52 0.52 13.35 0.57 11.50 0.62 9.91 0.67 8.52 0.72 7.32 0.77 6.25 0.82 5.30 0.87 4.45 0.92 3.69 0.97 3.00
#CH_TW # 0.0625 6.3 # 0.0792 6.3 # 0.0959 6.3 # 0.1064 5.93 # 0.0984 4.45 # 0.0903 2.96 # 0.0823 1.48 # 0.0743 0.00 # 0.0663 -1.48 # 0.0583 -2.96	This line indicates the method of specifying the normalized blade geometry. The normalized chord distribution and twist angle along span are given here. The number of points at which the distributions are given should be equal to the number of segments the blade is divided into in the `NS_NSEC` line. In this annotated input file, this line is not being used because the blade geometry is specified using the relative description above.




Stall delay models
DU_MODEL 1.0 1.0 1.0 22.5	Stall delay models to be used are indicated by these 2 lines. The UIUC model line, `DU_MODEL`, is followed by 4 inputs. The first 3 are the empirical constants in the model. Their best value is 1. The last value is the wind speed to be used in generating 3D data when using the model in the fixed-wind mode (described with the `AirfoilFileNames` line). The `CORRIGAN_EXPN` line indicates that the Corrigan model is to be used for stall delay. The value input in the line line is exponent to be used in the expression for the Corrigan model. Note that the specification of the post stall models has to occur before the airfoil data is read in to the program by the `AIRFOIL_MODE` line. If neither model is used, then the program uses the stall delay angle specified in the `AIRFOIL_MODE` line and keeps the C_lmax fixed for this angle range before starting post stall models.
#CORRIGAN_EXPN 1




Lines related to obtaining airfoil data from the code (fixed-wind mode)
OUTPROP turba-prop.in	Files are written out in these three lines that are used as input files to PROP, AERODYN and WTPLOT programs. The lines are followed by the name of the file desired. The `OUTPROP` line writes out a file that can be usedas input to the PROP93 program. This option can be used only with the `AirfoilFileNames` and the `StationRe` lines. The `OUTAERODYN` feature will write out an input file to AeroDyn/Yawdyn for ADAMS. The file is generated based on the input file described in Table 6.1 in the User's Guide for AeroDyn/YawDyn developed by Dr. Craig Hansen at the University of Utah for NREL. It should be noted that the user should provide a lot of information for use in YawDyn after the ADAMS input ends in the file. This line in the WTPREP input file just generates the file format. A lot of information like the rotor moment of inertia is not availble to WTPREP and hence is to be entered by the user once the input file is generated. The `OUTGRAPH` feature writes out data to a file that can be used for plotting with the WTPLOT software. These input files are generated in the fixed-wind mode only. Fixed-wind mode means that the airfoil data is generated at one wind speed, and there is an angle of attack sweep, similar to the wind tunnel situation. Variable-wind mode (next section) is similar to what happens in an experiment on a wind turbine. The airfoil data output from the code is generated "on the fly" during the PROP subroutine analysis. For instance, to compare the UIUC-stall-delay-model predictions with the CER experiment, it is necessary to compare the data for the variable-wind mode because the lift and drag increments predicted by the model depend on the wind speed and tip speed ratio. For each angle of attack at each station on the blade, there is a certian corresponding wind speed and tip speed ratio, which are most easily obtained during a PROP analysis.
OUTAERODYN turba-aerodyn.in
OUTGRAPH turba-wtplot.in




Lines related to obtaining airfoil data from the code (variable-wind mode)
PROPFileNames 10 uiucseg1.dat turbine A at station 1 uiucseg2.dat turbine A at station 2 uiucseg3.dat turbine A at station 3 uiucseg4.dat turbine A at station 4 uiucseg5.dat turbine A at station 5 uiucseg6.dat turbine A at station 6 uiucseg7.dat turbine A at station 7 uiucseg8.dat turbine A at station 8 uiucseg9.dat turbine A at station 9 uiucseg10.dat turbine A at station 10	This line is used to read in the filenames and titles (first line of data files) which are used when writing out the airfoil data "on the fly" during the analysis. This approach is refered to as the "variable-wind mode." More specifically, variable-wind mode means that the angles of attack are generated by using a wind sweep specified by the user in the analysis mode. As opposed to the variable-wind mode, data can also be obtained from the code in a fixed-wind mode, which is described with the `AirfoilFileNames`-line. For this input file, the UIUC model is on. The names of the data files are indicative of this. Note that when this line is used, the user must specify a file name and a title for each of the segments. In this input file, the blade is divided into 10 segments. Hence, 10 file names and titles are input. Since the data written to these files comes out of the analysis, this line must appear before the analysis lines in the input file. Data written to this file is wind speed, angle of attack, lift coefficient, drag coefficient and lift increment due to the UIUC model if it is on together with the "potential lift coefficient" (2 × pi × angle of attack which is used in the UIUC model). The files generated by the `PROPFileNames` line can be downloaded here.




Airfoil specifications
AIRFOIL_MODE 3 5 ../polardata/airfoil1ext 0.21 10 0 1.1 4 00 27 ../polardata/airfoil1ext 0.21 15 0 1.1 4 00 18 ../polardata/airfoil1ext 0.21 10 0 1.1 4 00 15 ../polardata/CYLINDER.TXT 0.24 0.10 3 0.1 4 00 30 ../polardata/CYLINDER.TXT 0.24 0.10 3 0.1 4 00 30	The mode 3 indicates that the airfoil data that follows is in the format of C_l, C_d and angle of attack. Mode 4 would indicate angle of attack, C_l and C_d. The number of airfoils which follow is being read in is indicated in the next line. The location of the airfoil is input in the next line. The airfoil parameters, viz, t/c ratio, stall angle, stall delay angle, C_lmax, insert angle for the Corrigan model, the start and end angles for the UIUC model are input for each airfoil. The line must occur after the stall delay models are specified.
AIRFOIL_FAMILY 5 0.00 4 1.0 0.02 5 0.955 0.26 1 0.40 0.60 2 0.80 0.95 3 0.20	This line indicates the distribution of airfoils along the blade span. The first column is the span wise location and the second column is the airfoil to be used from the `AIRFOIL_MODE` line. The airfoil properties at each segment along the blade are interpolated by using these airfoil distributions and the blending functions in the third column.
USE_AIRFOIL_FAMILY 1	The `USE_AIRFOIL_FAMILY`-line indicates which set of airfoils are used in the analysis. In this case, only one set of airfoils is used in the design file and the index is therefore "1". In general many `AIRFOIL_FAMILY`-lines can be used to prescribe many airfoil families.




Analysis lines
TIPON	Force the tip loss model to always on, even into the post-stall model region (Viterna region).
`DP` `1 72 0 999 2`	Specifies a design point. The parameters input are the design point number, the rpm, pitch, wind speed and the units for the wind speed. In this case, the wind speed is not used in any of the lines to follow. To make this clear, "999" is used to indicate to the user that the wind speed in this design point line is just a place holder. The number "999" is not used in any special way in the code.
`IDES`	Starts the design process. But for this file, there are no "design" steps. Still this line is needed to indicate the end of the rotor input parameters, and the start of the analysis. `IDES` stands for "initiate design".
RPM_DP 1 PITCH_DP 1 WIND_SWEEP 7 50.0 1 2.0 2D_SWEEP WRITE_FILES 40 45 55 95 100 50 RPM_DP 1 PITCH_DP 1 WIND_SWEEP 7 15 2 1 1D_SWEEP WRITE_FILES 35 75 85 90 80 95 99 32	This is the analysis mode to determine the rotor performance. Briefly, the rpm is taken from the first design point as is the blade pitch. The wind speed is swept over the range from 7 mph to 50 mph in increments of 1 mph (and the units are mph "2.0"). The `2D_SWEEP`-line performs the analysis, and all the data is saved in arrays in the process. The `WRITE_FILES` line writes out the data. The files generated by the `WRITE_FILES` line can be downloaded here.




More lines related to obtaining airfoil data from the code (fixed-wind mode)
StationRe 1 10 1 2 3 4 5 6 7 8 9 10	Airfoil data at particular blade segments with Re taken from the most previous analysis run. The number input after the `StationRe` line must be the same as that input after the `AirfoilFileNames` line. This is for data output for the fixed-wind mode. The data can be obtained for any or all of the segments in this case, unlike the `PROPFileNames` line.
AirfoilFileNames 10 wfix3duiuc1.dat turbine A at station 1 wfix3duiuc2.dat turbine A at station 2 wfix3duiuc3.dat turbine A at station 3 wfix3duiuc4.dat turbine A at station 4 wfix3duiuc5.dat turbine A at station 5 wfix3duiuc6.dat turbine A at station 6 wfix3duiuc7.dat turbine A at station 7 wfix3duiuc8.dat turbine A at station 8 wfix3duiuc9.dat turbine A at station 9 wfix3duiuc10.dat turbine A at station 10	These are the names of the output files and their titles for the fixed-wind mode. These lines must necessarily come before the `MakePROPAirfoilData` line because that line creates the data files and the file names have to be input before that line occurs in the input file. The angle of attack and the lift coefficient is written to the file first, followed by the angle of attack and the drag coefficient. The angle of attack values are the sweep described in the `AlfaMinMaxInc` line. The files generated by the `AirfoilFileNames` line can be downloaded here.
AlfaMinMaxInc 1 -10 50 2	This line gives the angle of attack sweep for generating data for the fixed-wind mode. If `1` is used, then the next line contains the minimum, maximum and increment angles for the sweep. If `2` is used, then the actual angles are specified.
`PrintHeaders`	This line causes the code to write to the screen the airfoil data for each station selected.
`Itype 3`	This line indicates screen output mode for the `PrintHeaders` line. Mode 3 (this example) indicates that the airfoil data is output in the format: angle of attack, Cl and Cd. Mode 4 outputs data as Cl, Cd and angle of attack.
`MakePROPAirfoilData`	This line generates the output data for the fixed-wind mode




Generate the PROP93 and PROPID output files (features not fully documented)
DUMP_PROP93 1 9	These two lines write out files which can be used for a PROP93 run and a PROPID input file respectively.
DUMP_PROPID 21




Stop reading in input data and stop execution.
*	This is the character that indicates the end of file. Everything after this character in the input file will be ignored by the program.