Fixed Defects
Issues | Short description of the source problem resolved in this version | |
---|---|---|
Documentation | FX-32675 | In the user guide, in the dedicated page about SimLab tutorial (using Flux Solver), some links were wrong.
These link have been updated for the 2024 release of Flux. |
Licensing | FX-33170 | If an Activation Key is set in the Altair License Utility, the License Manager now correctly detects this license and successfully activates it. |
Parallel Computing | FX-30698 | During the resolution of a scenario with parametric distribution in Flux 2D, if the user tried to interrupt the resolution before the solver reached the step “Loop for distributed solving,” secondary instances of Flux invoked by the distribution algorithm could remain active as background processes. Those Flux instances kept using machine resources, and the user was forced to manually kill the processes to release them. This bug has been solved in Flux 2024. |
Physics | FX-32682 | Detailed geometrical description with several strands in parallel for coil conductors region could result in wrongly-computed Joule losses in Flux 2D magnetic projects, because of an issue in the evaluation of the zero-frequency resistance of the involved coil.
The issue is now fixed, for both Transient and Steady State AC applications. |
Postprocessing | FX-32135 | When one exported in OML format the curves representing the double FFT of forces in machine airgap, the data were not written in the file in the right sequence, leading to reversed representations of double FFTs when using these .oml files in other tools, e.g. Compose. The issue has been fixed in Flux 2024 version. |
Solving | FX-32727 | An issue impacting the proper detection of the symmetry of the matrix in the assembled system of equations has been solved. Under certain circumstances, non-symmetric matrices could be wrongly detected as symmetric, leading to non-optimal automatic solver settings and eventually to an inability to solve a scenario. This bug is now corrected in Flux 2024. |
Solving | FX-31907 | The existence of spaces in the directory or path corresponding to the user's home or profile folder could prevent the solution of a scenario with the PETSc solver due to a bug. This issue is now solved in Flux 2024. |
Solving | FX-31619 | The Flux Supervisor parameters allowing users to pre-configure in a new project the default maximum number of iterations and the precision for the Newton-Raphson algorithm was not working as expected after recent improvements in the solver options. This issue has been solved in Flux 2024, and users can now continue to use these features as usual (Flux Supervisor Options→Flux→Solving→Maximum number of iterations for Newton-Raphson/Precision for Newton-Raphson). |
Solving | FX-25028 | The partial storage of scenario results (configurable in the “Results storage” tab, while creating or editing a solving scenario) was found to be incompatible with the initialization of state variables with a predicted solution (Solving options→ Advanced tab→ Initialization of state variables at the beginning of a step → With a predicted solution). Consequently, the solution of a scenario with both options simultaneously enabled has been forbidden in Flux 2024. |