DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to test where a printed part will bend or break with Nurb

Run a voxel stress simulation to see where a load concentrates and the weight the part breaks at.

Who it is forAn engineer or maker designing a functional part, such as a bracket or hook, that must carry weight.

The problemFDM prints often fail at layer adhesion, and it is hard to judge by eye whether a bracket will hold a given load.

The outcomePeak stress in MPa, how far the part sags, and the breaking weight quoted against layer adhesion.

What you need first

  • An AI subscription you already pay for, such as one that works with your agent or terminal
  • A Mac (the app is provided for Apple silicon and Intel) or a terminal with uv or pip available
  • A 3D printer and a slicer such as OrcaSlicer or Bambu Studio, if you want print time and filament estimates

Steps

  1. Install Nurb with uv tool install nurb or pip install nurb.
  2. Run nurb stress on the part you want to test.
  3. Read the peak MPa, sag, and margin to breaking in the output.
  4. Change the part's dimensions with the sliders or in its file, then run nurb stress again.
  5. Run nurb check to confirm the reshaped part still passes the printability rules.

Prompt for your agent

Using the nurb repo (Shpigford/nurb), run `nurb stress` on <target part name> and report the peak MPa, sag, and margin to breaking. Expected output: those three values. Verify by running `nurb check` on the same part afterward to confirm it still passes.

Caveat. The README presents the stress result as a voxel simulation quoted against layer adhesion, so treat it as an estimate and test real prints before trusting a load-bearing part.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page