2025 R1 01/14/2025
Features Updated
- PACZ extraction directory for the MCRE remote "Run On" feature for Linux is now configurable.
- Added support for MATLAB versions 2024a and 2024b.
- Added support for SolidWorks 2024.
- Added support for CATIA V5 2024.
- ModelCenter Help is now available as part of the online Ansys Help system.
- Support for Java 8 in ModelCenter products is now deprecated. Support for Java 8 will be removed in the 2025 R2 release.
Issues Addressed
- Resolved an issue where a published, expanded PACZ could not be inserted into a ModelCenter workflow.
- Resolved an issue where ModelCenter would not share licenses when starting MCRE instances via an SSH connection.
- Resolved an issue relating to the Java Selection Tool where a user could not correctly set the required Java related environment variables.
- Clarified error messaging when attempting to connect to MCRE on Linux over SSH.
- Resolved various issues with the PACZ Publisher and long variable names and aliases.
- Resolved an issue where assemblies could not be deleted from workflows.
- Resolved an issue where attempting to run an embedded optimization that used the Darwin algorithm would fail.
- Resolved an issue where component Plug-Ins could leak processes or files.
- Resolved an issue where attempting to use the optiSLang OCO algorithm with discrete design variables could cause an error stating "Specified cast is not valid."
- Resolved an issue where the optiSLang Adaptive DOE could run with design points that did not include the desired range.
- Resolved an issue where the optiSLang Adaptive DOE could not run design variables with enumerations containing levels.
- Resolved an issue where the optiSLang Adaptive DOE would not work with design variables that included non-double types.
- Resolved an issue where the optiSLang OCO algorithm could perform more than the maximum number of evaluations.
- Resolved an issue where the optiSLang OCO algorithm would attempt to write logs to a hardcoded path at the root of a user's hard drive.
- Resolved an issue where optiSLang optimization algorithms would error when there were failed runs in the Trade Study.
- Resolved an issue with the Excel Plug-In where macros would not execute if the Excel workbook being referenced contained spaces or parentheses in the filename.
Known Issues and Limitations
3D Scatter or Scatter Matrix plots may error and display incorrectly with all data aggregated along a single axis if the mouse pointer is hovered over the graph while it is being generated.
Workaround: Re-load the plot, making sure to not hover the mouse pointer over the plot while it is loading.
When performing a trade study using parallelization, Minerva-based components can fail and/or error.
Workaround: Disable trade study parallelization.
Attempting to load a file that was found via the search functionality in the Minerva Import Plug-In will cause an error.
Workaround: Browse to the file and select it without using the search.
- ModelCenter may attempt to check out too many
SimultaneousWorkflowExecutionlicenses when:- Using parallelization to perform a trade study on a workflow that contains a component that also has parallelization enabled
- Running an Execution Plan multiple times in parallel.
- When viewing the results of the optiSLang Post Processing Plug-In using the Data Explorer in ModelCenter, the Trade Study name is incorrectly shown as the name of a temporary file instead of the original Trade Study file name.