Input files

The following describes the input files needed for a typical optimization, as well as some common inputs.

Input Files

1. Grid files:

   1. grid.g: This will be referred to as the "fitting grid". This is is the grid that will be fit with B-splines. If you are doing an inviscid optimization, this is the only grid that will be needed and it will have grid spacings that are appropriate for an inviscid solve. As described in Multilevel Grid Approach, if a viscous optimization is being conducted an additional grid is required that contains the spacings appropriate for a viscous solve. The grid name grid.g is the default, another name can be specified in the input file as __________

   2. gridturb.g: This will be referred to as the "flowsolve grid". If a viscous optimization is being done, this file is required and is a grid that has grid spacings that are appropriate for a viscous solve, but would not be fittable via the B-spline fitting process. This grid must have the same number of nodes, blocks, etc. as the grid.g file. It doesn't strictly need to be the same geometry that is represented by grid.g, in which case the geometry in grid.g will be that upon which the optimization is started, but it is usually has the same geometry. The grid name gridturb.g is the default, another name can be specified in the input file as _______.

   3. grid.con: The grid connectivity file must correspond to both the grid.g and gridturb.g files. The grid name grid.g is the default, another name can be specified in the input file as __________

   4. grid.ncpts.g (optional): This is a Plot3D grid file that is used to specify the number of B-spline control points used for fitting each edge of each block. Most simply, the number of control points can be specified by the input GRID%NCPTS = (/N, N, N/), but for complex geometries this may not be sufficient as different blocks and directions may need fewer/more control points in order to get a good fit and robust mesh movement. In that case, this grid is used together with the input parameter GRID%READ_NCPTS = .true.. This grid.ncpts.g file is generated in ICEM the same was as the other grid files, but with the number of "nodes" on each edge being the desired number of control points. Only the number of control points are read from this file, all actual node information is discarded, so the geometry of this file is irrelevant. It just must have the same blocking topology (number of blocks, block numbering, edge directions, etc.) as the other grid files. This file is usually generated by simply taking the ICEM file that was used to generate the grid.g file and changing the number of nodes on each edge and then exporting the resulting grid as the grid.ncpts.g file.

2. Geometry control files:

   1. patch.con: This file tells the code which faces of which blocks will form the "patches", which are the B-spline surfaces on the geometry. This file is generated by the script create_patch, which takes the grid.g and grid.con files and generates this file. If using FFD-based control, no modification of this files is needed.

   2. ffd.b: This is a binary file that defines the FFD volume. It is generated by Genair.

   3. axial.b: This is a binary file that defines the axial curve. It is generated by Genair.

   4. axial.con: This is a text file that defines the geometric freedom of the FFD xsec points and axial control points. 

   5. axial.ctrl (optional): If the Axial Control framework is being used, this file specifies the geometric bounds and constraints. See Axial Control Framework for the description of this file.

3. Input files:

   1. input.param: Like any Jetstream run, this file defines the run behaviour. Below are a few optimization-related parameters

      • opt_method = 'optimize': Control method for doing an optimization

      • asdfasdf

      • asdfasdf

      • asdasdf

   2. runScript.slurm: The SLURM run submission script as usual.

4. Special files. These are optional files for certain constraints, etc.

   1. wbpatches.dat: For wing-body optimizations, this file describes how the geometric changes are propagated to the fuselage. See the description of the method and this file in Wing-Body Geometry Control .

   2. secAreaCon.dat: When sectional area constraints are used, as described in Sectional Area Constraints, this file describes their location and values. Sectional area constraints are used with the input parameter jtstrm% secAreaCon = .true. _____________