Skip to content
  • Search
Skins
  • Light
  • Brite
  • 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. Simulations & Solvers
  4. Errors during voxeling

Errors during voxeling

Scheduled Pinned Locked Moved Simulations & Solvers
2 Posts 2 Posters 991 Views 2 Watching
  • 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.
  • T Offline
    T Offline
    tenvo
    wrote on last edited by
    #1

    I have a very small wearable device with 4 different materials in the design. Using Bounding Box 9x subgrid, the number of cell was 3.388Gcells.

    In the voxeling process, there were errors in the console:

    Error : Dynamic exception type: class std::exception
    std::exception::what: Unable to allocate memory for bit matrix

    Error : Dynamic exception type: class std::bad_alloc
    std::exception::what: bad allocation

    Error : Dynamic exception type: class std::bad_alloc
    std::exception::what: bad allocation

    Error : Dynamic exception type: class std::exception
    std::exception::what: Unable to allocate memory for bit matrix

    Error : Dynamic exception type: class std::exception
    std::exception::what: Unable to allocate memory for bit matrix

    Error : Dynamic exception type: class std::exception
    std::exception::what: Unable to allocate memory for bit matrix

    Error : Dynamic exception type: class std::exception
    std::exception::what: Unable to allocate memory for bit matrix

    Error : Dynamic exception type: class std::exception
    std::exception::what: Unable to allocate memory for bit matrix

    Does these error messages indicate that the machine is running out of memory?

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

      Yes, bad alloc means the memory could not be allocated. Try to reduce grid size, and ensure your subgrid is substantially smaller than the total computational grid.

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      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