ZMT zurich med tech

We are excited to announce the release of Sim4Life V8.2, designed to enhance your simulation experience. Our latest release is focused on enhanced usability and performance, making advanced simulations more accessible than ever before. Please find more details on the new features of Sim4Life V8.2 here.

S4L_V8,2_News_Item.gif

Access it via sim4life.io, sim4life-lite.io, or sim4life.science, or download the latest desktop version from our website. A comprehensive list of Sim4Life V8.2’s new features, improvements, and fixes (web and desktop versions) is provided in our Release Notes.

Please send your feedback and suggestions to s4l-support@zmt.swiss.

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.

@halder This is the max modulation value I extracted, and the vast majority of the values are NaN. However, when I checked the slice viewer, I didn't notice any issues. Are these NaN values treated as 0 in the slice viewer? I extracted this value to create a 3D dataset, so I'm a bit confused about how to handle these NaN values.aaf9e88d-cb7e-4fb4-b7db-530bfcbc1b79-image.png