Awave Analysis Interface Module (AIM)
Awave Analysis Interface Module (AIM)
|
This is a walkthrough for using Awave AIM to analyze a wing, tail, fuselage configuration.
It is presumed that ESP and CAPS have been already installed, as well as Awave. Furthermore, a user should have knowledge on the generation of parametric geometry in Engineering Sketch Pad (ESP) before attempting to integrate with any AIM. Specifically this example makes use of Design Parameters, Set Parameters, User Defined Primitive (UDP) and attributes in ESP.
Two scripts are used for this illustration:
First step is to define the analysis intention that the geometry is intended support.
Next we will define the design parameters to define the wing cross section and planform.
The design parameters will then be used to set parameters for use internally to create geometry.
Next the Wing, Vertical and Horizontal tails are created using the naca User Defined Primitive (UDP). The inputs used for this example to the UDP are Thickness and Camber. The naca sections generated are in the X-Y plane and are rotated to the X-Z plane. They are then translated to the appropriate position based on the design and set parameters defined above. Finally reference area can be given to the Awave AIM by using the capsReferenceArea attribute. If this attribute exists on any body that value is used otherwise the default is 1.0.
In addition, each section has a capsType attribute. This is used to define the type of surface being create into a lifting surface or a body. The other attribute found on the first wing section is capsGroup. This is used to logically group cross section of a give capsType type together. More information on this can be found in the AIM Attributes section.
Vertical Tail definition
Horizontal Tail definition
Fuselage definition. Notice the use of the ellipse UDP. In this case, only translation is required to move the cross section into the desired location.
Store definition. This addition is to demonstrate the addition of a wing tip store in the Awave representation.
An example pyCAPS script that uses the above *.csm file to run Awave is as follows.
First the pyCAPS and os module needs to be imported.
Once the modules have been loaded the problem needs to be initiated.
Next local variables used throughout the script are defined.
Next the *.csm file is loaded and design parameter is changed - area in the geometry. Any despmtr from the awaveWingTailFuselage.csm file is available inside the pyCAPS script. They are: thick, camber, area, aspect, taper, sweep, washout, dihedral...
The Awave AIM is then loaded with the capsIntent set to LINEARAERO (this is consistent with the intention specified above in the *.csm file.
After the AIM is loaded the Mach number and angle of attack (Alpha) are set as aimInputsAwave. The Awave AIM supports variable length inputs. For example 1, 10 or more Mach and AoA pairs can be entered. The example below shows two inputs. The length of the Mach and Alpha inputs must be the same.
Once all the inputs have been set, preAnalysis needs to be executed. During this operation, all the necessary files to run Awave are generated and placed in the analysis working directory (analysisDir)
At this point the required files necessary run Awave should have been created and placed in the specified analysis working directory. Next Awave needs to executed such as through an OS system call (see Awave AIM Overview for additional details) like,
A call to postAnalysis is then made to check to see if Awave executed successfully and the expected files were generated.
Similar to the AIM inputs, after the execution of Awave and postAnalysis any of the AIM's output variables (AIM Outputs) are readily available; for example,
Printing the above variable results in,