Fixed Defects
Issues | Short description of the source problem resolved in this version | |
---|---|---|
Data Import/Export context | FX-32622 FX-34116 |
In Flux 2024.1, the orientation of forces computed in IO context has been corrected when applying on a moving mechanical sets. The movement of the mechanical set is now properly taken into account for 2D, 3D and Skewed applications. |
Data Import/Export context | FX-34015 FX-32475 |
In Flux 2024.1, some bugs occurring when using the simplified projective method dedicated to rotating machines for Skewed applications have been fixed. |
Data Import/Export context | FX-33502 | In Flux 2024.1, wrong results when computing Joule or iron losses in elements by using the dedicated thermal DataCollection have been corrected. |
Examples | FX-33590 | In the Help documentation (user guide), the
link for the document "Summary" in French for the application note "Flux-Hst:
Optimisation de la géométrie d'un contacteur" was not the good one. It has been fixed in 2024.1 release. |
Examples | FX-34691 | The test has been updated in Flux 2024 without
corresponding xml for each cases. Without these xml files the cases are not
displayed in the Supervisor of Flux. It has been fixed for Flux 2024.1. |
Mesh | FX-34256 | This 3D defect was linked to incorrect
management of the elements during the mesh import from SimLab to Flux when they
were in second order. This led to the creation of an incorrect topology in Flux
(intersections, superimpositions, overlaps, etc.). Since the Flux/SimLab 2024 versions, a better management of second-order elements has been implemented when processing mesh imports in Flux. |
Parallel Computing | FX-34309 | Occasionally, the parametric distribution
would stop with an error message because the Windows command used to retrieve
the number of running secondary Flux and display it in Flux logs was not
working. This has been fixed in Flux 2024.1: even if the Windows command doesn't work, parametric distribution continues to solve without an error message. |
Physics | FX-33269 | In a Flux 3D Steady-State AC Magnetic project
with two face regions of type "Thin conducting region (hyperbolic current
density through the thickness )", and three "Solid conductor volume regions",
the results were wrong compared to results obtained in 2D. The formulations are
automatically assigned to regions. The issue has been corrected: now, both 3D and 2D projects provide the same good results. |
Postprocessing | FX-34858 | In Flux 2D Transient Magnetic application,
inductance values could not be calculated with the "Computation of inductance
matrix" command if more than two stranded coils were indicated as sources or
targets. This issue is corrected: three or more stranded coils can be selected and the inductance matrices are computed. |
Solving | FX-34352 | In Flux 3D Transient Magnetic application with the option "initialized by static computation" activated, automatic settings for MUMPS solver could lead in some specific situations to an abnormal memory usage, thus preventing the user to solve. A fix has been developed and integrated into Flux 2024.1 version to avoid Flux requires more memory resources than necessary. |
Solving | FX-31962 | In case of hysteretic materials described by Preisach model, the solving process of parametric scenarios failed in Transient Magnetic applications when distributing the computations on several secondary Flux.
The issue has been fixed and the feature works now as expected. |
Solving | FX-31775 | In some circumstances one could have an error when trying to delete all the results of a distributed scenario. This issue has been fixed in this version. |
Solving | FX-33621 | In previous versions, some code optimizations could lead to error prompts when doing two parametric distribution solving in a row without stopping the solving part. The issue has been fixed in the current version. |