Best Of
Re: Can slc meet the standards of FDA for statistical analysis software used by CRO companies?
As far as I am aware the FDA uses SAS software to run SAS programs with SAS data sets.
Altair SLC can run SAS programs to create SAS data sets, and those SAS programs can be run using SAS software.
TBH I do not believe the FDA will notice, or care, whether Altair SLC or SAS software was used to run the programs and create the data sets sent to them! The FDA already accept data generated using R.
............Phil
PS. However, if you try to run existing SAS programs for the first time in Altair SLC, then you may find that these may fail if they use very new or undocumented features of the SAS programming language!
Re: A question about the material model of hysteresis
Hello
most of the information is on this page : https://help.altair.com/flux/Flux/Help/english/UserGuide/English/topics/HystereticMaterialsInFlux_IsotropicPreisach.htm?hl=preisach
I recommend you to use the Material Identification tool in order to fit any curve you have to these parameters if needed
Re: Air gap flux densities for a single node/point of a motor
Hello Divin,
The magnetic flux density is a quantity you can visualize and export from the standard Flux context.
The best way to export this quantity from the same nodes is to create a path with points coincident with nodes of interest. To do that you can create an arithmetic mesh line to assign at he sliding line and choose the right number of points to have along the path.
When you create a path you can choose the mechanical set to associate to the path as in the picture below. From this choice depends then the position during the solving steps; so if you want to have the path in the same position you have to choose the mechanical set fixed.
I hope this can help you.
Best regards,
Letizia

Re: I cannot find the Card Image Conduction
Hello Hassan,
Kindly proceed by following the steps indicated in the image. With just a single click, you can set the Heat Flux.

Regards,
Sriramanuj Prabhu.
Understanding how PSIM links with SPICE and what you can and cannot do with the link.
Since 2016 PSIM has supported a link with SPICE, but what does this mean?
What you can do.
The simple explanation is that you can decide to use a spice engine to run a simulation that has been built using the PSIM schematic editor, but there is no co-simulation between the PSIM engine and SPICE. Here is a tutorial video to help you get started.
A basic example is that a resistor defined with a PSIM schematic element will be converted into a spice resistor element. There is a selection of PSIM elements that are SPICE compatible, like the resistor the conversion can be very simple, for other elements a subcircuit is used in SPICE to represent what was a single element in PSIM. There are PSIM elements that are not SPICE compatible, these will typically be motor, digital control, and code generation elements. You must build a simulation with 100% spice compatible elements if you want to be able to run it with SPICE.
What are the options to simulate a PSIM schematic? There are three, PSIM, LTspice and Hyperspice

You can use the PSIM engine, the PSIM solve algorithm is not SPICE based and is typically much faster with better convergence than SPICE solvers. Please watch this webinar to learn more. Hyperspice was included in PSIM in the 2022.3 release, this is the Altair SPICE engine. PSIM can also generate an LTspice compatible netlist which can be run in LTspice. If you set the LTspice executable path in PSIM, LTspice will be called at the command line and the results loaded back into PSIM providing a seamless experience. You can also generate a generic SPICE netlist to run on other SPICE engines but you will have to inspect the syntax to ensure it is compatible.
What you cannot do.
There is no way to automatically import a SPICE model and convert it into elements that PSIM can simulate. There are two main model types of interest, PWM control ICs and switch models, both need to be manually recreated within PSIM.
There is a tuning process to fit a PSIM level 2 or level 3 model to model a diode with reverse recovery, a MOSFET, or an IGBT. In most cases a PSIM model that closely resembles the SPICE model can be made.
For PWM control ICs, the functional block diagram can be recreated within PSIM which can represent the functionality of the SPICE device.
I will mention again that you cannot simulate digital control, motor drives, or c code with the SPICE link.
Why?
There is no denying that there are many elements and models created for SPICE, with PSIM we provide users with the ability to link a PSIM schematic element with a spice model allowing you to use PSIM for design and then switch to manufacturers SPICE models without needing to recreate everything in a new simulation tool. However, SPICE is known for convergence issues and slow simulation speeds of switching power converters. We have not fixed this, but hopefully being able to verify the operation in PSIM before switching to SPICE will make you SPICE simulation troubleshooting easier.
For complex topologies convergence times should mean that you use PSIM instead of SPICE, so you should be looking to model your entire system with level 2/3 PSIM devices to ensure trouble free and fast simulations.
If you are hoping to model conducted EMI have a look at these resources
If you are hoping to model losses and efficiency you should consider our thermal models
Recent thermal module improvements
Motion Solve not starting
I'm operating on Windows 11. I've installed Motion Solve 2023 but I cannot get past the start-up screen.

Re: Monarch Perpetual Licenses Ending March / April 2024
Hi Ron,
Thank you for reaching out on this topic, it's important. I’ve attached the announcement from March of this year.
To further explain what’s happening, Datawatch was a small software company who outsourced their licensing to a third party named Nalpeiron. Nalpeiron is a common provider of licensing to desktop software vendors. Altair acquired Datawatch in 2018 and we’re a larger software company with our own license servers in-house. Once the development was completed to let the legacy Datawatch software solutions, including Monarch, run off Altair’s license servers, we informed Nalpeiron we would not be renewing their service. So it’s not so much that any licenses will be terminated, but a business decision not to carry two license systems with duplicate costs. That said, it is true that once the Nalpeiron license servers go offline, licenses using that legacy activation method will not be able to activate or perform heartbeat checks.
Any perpetual licenses with an annual maintenance & support contract are eligible for upgrade. If you have perpetual licenses without a support agreement, I’m sure our Sales team will be willing to work with you on a new agreement that is commensurate with the value provided and scale of your business.
Thanks,
Christian
Re: all of the result studios disappeared! The result is a blank page!!!
Could you give us an idea of what you're doing with your process? Perhaps post the process xml and source data? Also has this been working before and just stopped working now, or has it recently changed behaviour?
Best,
Roland
Create Dummy Optimization
Overview
Optimization responses can only be used within an optimization. Nevertheless responses like e.g. DRESP2 (equations …) could also be very useful in analyses, e.g. to define derived result outputs. The script is setting up a dummy optimization. One element will be selected and its property will be a designspace. DOPTPRM are modified so that the optimization will give identical results compared to an ordinary analysis.
Usage/Installation Instructions
1. Define responses.
2. Run script (select responses, select one shell elem).
Limitation
currently the dummy designspace only accepts shell elements, which means that at least one shell element must exist in the model
Functionality
Optimization Results Statics
Subfunctionality
Bulk Data Input Results Topology
Interface
OptiStruct
Re: NODES: Why?
Congrats on your achievements!
Those yellow spheres look like temp nodes. It's hard to say how they were created but one way to make them is by selecting nodes, CTRL+C, CTRL+V.
In 2022 they can be cleared by going to the Temp Nodes panel (CTRL+F search "temp nodes" to find this) and pressing the green "clear all" button.

In newer versions of HW, like 2023, you can right click on nodes in the Model browser and select "Delete Free Nodes"


