Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Progress on Vella Have started on the external fuel rail and other components. Starting to see where to use the LEAP 71 picogk kernel and where to use Autodesk Fusion MCP. So I am now combining computational engineering with agentic cad via Cursor utilizing my own design logic that...

16,408 görüntüleme • 3 ay önce •via X (Twitter)

14 Yorum

FutureNeon profil fotoğrafı
FutureNeon3 ay önce

@leap_71 @autodesk @cursor_ai Fuel rail packaging is where combustor and HP turbine constraints collide. What determines whether a component goes to PicoGK or Fusion?

Dylan Small profil fotoğrafı
Dylan Small3 ay önce

PicoGK generates highly complex meshes, but that's the tradeoff for its strength, it can produce insanely detailed parts and geometry that would be extremely difficult or time-consuming in traditional CAD. The CAD MCP is better suited for straightforward designs. It's far lighter on mesh complexity and file size, making it ideal for things like planetary gear systems or geometrically forgiving designs that just need to work.

FutureNeon profil fotoğrafı
FutureNeon3 ay önce

@leap_71 @autodesk @cursor_ai Fuel rail internal geometry is exactly where parametric CAD fights you hardest. Are you treating PicoGK output as final mesh for AM or exporting to a solver?

Tyler Reid profil fotoğrafı
Tyler Reid3 ay önce

@leap_71 @autodesk @cursor_ai This is really inspiring, and the first time I've seen someone really take ahold of picogk. Thanks for sharing

Adel Bucetta profil fotoğrafı
Adel Bucetta3 ay önce

@leap_71 @autodesk @cursor_ai progress on vella is one thing, but have you considered how your changes will integrate with the larger ai ecosystem? don't get stuck in a local optimization

Pawzard profil fotoğrafı
Pawzard3 ay önce

@leap_71 @autodesk @cursor_ai the hard part is figuring out where each tool actually earns its keep vs where youre fighting it whats the split looking like so far, like 70/30 leap71 vs fusion mcp?

neel daftary profil fotoğrafı
neel daftary3 ay önce

@leap_71 @autodesk @cursor_ai woah this looks insane...wow

Light profil fotoğrafı
Light3 ay önce

@leap_71 @autodesk @cursor_ai 🔥

Dale Sparrow profil fotoğrafı
Dale Sparrow3 ay önce

@leap_71 @autodesk @cursor_ai Completely underrated account

Chuck Petras profil fotoğrafı
Chuck Petras3 ay önce

@leap_71 @autodesk @cursor_ai @BrianRoemmele

安叫兽|Bird🕊️ 🔶 BNB profil fotoğrafı
安叫兽|Bird🕊️ 🔶 BNB3 ay önce

@leap_71 @autodesk @cursor_ai 这套流程跑通后改迭代应该会快很多

Brosko profil fotoğrafı
Brosko3 ay önce

@leap_71 @autodesk @cursor_ai curious how long before the 'own design logic' part becomes the actual product and the rocket is just the demo

Makaroni profil fotoğrafı
Makaroni3 ay önce

@leap_71 @autodesk @cursor_ai baking your own design logic into the build flow is the move that part dont get enough credit 🔥

king arthur profil fotoğrafı
king arthur3 ay önce

@leap_71 @autodesk @cursor_ai combining computational engineering with agentic cad is a smart workflow. mixing picogk and fusion mcp like that should save real iteration time.

Benzer Videolar

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!

Andrew Ng

142,256 görüntüleme • 1 yıl önce