- Detached instances of System Coupling
A System Coupling session that was started in GUI Server mode, as described in Reconnecting the GUI to a Running Coupled Solution, can be ended cleanly only from a connected instance of the System Coupling GUI. If this is not possible, you must end it manually by issuing an OS-specific kill request.
To do this, you will need the process ID for the job to be killed. This information is available in Transcript/Log for the coupled analysis.
- Orphaned GUI Server files
In most cases, the GUI Server (sycGui.srv) file should not be removed manually. This file is automatically removed from the coupling working directory the instance of System Coupling running in GUI Server mode exits. However, unexpected termination of a coupling run may leave orphaned (that is, not connected to any active session) GUI Server files, which prevents subsequent instances of System Coupling from starting in GUI Server mode in that directory.
If a previous run terminated unexpectedly or was killed manually (or if you are otherwise certain that no System Coupling instance is running in GUI Server mode in that directory), then you can delete the orphaned file and restart System Coupling.
- Orphaned Solution Lock files
In most cases, the Solution Lock (sycSolve.lock) file should not be removed manually. This file is automatically removed from the coupling working directory when the solution stops. However, unexpected termination of a coupling run may leave orphaned (that is, not connected to any active session) Solution Lock files, which blocks any subsequent solves in that directory.
If a previous run terminated unexpectedly or was killed manually (or if you are otherwise certain that no solution is running in that directory), then you can delete the orphaned file and reattempt a solve.
- GUI scaling issues on 4K monitors
Users of the System Coupling GUI with 4K monitors may encounter incorrect scaling of text and other components of the GUI. If this happens, set the following environment variables:
QT_AUTO_SCREEN_SCALE_FACTOR = 0 QT_SCALE_FACTOR = 2 The value of
2for the QT_SCALE_FACTOR variable is suggested, but some experimentation with different values might be required.For details, see Environment Variable Reference in the QT Documentation.
- Non-automatic proxy settings may prevent the GUI from reconnecting
In some cases, non-automatic proxy settings on your computer may prevent the System Coupling GUI from reconnecting to a running coupled solution. When this occurs, you will receive a message indicating the nature of this error.
Note: Currently, this issue has been reported only on Windows systems, but could potentially occur on a Linux system, as well.
You may address the issue using the following workarounds:
Workaround 1: Switch to an automatic proxy setting.
Windows: Go to Settings > Network & Internet > Proxy and ensure that Automatically detect settings is turned to
On.Linux: If the error occurs on a Linux system, contact your IT support team for instructions.
Workaround 2: Use an environment variable to disable proxying.
Use this workaround if the issue was not resolved by using an automatic proxy setting OR when your machine is required to use a non-automatic setting.
Create a new system environment variable called SYC_NO_PROXY. No value is required.
- GUI issues caused by inadequate remote graphics setup
When the System Coupling GUI is run on a remote system without an adequate remote graphics display set up it may crash at start-up. (For details on graphics setup requirements, see the related Ansys installation documentation.)
If issues are encountered, try setting the environment variable QT_QUICK_BACKEND to
softwarebefore starting the GUI.For details, see Switch Between Adaptations in Your Application in the QT Documentation.
- Charting Limitation
If a single iteration is performed per time step, then some or all of the charting data may be plotted on the wrong time step. This is similarly true for the charting data file.