Posts

#4441 Rhino3D, Grasshopper and Ollama-supported Local LLM

-
#4441 Rhino3D, Grasshopper and Ollama-supported Local LLM #4441  What could I do withRhino3D, Grasshopper and an Ollama-supported local LLM? Combining Rhino3D , Grasshopper , and a local Ollama LLM opens up a powerful frontier: Generative Design Engineering . By linking a local, private LLM directly to a parametric CAD environment, you can bypass the cloud, ensure absolute data privacy, and build a closed-loop system where AI interacts directly with 3D geometry and logic. Because Grasshopper can execute Python scripts (via the CPython component in Rhino 8 or GHPython in Rhino 7), you can stream data back and forth between Ollama's local API endpoints ( http://localhost:11434 ) and your viewport. Here is a breakdown of what you can build and achieve with this stack, categorized by architectural pattern: 1. Natural Language to Geometry (Semantic Modeling) Instead of manually dragging sliders and wiring components, you can use the LLM as a translation layer between human intent and p...
Post a Comment
Read more

#4440 Prompts for Domains -> Sub-Domains -> Systems Breakdown -> JSON -> Cypher Statements

-
Image
#4440 Prompts for Domains -> Sub-Domains -> Systems Breakdown -> JSON -> Cypher Statements #4440 I have 3 consecutive prompts: 1) "Within domain [domain, e.g. Mechanical Systems], list 15 sub-domains",  2) "List 10 unique systems within each of transportation systems domain sub-domains",  3) "Break down [system] into subsystems, components and parts, with functional description for each. Identify interaction relationships between entities Respond with a JSON list." Improve these prompts to run in sequence, producing complete, correct and consistent valid JSON output. To make these prompts work seamlessly in a sequential pipeline—where the output of one smoothly feeds into the next—we need to enforce strict structural constraints. The biggest risks in sequential prompting are hallucination , inconsistent formatting , and truncated JSON (especially in prompt 3, which asks for a massive amount of data). Here is an improved, production-ready seque...
Post a Comment
Read more

#4439 AI Agents

-
#4439 AI Agents #4439  I don't trust AI agents to be deterministic, therefore I cannot predict what they will do, and they can do damage without intervention. That is a completely valid, deeply rational stance to take. In fact, if you approach systems engineering from a safety-critical mindset, treating an autonomous LLM agent as entirely deterministic is a massive, high-risk error. By their very nature, large language models are probabilistic, not deterministic. Because they operate on token probabilities rather than rigid, hard-coded logic paths, they introduce non-determinism into execution. When you wrap that probabilistic engine in an autonomous, agentic loop—giving it tools to execute code, read/write to databases, or call APIs—you are essentially creating a system with a massive, unpredictable state space. Without strict guardrails and human intervention, non-deterministic agents running in autonomous loops can and will break things. If you want to leverage the reasoning p...
Post a Comment
Read more