We strongly recommend that you use caution when directly modifying any of the content in any of the ANSYS Workbench project directories or subdirectories other than user_files. You should work through the ANSYS Workbench GUI to manage your project as much as possible. ANSYS Workbench may not recognize or be aware of any changes that you make directly in the file system (such as adding or removing a file).
If you have deleted any project files through the file system and not through the ANSYS Workbench GUI, you may see a warning message when you attempt to open the project. The error message will list the missing file(s). The corrective action depends on the type of files that are missing:
For files that are programmatically integrated with ANSYS Workbench (such as database files, geometry files, engineering data files, application-generated files, and so on), use > to open the Files pane, where you can use the context menu to repair a file or permanently remove it from the project’s file list if it is no longer needed. Repairing these types of files should be done judiciously; it is possible to use files or file types that are not similar to the original. Missing or erroneous files can cause unintended consequences for project stability and usability.
For files that are not programmatically integrated with ANSYS Workbench (such as user-supplied input
files, dpn files, and so on), you can replace them using your
file system and then open the project again. These files may not be necessary for the
project; in this situation, you can safely ignore the warning message.
The project system may delete, back up, or restore files when:
Deleting, duplicating, or replacing systems in the schematic
Opening an application for a cell
Closing a project without saving
Archiving a project
Switching to the next design point during the execution of the Update All Design Points operation
While the project system is performing one of these operations, you cannot have project files open in other applications (such as a text editor) or have the directories open in Windows Explorer. Doing so may cause these file management operations to fail.
You cannot move a project or any of its associated files to another machine while a background run is in progress. File information for the background run is, by necessity, machine-specific. You cannot package or modify the background run while it is in progress.
You will also have errors if you move a project that has references to files outside of the project directory to a different machine or location. By opening the project from a different machine or location, those file references will no longer resolve unless the file is still available under the same absolute path.
Copied images exist in only one location on disk that is referenced and do not exist as physical copies. If you delete an image that has been copied, all pointers to the copies of that image will contain broken links.
If your project name contains characters that are not native to your local operating system the project may fail to save, and if it fails, may corrupt the data.