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

More documents

Recommendations

Info

the abscissa in the gain schedule plots of Analysis Mode. Thus, gain schedule plots can be made against the case number, velocity, angle of attack, or any other parameter which is defined in this section. In addition to this, these values will eventually be referenced as constants by the User Defined setup window. For example, if a column title from the Parameter window were to be passed to a function declared in the User Defined window, the value of the Parameter for that particular case would be used in place of the column title name. By default, the Parameter window initially has only the case number listed. This value can not be removed or edited. To add parameters, the user would press the Add/Remove Parameter button on the Button Toolbar. A small window will appear, as shown in Figure 26. Figure 26 - Add/Edit/Remove/ Parameter GUI Using this GUI, the user can create a new column, remove an existing column, or edit the name of an existing column. The action to be performed is defined by the top pull-down menu of the window. If a parameter is to be edited or removed, the Field pulldown window would be used to select one of the current parameters. The Name edit box is used to specify the name of a new parameter, or the new name of the edited parameter. 45
Once the new column is added, the user may define values for each case. If a cell is left blank or with the default value of “-“, that particular case will be excluded from the cases used in a gain schedule plot. 2.2.6 Constructing A Batch Problem Thus, to put a perspective on how each component works in the construction of a Batch Problem, a typical problem would be created as such: The user would first create and optimize a CONDUIT problem to serve as the template of the Batch Problem. Typically, this template problem would be created so that it is the best match of all of the cases. A new directory would be created and the template problem would be copied there. Batch Mode would be started, and the template case in the newly created directory would be selected. Upon starting Batch Mode, the GUI would contain one case, the template. The user would then create however many families deemed necessary, and create any number of cases in each family. The settings for the cases would then be edited using the Batch Mode GUI. Once all cases were configured, the Create Batch Problem command would be selected under the File Menu. Batch Mode would then create subdirectories for each case, modify the files that make up the individual problems, and copy these files to the individual subdirectories. Thus, the Batch Problem will have been created, the subdirectories each containing individual CONDUIT problems. The next step is to switch to Run Mode to optimize or evaluate the Batch Problem. 46
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 and 40: to have very high Cramer Rao percen
Page 41 and 42: means to create, modify, and save t
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: the casual observer is that since t
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?