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

not make any improvements. As with the Phase column, the cells in this column are also
colored red, yellow, and green to indicate their merit. A message indicating a serious
problem in the particular case, such as “A feasible point is not found to satisfy all hard
constraints”, will result in a red cell. Messages that reflect cases in need of minor
alterations are colored yellow. An example would me the message: “Further decrease of
the most active specifications cannot be achieved.” Lastly, a successful optimization is
colored green. This could be due to a successful COMATLAB exit message, the
optimization reaching a specified number of iterations, or by the optimization reaching a
specified phase. As with the phase column, the coloring of the Optimization Result
Messages allows the user to evaluate the results at a glance.
The Button Toolbar changes completely between Setup and Run Mode. Unlike
the configuration in Setup Mode, Run Mode has only one “window” and thus, all buttons
in the toolbar perform actions. As implied by its name, the Run button starts the Batch
optimization. Just to the right is the Stop button, which is used to stop a currently
running Batch optimization. As in CONDUIT, pressing the stop button will stop the
optimization after the currently running iteration is finished.
The next object on the Button Toolbar is an iteration status message, listing the
current iteration of the case that is running, or the total iterations run of the last completed
case. As with the Iteration column of the Main Window, the total iterations to be run for
the particular case is listed to the right of a “/”. This total works in the same way as the
Iteration Number display of the CONDUIT GUI. If a number of iterations to run was
specified for a case, that number appears on the right of the slash. If a stop condition was
52