ZMT zurich med tech

Sim4Life V9.4 was released on March 5, further strengthening its position as the platform of choice for neurostimulation modeling, with targeted improvements to quality, robustness, and usability driven by demanding real-world application work. Key highlights of the new release include: Thermal unstructured stationary solver: New solver enabling the calculation of steady-state temperature distribution in complex geometries using an unstructured mesh. NVIDIA Blackwell GPU support: Added support for NVIDIA Blackwell architecture GPUs, ensuring compatibility with NVIDIA’s next-generation GPU hardware. Improved alignment between GUI and Python workflows , a clearer API structure, and more accessible documentation support large-scale, script-driven studies. Rebuilt manual and Python API reference for an improved browsing experience and search functionality. Stability, performance, and quality assurance: Improved robustness and performance for complex, large-scale models Cleaner, more consistent user interface (Web version) to improve focus during modeling and simulation setups. Integrated AI assistant (Web version): Accessible directly from the search bar to answer questions about tools, workflows, solvers, and APIs. Sim4Life V9.4 Web is available on all our cloud platforms for commercial users, researchers, and students. Sim4Life V9.4 Desktop is available directly through the Automatic Software Update window in the Sim4Life GUI. Your current license file provided by ZMT remains valid for this version. A detailed list of all changes can be found in the Release History. 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.

I've been comparing running EMLF simulations, in some cases assigning anode=100V and cathode = 0V, vs. anode = 50V and cathode = -50V. Theoretically, these should produce the same results, as the potential difference is the same in each, but that's not what I am finding. It seems as if a reason for this are the 'holes' in the simulation, which are assigned with the conductivity of the background material, which is air. This produces large regions of effectively 0 S/m conductivity within the model, leading to voxels that are solved as 0V throughout the simulation. These voxels then alter the path of current within the model, which would otherwise be limited to flowing between electrodes, particularly if a cathode is assigned as 0V for instance. Is the answer to this filling the models with a material that could be assigned as 'fat', as is done in the following paper? https://www.nature.com/articles/s41551-026-01684-w What else could be making these choices of electrode boundary conditions nonequivalent? @bryn would love your input on this.