Skip to content
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

ZMT zurich med tech

  1. Home
  2. Sim4Life
  3. Anatomical Models
  4. How to discretize anatomical models for unstructured EM LF solvers?

How to discretize anatomical models for unstructured EM LF solvers?

Scheduled Pinned Locked Moved Anatomical Models
5 Posts 3 Posters 572 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    gbgbha
    wrote on last edited by
    #1

    I am using the posable Fats model and and the unstructured EQS solver. In the documentation, I found two tutorials on unstructured solvers and already did those. They are certainly simple enough to follow, but I could not apply it to the human model. Specifically, I do not know how to properly discretize the model with multidomain mesh tool. What do I need to know?

    1 Reply Last reply
    2
    • AntoninoMCA Offline
      AntoninoMCA Offline
      AntoninoMC
      wrote on last edited by
      #2

      Hi @gbgbha ,
      You need first to create an unstructured mesh on the whole computational domain. You can do that using the Octree meshing engine, that is one of the multiple meshing engines offered in Sim4life, part of the Multidomain Meshing tool.
      One question: do you really need to use the unstructured solver for your application? In many cases, there is no need to use the unstructured solver, and the LF solvers based on a rectilinear discretization is sufficient. In general, the use of unstructured solvers is suggested when you have implanted electrodes, or when you need to consider thin layers (e.g. perineurium of fascicles or the epineurium of a nerve), or also when it is fundamental to properly discretize the electrode geometries to avoid strong staircasing artifacts.

      I hope to have been of help.

      G 1 Reply Last reply
      1
      • AntoninoMCA AntoninoMC

        Hi @gbgbha ,
        You need first to create an unstructured mesh on the whole computational domain. You can do that using the Octree meshing engine, that is one of the multiple meshing engines offered in Sim4life, part of the Multidomain Meshing tool.
        One question: do you really need to use the unstructured solver for your application? In many cases, there is no need to use the unstructured solver, and the LF solvers based on a rectilinear discretization is sufficient. In general, the use of unstructured solvers is suggested when you have implanted electrodes, or when you need to consider thin layers (e.g. perineurium of fascicles or the epineurium of a nerve), or also when it is fundamental to properly discretize the electrode geometries to avoid strong staircasing artifacts.

        I hope to have been of help.

        G Offline
        G Offline
        gbgbha
        wrote on last edited by
        #3

        hi @AntoninoMC,
        thank you for replying. I want to use the unstructured solver because the model need to be properly discretized to avoid numerical errors, while not taking up a long time, as I need to repeat the simulation at multiple frequencies. The structured solver takes about an hour to run and achieve adequate accuracy per our requirements (with appropriate grid settings & convergent criteria).
        I have tried both the faceted Geometry and the Octree-based meshing engines but neither worked. The task manager shows 0% (see attached screenshot), and after a while no multi-domain mesh was produced.
        Untitled.png

        1 Reply Last reply
        1
        • brynB Offline
          brynB Offline
          bryn
          ZMT
          wrote on last edited by
          #4

          Your log window shows a "bad allocation", which means the system ran out of memory. I guess this was from the Octree mesher.
          I would recommend to reduce the budget for the element count (e.g. start with 1-5 Mio) and then increase the element budget gradually until you get a level of detail that is sufficient for you application.

          1 Reply Last reply
          0
          • G Offline
            G Offline
            gbgbha
            wrote on last edited by
            #5

            thank you, @bryn, for the tip!

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Search