Issues Short description of the source problem resolved in this version
Data Import/Export context FX-23269 Bulk data files (.FEM) generated by the Import/Export context for force export now contain a header providing additional useful information issued from the Flux project. Moreover, the DLOAD card comment in such files now automatically displays the rotation speed if this quantity was imposed in the project's mechanical set.
Data Import/Export context FX-22759 The management of symmetries and periodicities in 3D Transient Magnetic projects has been optimized. This improvement leads to significantly shorter computation times at the first solving step in projects that contain several symmetries and periodicities and that manipulate data collections created with the Import/Export context before the resolution.
Documentation FX-23764 In the help menu of the supervisor (and in the help menu of Flux), the link "Altair Flux video" did not work anymore. The web page did not exist anymore.

This link has been replace by a link to the Altair Flux Applications web page:

The name "Altair Flux video" has been renamed" in "Altair Flux applications".

Flux e-Machine Toolbox FX-22699 When starting a test in FeMT it is now possible to choose if the test will be run with Dynamic Memory Allocation or User- defined Memory Allocation.

In the previous releases the memory mode used to run the test was depending on the memory mode of the Flux application that generated the FeMT coupling component. Then for a given coupling component it was impossible to change the memory mode used to run the test.

Now in the test "Parameters" the user can set the "Numerical Memory" to 0 in order to run the test with Dynamic Memory or enter a fixed amount of memory to run the test with User-defined memory.

This change also applies to the FeMT command-line. When using the "emtcli" to run a test the user provides an input file to define the test parameters. In this file this line is used to specify the memory allocation: NumericalMemory=8192

The test can be run with Dynamic Memory by specifying: NumericalMemory=0

Physics FX-10707 Permanent magnets are not supported in Steady-State AC Magnetic applications. However, after the verification performed with the Check Physics command, Flux did not display a clear error message prompting the existence of such entities if that was the case. This behavior has changed in Flux 2022.1: from now on, the Check Physics command will trigger an unequivocal message to block the resolution of Steady-State AC Magnetic projects under such circumstances.
Postprocessing FX-18679 A .FLU project has been solved in 2D transient magnetic application. This project represents a slab with a Preisach hysteresis model and a resisivity Rho submitted to a magnetic tangential field, the magnitude of which has a sine wave variation in time. The use of the command "Spatial transient computation" with "Computing average values" with spatial formula "dPowV-dLossV" (mean over the last time period [0.003 s; 0.004 s] of the simulation). This formula "dPowV-dLossV" corresponds to the mean hysteresis loss densities. Irregularities were obtained which can be seen when displaying the isovalues of this spatial quantity. The quantity dLossV corresponds to the Joule loss density (Rho*mod(J)^2). dPowV is the sum of dLossV and the hysteresis loss density. dPowV and dLossV have high values and their difference has values one or two orders of magnitude lower.

The command "Spatial transient computation" with "Computing average values" has been improved:

1- the computation with "Computing average values" has been improved. What was done was the statistical average of the values for all time steps. Now an integral over the time period [t1,t2] is performed and the result is divided by the value t2-t1.

2- the computation with "Spatial formula - values at nodes" has been improved.

3- an option to compute an element-wise constant spatial quantity has been added: "Spatial formula - constant value per element".

Now the displayed isovalues are smoother with both options "Spatial formula - values at nodes" and "Spatial formula - constant value per element".

Postprocessing FX-16227 When a "Predefined (energy, force,... )" or a "Point (a spatial quantity at a point)" sensor was not entirely described, there was no message displayed to warn the user of the software. It is the case when:

- the coil conductor of the sensor is missing, because it has been deleted,

- a component of the electric circuit is missing, or

- when the point coordinates do not correspond to the region/volume/face constraint, and the value of this sensor was NaN.

Now a clear message is displayed to warn the user that the sensor is not entirely described.

Solving FX-21554 The solving of a project with multi-responses shape optimization is faster from this version.
Solving FX-21747 The solving of a non-linear project with shape optimization for the magnetic force or for the torque is faster from this version.
Solving FX-22911 Using the distribution option set in a Scenario, it is now possible to compute a free-shape optimization and distribute the computation across remote nodes and/or locally, allowing a major speed-up of the optimization process.
Solving FX-14338 The circuit solving for the static initialization is now using Mumps Local instead of SuperLU, allowing better performances and scaling.
Solving FX-19444 If the MPI options are defined through the Supervisor and only the local node is used (i.e.: no remote nodes were used), Mumps local will be used instead of its distributed version to speed up the linear solver processes.