altair flux™ 2019 · 2019. 7. 11. · altair flux™ 2019.1 1 release notes: altair flux™...

Altair Flux™ 2019.1

Release Notes

Contents

1 Release Notes: Altair Flux™ 2019.1......................................................................... 3

1.1 Essential Information of Flux 2019.1............................................................................. 41.2 New features of Flux 2019.1........................................................................................ 51.3 Resolved Issues of Flux 2019.1...................................................................................19

2 Release Notes: Altair Flux™ 2019.0.1....................................................................24

2.1 Resolved Issues of Flux 2019.0.1................................................................................ 25

3 Release Notes: Altair Flux™ 2019...........................................................................27

3.1 Essential Information of Flux 2019.............................................................................. 283.2 New features of Flux 2019......................................................................................... 293.3 Resolved Issues of Flux 2019......................................................................................43

4 About external software – supported version.....................................................46

5 About protection and installation........................................................................... 48

2

Release Notes: Altair Flux™2019.1 1

1 Release Notes: Altair Flux™ 2019.1

Flux 2019.1 is available with new features, corrections and improvements. It can be applied as anupgrade to an existing 2019 installation, or it can be installed without first installing Flux 2019.

This chapter covers the following:

• 1.1 Essential Information of Flux 2019.1 (p. 4)

• 1.2 New features of Flux 2019.1 (p. 5)

• 1.3 Resolved Issues of Flux 2019.1 (p. 19)

Altair Flux™ 2019.11 Release Notes: Altair Flux™ 2019.1 p.4

1.1 Essential Information of Flux 2019.1

Essential information about Flux 2019.1

For Flux 2019.1 the user has the possibility to be protected by "HWU" protection (Windows andLinux) exclusively.

The Legacy protection has been removed.

In order to use the version HWU, you need:

• HW license file Version 19.0

• License Manager-LMX Version 14.0.4

Flux 2019.1 is available for Windows and Linux OS:

• Windows 7, Windows 10

• Red Hat and CentOS 6.6/7.2

• SLES 12 SP2

Flux 2019.1 takes into account several user feedbacks, and around 40 issues have been solved in thisversion.

Distributed computing with MPI is available in Flux for Windows and Linux and can be used withPBS. However, qualification on Windows cluster connected with InfiniBand has not been doneand Linux clusters is highly recommended for parallel computing.

It is now possible to install Flux on Windows or Linux without administrator rights with limitedfunctionalities.

• for Windows, please consult the installation guide § 2.2.3 Other Flux Components Installation

• for Linux, please consult the installation guide § 2.3.4 Flux API Installation

Minimum memory required:

• For Flux 2D: 8 GB of RAM

• For Flux 3D, Skew and PEEC: 12 GB of RAM

SPEED import is not available since Flux 2018 version. Please use a previous Flux version to importyour SPEED file.

Proprietary Information of Altair Engineering


1.2 New features of Flux 2019.1

New features dealing with Physics

New features Description

Magnetdemagnetization

during solving process

Flux 2019.1 offers the capability to take magnet demagnetization phenomenainto account during solving process for 2D and 3D transient applications,thus empowering the modelling of devices like rotating electrical machines.For example, computation of typical quantities such as motor torque orelectromotive force are now more accurate and new analysis like the evolutionof the remanent flux density on magnets are available.

This feature, based on a static Preisach model implemented in the Flux solver,applies to permanent magnets described by non-linear materials defined bytheir coercive force Hc and their remanence Br.

Figure 1: B(H) curve showing demagnetization




Figure 2: Colour shades of remanent flux density on a magnet

Upgrade of one non-linear magnet model

To make demagnetization possible during solving process, the model forpermanent “Nonlinear magnets described by Hc and Br module” hasbeen upgraded with Flux 2019.1, to have a closed-loop B(H) characteristic,which is necessary to compute demagnetization phenomena. The previousand the new models are compared in the picture below.

In case you have a Flux project solved with a previous version of the software,you are invited to delete results and solve the project again to take benefit ofthis enhanced model.




Multi-parametriccomputationof iron losses

In addition to already-available iron losses computations on regions andpoints, Flux 2019.1 adds the ability to calculate these losses for multi-parametric scenarios with a single click.

Results of this computation, which applies to laminated regions for bothBertotti and LS models, are gathered and stored in a dedicated I/O parameter,whose values can be easily displayed by plotting 2D or 3D curves and alsoexported as row data tables. Creation of efficiency maps, as well as definitionof optimization process are now more straightforward than ever.

At the same time, the dialog box for running all these iron lossescomputations was refactored to make it more user-friendly.



New features dealing with Solving


Simplification of"Nonlinear system

solvers"solving options

With Flux 2019.1, the Nonlinear system solver options tab has beensimplified. In Standard mode, the user has only to choose between 4 typesof method for computing the relaxation factor for Newton-Raphson beforesolving:

• Automatically specified method• Maximal factor method• Optimal method (computation)• Optimal method with a stabilization stage

By doing this, the options have been standardized. The older solvers used inthe previous version of Flux stay available through the Advanced mode. Thismode can be set using the supervisor.

Solving process options are applicable for all physical applications of Flux 2D,3D and Skew.

Simplificationof "Advanced"solving options

With Flux 2019.1, the Advanced tab has been simplified. The method forgauge for edge variables choice appears only in 3D, when we could needit. So now, the method for gauge for edge variables choice doesn’t appearin 2D or Skew.

By doing this, the options have been simplified. The method for gauge foredge variables stay available through python command.




Speed-up thecomputation for

non-meshed coils

With Flux 2019.1, the computation of Hj by Biot-Savart for eachnon-meshed coil during the solving was speed-up by refactoring andparallelizing the code. Therefore, the computation of the flux for the magneticscalar potential formulation without circuit was also speed-up.

Remeshing with Aformulation in 3D

In Flux 2018.0, we implemented the magnetic vector potential formulation,or A formulation, for 3D project. This formulation cannot take into accountthe movement. Until now, you had to use the magnetic scalar potentialformulation, or ϕ formulation, into your 3D projects with movement.

With Flux 2019.1, you could now use the 3D A formulation for translatingmotion, i.e. with compressible mechanical set. To take into the movement inthis case, the idea is to remesh the compressible mechanical set.

This new feature is only available with the MeshGems mesher.

Induction machinewith a slip modeled

in the AC state by theA formulation in 3D

In Flux 2018.0, we implemented the magnetic vector potential formulation,or A formulation, for 3D project. This formulation could not take into accountthe slip of the 3D induction machine in the AC state. Until now, you had touse the magnetic scalar potential formulation, or ϕ formulation, into your 3Dinduction machine in the AC state.

With Flux 2019.1, you can now use the 3D A formulation to model the slip ofinduction machine in the AC state.

This new feature is available only without movement of the mechanical sets.

Results previewImprovement

During solving the evolution of predefined quantities and / or quantitiesdefined by the user are displayed. Quantities which can be displayed duringthe solving are:

• Predefined quantities of mechanical sets

• I/O parameters

• Real scalar sensors

The user can thus predict the quantities that he wishes to control during thesolving by creating the sensors / parameters necessary beforehand.

Flux 2019.1 improvement: By default all eligible sensors / parameters aretaken into account. If the user does not wish to see them all, the names ofthe unwanted sensors / parameters must start with the character _.

Example: _Param1.



New features dealing with Post-processing


Animationimprovement

The codec used to generate movies via the Animation in Flux has beenupdated.

Now the animations are more robust, with a much smaller size but alwayswith good quality

H3D export of Fluxresults for augmented

post-processing

Two new features are available with Flux 2019.1 to export results in H3Dformat to be read by other Altair software, like HyperView, HyperGraph,OptiStruct, AcuSolve or SimLab.

The first one, presented here, is available via the Flux scenario dialog box andit is mainly proposed to users willing to take benefit of all the extended post-processing capabilities offered by HyperView and/or HyperGraph. The selectedquantities are exported for all scenario steps and on the whole computationdomain; the H3D file is generated during the Flux computation, thus allowingthe user to have preview of colour shades, arrows, etc, without waiting theend of solving. The generation of this H3D file does not yet work with Flux2019.1 in case of distributed computations and in case of domain remeshing(e.g. adaptive time-step, geometric parameters piloted by the scenario).




H3D export ofFlux results for

multiphysics couplings

This second feature related to H3D export has the main goal to make Fluxeven more integrated into the multiphysics processes that involve other Altairtools, like OptiStruct, AcuSolve and Simlab. This H3D export is available onlyafter the Flux computation is completed and it is accessible via the Import/Export context for all data collections, in the same manner as the othermultiphysics exports are (Nastran, native OptiStruct, native Acusolve, etc.).The H3D generated file may contain one quantity only, computed on the user-defined support, on a user-selected list of scenario-steps.



New features dealing with Coupling


Flux - HyperStudyCoupling

HyperStudy is a multi-disciplinary design exploration, study, and optimizationsoftware for engineers and designers.

It is interesting to couple it with Flux to leverage the HyperStudy approaches(DOE, Fit, Optimization and Stochastic) for Flux models design exploration andoptimization.

The HyperStudy to Flux connection allows exploring efficiently the designspace of any electromagnetic devices modelled in Flux (motor, actuator,transformer…)

Before this 2019.1 version, The coupling between Flux and HyperStrudy hasbeen possible via the Got-It component. Starting from Flux 2019.1 it exist inFlux a dedicated command to generate a coupling component dedicated forHyperStudy. A xml file has been created and HyperStudy 2019.1 can read it toachieve a study of otpimisation with Flux.




Linux Flux API With Flux 2019.1, we can now use in Linux the same APIs as in Windows topilot Flux.

Flux-Activateco-simulations

An enhanced version of the Flux-Activate coupling component is introducedwith Flux 2019.1 and Solid Thinking Activate 2019.2: in the Flux environmentthe definition of the coupling component remains the same, however its GUIon the Activate side was improved:

• to introduce an “Advanced” tab for Flux memory settings

• and to add in the “Parameters” tab two new options: the “maximumcomputation interval” and the “output extrapolation order”. Both areintended for providing more flexibility to users when they drive Flux byActivate and for enhancing simulation performance

In particular, the field “maximum computation interval” enables the user toforce a Flux computation even if the input values provided by Activate havenot changed during this interval. In fact, some electromagnetic phenomenamay have modified the Flux output values that it is necessary to send toActivate to improve the accuracy of the whole co-simulation process.

The option “output extrapolation order” allows Activate to linearly extrapolate(order set to 1) the Flux outputs for usage as Activate inputs in the nextcomputation steps, thus guaranteeing better result quality with respect toprevious versions where Activate inputs coming from Flux were never changed(extrapolation order to set 0).



New features dealing with dedicated tool for e-Machine post-processing


Flux e-Machine Toolbox

Flux e-Machine toolbox is a new application in Flux dedicated for ElectricMachine. This tool permits to compute and postprocess results dedicated fore-Machine like efficiency maps. It's a first version. It is planned to enrich thepossibilities of postprocessing in future versions.

List of new examples

New examples Description

Wireless powertransformer (3D)

This model is based on the wireless power transfer demo kit DC2386A byLinear Technology. It features two different boards for the transmitter and thereceiver: the transmitter coil is circular spiral coil with reported inductancevalue of 24 µH, while the receiver coil has 47 μH inductance value. During thisexample coupling coefficient and self and mutual inductances of the coils willbe calculated. Finally, for a deeper understanding of the transfer process andin order to improve it a capacitor will be added in series with the transmitterand receiver coils and its influence will be analyzed.




FeMt 2D The Efficiency MAP of electrical motors becomes one of the key points for thedesign of electric motor. Indeed, for users of Flux software, it is interestingto know the optimal operating points of their electrical machines. And this inorder to find directly the most advantageous areas in terms of efficiency in thetorque-speed envelope characteristics of the machine. The main objective ofFeMT tool is to obtain the efficiency MAP for the electrical motors.

Coupling Flux-Activateon E-mobility motor

Electrical machine are used everywhere and it will be a major issue forsustainable development. Today it’s a true challenge to make an efficientdesign of an electrical machine which should answer to several points:the influence of eddy current on the machine works, how to optimize themachine, what is the best strategy command in order to manage the energyconsumption… all those questions are crucial points wondering by designers.That’s why it is necessary to know how to model the behavior of an electricalmachine with different levels of modeling in order to simulate a completesystem as a powertrain for electrical car. There are different approachesto represent the behavior of a Permanent Magnet Synchronous Machine(PMSM). The first one is an analytical approach with Park model (classicalfirst approach). The second one is using magneto-static tables calculatedwith finite element (software Flux) or FluxMotor, these model gives a betteraccuracy. The last model is the co-simulation between the finite elementsoftware in transient mode and the Activate. The case of co-simulationdepending on the type of the kinematics, there are two cases: with coupledload and multiphysics position. A comparative study has been made to showwhat are the advantages and disadvantages of each method.

List of new macros

New Macros Description

ComputeSkewEffectFromCurve

Compute skewed cogging torque from MS computation.

Input:

• Skew angle

• Value to compute

• Mobile mechanical set

Output:

• Superimposed curve

• One spatial quantity for skewed cogging




Find_rotor_angle_2D

This macro is used to find the rotor angle for t=0s in order to align itwith the magnetic induction generated in the airgap by the referencephase (e.g., phase A). It is applied to radial synchronous machinesin 2D transient magnetic application.

Input:

• Number of pole pairs

• Current sources corresponding to electrical phases (the first onebecomes the reference phase)

• The rotor mechanical set

• The stator mechanical set

Output:

• New variable (parameter defined by a formula) called POS_INIwhich contains the desired initial rotor angle for t=0s (indegree)

Find_rotor_angle_Skew

This macro is used to find the rotor angle for t=0s in order to align itwith the magnetic induction generated in the airgap by the referencephase (e.g., phase A). It is applied to radial synchronous machinesin skewed transient magnetic application.

Input:





Output:


Find_rotor_angle_3D

This macro is used to find the rotor angle for t=0s in order to align itwith the magnetic induction generated in the airgap by the referencephase (e.g., phase A). It is applied to radial synchronous machinesin 3D transient magnetic application.

Input:








Output:


CreatePark_Iabc_Drivenby_Idq

Create Iabc variables driven from Id, Iq variables in order tocompute Torque versus Id and Iq from magnet motors.

Input:

• Parameter corresponding to I_A

• Parameter corresponding to I_B

• Parameter corresponding to I_C

• Mobile mechanical set

• Number of poles

• Angle for which rotor is aligned with phase a

• Maximum value for Id

• Number of values for Id

• Maximum value for Iq

• Number of values for Iq

• Number of positions for rotor position

Output:

• Create ID and IQ parameters

• Create ID_DRIVEN and IQ_DRIVEN I/O parameters driven bysolving scenario

• A solving scenario is created (ready to be solved withdistribution of computation)

ConvertCSVFileToOMLFile

Convert directly CSV file into OML file. The input data are recognized.

Input:

• Select CSV file

Output:

• Create a result OML file with name created from the initial file(*_res.oml)




CreateLookUpTableFromTMProject

Create look up table from TM project of Flux abc and torque versusId, Iq and rotor position.

Input:

• Select CSV file

Output:

• Create a result OML file with name created from the initial file(*_res.oml)

• It will also include more data such as phase resistance, endwinding inductance, electric period and initial rotor position



1.3 Resolved Issues of Flux 2019.1

Resolved Issues

Issues Short description of the origin problem resolved in this version

Bertotti FX-8456 Bertotti window can re-open with the same parameters

It would be useful if the Bertotti window can re-open after a computationso that it is easy to compute Bertotti losses on various regions separatelywith the same options

CAD Import FX-8105 after having imported 2D STEP file, impossible to extrude face

Circuit FX-12912 When I modified the circuit and I leave the context, the context circuitdisappears

1- Enter into the circuit context

2- Modifiy the circuit

3- Leave the circuit context → the circuit disppears.

You will find attached the Flux project. To reproduce the bug, you need toenter in the circuit, make a modification and leave the circuit context.

Circuit FX-11245 Add possibility to choose the type of open circuit in solid conductor 2D

In 2D, in solid conductor menu, we ask the customer if he want to use SCdescribed by circuit, or No circuit : open or short circuited.

In case of open circuit, if we have two separate region (there is nocontact), the two regions are in parralel in the circuit. See draw.

As a Flux user, I want to have the possibility to separate both circuit.

Circuit FX-11234 modify table explaining solid conductor short-circuit or open-circuit indocumentation

Coupling FX-12183 Flux-Activate: Solving time increased (*4) between Flux12.3 & 2018.1.3

Coupling FX-8175 Modify the dialog box for HyperStudy coupling

The request is to get inputs and outputs sorted alphabetically(picture_1.png) in order to make easier the selection.

Environment FX-12746 Change the default value for the number of cores for Flux in the supervisoroptions

When Flux is installed, the number of cores set by default for Flux is thenumber of cores of the machine divided by two




So if the machine has 48 cores and if the user don't change the optionsin the supervisor Flux will start with 24 cores. So when he will start thesolving Flux will need 45 HWUs instead of 25 HWUs

I suggest to set the value to 4 cores by default

Environment FX-12517 Problem with Jython libraries load in fluxserver.wfg

Environment FX-12347 Linux – Flux 2019 HWU – Supervisor: at the top left, there is Altair Flux…instead of Altair Flux™

Environment FX-11865 Problem on Flux supervisor . Missing R from "Altair "

Environment FX-11504 Error message color when remaining faces withou face regions

When we make check physics in a 2D project, and for a given reason weforgot to assign face regions to a given number of faces, Flux return thefollowing text in black color:

Begin of physical check ...

The following faces are not inside any surface region:

1 2 3 4 5 6 7 8 9 10 11

Please use the "Assign regions to faces" command in the "Physics" menu.

So there are some users that do not pay attention to that if it is not inorange or red color.

Environment FX-8148 Clean sub-menus Import and Export in 2D, Skew, 3D

I/O context FX-11883 Import/Export context : mesh import does not work if the project is notmeshed

I/O context FX-11826 in I/O context in mechanical part add possibility to compute dFlap2Wforces

I/O context FX-11825 in I/O context, add the possibility to combine continuous and dFlap2Wcomponents of forces

Mesh Import FX-12735 Error Messages while importing simlab files into Flux

The error message should be improved in the source code informing theuser of a possible intersection of solids.

Mesh Import FX-12569 When I try to solve the project with face elements, Flux display an errormessage.




The project involves importing a bdf (face elements) file into Flux 3D andcreate the physics that goes with it. After when I try to solve the projectFlux display an error message. Problem in shell element.

Mesh Import FX-10780 Mesh import: Complete infinte box fails on this case

The mesh import is done without problem, but the complete infinite boxfails (I tried several fusion angle values at the import (45°, 60°,...) but itdoesn't work).

Modeler FX-8424 Crash in Flux due to a cut cancelled in the modeler

Physics FX-10976 Region with current density is proposed in 3D, whereas there is noformulation associated.

In the volume 5 of user guide, we don't mention this region. However inthe html help, this region is specific to 2D and 3D (see capture.jpg)

One customer from Spin try to use this region in 3D. The model can't bedone in 2D.

Physics FX-10469 Wrong curve for non linear magnet model

With the current description of a material, the model plots a wrong curve.By checking the same plotting on the material manager it seems that themodel does not work for this value.

Physics FX-9740 No closing has been made

With the project "meshed after cut surface impedance", make a manualcheck physic (no python command) and try to close the project. There iserror message.

This error doen't affect the project, and this one could be closed after asecond try.

Physics FX-9724 Problem with formulation : the formulation has not been found

check physic give an error : the formulation has not been found.

This message occurs even if I change all region in air vacuum, delete thecircuit etc....

Physics FX-8640 Check physic with laminated region and Jiles atherton material

Physics FX-8504 In 3D MH it is allowed to use non linear material for volume regionsdescribed by impedance surface, but when we put an I/O parameter forthe resistivity of this material Flux give an error message




Physics FX-8138 Remove the limitation on the number of points in spline curve when weused equivalent curve (h or b sinus)

Postprocessing FX-7488 Don't update isovalues each time that we create a curve

Postprocessing

FX-12164Have lighter videos or gifs from animations

Postprocessing

FX-10907 Mask the field "Post-processing discretization" for "impedance-type"applications

In Flux PEEC, for impedance-type applications (i.e., ConductorImpedances and Conductor Impedances with Capacitive Effects) the field"Post-processing discretization" for Unidirectional Conductors (both Tubeand Assimilation) has no interest since it has no effect on computationsand results.

It should be better to hide it for the two impedance-type applications, thetwo types of Unidirectional Conductors and for all status (not-solved, CAPSsolved, solved) of the project.

Results FX-12141 Different result on identical project MHT with surface impedance

Results FX-9817 Automatic formulation - Result different between Full and Periodic model

Results FX-8490 Strange results in this project when we compute the Flux in a non meshcoil

Results FX-8478 error concerning current density computation

Solving FX-12687 Impossible to launch Flux 2018.1.3 in Linux machine

Solving FX-12516 in 2D MT, solving time is increasing too much with number of steps

Solving FX-12488 On this 3D project MUMPS does not work where as ICCG is OK

Solving FX-12463 no solving with Flux 2019 with this 2D magnetic transient project involvingGroovy non linear magnet

Solving FX-11975 The solving of this project failed during the first step with MUMPS. Theerror message contains an estimation of the required amount of memorybut this value is not reallistic

Solving FX-9558 Error during solving with local radiation (no error with infinite radiation)

Solving FX-12773 Different behavior for solving with mumps between win7 & win10

On win7, the resolution is going well but on win10 mumps says that itcannot reverse the matrix (cf .report). I already told her to reduce the




numerical memory to let MUMPS take more memory but it doesn't changeanything.

Solving FX-12163 The error message when MUMPS has not enough memory is not complete,a part of the message is missing


Release Notes: Altair Flux™2019.0.1 2

2 Release Notes: Altair Flux™ 2019.0.1

Flux 2019.0.1 is available with corrections and improvements. It can be applied as an upgrade to anexisting installation of Flux 2019.


• 2.1 Resolved Issues of Flux 2019.0.1 (p. 25)

Altair Flux™ 2019.12 Release Notes: Altair Flux™ 2019.0.1 p.25

2.1 Resolved Issues of Flux 2019.0.1

Resolved Issues


FX-12753 Strange behavior of a solved project in Flux 2019

After to have changed the selected step, problem to close and save a solving projectcontaining mechanical set. The problem appear only if the user close the project after tohave change a selected step without save, by the cross symbol (to close Flux). A dialogbox appear to propose to save or not. The save is not done correctly by this way, andthe project become corrupted.

FX-12482 N is not evaluated when importing a data support

With Flux 2019, the use of formulas involving the normal vector N on data supportimported via the Flux Import/Export context was limited to cylindrical faces (e.g. airgapof motors). In case the user tried to use a support covering the inner lines of the stator(slots + teeth) the evaluation of N was wrong, avoiding the use of typical forces/NVHformulas.

With Flux 2019.0.1, this issue is fixed: the normal vector N is correctly computed.

FX-11060 Normal symmetry is not taken into account with nastran import

In this project, I try to impose a symmetry with B normal on XY plane but it is not takeninto account during solving.

The coordinates of all nodes are well positioned in the right plane. The surfaces are notexactly on the plane since it is a list of facets.

After to apply manually the same boundary conditions, the behavior is normal asexpected.

FX-10493 Nothing happens when changing z-coordinate of points with "Edit" or "Edit array"command

In this .FLU project, the modification of the z-coordinate of 4 points (46,47,149,150)with the "Edit array" command does not change the coordinates of the points. Thepoints does not have their position changed and in the "Geometric complements" tabof the dialog box of a point, the coordinates have not changed. The z coordinate ofthese points is modified from 19.25 to 25. The points are created by a primitive inthe modeler. The interdiction to modify these points is done if the application is notdefined, but after to define the application, there is any interdiction. The interdictionof modification of points (coordinates or type) and lines (type) should be done for allstates of the project.


Altair Flux™ 2019.12 Release Notes: Altair Flux™ 2019.0.1 p.26


FX-12624 Bug with prediction for initialization of the current step

With Flux 2019, we have sometimes wrong results from the fifth time steps with theinitialization of variables by a predicted solution. With Flux 2019.0.1, the method toinitialize variables by a predicted solution works now very well and it is very useful forhysteresis project.

FX-11674 Hysteresis (JA & Preisach) materials: false results with adaptive time step in 2D

With Flux 2019, 2D projects using hysteresis materials (JA or Preisach) could providewrong results (values of B too much high and "noised" curves) when the user solvedwith adaptive time steps, which is a smart methodology to enable/improve solvingconvergence.

With Flux 2019.0.1, adaptive time step strategies work fine and can be used to solvemodels with hysteresis materials. See description of FX-12624 for additional details.


Release Notes: Altair Flux™2019 3

3 Release Notes: Altair Flux™ 2019

Flux 2019 is available with new features, corrections and improvements. Flux 2019 is a major release.


• 3.1 Essential Information of Flux 2019 (p. 28)

• 3.2 New features of Flux 2019 (p. 29)

• 3.3 Resolved Issues of Flux 2019 (p. 43)

Altair Flux™ 2019.13 Release Notes: Altair Flux™ 2019 p.28

3.1 Essential Information of Flux 2019

Essential information about Flux 2019

For Flux 2019 the user has the possibility to be protected by "HWU" protection (Windows and Linux)exclusively.

The Legacy protection has been removed.

In order to use the version HWU, you need:

• HW license file Version 19.0

• License Manager-LMX Version 14.0.4

Flux 2019 is available for Windows and Linux OS:

• Windows 7, Windows 10

• Red Hat and CentOS 6.6/7.2

• SLES 12 SP2

Flux 2019 takes into account several user feedbacks, and around 40 issues have been solved in thisversion.

Distributed computing with MPI is available in Flux for Windows and Linux and can be used withPBS. However, qualification on Windows cluster connected with InfiniBand has not been doneand Linux clusters is highly recommended for parallel computing.

The new feature “Flux starting guide” is only available in Windows (not in Linux).

It is now possible to install Flux on Windows or Linux without administrator rights with limitedfunctionalities.

Minimum memory required:

• For Flux 2D: 8 GB of RAM

• For Flux 3D, Skew and PEEC: 12 GB of RAM

SPEED import is not available since Flux 2018 version. Please use a previous Flux version to importyour SPEED file.

The Student Edition of Flux 2019 will be available few weeks after the release of theprofessional edition.



3.2 New features of Flux 2019

New features dealing with Environment


Branding FluxTM become Altair FluxTM.

User Mode A user mode has been implemented. Thus the user has the choicebetween 3 modes:

• Standard: the standard mode.

• Beta: gives early access to a set of features which will be officiallysupported in a future release.

• Advanced: This mode gives access to a set of expert functionalitiesand also to beta features (this mode includes the beta mode).

Renaming of the command"Run a python file"

Labels and python command have been changed for running a pythonfile:

• Label

◦ Run a python file: Run a python file with full GUI refresh

◦ Run a python file in silent mode : Run a python file withreduced GUI refresh (faster)

• Python command

Before Flux 2019 Starting from Flux 2019

With GUIrefresh

executeSpy('file.py') runPy('file.py')

WithoutGUI

refresh

executeBatchSpy('file.py')runPyInSilentMode('file.py')

Note: The "legacy" python commands are alwayscompatible with Flux 2019 and future version.



New features dealing with Meshing


Visualize volumeelements internal tosolids by a cut plane

Possibility to visualize volume mesh element according to a plan definedby 3 points.

New mesh generatorby "Layers"

This mesh generator, based on the MeshGems-Hybrid module of Distene,is a mixed mesh elements generator in Flux (it creates hexahedra,prisms, pyramids, or tetrahedra).

It allows to mesh the skin depth with extruded elements (prisms,hexahedra) and relax the mesh in the remaining volume.

It is based on the initial surface mesh of the volume without modifyingit.

Mesh Import - wire body Now, when importing mesh, wire body are also imported into Flux, toallow using line region later.

Improvement of shellelements generation

with mesh import

The orientation of the current density on the shell bodies in areas waswrong where the surface elements had been merged during the meshimport. The improvement implemented has been to take into accountthe correct normal vector on these faces (merged surface elements) inthe different Flux algorithms.



New features dealing with Physics


Preisach Model (Hysteresis)

in Beta mode

A new static vectorial hysteretical model has been developped in Fluxin Beta mode (Supervisor option). This model is easier to use than theJiles-Atherton model. The Preisach model is more powerfull to generateminor loops. This model comes in two materials.

• A material with four coefficients : Br,Bsat,Hc,s that represent amajor loop.

• A material with 3*n coefficients intended to fit measurements data(by a fitting tool), in order to be as precise as possible, the fit mustbe made from the largest cycle performed during the simulation. Ifwe are close to the major loop we identify the major loop, if we arecloser to a minor loop it is better to identify this minor loop.

Table 1: Fitting example: identification of the material M800-50A

Values ai bi ci

0.33 168.2 174.79M800-50A

0.65 27.18 129.51




Note: If you want test and use the fitting tool with the newhysterical material, please contact the Support.

To get a better convergence with these materials, someresolution options must be selected :

• Method for computing the relaxation factor for Newton-Raphson:

◦ Maximal factor method (2D and 3D)• Initialization of state variables at the begining of a time

step:

◦ With predicted solution (only 3D)

◦ With the previous step solution (only 2D)

Speed up of ironlosses computationin post processing

Some improvements have been done with the new iron losses model,especially for the computation time in postprocessing.

New features dealing with Solving


Result Preview During the solving, a set of curves are automatically displayed and givethe evolution of the main quantities in runtime.

If the evolution is wrong, the user can stop directly the solving andadjust his model.




Add a Newton-Raphson tofixed point switch for themaximal factor method

For non-linear solving using this relaxation method is now more robustand can improve convergence

Simplification of GUI forsolving process options

With Flux 2019, the Linear system solver options tab has beensimplified. In Standard mode, the user has only to choose between 2types of solver before solving:

• Direct solver• Iterative solver

By doing this, the options have been standardized. The older solversused in the previous version of Flux stay available through theAdvanced mode. This mode can be set using the supervisor. The filteredoptions are set to a default value.

Solving process options are applicable for all physical applications of Flux2D, 3D and Skew.

New initializationmethod by prediction

With Flux 2019, a new initialization method of the state variables at thebeginning of each time step is proposed to the user.

This method consists in computing a predicted solution of the currenttime step using previous ones to converge faster.

Matrix size estimatorimprovement

The estimation of the matrix size could be excessively overestimated,causing a memory-based error message whereas the solving would havebeen possible. A fix has been done to reduce the cases of excessiveoverestimation.




Automatic local/distributed solver strategy

An automatic selection between MUMPS local and distributed is donebased on the dimension of the problem and the correctness of the userconfiguration. User can still use manual selection by using « advancedmode ».

Ensure compatibility withother batch schedulers(parallel computing)

Commands used for parametric distribution through PBS are nowaccessible and can be modified, making all Altair Flux/PBS features cannow be used with other batch schedulers.

New features dealing with Post-processing


3D curve dedicatedto rotating machine

The 3D curve dedicated to rotating machine allows computing aformula values along a computing circle positioned around a rotatingmachine rotation axis. Those values are collected for a set of timesteps (feature available only in Transient Magnetic application). Oncecollected, the values are represented in a 3D curve having in abscisesthe time and the angular position along the computing circle. A specificoption allows eventually to compute those values in 2D Fourier domaindepending on the motor-harmonic and the spatial order.

New features about dedicated contexts


Context of DataImport/Export

The data import/export context is a Flux environment dedicated toexchanges between Flux and a third party software.

It allows making a weak coupling with another application software:

• Vibroacoustics

• Thermal

• Any other physical application

This context is implemented in Flux since the 2018 version. It is enrichedand more robust at each version. In this 2019 version, a thermal exportto OptiStruct has been added.



New features about some added commands


Active scenario

A new command getActiveScenario() has been implemented to havethe possibility to know which solving scenario is ON when opening Fluxwith PyFlux.

For example, the calling of Flux from SimLab is simplified with this newpython command.

When opening a solved project that has several scenarios, the post-processing operations point to a given step of a scenario. This newgetActiveScenario() command allows knowing which one.

In a scrip, you have acces to the following command:

result = getActiveScenario()

print result.name

The instance of the active scenario is returned by the command.

Reminder: there is a family of commands to control the post-processing inpython (see the document How to get the steps of a scenario availablefrom Flux Supervisor)

new APIs about user I/O parameters (Groovy)

void stopSolvingASAP()

The user have the possibility to stop a solving process by evaluation of acriterion.

Typical example: a sensor reach a wished data.

public boolean isSolving()

The user wants to know if he is in solving or in post-processing.

Typical example: in solving, the user compute a value that he wants tostore in a file. In post-processing, he wants to read this value in the file.

public int getStepIndex( )

In solving, the user wants to know what is the current step number.

Typical example: In solving, l'utilisateur wants to store values in a file, sohe must empty the file at the begining of the solving process.

New features about examplesAs a reminder, all examples are accessible via the Flux supervisor, in the context of Open an example.




Flux_Compose_Induction_Motor This example is dedicated to Flux-Compose coupling. The Composescript will perform a linear search to find the input voltagenecessary to obtain the nominal current during a rotor blocked test.Once the Flux simulation is done the rest of the process is carriedout in Compose.

New features about "How to"

New "How to..." Description

How to Experimentwith NumPy in Flux?

New

NumPy is a Python module widely used in scientific computing areaand could improve the capacity of what Flux users could achievewhen they write PyFlux scripts.

However, NumPy is a native C-Python module whereas PyFluxscripts are executed by Jython, a Java Python interpreter, whichis not able to execute C Python modules thus preventing NumPyusage with Flux.

Nowadays a third-party project named JyNI (Jython NativeInterface) provides an experimental solution to execute native CPython with the Jython interpreter, starting with Jython 2.7.1

Since Flux 2018.1 release, Flux has been upgraded to use Jython2.7.1 and it becomes possible to use the JyNI library to experimentwith native C Python modules like NumPy.

How to use Altair Flux™ 2019with PBS via Display Manager

Update

The 2018.0 version of Flux offered the possibility to use PBSProfessional Compute Manager to compute distributed jobs. WithAltair Flux™ 2019, the possibility to post-process the solved projectslocated on your cluster is now available through Display Manager.

In PBS Display Manager, double-clicking Flux-GUI icon allows you tochoose the version and also the application type to open, since theversion 2019 of Flux, thanks to the drop menu.

How to launch Altair Flux™

2019 via command lineUpdate

The three command line options to run python file are renamed:

• -runPy replaces -executeSpy

• -runPyInSilentMode replaces -executeBatchSpy



New "How to..." Description

• -runPyInSilentModeAndExit replaces -executeBatchSpyAndExit

How to set Altair Flux™

2019 for Batch SchedulersNew

This document will provide the necessary knowledge to be able toset Altair Flux up for a canonical use, i.e.: solve one large-scaleproject using distribution with allocated resources.

How to get thesteps of a scenario?

New

Some API have been implemented to allow the user to selectsteps to quickly postprocess. All methods have been added on thestructure SCENARIO

• isPostprocessingOK()

• getValuesParameter()

• getIndexStep (String[] parameterNames, double[] values)

• selectIndexStep(int index)

• selectFirstStep()

• selectLastStep()

• selectNextStep()

• isValidStep(int index)

List of updated macros

Updated Macros Description

ComputeInductanceMatrix

Compute the inductance matrix of a rotating machine

Input:

• A solving scenario with results

• The current sources corresponding to the stator supply

• The stator coils

• The face regions corresponding to the magnets

• The face regions corresponding to the magnetic circuit

• A name for the resulting project

Output:

• Curves corresponding to each inductance

• I/O tabulated parameters corresponding to each inductance




SlippingMeanValue

Calculate the slipping Mean value and assigns it to an I/O variationparameter.

Input:

• select chosen variation parameter

• select the name of the quantity

• select number of steps

• select solving scenario

Output:

• Creates an I/O variation Parameter containing the slippingMean value

SlippingRMS

Calculate the slipping RMS value and assigns it to an I/O variationparameter.

Input:

• select chosen variation parameter

• Select the name of the quantity

• Select number of steps

• select solving scenario

Output:

• Creates an I/O variation Parameter containing the slipping RMSvalue

CreateSensorFor2DMotorSlotForce

Create sensors to compute force on slots for motors

Input:

• Select the magnetic region on which you want to compute force(usually rotor, stator or magnets)

• Select one starting line (preferably on one extremity)

• Select the coordinate system around which the motor isrotating

• Indicate “Yes” for radial forces or indicate “No” for tangentialforces

Output:

• Create cylindrical coordinate system

• Create spatial quantity

• Create automatically sensors to compute force on slots




CreateSensorFor3DMotorSlotForce

Create sensors to compute force on slots for motor (3D or skew)

Input:

• Select the magnetic region on which you want to compute force(usually rotor, stator or magnets)

• Select one starting line (preferably on one extremity)

• Select the coordinate system around which the motor isrotating

• Indicate “Yes” for radial forces or indicate “No” for tangentialforces

Output:

• Create cylindrical coordinate system

• Create spatial quantity

• Create automatically sensors to compute force on slots

List of New Macros


HalbachMagnetization2D

Generate Halbach magnetization for the selected face regions. Anew material “Halbach_magnet” with the desired orientation andremanence induction will be defined and assigned to these faceregions.

Input:

• Remanent flux density (T)

• Magnet relative permeability

• Angle for maximum remanent induction (degrees)


• Face regions of the magnets with Halbach magnetization

Output:

• Create a new material with the desired magnetization profileand assign it to the magnet’s face region.

HalbachMagnetization3DGenerate Halbach magnetization for the selected volume regions.A new material “Halbach_magnet” with the desired orientation andremanence induction will be defined and assigned to these volumeregions.




Input:

• Remanent flux density (T)

• Magnet relative permeability

• Angle for maximum remanence induction (degrees)


• Face regions of the magnets with Halbach magnetization

Output:

• Create a new material with the desired magnetization profileand assign it to the magnet’s volume regions.

Sensor_Display

Display points corresponding to punctual sensors

Input:

• Select punctual sensors

Output:

• Display points as multi-points support

ExportCurveVsPhaseFromAC

Generate a curve versus phase starting from a complex numberdefined by modulus and phase

Input:

• Formula to export (should be a complex number)

• Start angle (°)

• End angle (°)

• Angle step (°)

• File name

Output:

• Create a new file

ExportNastranVariousSpeeds

Generate OptiStruct or Nastran files for different speeds for vibro-acoustic analysis

Input:

• Angpos rotor parameter

• Case parameter

• Number of cases (speeds)

• Minimal angle of the scenario

• Maximal angle of the scenario




• Radius (in m)

• Slot opening angle (in degree)

• Computation support

• Name of force computation

• Name of exported files

• Overwrite existing force computation

• Format (1=Nastran bulk, 2 OS fem, …)

• If format =1 or 2, number of harmonics

• Export only Global DLOAD

Output:

• Create one file of force for each case (speed)

FindOutCornerPoint_Imax_Angle

Find out the corner point of the Torque Vs Speed curve startingfrom an unresolved Flux Project.

Input:

• current Source

• value of Imax

• value of SpeedMin

• value of SpeedMax

• the step value of the speed

• value of the Vrms max of the inverter

• solving Scenario

• the user's defined variation parameter for speed

• the user's defined variation parameter for the angle

• the user's defined variation parameter for the maximal current

• value of AngleMin

• value of AngleMax

• value of Angle Step Value

• the extension of the name of the file (for example ‘solved’)

Output:

• variation Parameter containing the corresponding Speed toVrms max

FindOutMaxSpeed_Imax_Anglefind out the Maximal speed in the Torque Vs Speed curve startingfrom an unresolved Flux Project.

Input:




• current Source

• value of Imax

• value of SpeedMin

• value of SpeedMax

• the step value of the speed

• value of the Vrms max of the inverter

• solving Scenario

• the user's defined variation parameter for speed

• the user's defined variation parameter for the angle

• the user's defined variation parameter for the maximal current

• value of AngleMin

• value of AngleMax

• value of Angle Step Value

• the extension of the name of the file (for example ‘solved’)

Output:

• Variation Parameter containing the Maximal speed



3.3 Resolved Issues of Flux 2019

Resolved Issues


Supervisor FX-8913 Flux supervisor freeze when a cache folder path is entered

Geometry FX-9710 Problem with complete infinite box. In the two attached projects, theinfinite box is created by two ways. In the first project: The infinite boxis created by create faces + create volumes. In the second project: Theinfinite box is created by complete infinite box

The 1st project is solved with a warning concerning electric cut loop (andit is true, it is not necessary to create it), the 2nd one can not be solvedbecause of this error message.

Just to remind that the two projects are the same, It is a body carsurrounded by air.

Mesh FX-12151 Two identical magneto-static project gives different results

The two projects are identical, but the results obtained in the two projectsare differents.

Mesh FX-12010 Bad visualization of mapped mesh on a cut plane

when we want to visualize mesh on cut plane , and a volume is build onlywith parralepiped mesh element ( mapped and extrusive), the mesh onthe cut plane is done with tetra only.

Mesh FX-7909

FX-8142have a possibility to better display mesh inside 3D volume

Mesh FX-12160 In the case of 3D overlay (SPM motor and IM motor), we activateadvancing front (Netgen mesher) mesh generator. Once the projectis created, it is impossible to modify the mesh option in order to setMeshGems option.

Circuit FX-11957 In this project with mesh import and with terminal of solid conductorassigned to faces, the electric circuit is delete if we enter in the circuiteditor context.




Circuit FX-10712 Interface problem in the menu circuit : when a circuit is deleted, the menuto import circuit doesn't appears anymore.

Circuit FX-8521 In Flux if we have defined a sensor of Flux associated to a stranded coilconductor component of the circuit, the association is broken if we enter inthe circuit editor.

In a SENSOR_1 is associated to the stranded coil conductorCOIL_CONDUCTOR_1, if we open and close the circuit editor contextSENSOR have no more stranded coil conductor

Material FX-11397 Curve for Materials with Spline uses non linear interpolation while duringsolving the real curve that is used is a linear interpolation between points.

This is very confusing for customers : they see "Spline" and they can plotit as a nice smooth curve whereas during solving it will be considered as alist of segments.

Memory FX-10516 MUMPs memory limitation without warning

When MUMPs RAM memory is limited by the user (see solving processoptions in the attached image), an error arises if the required RAMmemory is over the limitations. The same error occurs when the computerhas reached its own RAM limit.

Since both situations are different (one can be directly solved by theuser within Flux and the other not), I think it will be convenient displaya warning message when this limitation may be too low for the expectedMUMP requirements.

Solving FX-7769 When we stop the simulation and when we do continue solving theprocess, Flux display an error message

Solving FX-9696 Impossible to solve the projet in presence of the path

Distribution FX-11399

FX-11347

FX-11276

Impossible to distribute with one geom parameter and the angularposition

PyFluxcommand

FX-11429 Have the possibility to know which solving scenario is ON when openingFlux with PyFlux. It will simplify the calling of Flux from SimLab.




PyFluxcommand

FX-8535 Add compute method for evolutionFormula

When EvolutioFormula contains a PARAMETER (exampleEvolutionFormula[10].FORMULA = '360/PARAMETRE'), it's impossible toevaluate the formula before solving. In Python, we have often this issue.

Coupling FX-11673 Flux-Flux coupling (Magneto-Thermal coupling)

The magnetic project of this Flux-Flux coupling project (magneto-thermalsimulation) presents an error at the end of the resolution but only if themultiphysics solving session is activated. Otherwise, the same scenario issolved correctly.

Coupling FX-11882 Import/Export context takes a long time to import a mesh in solvedprojects

Using the tutorial Vibro to OS (WoundRotor case) the import of meshtakes 4 minutes while it is instantaneous in the mechanical analysiscontext.

Good news is that it only takes 1 sec if you do it before solving. So it mustdo checks on all solving steps. Please also check the deletion process.

Macro FX-11647 Wrong behavior of the ComputeInductanceMatrix macro

The python generated by the ComputeInductanceMatrix macro and byextension the computation are corrupted.

The problem is due to the python interpretor which replaces the list of theinstances by the key word ALL on the fields CURRENTSUPPLY and COILS

Postprocessing FX-11182 Update the video compiler for animations

Documentation FX-11460 Add documentation on "Distribution Manager" and "Server Manager"boutons from the supervisor

Add information in the installation guide

Documentation FX-7630 give user facility to open memento (from supervisor for instance)

Documentation FX-8540 Add a better link to the list of macro

Label FX-11557 French labels "Plan de reference" in the modeler


About external software –supported version 4

4 About external software – supported version

External programsThe use of external programs can be achieved with the versions listed in the table below.

Fluxfunctionalities

Externalsoftware

Supportedversion

Supported OS Flux OSWin64

Flux OS Lin64

2016b

Flux 12.2

Flux 12.3

Flux 2018

Flux 2018.1

Flux 2019

Flux 2019.1

2017a & 2017b

Flux 12.3

Flux 2018

Flux 2018.1

Flux 2019

Flux 2019.1

Flux - SimulinkCoupling

Matlab -Simulink

2018a & 2018b

64 bits

Flux 2019

Flux 2019.1

Distributioncomputing

CDE 2.232 bits (canbe installedin a 64 bits

Altair Flux™ 2019.14 About external software – supported version p.47

Fluxfunctionalities

Externalsoftware

Supportedversion

Supported OS Flux OSWin64

Flux OS Lin64

to exchangewith Flux)

External Altair programsExternal programs coupled with Flux 2019.

Functionalities Altair software Compatible versionwith Flux 2019

Export to .. (Vibroacousticsand mechanical analysis)

OptiStruct

Export to.. (Thermal analysis) AcuSolve

Co-simulation Activate

Mesh import HyperMesh

Mesh import SimLab

Optimization HyperStudy

2019 version and more


About protection andinstallation 5

5 About protection and installation

Since the 2019 version, there only one Flux installer, the HWU licensing system. The Legacy licensingsystem is no longer released.

About HWUSince the 12.2 version, it is possible to use the HyperWorks Units as protection system. The HWUscount is split into 2 parts:

• GUI = description of geometry+ mesh + physics + postprocessing of results

• Solver = computation of the model

All the applications are covered.

HWU for Flux 3D/ Skew / PEECFor Flux 3D/Skew/PEEC, the HWU licensing system is the same as all HyperWorks solvers:

• GUI = 21 HWUs

• Solver = 30 HWUs

HWU for Flux 2DFor 2D users exclusively, the offer has been adapted. There is no GUI / Solver distinction. By default,the user has access to all applications and with 15 HWUs.

Documentation installationThe setup specific to the documentation is integrated on the main setup of Flux. Since Flux 11.2,documents and examples are automatically installed with the main setup of Flux.

About installation - CDE and CSSThe Computing Distribution Engine tool (CDE) and the Computing Soft Server (CSS) allowingdistributing computations, are not installed with the main setup of Flux. The user shoud install itsstarting from the supervisor (only in Windows). For more information please consult :

• for Windows, th installation guide § 2.2.3 Other Flux Components Installation

• for Linux, the installation guide § 2.3.4 Flux API Installation

Graphics cardsIt is necessary for the proper functioning of our software that the driver of the graphics card is as up-to-date as possible. In our experience a "Windows Update" is not sufficient, it is essential to install thelatest driver supplied by the manufacturer of the card.

Eg for NVIDIA: http://www.nvidia.com/Download/index.aspx?lang=en-us

http://www.nvidia.com/Download/index.aspx?lang=en-us

altair flux™ 2019 · 2019. 7. 11. · altair flux™ 2019.1 1 release notes: altair flux™...

Documents