Completion of the Optimization Process

Within this section completion of the optimization process is described.

After the optimization loop has been completed, the directory jobname is cleaned up. First, all unnecessary files are deleted. The configuration files determine which files and in what scope (NEVER, FIRST_LAST or EVER) files are saved or deleted. Different decisions for “wildcards” can be made in the configuration files (copy, delete etc.). Further details can be found in the specification of the CONFIG command.

Directories and Files after the Completion of Optimization

The user has a wide range of files for evaluation after optimization has been completed, including the complete model of the initial design and a complete model of the optimized design. Files with additional information are created that serve for the quick evaluation of the optimization. Following subdirectories of jobname directory are created:

  • TOSCA_DB: contains the database of the optimization program. It is only needed if a restart is required in topology optimization.
  • SAVE.ext: contains the database of the optimization program. It is only needed if a restart is required in topology optimization.
  • TOSCA_POST: Contains the files for postprocessing the optimization results. In addition, the protocol file TOSCA.OUT can be found in this directory. The results of Tosca Structure.smooth are normally saved in this directory as well.
The protocol file TOSCA.OUT is copied to the directory TOSCA_POST after the optimization has been successfully completed. If the optimization stopped due to an error, the logfile is copied into the directory DB_ERROR.