AllyshipContent Radar

Hands-on 193

Công cụ, thử nghiệm và hướng dẫn thực hành

Crawl live-1795068900000 · 13:22 19 thg 11, 2026 · Xuất bản 13:29 19 thg 11, 2026

37

NVIDIA DGX Spark Developer Kit Turns a Desk Into a Supercomputing Lab

55.4

Hướng dẫn Allen Bourgoyne

At SC26, an annual supercomputing conference taking place this week in Chicago, NVIDIA is introducing the DGX Spark HPC Developer Kit for researchers, academics and developers. The kit is a four-node cluster of NVIDIA DGX Spark systems , each connected directly to its two neighbors in a ring, with an NVIDIA HPC SDK installation playbook coming soon. Researchers get a place at their desk to run multi-node scientific workloads, AI models and agents, instead of waiting for time on a shared GPU cluster. The kit puts the GB10 Grace Blackwell Superchip on researchers’ desks. A Supercomputing Lab on Any Desk The DGX Spark Developer Kit changes how researchers work. Read All NVIDIA Announcements From SC26 It scales from one system, or node, to four — linked directly to one another over NVIDIA ConnectX-7 networking, with no network switch to buy or set up. At four nodes, it provides 512GB of combined memory and 16TB of NVMe storage that provides researchers more capacity to distribute models and scientific workloads across the cluster. With NVFP4, researchers can deploy models with up to 700B parameters locally across the four DGX Spark clusters, such as DeepSeek V4.1. With that much power at the desk, researchers with a fixed compute and server allocation no longer have to wait in a queue for every job. Teams can develop and debug on their own, saving server hours for production runs and keeping unpublished results, and proprietary datasets on premises. The playbook for NVIDIA HPC SDK is coming soon, bringing GPU-accelerated C, C++ and Fortran compilers, libraries and message passing interface tools to the DGX Spark cluster — the same development tools used on NVIDIA-powered supercomputers. Teams can build and test scientific applications across four nodes, check how computation and data are distributed, and debug communication issues before scaling to larger systems. The kit brings scientific simulation and AI models and agents to the desktop, with demonstrated four-system workloads including LAMMPS with Kokkos for materials simulation and NAMD for molecular dynamics. The broader DGX Spark community has validated GROMACS for molecular dynamics, OpenFOAM for fluid dynamics, WRF for weather modeling and NVIDIA NIM microservices such as OpenFold3 and Boltz-2 for predicting biomolecular structures. Running on DGX Spark, new open dataset and post-training recipes for Nemotron 3.5 Super VL help researchers adapt the model for life sciences and chemistry, enabling secure scientific workflows on infrastructure organizations control. What Researchers Can Do With It The kit opens up new possibilities for researchers. Researchers can explore agent-assisted workflows that prepare simulation inputs, launch runs and summarize results, while the scientists validate the setup and conclusions. Researchers can also train AI models that approximate slow simulations, then use them to refine wing designs toward minimum drag. Before committing supercomputer time, a team can narrow a 10-million-cell simulation to the 50-500 dimensions that matter. Kvantify is using NVIDIA cuQuantum, and reports running tensor-network simulations of quantum-chemistry circuits with up to 70 qubits and 975 gates on a single DGX Spark, benchmarking circuits generated for penicillin ground-state energy calculations. CYRAN AI , an IIT Delhi spin-out, uses DGX Spark and its PixelFlux library to accelerate JPEG 2000 decoding for large satellite images, supporting local geospatial analysis. OpenFold shows how researchers can fine-tune OpenFold3 on NVIDIA DGX Spark to improve protein-ligand structure predictions for drug discovery. The Rubin Lab at IGI at University of California, Berkeley is using a DGX Spark and NVIDIA Evo 2 model to predict bacterial traits directly from genome sequences by comparing embeddings from genomic and protein language models against the classical baselines. With no 11-hour cluster queue times, results arrived 15x sooner on DGX Spark. The Hartwig Group at UC Berkeley is using a DGX Spark to perform LoRA fine-tuning on the Nemotron 3 Super 120B-A12B model for chemistry machine learning, training a prediction head on experimental values. By running locally on the Spark using NVFP4 quantization, the lab successfully fit a 120B-class model on a single device and bypassed multi-day cluster queue times, allowing them to run continuous eight- to 24-hour training fits back-to-back. Where to Find the Kit The developer kit is on display at SC26 and available for sale. DGX Spark products and cables can be purchased from top OEM partners and are also available through NVIDIA Marketplace . Partners include Acer, ASUS, Dell Technologies, GIGABYTE, H3C, HP, Lenovo, MSI and xFusion. An NVIDIA playbook for building and running the NVIDIA HPC SDK, a software development kit for scientific computing, is coming soon. Once available, it will give scientists and researchers a local platform to develop multi-node GPU applications, explore FP32 and mixed-precision algorithms and run molecular dynamics and materials simulations using LAMMPS with Kokkos before scaling to data center systems. Learn more about NVIDIA DGX Spark . Subscribe to the NVIDIA Local AI newsletter . Follow NVIDIA RTX Spark on X , Instagram , TikTok and Facebook . See notice regarding software product information. Read All NVIDIA Announcements From SC26

NVIDIA Blog · 17 thg 11, 2026

Nguyên văn nguồn
Chi tiết nguồn
39

I’ve noticed open sourcing your saas is the new saas playbook

55.1

Hướng dẫn gregisenberg

I’ve noticed open sourcing your saas is the new saas playbook 1. pick the job your customers hire you for 2. turn your best workflows for that job into skills 3. open source them on github 4. make them work in claude code, codex, cursor and openclaw on day one 5. ship an MCP so agents can use your product directly 6. post the repo with a list of every skill inside (like this one) 7. every install puts your brand inside someone's agent, and it gets used every day 8. the free skills do the work once. the paid product does it every week, with your data, hosting and support 9. upsell to done for you, team plans and the hosted version 10. keep shipping new skills. every one is a new launch Your free skills are the new free trial. saas has gone open source for real

X · 17 thg 11, 2026

Nguyên văn nguồn
Chi tiết nguồn
40

My way of contributing to PyTorch since I joined: complain and whine until something happens :D

55.1

Hướng dẫn giffmana

My way of contributing to PyTorch since I joined: complain and whine until something happens :D I was super happy by PyTorch team's reaction on this one! I complained about their current RNG API. I think it's horrible. I made a prototype of what I think it should look like, and we used that in our research codebase; but the implementation was horrible hacks on top of the current API. Then, I wrote a big doc explaining what I think the design should be like, and why, and how the current API simply doesn't allow it. I didn't hear much for a little while, but then they came back with a whole new design, largely the way I wanted it, plus some more. We iterated a little more on the rough edges of that (we iterated == I try it and complain), and here we are. (This is just my perspective, I'm sure there were others also requesting something like it, that I didn't see.) It's inspired by both NumPy's new API and JAX's API, but it also goes beyond both. I really like it; if you embrace the API, it gives you full control and awareness of PRNG in your codebase. It even forces you to think and make decisions you wouldn't have realized that you otherwise made implicitly, until they come back and bite you! This makes me think, maybe I should write a little guide/example of how to use it in some toy training codebase some time...

X · 17 thg 11, 2026

Nguyên văn nguồn
Chi tiết nguồn
41

TokenEconomizer: Learning from Experience to Make AI Coding Agents More Efficient

54.9

Hướng dẫn Aaron J. Li, Weijia Xu, Chandan Singh, Jeevana Priya Inala, Bin Yu, Ion Stoica, Michel Galley, Jianfeng Gao

At a glance Developers use AI coding agents in the same codebases day after day, yet agents often start each session from scratch: rediscovering familiar facts, loading unused tools, and repeating unsuccessful approaches. TokenEconomizer is an open-source plugin that learns from an agent’s past sessions in a repository to reduce waste in future sessions, without modifying the agent or its underlying model. Across 277 real bug-fixing tasks, TokenEconomizer reduced costs by 18.4–30.9% across multiple AI coding agents. Costs fell in every repository tested, while task success rates remained broadly stable. AI coding agents are increasingly helping developers fix bugs and build features largely on their own, but every interaction with their models consumes tokens. In each session , an agent sends instructions, tool descriptions, and session history to its model. Most efforts to reduce this cost focus on individual tasks. Yet developers return to the same repositories, giving agents an opportunity to learn from previous work. Without that learning, an agent may repeatedly rediscover how to run tests, load tools it never uses, or spend dozens of turns revisiting the same error. In our paper, TokenEconomizer: Experience-Driven Black-Box Cost Control for Coding Agents , we ask a simple question: can experience in a repository help an agent solve future tasks more efficiently? TokenEconomizer, an open-source plugin from UC Berkeley, Microsoft Research, and Microsoft Security, turns completed sessions into guidance for subsequent ones. It reduces waste without changing the agent or its underlying model, so developers can use it alongside the coding agents they already rely on. Figure 1. Each finished session teaches TokenEconomizer something about the repository, so later sessions cost less tokens. Where the tokens go We first profiled Claude Code on 60 tasks from SWE-Bench, a benchmark of real bug fixes in open-source Python projects, running each repository’s tasks in sequence. Three kinds of waste recurred: Rediscovering the same facts . After a repository had accumulated at least five completed tasks, 30% of tool calls repeated an action from an earlier task in that repository. Only 7% matched an action in another repository’s history. Paying for unused tools . The agent received 23 tool descriptions on every turn, but 16 were never called. Getting stuck on failures . The 17% of tasks that failed accounted for 32% of the spending. We also tested three popular open-source plugins, each built around a fixed cost-saving strategy. Each lowered costs in some repositories but not others. Together, these findings suggest that effective cost control must adapt to the repository, rather than apply the same strategy everywhere. How TokenEconomizer works After each session, TokenEconomizer reads the session’s log and updates what it knows about the repository. It then acts through three mechanisms, using only interfaces the agent already provides, as illustrated in Figure 2. Micro-skills capture repository-specific knowledge in one-line notes. TokenEconomizer identifies recurring patterns across sessions and proposes corresponding notes. They are added to the agent’s starting context only after several sessions have confirmed the pattern, and retires the note if later evidence contradicts it. Tool pruning removes tools that repository history suggests the agent is unlikely to use , while always retaining core tools for running commands and editing files. Removed tools can be restored if needed. Failure-loop intervention watches for an agent that keeps hitting the same failure. A judge model decides whether the agent is truly stuck or still making progress. If it is stuck, the agent gets a short note suggesting a different approach. In the open-source plugin, if the agent is still stuck after the note, TokenEconomizer alerts the developer rather than stopping the work itself. Figure 2. TokenEconomizer works alongside an unchanged coding agent. Micro-skills add learned facts, tool pruning trims the loaded tools, and failure-loop intervention redirects stuck work. Each finished session updates all three. The controller is designed to revise its decisions as new evidence arrives. Reported savings also account for the cost of TokenEconomizer’s own model calls. Saving costs in every repository We evaluated TokenEconomizer on 277 SWE-Bench tasks from six repositories, using five different AI coding agent and model combinations. For each repository, TokenEconomizer started with no prior session history. TokenEconomizer lowered the average cost by 18.4–30.9%, as shown in Figure 3, and saved the most in all 30 repository-combination pairs without performance loss. By contrast, lowering the model’s reasoning effort saved similar or larger amounts but led to substantial performance degradation. Figure 3. On SWE-Bench, TokenEconomizer lowered mean cost per task by 18.4–30.9% across five agent–model combinations (left), while Pass@1 rose in four of them (right). Savings grow as experience accumulates. Early tasks can cost more while TokenEconomizer learns, but cumulative costs fell below the default in every repository by the sixth task, shown inFigure 4. Each mechanism contributes savings on its own, and combining all three delivers the largest reduction. Figure 4. Cumulative cost change relative to default over each repository’s tasks, using Claude Code. Starting with no history, every repository becomes cheaper by the sixth task. The savings also carried over to sequential web development, with costs 16.0–21.2% lower on Web-Bench. On security auditing, where every task is in a new repository, costs were 6.4–19.6% lower. Looking ahead TokenEconomizer opens a path toward coding agents that learn not only how to solve tasks, but also how to spend computation more effectively. Its lightweight controller shows how experience can improve efficiency without changing the underlying agent or model. The open-source plugin ma

Microsoft Research · 17 thg 11, 2026

Nguyên văn nguồn
Chi tiết nguồn
42

⚠️ Numerical issues can go on silently for decades like in the softmax/CE! Similar issues are present in other widely-used divergences like the KL and JSD

54.8

Hướng dẫn brandondamos

⚠️ Numerical issues can go on silently for decades like in the softmax/CE! Similar issues are present in other widely-used divergences like the KL and JSD I just posted this paper overviewing what they are and how to fix them: 📚 https://arxiv.org/abs/2611.18511

X · 16 thg 11, 2026

Nguyên văn nguồn
Chi tiết nguồn
37–42 / 106
Trang 7 / 18