Awesome Life - Full Contents for AI Ingestion
website·Indexed 30 days ago
https://butteryoon.github.ioA comprehensive collection of technical content curated for AI ingestion, covering topics such as Reinforcement Learning (RL), RAG and AI agents, LLM benchmarks (Toss Benchmark, OpenAI MentalHealthBench), and hardware optimizations from NVIDIA and Google DeepMind.
What's inside Awesome Life
- MentalHealthBench is a public benchmark created by OpenAI in collaboration with over 80 licensed mental health professionals from 22 countries and 19 languages. Unlike previous evaluations that focused primarily on emergency situations, MentalHealthBench covers the full range of mental health conversations, from daily emotional support to acute crises. It evaluates core behaviors such as safety, context exploration, respect for user autonomy, and the provision of actionable advice when appropriate.
Overview of the Toss Benchmark for LLM Evaluation
The Toss Benchmark was developed by the Toss LLM Modeling team to address the gap between public leaderboards (which often focus on English and 'Reasoning On' settings) and actual operational environments (which require Korean language proficiency and often operate with 'Reasoning Off/Low'). It measures two primary dimensions: General Korean Performance (Math, Coding, Knowledge) and Domain Performance (Policy Compliance and Commerce Knowledge).Overview of frontier-scale open-weight models (Sept 2026)
As of September 2026, several frontier-scale open-weight models have been released, countering claims that open-source AI is declining. Notable high-parameter models include:
- Kimi K3 (2.8T)
- Qwen3.8-Max (2.4T)
- DeepSeek V4-Pro (~1.6T)
- Tencent Hy4 Preview (770B / 49B active MoE)
- GLM-5.3 (~753B)
- Shanghai AI Lab Atria Dawn Preview (744B MoE)
Overview of NVIDIA's Robotaxi Computing Stack
NVIDIA's robotaxi ecosystem is built around three primary computing domains. The depth of adoption varies by company, ranging from using only training infrastructure to implementing the full stack:
- Training & Simulation: Includes NVIDIA supercomputers for neural network training and AlpaSim for simulation.
- In-Vehicle Computing: Centered around DRIVE AGX Thor (SoC) and DriveOS.
- Architecture & Frameworks: Hyperion serves as the overarching architecture, while Alpamayo provides open models, simulation tools, and datasets.
Technical Trend: Vision-Language-Action (VLA) models are becoming central to in-vehicle inference, supported by Chain-of-Thought (CoT) reasoning data during training and dual Thor configurations in vehicles.
Overview of DiffusionGemma text generation
DiffusionGemma is a non-autoregressive language model based on the Gemma 4 architecture. Unlike standard LLMs that generate tokens sequentially, DiffusionGemma uses a diffusion head to refine text blocks by removing noise from up to 256 tokens in parallel per step. It is a 26B Mixture-of-Experts (MoE) model that activates 3.8B parameters per step and is released under the Apache 2.0 open weights license.Understand NVIDIA's Robotaxi Full-Stack Computing Architecture
NVIDIA divides the Robotaxi development lifecycle into three distinct computing layers. This modular approach allows developers to adopt one or all of these layers depending on their needs:
- Learning Computer (DGX & Alpamayo): Used for training driving models using fleet data. It utilizes the Alpamayo portfolio, which includes open inference Vision-Language-Action (VLA) models, simulation frameworks, and physical AI datasets. It employs Chain-of-Thought (CoT) reasoning to handle 'long-tail' (rare) driving scenarios.
- Simulation & Verification Computer (RTX PRO, Omniverse, & Cosmos): Used to generate and test millions of synthetic corner-case scenarios. Omniverse NuRec reconstructs real driving scenes from sensor data, and the Cosmos world foundation model modifies these scenes based on physics (weather, lighting, traffic) to expand training data.
- In-Vehicle Computer (DRIVE AGX Thor & Hyperion 10): The real-time execution layer. Hyperion 10 is a reference architecture for Level 4 Robotaxis featuring dual DRIVE AGX Thor SoCs (Blackwell platform) and a redundant sensor suite for 360-degree fusion.
NVIDIA SANA-WM World Model capabilities
SANA-WM is an open-source world model capable of generating 720p, 1-minute long videos with precise 6-DoF control using a single image and a camera path. A 2.6B parameter distilled version in NVFP4 format can generate 60 seconds of video in 34 seconds on a single GeForce RTX 5090, offering up to 36x higher throughput than similar open models.Personalized Ranking Model Architecture: GDCN + MoE
To move from coarse segment-based recommendations (gender/age) to personalized ranking, a deep learning ranker was developed through three iterations:
- DCNv2 (Baseline): Used for initial insights. Confirmed that long-term features (e.g., 7-day windows) improve performance for light users and that low-rank weight separation (rank 32) maintains performance while reducing complexity.
- DCNv2 + MoE (Mixture of Experts): Added a Single-gate 3-Experts MoE layer to bridge the prediction gap between light and heavy users, as a single network struggled to generalize across diverse activity patterns.
- GDCN + MoE (Gated DCN): Replaced DCNv2 with GDCN (Gated DCN) because DCNv2 is too sensitive to changes in feature distributions (e.g., when Two-Tower embedding versions change). GDCN uses an information gate to selectively weight features, providing better stability.
Configure Hyperion 10 In-Vehicle Computing and Sensing
Hyperion 10 serves as the reference architecture for Level 4 autonomous Robotaxis. It is designed for high redundancy in both computing and sensing to ensure operational continuity if a component fails.
Hardware Specifications:
- Computing: Dual NVIDIA DRIVE AGX Thor SoCs based on the Blackwell platform.
- Sensing Suite:
- 14 High-definition cameras
- 9 Radars
- 3 Lidars
- 12 Ultrasonic sensors
- Software Safety: Uses Halos OS to provide a production-grade safety foundation, supporting independent inspection, system verification, and continuous testing from cloud to vehicle.
Select quantized embedders using PTQ measurement maps
A study on Post-Training Quantization (PTQ) for BGE, E5, GTE, and Jina model families (24 models) mapped nDCG@10 degradation patterns for INT4/INT8 quantization based on architecture, training objective, and data scale. This data helps developers choose the optimal bit-width for embedders in vector databases.Resource: ThakiCloud/skillret-ptq-measurements Paper: https://arxiv.org/abs/2609.16391Use SGLang /v1/score for LLM-based classification
SGLang provides a
/v1/scoreendpoint that allows an LLM to act as a classification engine. Instead of generating a sequence of tokens, it evaluates the probability distribution of the very next token. This is significantly faster than standard generation because it requires only a single forward pass regardless of the desired output length.Key Implementation Details:
- Query Construction: The
queryshould contain the prompt up to the point immediately before the answer is expected. - Label Tokens: You must provide the token IDs of the possible labels (e.g., 'A', 'B', 'C') in the
label_token_idsfield. The model will return the scores for these specific tokens. - Single-Token Constraint: Each label must be represented by a single token in the model's vocabulary. If a category name (e.g., "Noise Complaint") consists of multiple tokens, you must map it to a single-token symbol (like 'A') in the prompt and handle the mapping in your application logic.
- Tokenizer Verification: Token IDs vary by model. You must use the specific model's tokenizer to verify the correct IDs for your labels.
import requests requests.post(f"{BASE_URL}/v1/score", json={ "model": MODEL, "query": prompt, # Prompt ending just before the answer "items": [""], "label_token_ids": [32, 33, 34], # Example IDs for 'A', 'B', 'C' "apply_softmax": True, })- Query Construction: The
Improve Closed-Loop Evaluation with Refuse, Decompose, Refresh
To bridge the gap where reproducible closed-loop evaluations may still support false claims, the 'Refuse, Decompose, Refresh' framework implements a three-step contract:
- Refuse: Abstain if there is no clean reference stream or matching runtime comparison.
- Decompose: Report protocol execution, operational false acceptance, and structural hypotheses separately rather than as a single PASS/FAIL.
- Refresh: Treat distribution shift alarms as requests to invalidate and recalculate reference maps rather than evidence of defects.
Reference: https://arxiv.org/abs/2609.20538