ZMT zurich med tech

Sim4Life V9.2 was released on December 9, featuring new capabilities, numerous bug fixes, and platform-wide enhancements for even better performance and usability. Key highlights of the new release include: Advanced third-generation anatomical modeling with AI-powered tools that generate solver-ready models directly from MRI/CT scans. New Broadband Skin Model enabling absorbed power density (APD) evaluation for regulatory compliance and device safety assessments across the 10-110 GHz frequency range. New Deep Brain Stimulation (DBS) / Stereoelectroencephalography (sEEG) electrode generator, supporting streamlined model creation for neurostimulation applications. Upgraded ViP models (Duke, Ella, Fats, Billie, Thelonious, and Yoon-sun), now featuring more realistic articulation geometries, including extreme postures. A detailed list of all changes can be found in the Release Notes . Download Sim4Life V9.2 is available for download via item 4. Sim4Life Installer, or directly through the Automatic Software Update window in the Sim4Life GUI. License Your current license file provided by ZMT remains valid for this version. We thank you for your valuable feedback and hope this release further enhances your productivity and workflows. For additional feedback or suggestions, please feel free to contact us at s4l-sales@zmt.swiss. The Sim4Life Team

When the stop button is pushed in the task manager, while a simulation is running, it will generate an event that is equivalent to "enforcing" a "convergence reached" state from the solver perspective. That's why the following log will appear inside the Solver-Log tab WARNING: [...] Simulation end request received. The solvers starts to consider this. Steady state detected at iteration x, remaining time steps are y. Simulation performed z iterations. Elapsed time for 'Time Update' was xx:xx:xx wall clock time.

Hi, there aren't any known issues with the Multiplier tool that would prevent you from scaling your field by any arbitrary value. Is it possible that in your script, you are using the same variable 'output1' for each case and as such are calculating the same value each time? If you are still having issues, could you share your project and script with the support team via s4l-support@zmt.swiss?