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

How to estimate print time and filament cost before printing with Nurb

Use Nurb slice to get minutes and grams from your installed slicer before a design is final.

Who it is forA print farm operator or hobbyist who needs to quote or budget a print and decide between design options.

The problemDesign changes can double print time or filament use, and it is costly to find out after the part is already printed.

The outcomePrint time in minutes and filament in grams for each part, so design changes can be compared while they can still move.

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 OrcaSlicer or Bambu Studio, which Nurb uses for slicing.
  2. Install Nurb with uv tool install nurb or pip install nurb.
  3. Run nurb slice to get print time and grams of filament for the project's parts.
  4. Change a dimension with a slider or in the part file, then run nurb slice again to compare.
  5. Run nurb export to write the print-ready 3MF once the design is settled.

Prompt for your agent

Using the nurb repo (Shpigford/nurb), run `nurb slice` on <target part name> and report print time in minutes and filament in grams. Verify that a slicer was found, since the README says nurb drives an installed OrcaSlicer or Bambu Studio.

Caveat. Nurb slice only works when OrcaSlicer or Bambu Studio is installed, and the README says export still writes the 3MF either way.

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