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

An initial Pcomb is run, and the problem optimization is started with the appropriate stop
condition, just as it would be done manually in CONDUIT. At each iteration, the current
status is output to the Run Mode GUI. Additionally, a text file, named “RunStatus” is
created in the Batch Problem directory, which lists the current status of the run.
If an optimization stops due to an error message, Batch Mode will decide whether
or not to run an automated sensitivity analysis. It makes this decision based on the
current phase and the exit message returned from COMATLAB. If a sensitivity analysis
is to be run, Batch Mode will perform the analysis using the specs critical to the current
phase, and the non-frozen design parameters. Based on the analysis, design parameters
would then be frozen, and the optimization would continue. The process then repeats
until any of three conditions occur:
1. It is determined that a sensitivity analysis is not to be run, based on the error message
and current run conditions.
2. All design parameters were frozen as a result of the sensitivity analysis.
3. No design parameters could be frozen based on the sensitivity analysis.
After the case has been run, it is saved in the same exact manner as a regular
CONDUIT problem. The Iteration History is also saved in the standard format. In
addition to these two files, Batch Mode saves other parameters such as the optimization
end message and run order to the “.b” file of the current problem. Thus, this information
will be available to display the next time the Batch Problem is loaded.
49