ভক্সেল৫১ ৩.০-র সাথে পরিচিত হোন: ফিজিক্যাল এআইয়ের জন্য একটি একীভূত মাল্টিমোডাল ডেটা প্ল্যাটফর্ম

এটি ফিডে পাওয়া অংশবিশেষ। এটি সংক্ষিপ্ত বা প্রকাশকের মূল ভাষায় হতে পারে।

Voxel51 has released Voxel51 3.0, a very important update to its data platform. Voxel51 3.0 is an end-to-end multimodal data platform that puts search, curation, annotation and evaluation in one system. It targets teams training models on sensor data from robots, vehicles and factories. The release adds Voxel51 Agent, a data provenance layer and free self-service access. TL;DR Scale: Voxel51 Agent ships with 45+ MCP tools, 80+ operators and 18 open-source skills. Runs on: Hosted web app at app.voxel51.com, or self-hosted in cloud, hybrid, on-prem and air-gapped setups. No local GPU requirement disclosed. Performance: No product benchmarks published. Voxel51 cites its own survey data instead. Best: Free tier includes Voxel51 Agent, 30,000 inference requests and 30 compute hours per month. Worst: Free tier caps at 3 datasets of 10,000 samples each and 20 GB of storage. What is new in Voxel51 3.0? Voxel51 3.0 expands the platform beyond its roots in visual data with 3 core additions. Time-series multimodal support: Teams can view multiple sensor streams on 1 timeline. Segment-level embeddings find specific moments inside long recordings. Unified annotation: Labeling covers 2D, 3D, video and multimodal data. It includes automated QA, annotator metrics and human-in-the-loop review. Agentic Labeling: Vision-language models generate labels from natural-language instructions and examples. Supported modalities include MCAP, images, video, 3D point clouds, meshes, DICOM, NIfTI, geospatial data and audio. How does Voxel51 Search work? Voxel51 Search is a persistent hybrid index. It indexes datasets and computes embeddings automatically, so search works from day 1. Semantic retrieval finds visually or semantically similar moments, even without shared labels. Lexical and structured queries handle exact terms, timestamps, sensor fields and metadata. Embeddings and structured fields stay in native form and are combined at retrieval time. Vector retrieval runs on L