Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

your agent doesn't need a graph. it needs a verifier that isn't doing five jobs at once. a loop is already a graph - one node, one edge back to itself. you add a node when you'd hire a specialist. not before. here is the list of all 5...

rohit4verse's profile picture

Rohit

24,292 subscribers

15,837 Aufrufe • vor 11 Tagen •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

🎉 IT'S HERE, Node-It Add-On is LIVE! The wait is over. Node-It is officially released! Whether you're a Blender beginner or a pro, this node toolkit will change the way you create. Node-It is here to boost your creativity and speed up your process. (hellyeah) More in the coms>>
1:05

🎉 IT'S HERE, Node-It Add-On is LIVE! The wait is over. Node-It is officially released! Whether you're a Blender beginner or a pro, this node toolkit will change the way you create. Node-It is here to boost your creativity and speed up your process. (hellyeah) More in the coms>>

Pierre Lazarevic

17,256 Aufrufe • vor 1 Jahr

Graph Convolutional Network by hand ✍️ ~ 12 steps walkthrough below Graph Convolutional Networks (GCNs), introduced by Thomas Kipf and Max Welling in 2017, are the tool for data shaped like a graph: social networks, recommendations, biological networks, drug discovery, molecular chemistry. I drew and calculated a simple GCN entirely by hand. Goal: run a two-layer GCN, then a small classifier, on a five-node graph, filling in every cell yourself. 1. Given A graph of five nodes, A to E, with edges between some of them. 2. Adjacency matrix (neighbors) Put a 1 wherever two nodes share an edge, in both directions. 3. Adjacency matrix (self) Add 1s down the diagonal, one self-loop per node. That is just adding the identity matrix. 4. Messages Multiply each node's embedding by the weights and biases, then ReLU. Negatives become 0. 5. Pooling Multiply the messages by the adjacency matrix. Each node gathers the messages of its neighbours and itself. 6. Visualize Node A pools [3,0,1] + [1,0,0] = [4,0,1]. 7. Second GCN layer Messages again: weights, biases, ReLU. 8. Pooling again Pool over each node and its neighbours, once more. 9. Visualize Node C pools [1,2,4] + [1,3,5] + [0,0,1] = [2,5,10]. 10. Fully connected layer Weights, biases, ReLU. This time there are no neighbours to pool, just the node itself. 11. Linear layer One more: weights and biases. 12. Sigmoid Squash each score to a probability (≥ 3 → 1, 0 → 0.5, ≤ -3 → 0). That is the classification for each node. You have just classified every node in the graph by hand. ✍️ The outputs: A: 0 (very unlikely) B: 1 (very likely) C: 1 (very likely) D: 1 (very likely) E: 0.5 (neutral) The takeaway: a GCN layer is two parts. The top part pools each node with its neighbours through the adjacency matrix. The bottom part is an MLP that transforms each node on its own. A transformer layer has the same two parts, with an attention matrix where the adjacency matrix was. Both matrices do one job, mixing across positions: attention over tokens, adjacency over nodes. In my class I call the GCN the transformer's little cousin: a bit more stubborn, because its attention is fixed by the graph rather than computed from Q, K, and V. Draw the two side by side and the resemblance is hard to miss. 💾 Save this post! #AIbyHand #GraphNeuralNetworks #DeepLearning
0:23

Graph Convolutional Network by hand ✍️ ~ 12 steps walkthrough below Graph Convolutional Networks (GCNs), introduced by Thomas Kipf and Max Welling in 2017, are the tool for data shaped like a graph: social networks, recommendations, biological networks, drug discovery, molecular chemistry. I drew and calculated a simple GCN entirely by hand. Goal: run a two-layer GCN, then a small classifier, on a five-node graph, filling in every cell yourself. 1. Given A graph of five nodes, A to E, with edges between some of them. 2. Adjacency matrix (neighbors) Put a 1 wherever two nodes share an edge, in both directions. 3. Adjacency matrix (self) Add 1s down the diagonal, one self-loop per node. That is just adding the identity matrix. 4. Messages Multiply each node's embedding by the weights and biases, then ReLU. Negatives become 0. 5. Pooling Multiply the messages by the adjacency matrix. Each node gathers the messages of its neighbours and itself. 6. Visualize Node A pools [3,0,1] + [1,0,0] = [4,0,1]. 7. Second GCN layer Messages again: weights, biases, ReLU. 8. Pooling again Pool over each node and its neighbours, once more. 9. Visualize Node C pools [1,2,4] + [1,3,5] + [0,0,1] = [2,5,10]. 10. Fully connected layer Weights, biases, ReLU. This time there are no neighbours to pool, just the node itself. 11. Linear layer One more: weights and biases. 12. Sigmoid Squash each score to a probability (≥ 3 → 1, 0 → 0.5, ≤ -3 → 0). That is the classification for each node. You have just classified every node in the graph by hand. ✍️ The outputs: A: 0 (very unlikely) B: 1 (very likely) C: 1 (very likely) D: 1 (very likely) E: 0.5 (neutral) The takeaway: a GCN layer is two parts. The top part pools each node with its neighbours through the adjacency matrix. The bottom part is an MLP that transforms each node on its own. A transformer layer has the same two parts, with an attention matrix where the adjacency matrix was. Both matrices do one job, mixing across positions: attention over tokens, adjacency over nodes. In my class I call the GCN the transformer's little cousin: a bit more stubborn, because its attention is fixed by the graph rather than computed from Q, K, and V. Draw the two side by side and the resemblance is hard to miss. 💾 Save this post! #AIbyHand #GraphNeuralNetworks #DeepLearning

Tom Yeh

16,800 Aufrufe • vor 1 Monat

New ways to make your nodes happy. → Connect many to one Select multiple nodes and connect them all at once. → Connect one to many Pick a node, hold Shift, and hover all the nodes you want to connect it to. → Create a prompt from handle Double click a node's handle. A prompt node magically appears.
0:26

New ways to make your nodes happy. → Connect many to one Select multiple nodes and connect them all at once. → Connect one to many Pick a node, hold Shift, and hover all the nodes you want to connect it to. → Create a prompt from handle Double click a node's handle. A prompt node magically appears.

Figma Weave

11,543 Aufrufe • vor 2 Monaten

Introducing - Agents Most AI tools are a prompt box. You ask for a thing, a thing appears. No idea what happened in between. The Customuse AI agent isn't. You hand it a goal. It builds the actual node graph in front of you, with nodes you can see, rewire, edit. A real creative collaborator. Live Now.
0:30

Introducing - Agents Most AI tools are a prompt box. You ask for a thing, a thing appears. No idea what happened in between. The Customuse AI agent isn't. You hand it a goal. It builds the actual node graph in front of you, with nodes you can see, rewire, edit. A real creative collaborator. Live Now.

Customuse

1,098,693 Aufrufe • vor 1 Monat

#b3d tip: To keep complex node trees organised, you can use Node Groups. They reduce part of a node tree to a single node, which you can enter/exit by pressing TAB. You can also create inputs, so that you can control values inside the Node Group without having to open it.
0:46

#b3d tip: To keep complex node trees organised, you can use Node Groups. They reduce part of a node tree to a single node, which you can enter/exit by pressing TAB. You can also create inputs, so that you can control values inside the Node Group without having to open it.

Jan van den Hemel

39,369 Aufrufe • vor 3 Jahren

How to Convert Your ComfyUI Workflow into an APP Mode Workflow App Mode is a new way to view and run any ComfyUI workflow. When you enter App Mode, the node graph disappears and is replaced by a clean, purpose-built interface: just the inputs your user needs.
4:04

How to Convert Your ComfyUI Workflow into an APP Mode Workflow App Mode is a new way to view and run any ComfyUI workflow. When you enter App Mode, the node graph disappears and is replaced by a clean, purpose-built interface: just the inputs your user needs.

ComfyUI

79,215 Aufrufe • vor 3 Monaten

Does your wallet run a Bitcoin node for you? 🤓 Liana wallet runs a Bitcoin node for you and connects to it with just one click 🤯 Check out this 1-min video
1:02

Does your wallet run a Bitcoin node for you? 🤓 Liana wallet runs a Bitcoin node for you and connects to it with just one click 🤯 Check out this 1-min video

Liana Wallet

18,365 Aufrufe • vor 8 Monaten

Another round of Delights just dropped. → Unpack Nodes Select a node with many assets, and Unpack it to control each one individually. → Create Iterators Turn a node containing multiple assets into an iterator that processes each asset one by one. → Delete and maintain flow Shift + Delete to remove a node. The rest of the flow stays intact. What’s missing from your workflow? Tell us
0:21

Another round of Delights just dropped. → Unpack Nodes Select a node with many assets, and Unpack it to control each one individually. → Create Iterators Turn a node containing multiple assets into an iterator that processes each asset one by one. → Delete and maintain flow Shift + Delete to remove a node. The rest of the flow stays intact. What’s missing from your workflow? Tell us

Figma Weave

14,536 Aufrufe • vor 3 Monaten

ANTHROPIC LEAKED A GRAPH WHERE ONE FILE WITH 7 ITEMS CUTS YOUR WORK FROM 8 HOURS TO 40 MINUTES AND TAKES 40 DECISIONS A DAY OFF YOU autonomy isn't a slider you drag to the right - it's a graph with 7 steps, and exactly one edge leads into each one. your approve is worth nothing until there's a description of what the output should be - otherwise you're approving something nobody defined. you can't run a batch without checkpoints, because one crash in the middle rolls back all 40 tasks at once. the agent already works without you, and until it writes down what it did there's nothing to check the report against. this is where the point of no return sits: past it the loop runs while you sleep. the approval didn't disappear - you moved it onto an evaluator that never gets tired and never lets one through. silence is only allowed when there's a list of what breaks it: money, deletion, anything leaving the system. the last one is the brake - a turn limit and a budget cap, whichever runs out first kills the run. you build the brake before the engine - an agent you can't stop isn't autonomous, it's just unattended. skip one edge and nothing crashes and nobody warns you - the system quietly settles two steps lower and keeps running. save this - 7 steps, 7 artefacts, zero ways to jump one ↓
0:58

ANTHROPIC LEAKED A GRAPH WHERE ONE FILE WITH 7 ITEMS CUTS YOUR WORK FROM 8 HOURS TO 40 MINUTES AND TAKES 40 DECISIONS A DAY OFF YOU autonomy isn't a slider you drag to the right - it's a graph with 7 steps, and exactly one edge leads into each one. your approve is worth nothing until there's a description of what the output should be - otherwise you're approving something nobody defined. you can't run a batch without checkpoints, because one crash in the middle rolls back all 40 tasks at once. the agent already works without you, and until it writes down what it did there's nothing to check the report against. this is where the point of no return sits: past it the loop runs while you sleep. the approval didn't disappear - you moved it onto an evaluator that never gets tired and never lets one through. silence is only allowed when there's a list of what breaks it: money, deletion, anything leaving the system. the last one is the brake - a turn limit and a budget cap, whichever runs out first kills the run. you build the brake before the engine - an agent you can't stop isn't autonomous, it's just unattended. skip one edge and nothing crashes and nobody warns you - the system quietly settles two steps lower and keeps running. save this - 7 steps, 7 artefacts, zero ways to jump one ↓

Sprytix

41,611 Aufrufe • vor 5 Tagen

Creator of agent loops: "Anthropic also using my agent systems formula and still the biggest mistake in agents: is skipping Graphs" his 3 rules for every agent: rule 1 → loop it, don't run once - think, act, observe, repeat - cut the context and it forgets why it started rule 2 → an agent is memory + tools + reasoning - drop one and it breaks rule 3 → stop fine-tuning the model - the real alpha is the infrastructure around it the formula behind every AI agent - explained by the one who wrote it one agent → a loop → a graph of loops → a system that never forgets watch & bookmark - then read how to wire it into a graph ↓
45:37

Creator of agent loops: "Anthropic also using my agent systems formula and still the biggest mistake in agents: is skipping Graphs" his 3 rules for every agent: rule 1 → loop it, don't run once - think, act, observe, repeat - cut the context and it forgets why it started rule 2 → an agent is memory + tools + reasoning - drop one and it breaks rule 3 → stop fine-tuning the model - the real alpha is the infrastructure around it the formula behind every AI agent - explained by the one who wrote it one agent → a loop → a graph of loops → a system that never forgets watch & bookmark - then read how to wire it into a graph ↓

codila

23,915 Aufrufe • vor 24 Tagen

The next evolution of the OptimAI Core Node is coming, and it’s bringing one of our most powerful innovations yet: The Data Mining Agent. Become an OptimAI Node: 🔍 What is the Data Mining Agent? A fully autonomous agent running on your Core Node that: + Scans, retrieves, and indexes real-time public web data + Transforms raw information into actionable intelligence + Powers faster, smarter, adaptive Persona AI systems 💡 Why It Matters: Agentic AI is only as strong as the data it can access. Centralized APIs are slow, expensive, and limited. With the Core Node + Data Mining Agent, every contributor turns their desktop into a data supernode, accelerating AI evolution and giving our community a massive edge. ⚡ We’re not just building tools - we’re architecting the global backbone of Agentic AI, powered by you. Stay tuned for teasers, and get ready to upgrade your node. The future is decentralized. The future is agentic. And you are a key part of it. 💪 The more you contribute, the more you earn. Let’s BUIDL the future of AI together.
0:31

The next evolution of the OptimAI Core Node is coming, and it’s bringing one of our most powerful innovations yet: The Data Mining Agent. Become an OptimAI Node: 🔍 What is the Data Mining Agent? A fully autonomous agent running on your Core Node that: + Scans, retrieves, and indexes real-time public web data + Transforms raw information into actionable intelligence + Powers faster, smarter, adaptive Persona AI systems 💡 Why It Matters: Agentic AI is only as strong as the data it can access. Centralized APIs are slow, expensive, and limited. With the Core Node + Data Mining Agent, every contributor turns their desktop into a data supernode, accelerating AI evolution and giving our community a massive edge. ⚡ We’re not just building tools - we’re architecting the global backbone of Agentic AI, powered by you. Stay tuned for teasers, and get ready to upgrade your node. The future is decentralized. The future is agentic. And you are a key part of it. 💪 The more you contribute, the more you earn. Let’s BUIDL the future of AI together.

OptimAI Network

50,452 Aufrufe • vor 11 Monaten

One node Render→Painting! 🎨 The Paint filter is a node that I made with the help of the #blender team and will come with Blender 5.2 as part of the Online Essentials. Tutorial on Wednesday. Can't wait to see what you all do with it!
0:27

One node Render→Painting! 🎨 The Paint filter is a node that I made with the help of the #blender team and will come with Blender 5.2 as part of the Online Essentials. Tutorial on Wednesday. Can't wait to see what you all do with it!

Pau Homs

109,920 Aufrufe • vor 2 Monaten

MOST PEOPLE BUILD AI AGENTS BACKWARDS. They start with prompts, then add tools, memory, subagents, dashboards, and a graph nobody can debug. Then they wonder why the agent is expensive, confused, and unreliable. The better order is simple: harness first loop second graph only when needed A harness gives the model a workspace, tools, permissions, logs, and a definition of done. A loop lets it try, fail, read feedback, repair, and stop. A graph only makes sense when the workflow branches: approvals, parallel work, durable state, different routes, restart recovery. A graph is not a smarter prompt. A loop is not a production system. A harness is not just a system prompt. Most agents do not fail because the model is weak. They fail because nobody defined what success means.
2:07

MOST PEOPLE BUILD AI AGENTS BACKWARDS. They start with prompts, then add tools, memory, subagents, dashboards, and a graph nobody can debug. Then they wonder why the agent is expensive, confused, and unreliable. The better order is simple: harness first loop second graph only when needed A harness gives the model a workspace, tools, permissions, logs, and a definition of done. A loop lets it try, fail, read feedback, repair, and stop. A graph only makes sense when the workflow branches: approvals, parallel work, durable state, different routes, restart recovery. A graph is not a smarter prompt. A loop is not a production system. A harness is not just a system prompt. Most agents do not fail because the model is weak. They fail because nobody defined what success means.

Fluixo

11,279 Aufrufe • vor 15 Tagen

OXFORD AI PROFESSOR FED 100,000 MANUSCRIPTS DATING BACK TO 3000 BCE INTO A SINGLE KNOWLEDGE GRAPH - AND THEN ASKED IT HOW MUCH TRUTH IS IN MORMONISM the answer came back at 2% this is what an AI brain looks like when you've trained it on over 100,000 historical manuscripts going back to 3000 BCE every node in the graph is a concept and every connection shows how ideas relate across 5,000 years of human knowledge the system didn't just give an answer - it traced its reasoning across thousands of interconnected sources and cross-referenced historical records before producing a single number he's now taking questions on what to ask it next the list of topics people want tested is exactly what you'd expect.
0:27

OXFORD AI PROFESSOR FED 100,000 MANUSCRIPTS DATING BACK TO 3000 BCE INTO A SINGLE KNOWLEDGE GRAPH - AND THEN ASKED IT HOW MUCH TRUTH IS IN MORMONISM the answer came back at 2% this is what an AI brain looks like when you've trained it on over 100,000 historical manuscripts going back to 3000 BCE every node in the graph is a concept and every connection shows how ideas relate across 5,000 years of human knowledge the system didn't just give an answer - it traced its reasoning across thousands of interconnected sources and cross-referenced historical records before producing a single number he's now taking questions on what to ask it next the list of topics people want tested is exactly what you'd expect.

Noisy

267,626 Aufrufe • vor 2 Monaten

Gave UEFN its own blueprint graph. Python tool running inside the editor. Scans your level and parses your Verse code to draw a full visual map of your game logic. What it shows you: - Every device in your level as a node - Every @ editable reference between devices - Every event subscription and function call - Which Verse functions are actually being used vs sitting there doing nothing What it catches: - Broken connections where an @ editable points to nothing - Orphan devices with zero connections - Unassigned editables you forgot to wire up What you can do with it: - Click a node, and it selects the device in your viewport - Double-click to fly straight to it - Open the Verse file in VS Code with one button - Search and filter by device type - Zoom in and out - Add notes to any device - Export the whole graph as a doc
0:32

Gave UEFN its own blueprint graph. Python tool running inside the editor. Scans your level and parses your Verse code to draw a full visual map of your game logic. What it shows you: - Every device in your level as a node - Every @ editable reference between devices - Every event subscription and function call - Which Verse functions are actually being used vs sitting there doing nothing What it catches: - Broken connections where an @ editable points to nothing - Orphan devices with zero connections - Unassigned editables you forgot to wire up What you can do with it: - Click a node, and it selects the device in your viewport - Double-click to fly straight to it - Open the Verse file in VS Code with one button - Search and filter by device type - Zoom in and out - Add notes to any device - Export the whole graph as a doc

Immature

12,060 Aufrufe • vor 4 Monaten

Quick Menu by passivestar. This is a free, all-in-one, node-powered add-on that bundles a whole pile of workflow tools into one slick menu. 👇Link In Comments
2:15

Quick Menu by passivestar. This is a free, all-in-one, node-powered add-on that bundles a whole pile of workflow tools into one slick menu. 👇Link In Comments

3DxDEV

139,233 Aufrufe • vor 18 Tagen