Developement Of A Batch Mode For Conduit And Its ... - Cal Poly

More documents

Recommendations

Info

2 Development of Batch Mode 2.1 Introduction While CONDUIT is a very powerful design tool, it is limited in that it can only analyze an aircraft at a single design point. Running or analyzing more than one problem requires a significant amount of user intervention. Batch Mode was created with the intent of providing the capability to run multiple CONDUIT problems automatically. In order to accomplish this goal, three requirements had to be addressed. First, Batch Mode had to have the ability to create several CONDUIT problems. In doing so, it also had to have the capability to modify every parameter of a problem which might be varied by a user in CONDUIT, when creating multiple cases to gain schedule, etc…. The second requirement of Batch Mode was that it had to be able to automatically run the multiple cases in such a way as to minimize user intervention. Finally, Batch Mode had to incorporate the means to quickly and effectively view the results of a large number of CONDUIT problems. These three requirements, dealing with the creation, execution, and analysis of multiple CONDUIT problems, were developed into separate modes, henceforth to be referred to as Setup Mode, Run Mode, and Analysis Mode respectively. 2.2 Setup Mode As mentioned in the Batch Mode introduction, the purpose of Setup Mode is to create multiple CONDUIT problems. To do so, it had to be decided how the multiple problems were to be organized, and how they were to be saved on disk. Furthermore, the parameters available to be varied between cases had to also be defined. Finally, the 29
means to create, modify, and save the multiple cases had to be developed based on the criteria above. 2.2.1 Creating the Batch Problem Batch Mode does not replicate all the functionality of the CONDUIT GUI. Doing so would not only be redundant, but unnecessary, since varying certain parameters would cause the cases to become unrelated. Since Batch Mode can not create new CONDUIT cases, it uses a previously created CONDUIT problem which it modifies to create the remainder of the problems. This “template” problem is created by the user prior to entering Batch Mode. Typically, it is set up as one of the cases to be created and run in Batch Mode. The case is then fully optimized in CONDUIT to ensure that the template problem is set up so that it will properly optimize, and to obtain a starting set of design parameters for all other cases. Once the template case has been created and optimized, a new directory is created. The template file is then copied to the new directory. Upon opening Batch Mode, the user picks the name of the template file in the newly created directory. The name of the template file becomes the name of the “Batch Problem”, while the new directory and all files and directories under it, make up the Batch Problem itself. 2.2.2 Modifying the Cases Using the Setup Mode GUI, the user can then modify all parameters useful to a multi-problem analysis. These parameters include the following: 30
Page 1 and 2: THE DEVELOPMENT OF A BATCH MODE FOR
Page 3 and 4: APPROVAL PAGE TITLE: The Developmen
Page 5 and 6: ACKNOWLEDGEMENTS I would like to th
Page 7 and 8: 3.2 BASELINE OPTIMIZATION..........
Page 9 and 10: LIST OF FIGURES FIGURE 1 - COOPER-H
Page 11 and 12: Acronyms NOMENCLATURE ASE - Automat
Page 13 and 14: This rating system was used in conj
Page 15 and 16: Figure 2 - CONDUIT specs As in the
Page 17 and 18: eing ideal for the computations nec
Page 19 and 20: They are typically used as gains, h
Page 21 and 22: stability of the system, checking p
Page 23 and 24: • Time Line - The time response i
Page 25 and 26: 1.1.6 Init File (Setup Mode) One la
Page 27 and 28: 1.1.8 Pcomb (Run Mode) Figure 10 -
Page 29 and 30: 1.2 Method of Optimization A CONDUI
Page 31 and 32: Thus, different step sizes would be
Page 33 and 34: attempt to push the objective specs
Page 35 and 36: the Sensitivity Tools, which are us
Page 37 and 38: The Sensitivity Tools looks at the
Page 39: to have very high Cramer Rao percen
Page 43 and 44: eing opened by a regular session of
Page 45 and 46: in Figure 19. The Batch Mode GUI is
Page 47 and 48: window, within each Mode, the Displ
Page 49 and 50: The File menu contains the commands
Page 51 and 52: Setup, Run, and Analysis, so are th
Page 53 and 54: Figure 24 - General setup window
Page 55 and 56: the casual observer is that since t
Page 57 and 58: Once the new column is added, the u
Page 59 and 60: specific. The method fails when the
Page 61 and 62: 2.3.3 Run Mode GUI Figure 27 - Run
Page 63 and 64: not make any improvements. As with
Page 65 and 66: specific run order is not required,
Page 67 and 68: Order Cases, and Mode buttons all b
Page 69 and 70: uttons, a zoom out feature, and ove
Page 71 and 72: Plot 1 Page 1 Plot 2 Display Area P
Page 73 and 74: same way as in Run Mode. Two window
Page 75 and 76: Figure 35 - Multiple case plot The
Page 77 and 78: Figure 37 - Add/Edit/Remove Plot GU
Page 79 and 80: Figure 38 - New Gain Schedule plot
Page 81 and 82: Figure 39 - Multiple page concept 7
Page 83 and 84: the user may choose to freeze addit
Page 85 and 86: In the case above, if there were an
Page 87 and 88: parameter 8 would not resolve the c
Page 89 and 90: The logic of the table above is sim
Page 91 and 92:
process would repeat until all Cram
Page 93 and 94:
opponent. The computer would then r
Page 95 and 96:
Figure 45 - Example Cramer Rao plot
Page 97 and 98:
method are exceeded, the result wou
Page 99 and 100:
this capability to the automated ru
Page 101 and 102:
not exorbitantly large, and thus th
Page 103 and 104:
connected through mechanical linkag
Page 105 and 106:
Figure 52 - Control System block Th
Page 107 and 108:
Figure 54 - Roll - Attitude Hold bl
Page 109 and 110:
chosen for the template was that of
Page 111 and 112:
Figure 58 - Initial Optimized basel
Page 113 and 114:
integrator in the lateral controlle
Page 115 and 116:
only the four lateral gains were ac
Page 117 and 118:
GUI, ten more cases were added usin
Page 119 and 120:
the Plot Multiple feature of the An
Page 121 and 122:
method was causing problems. Thus t
Page 123 and 124:
Figure 67 - Corrected gain schedule
Page 125 and 126:
constant, and the remaining stabili
Page 127 and 128:
simpler parameters, it provided gre
Page 129 and 130:
was then started by pressing the Ru
Page 131 and 132:
of the critical parameters, however
Page 133 and 134:
simply because the system is not a
Page 135 and 136:
The HQ Window, as developed already
Page 137 and 138:
not, then the specs most critical t
Page 139 and 140:
BIBLIOGRAPHY 1. Frost, Chad R. “D
Page 141:
APPENDIX 130
show all

Developement Of A Batch Mode For Conduit And Its ... - Cal Poly

Create successful ePaper yourself

Delete template?

Save as template?