Sim4Life

579 Topics 1.8k Posts

Subcategories


  • Installing Sim4Life and configuring licenses

    29 Topics
    104 Posts

    These error messages can be safely ignored, but I will pass them along to see if such overzealous and misleading error messages can be suppressed in the future.

  • Working with CAD models

    53 Topics
    182 Posts

    The first method might not be working if your spline doesn't have a parametrization. If you click on the spline in the Model tree and don't see a list of points in the Controller window, then the information is no longer available and you'll have to stick to the second method.

  • Working with models from the Virtual Population

    46 Topics
    209 Posts

    Thank you for the detailed answer!

  • FDTD, Low-Frequency, Neuron, Mode-Matching, Flow, Acoustics, etc...

    217 Topics
    647 Posts

    @brown
    Thank you, I will check these things. Additionally, there are some warning messages which may help:
    7427af6d-b388-4d9a-b629-2678e1872293-image.png
    Is the mesh division not precise enough?

  • Postprocessing results

    92 Topics
    258 Posts

    Wow I can't believe I missed that. Thank you so much! The warning definitely threw me off

  • Scripting interface for Sim4Life

    113 Topics
    315 Posts

    Would like to know too in 2024 🙂

  • Running Sim4Life over a network

    3 Topics
    5 Posts

    I eventually configured Sim4Life on a Cloup GPU workstation (paperspace.com). The workstation has an Intel Xeon E5-2630 v3 processor, 16 virtual cores, 90 GB of RAM, and two NVIDIA Ampere A6000 GPUs, each with 48 GB of GPU memory. For Exablate Neuro transducers (220 and 670 kHz) simulations, the workstation improved simulation speed from about 200 Mcell/s with an 8-core OpenMP configuration, to about 12000 Mcells/s with two GPUs.

    The workstation allows simulations (1449x1149x816 grid, 200 periods, 670 kHz, 0.22 mm max step for 10 points per wavelength) in about 40 minutes with Fourier-domain sensor recordings and about 4 hours with Time-domain sensor recordings. Time-domain simulations seem only compatible with a single GPU, while Fourier-domain sensor simulations can use both GPUs. Also, the Fourier domain field sensor recordings create simulations that look unstable (or less accurate) compared to the time-domain field sensor recordings, with all other factors equal. Only the time-domain simulations have readily matched previous studies, but the simulation time is still too long.

    Can the time-domain sensor acoustic simulation be run on multiple GPUs? Also, most of the time for Fourier-domain simulations is spent "allocating memory for the voxel array." Is there a way to configure the GPU to preallocate memory or another way to reduce the amount of time to distribute the array memory?
  • Editing the excitation signal

    2
    0 Votes
    2 Posts
    330 Views

    I think your signal was fine, but your settings for the Field Sensor need to be changed.

  • Invalid Bounding Box Error

    2
    0 Votes
    2 Posts
    327 Views

    2kHz will probably not be feasible in most propagating media, because the wavelength will simply be too large compared to the grid resolution your geometry requires (leading to unreasonably large time steps).
    You might want to check for e.g. what your grid look like, especially the padding at the boundaries of your computational domain.

  • This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • CEM43 / Arrhenius Thermal Damage

    1
    0 Votes
    1 Posts
    229 Views
    No one has replied
  • how to model a bent wire with a fixed length?

    10
    0 Votes
    10 Posts
    837 Views

    Thanks for the code.

    Actually I need to model some wires with the fixed length, with one part in the brain in different spots and the remaining out of the brain, It takes a long time to model each one and I'm looking for a way to make them in a shorter time.

    Thanks.

  • grid resolution of wire and insulation

    3
    0 Votes
    3 Posts
    465 Views

    Thanks for your reply.