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

More documents

Recommendations

Info

the search direction and step size have been determined, the design parameters are changed accordingly and COMATLAB exits. As mentioned earlier, CONDUIT has a priority hierarchy for specs. In order to accommodate for these priorities in the optimization, COMATLAB changes the active constraints of the problem based on the current conditions of the specs. There are three possible conditions, referred to as Phases, that correspond to the three spec constraint types. They are listed below in the order that they would normally be encountered during an optimization. • Phase 1 – Characterized as having one hard constraint not satisfied in Level 1, this phase concentrates only on the hard constraints, attempting to push them into Level 1. In doing so, COMATLAB will sacrifice the ratings of soft and objective specs, if necessary. • Phase 2 – In this phase, all hard constraints have been satisfied in Level 1, however one or more soft constraints have not. Thus, this phase will concentrate on the soft constraints, pushing them into Level 1 at the expense of the objective specs but without violating the Level 1 ratings of the hard constraints. • Phase 3 – The final phase of a successful optimization, the optimization enters this phase when all hard and soft constraints have been moved into Level 1. Objective specs may or may not be Level 1. The optimization continues in this phase, pushing the objective specs as far as possible into Level 1. As with the previous phases, COMATLAB will not allow the hard or soft constraints to be pushed out of Level 1 to improve objective specs. As a result, COMATLAB will degrade the hard and soft constraints right up to the Level 1/2 border, in an 21
attempt to push the objective specs as far into Level 1 as possible. The optimization continues until COMATLAB can no longer move the objective specs. During an optimization, COMATLAB will eventually not be able to determine a search direction and step size that will improve the system. This could occur in any phase, and any iteration number. COMATLAB will then exit, indicating the reason for stopping: • “A proper search direction cannot be found.” - In this case, the optimization routine can’t determine how to modify the design parameters to improve the system. This is usually caused by COMATLAB having too many degrees of freedom in which to move, and thus the problem of finding a search direction becomes indeterminate. By reducing the number of active design parameters, this could be remedied. However, this end message can also be a result of invalid design parameters, those that would result with invalid results from the specs. Thus, to remedy this problem, the initial design parameters should be refined, and a sensitivity analysis should be run to freeze design parameters. • “A local minimum has been obtained.” – This message indicates that the system has been optimized, but that it is not necessarily the best solution. As stated earlier, there may be several local minimums, while there is only one absolute minimum. In the case of this exit message, COMATLAB has determined that the current point is one of several local minimums, and that it could not find an absolute minimum. • “A feasible point is not found to satisfy all hard constraints.” – This indicates that given the initial starting point, the optimization routine could not determine any 22
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: Thus, different step sizes would be
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 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?