Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Tension Map / Dynamic Squish 1. Geo Node to capture the distance between "Edge Vertices" node Position 1 & 2 as `before_edge_dist` 2. Curve modifier 3. Geo Node same again as `after_edge_dist`. `after_edge_dist / before_edge_dist = diff`. 4. Use the diff to mix normal maps

192,856 görüntüleme • 4 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

[Graph Convolutional Network] by hand ✍️ Graph Convolutional Networks (GCNs), introduced by Thomas Kipf and Max Welling in 2017, have emerged as a powerful tool in the analysis and interpretation of data structured as graphs. This exercise demonstrates how GCN works in a simple application: binary classification. -- Goal -- Predict if a node in a graph is X. -- Architecture -- 🟪 Graph Convolutional Network (GCN) 1. GCN1(4,3) 2. GCN2(3,3) 🟦 Fully Connected Network (FCN) 1. Linear1(3,5) 2. ReLU 3. Linear2(5,1) 4. Sigmoid Simplications: • Adjacent matrices are not normalized. • ReLU is applied to messages directly. -- Walkthrough -- [1] Given ↳ A graph with five nodes A, B, C, D, E [2] 🟩 Adjacency Matrix: Neighbors ↳ Add 1 for each edge to neighbors ↳ Repeat in both directions (e.g., A->C, C->A) ↳ Repeat for both GCN layers [3] 🟩 Adjacency Matrix: Self ↳ Add 1's for each self loop ↳ Equivalent to adding the identity matrix ↳ Repeat for both GCN layers [4] 🟪 GCN1: Messages ↳ Multiply the node embeddings 🟨 with weights and biases ↳ Apply ReLU (negatives → 0) ↳ The result is one message per node [5] 🟪 GCN1: Pooling ↳ Multiply the messages with the adjacent matrix ↳ The purpose is the pool messages from each node's neighbors as well as from the node itself. ↳ The result is a new feature per node [6] 🟪 GCN1: Visualize ↳ For node 1, visualize how messages are pooled to obtain a new feature for better understanding ↳ [3,0,1] + [1,0,0] = [4,0,1] [7] 🟪 GCN2: Messages ↳ Multiply the node features with weights and biases ↳ Apply ReLU (negatives → 0) ↳ The result is one message per node [8] 🟪 GCN2: Pooling ↳ Multiply the messages with the adjacent matrix ↳ The result is a new feature per node [9] 🟪 GCN2: Visualize ↳ For node 3, visualize how messages are pooled to obtain a new feature for better understanding ↳ [1,2,4] + [1,3,5] + [0,0,1] = [2,5,10] [10] 🟦 FCN: Linear 1 + ReLU ↳ Multiply node features with weights and biases ↳ Apply ReLU (negatives → 0) ↳ The result is a new feature per node ↳ Unlike in GCN layers, no messages from other nodes are included. [11] 🟦 FCN: Linear 2 ↳ Multiply node features with weights and biases [12] 🟦 FCN: Sigmoid ↳ Apply the Sigmoid activation function ↳ The purpose is to obtain a probability value for each node ↳ One way to calculate Sigmoid by hand ✍️ is to use the approximation below: • >= 3 → 1 • 0 → 0.5 • <= -3 → 0 -- Outputs -- A: 0 (Very unlikely) B: 1 (Very likely) C: 1 (Very likely) D: 1 (Very likely) E: 0.5 (Neutral)

Tom Yeh

46,779 görüntüleme • 2 yıl önce

OptimAI Lite Node v1.1: Built for Scale, Designed for You! 💕 In just 2 weeks since the launch, the OptimAI Network has seen explosive growth—130,000+ active node participants powering the future of decentralized AI. With this incredible momentum came a new challenge: ensuring our network could scale seamlessly to support massive concurrent connections and real-time participation. That’s why we’ve rolled out OptimAI Lite Node v1.1—a major upgrade focused on: + Stabilizing infrastructure to handle high traffic from a global community. + Enhancing performance for smoother data mining, validation, and edge compute participation. + Refining user experience with UI updates that make contributing effortless. Every line of code and infrastructure upgrade was made with one goal in mind: to support YOU—the builders, validators, and visionaries of the OptimAI ecosystem. Now’s the time to bring more friends into the journey. 🔥 The more we grow, the smarter and stronger the network becomes—and the greater the rewards. Let’s keep building, validating, scaling. Together we’re not just powering AI—we’re reshaping how it’s built. Join or revisit the node here: 🌐 Chrome Extension: 📱Telegram Mini-App: What’s Coming Next: OptimAI Edge Node & the Rise of Agentic AI 🔸OptimAI Edge Node (Mobile) We’re working hard on the next major release: the Edge Node for mobile, which will allow mining and AI tasks to run in the background—unlocking more earning opportunities and decentralized compute power from your smartphones. 🔸More Task Types & Missions Expect new types of contributions, from AI-enhanced data validation to edge inference and scraping automation—powered by autonomous mining agents. 🔸Expanded Rewards Program As we grow, more reward tiers, bonuses, and campaigns will be introduced. Your participation now paves the way for long-term benefits. Also, do not forget to checkout our article below and learn more about our latest Community Tips & Best Practices!👇 __________________ OptimAI Network #L2 #DePIN Reinforcement Data Network for #Agentic #AI Mine Data. Fuel AI. Earn Rewards. Turn Your Data into Tomorrow’s AI #Agent. Visit our website at:

OptimAI Network

76,486 görüntüleme • 1 yıl önce

a contractor in Shenzhen priced a ¥12,470,900 hospital contract, about $1.7m, in one afternoon and beat firms carrying forty people he explained how he did it: the bid consultancy he used to pay took three days and ¥46,000 for the same envelope. he did this one alone, off one screen, at 11.4% margin, uploaded before the 17:00 cutoff 214 pages of tender documents read, 68 binding clauses pulled out, 9,485 building parts loaded, 14 places found where a duct and a beam sit in the same cubic metre, deepest one 38mm, all of them fixed, 3,318 lines of quantities priced and the package encrypted and uploaded before the 17:00 cutoff this is Graph Engineering: the job gets cut into small nodes, one narrow task each, wired so that one node's output is the next node's input, and any node is allowed to stop the whole run. it turns a model that answers you into a machine that finishes the job: - give every node one job and one output. a node doing two things fails at both and you cannot tell which one broke - put the cheapest rejection first. his qualification node reads clause 7.4, foreign-owned firms barred, and ends the run four seconds in, before anything expensive touches the model - what moves between nodes is a file. the model travels as a model, the quantities as a table, the price as a number - build exactly one loop: the checker finds 14 collisions, the fixer drops the duct 550mm, the checker runs again, and nothing moves on until the count is zero - cap that loop, or a graph will grind on three impossible clashes until the deadline passes - keep one node whose only job is to say no, and give it authority over everything above it - log each node's output on its own, because when the price comes out wrong you need to know which node believed the wrong thing - run the expensive nodes last, always the catch is that a graph is an extremely confident machine: point it at an outdated rate book and it prices an entire hospital off it without a single node noticing, because no node is asked to doubt the input, only to process it so the nodes that earn their keep are the ones that reject, and almost nobody builds those first bookmark this, the full build with all nine nodes and what each one hands to the next is written out in the article ↓

Argona

38,189 görüntüleme • 1 ay önce