Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

@geometrynodes tree gen + simulation. Needs some springiness.. kinda sloppy tree #b3d Based on harry blends wiggle stuff.

60,071 görüntüleme • 6 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

I just inscribed the WORLDTREE module to Termina! You can now build, save, and import entire worldtree's, cached locally, with or without full content scraping! TRY > worldtree bitmap > worldtree bitmap full This may take some time, or you can BRING YOUR OWN DATA from here: All the commands in worldtree are essentially created to contribute towards the FULL scan, but you can run them separately. The "worldtree bitmap" command strictly builds the tree with inscription ID's. The info command takes the existing worldtree cache and adds info for each inscription ID. The metadata command does the same for metadata. The content command does the same, but scrapes all text-based inscriptions, including plain-text, HTML (titles, headers, body text, comments), JS (comments), CSS (comments). The enrich command combines the info, metadata, and content commands and runs them one by one on every inscription ID on the existing tree. The full command runs "worldtree bitmap" and then enriches each inscription ID tree by tree. This all gets cache to your local computer via indexDB. Export the cache with "worldtree save". Import existing worldtrees with "worldtree file". Currently the cache is just shy of 29mb. I suggest you download the existing worldtree from the github link above, and import it into Termina. This way you don't have to spend all day having this run. The best use-case for this is if you know there have been updates to the tree and want to add to the existing repository (best to use github desktop for files over 25mb). This will be saved ready for the next modules to make use of all this juicy data! Can't wait for what's next...

bitoshi blockamoto 🧱 BITMAP 🟧

12,684 görüntüleme • 11 ay önce

Researchers built a new RAG approach that: - does not need a vector DB. - does not embed data. - involves no chunking. - performs no similarity search. And it hit 98.7% accuracy on a financial benchmark (SOTA). Here's the core problem with RAG that this new approach solves: Traditional RAG chunks documents, embeds them into vectors, and retrieves based on semantic similarity. But similarity ≠ relevance. When you ask "What were the debt trends in 2023?", a vector search returns chunks that look similar. But the actual answer might be buried in some Appendix, referenced on some page, in a section that shares zero semantic overlap with your query. Traditional RAG would likely never find it. PageIndex (open-source) solves this. Instead of chunking and embedding, PageIndex builds a hierarchical tree structure from your documents, like an intelligent table of contents. Then it uses reasoning to traverse that tree. For instance, the model doesn't ask: "What text looks similar to this query?" Instead, it asks: "Based on this document's structure, where would a human expert look for this answer?" That's a fundamentally different approach with: - No arbitrary chunking that breaks context. - No vector DB infrastructure to maintain. - Traceable retrieval to see exactly why it chose a specific section. - The ability to see in-document references ("see Table 5.3") the way a human would. But here's the deeper issue that it solves. Vector search treats every query as independent. But documents have structure and logic, like sections that reference other sections and context that builds across pages. PageIndex respects that structure instead of flattening it into embeddings. Do note that this approach may not make sense in every use case since traditional vector search is still fast, simple, and works well for many applications. But for professional documents that require domain expertise and multi-step reasoning, this tree-based, reasoning-first approach shines. For instance, PageIndex achieved 98.7% accuracy on FinanceBench, significantly outperforming traditional vector-based RAG systems on complex financial document analysis. Everything is fully open-source, so you can see the full implementation in GitHub and try it yourself. I have shared the GitHub repo in the replies!

Avi Chawla

973,546 görüntüleme • 7 ay önce