Projects in optiSLang have a certain directory structure.
*.opf
The optiSLang project file. This contains the workflow, algorithm settings, all in-core data.
*.opr
The optiSLang reference files directory.
*.opd
The project working directory. This may be zipped into the project file. The *.opd contains all optiSLang results and solver outputs.
reffildir
A directory for backup copies. During execution, integrations can create backups and store them here. Currently, this is only done by the Ansys Workbench node. This directory is used as temporary working directory as well.
reffildir is the default name and can be changed for all new projects in the Configuration settings or for the current project in Project settings.
Using this backup directory allows you to encapsulate all relevant data for project transmission and reconstruct the project after a crash.
Systems (Algorithms)
Example: *.opd/AMOP/
The working directory for a specific system. Edit system or use the Other tab for data purging options, naming, etc.
Design directories (Solver in distinct working directory)
Example: *.opd/AMOP/Design001
A working directory for each design evaluated in the related system. All (parameterized and other) solver files are copied here and the solver is executed. Result files are expected here or in a subdirectory.
At runtime, every solver run started by optiSLang creates its own working directory (design directory). The number of directories is equal to the number of designs shown in the history plots. In these directories, the modified input files from the optimization process and the result files from the solver runs are stored and processed. optiSLang automatically redirects the output streams of your solver runs into the solver_output.txt file, in the appropriate design directory. For failed designs, check the contents of this file.
Input File
Output File
Solver Output
Distinct working directory
Working directory for each solver (for example, load case).
optiSLang monitoring database file.
Example: *.opd/AMOP/AMOP.omdb
*.omdb files are Postprocessing files that are automatically generated. They are located in the directory of the corresponding algorithm.
Monitoring database files (*.omdb, *.log)
*.inuse
Contains information on who opened a project. This directory will be removed when you close the project.
In addition, loaded projects have directories used for active project files. These directories are located dependent on the platform in use.
Linux: /tmp
Windows: %APPDATA%\Local\Ansys\optiSLang\Projects\Running
When you close a project, the associated directory is automatically removed.
To change the project settings that define location and contents of working directories, see Project Settings.
Restrictions for Project File Names
Restrictions of project names are the common file name restrictions and depend on the current file system. In general, Unicode character are allowed. Some file system utilities prohibit specific control characters:
Unix
"/"
Windows
"\", "?", "*", ":", "|", "(quote), "<", ">"