---
type: "post"
id: "nvidia-announced-nemotron-for-science-at-sc26-an-109935"
slug: "nvidia-announced-nemotron-for-science-at-sc26-an-109935"
title: "NVIDIA announced Nemotron for Science at SC26, an open stack for building scientific research agents."
description: "NVIDIA’s technical blog lays out a recipe for post-training Nemotron 3.5 Super VL on scientific tasks, using experimental records as verifiable feedback."
retrieval_nugget: "NVIDIA’s technical blog lays out a recipe for post-training Nemotron 3.5 Super VL on scientific tasks, using experimental records as verifiable feedback. For teams building specialized agents, the important idea is to make the desired scientific outcome—not fluent reasoning—the training signal, then evaluate whether adaptation improves performance."
published_at: "2026-11-17"
updated_at: "2026-11-17"
record_date: "2026-11-17"
date_kind: "published_at"
topics: ["claude"]
entities: ["NVIDIA","Nemotron 3.5 Super VL","Nemotron Litmus-Bench V2.0","NeMo Gym","NeMo RL","MetxBioDB","Claude Sonnet 5.5"]
related_patterns: ["scientific-agents-need-artifact-evidence"]
novelty_label: "new_fact"
what_changed: "NVIDIA now presents Nemotron for Science as an open research-agent stack, with scientific datasets, tools, and a post-training recipe that reports accuracy gains on drug-metabolism prediction."
prior_refs: []
source_url: "https://developer.nvidia.com/blog/post-training-nvidia-nemotron-to-increase-accuracy-in-your-scientific-domain"
source_urls: ["https://developer.nvidia.com/blog/post-training-nvidia-nemotron-to-increase-accuracy-in-your-scientific-domain"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:nvidia-announced-nemotron-for-science-at-sc26-an-109935"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/nvidia-announced-nemotron-for-science-at-sc26-an-109935/","markdown":"https://newruntime.com/posts/nvidia-announced-nemotron-for-science-at-sc26-an-109935.md","json":"https://newruntime.com/posts/nvidia-announced-nemotron-for-science-at-sc26-an-109935.json"}
markdown_url: "https://newruntime.com/posts/nvidia-announced-nemotron-for-science-at-sc26-an-109935.md"
---

# NVIDIA announced Nemotron for Science at SC26, an open stack for building scientific research agents.

## Retrieval answer

NVIDIA’s technical blog lays out a recipe for post-training Nemotron 3.5 Super VL on scientific tasks, using experimental records as verifiable feedback. For teams building specialized agents, the important idea is to make the desired scientific outcome—not fluent reasoning—the training signal, then evaluate whether adaptation improves performance.

## Summary
NVIDIA’s technical blog lays out a recipe for post-training Nemotron 3.5 Super VL on scientific tasks, using experimental records as verifiable feedback. For teams building specialized agents, the important idea is to make the desired scientific outcome—not fluent reasoning—the training signal, then evaluate whether adaptation improves performance.

## What happened
NVIDIA’s November 16, 2026 technical blog describes Nemotron for Science as a collection of models, datasets, tools, and recipes for scientific agent workloads. It identifies Nemotron 3.5 Super VL as an open, customizable multimodal model and Nemotron Litmus-Bench V2.0 as an open-source chemistry-reasoning dataset and benchmark focused on molecular properties. The article’s central contribution is a practical post-training walkthrough, not just a model announcement: it shows how to start with experimental records, build a task-specific reinforcement-learning environment, train against an automatic verifier, and measure results.

The worked example is drug-metabolism prediction. Given a parent compound and a metabolizing enzyme, the model predicts the resulting metabolite. The training records come from MetxBioDB, described as a database of experimentally confirmed biotransformation reactions. The blog converts records containing molecular structures, enzyme and reaction information, and measured outcomes into prompts paired with ground-truth answers. The model submits a predicted metabolite through a tool call; a verifier compares the predicted and reference molecular fingerprints using Tanimoto similarity, a score from zero to one. NVIDIA says the reward can be built from a simple sequence-similarity function or a more specialized tool such as cheminformatics software, molecular simulation, or a live autonomous lab. The intended reward should track the scientific outcome the team wants.

NVIDIA uses NeMo Gym to provide the environment infrastructure and NeMo RL for post-training. The described direct-training setup uses group relative policy optimization (GRPO) with low-rank adapters. The environment supplies an experimental input, the agent reasons and makes a tool submission, and the verifier returns a score without human preference labeling. In the drug-metabolism example, NVIDIA reports that supervised fine-tuning improved accuracy by 12%, and RL post-training added a further 17%, at a 16,384-token output budget. These are the blog’s reported results for its task and setup.

The article also presents distillation as an optional warm start when the base model needs a capability boost or RL convergence is slow. A teacher model generates reasoning traces against the same environment; NVIDIA’s example uses Claude Sonnet 5.5 and filters traces by Tanimoto score. At a threshold of at least 0.7, it retained 1,123 high-quality traces from 1,934 training prompts for a supervised fine-tuning corpus. The blog notes that a plausible-sounding trace is not necessarily good: the predicted answer must score against the ground truth. Its sample GRPO run uses four nodes with four GPUs each and up to 100 training steps, illustrating the substantial compute used in this recipe.

## What the archive adds
New Runtime’s earlier coverage on [Nemotron 3.5 Super VL](https://newruntime.com/posts/but-meta-isn-t-the-only-company-seeking-5bc9dc/) described an open multimodal model for specialized agent workflows. NVIDIA’s new article adds a concrete post-training method: experimental data becomes an automated verifier and reward loop for a scientific task. This is a new fact on a known Nemotron story, moving from model capability to a customization recipe.

## Trend signal
This supports [scientific agents need artifact evidence](https://newruntime.com/patterns/scientific-agents-need-artifact-evidence/). The recipe evaluates predicted metabolites against experimentally confirmed outcomes, and the training signal can be inspected as a similarity score rather than accepted on the strength of fluent reasoning. It is a useful example of tying scientific-agent claims to task artifacts. It does not establish that the resulting model’s outputs are reliable across other compounds, datasets, or scientific domains.

## Why it matters
Teams often have domain data but lack a clear path from records to agent improvement. This recipe offers a bridge: define a narrow task, represent experimental examples as prompts, expose a submission tool, and make a verifier score the output against the known result. That creates a loop that can train a model without collecting human preference rankings for every response.

The key design decision is the verifier, not the choice of a fashionable training algorithm. Tanimoto similarity is useful for molecular structure comparison, but another domain may require a simulator, a formal constraint checker, or a measured outcome. A reward that is easy to compute but weakly related to the real scientific objective can steer the model toward the wrong behavior. Teams should therefore validate that their scoring function corresponds to the result they actually care about and use held-out data to test whether fine-tuning generalizes. Distillation may help establish a starting policy, but it adds dependence on teacher quality and filtering choices. NVIDIA’s article makes these mechanisms explicit enough for a research engineering team to evaluate the approach against its own data and compute budget.

## Limits and uncertainty
NVIDIA reports the accuracy gains for its drug-metabolism setup, but those figures do not by themselves establish performance on other tasks, datasets, or scientific fields. The article’s results are company-reported; they have not been independently checked here. Similarity to a reference metabolite is the selected metric, and the blog’s recipe depends on the reward being a valid proxy for scientific usefulness. The walkthrough also demonstrates a multi-node, 16-GPU training run, so its operational cost may be material. How results transfer to a team’s own records, verifier, model configuration, and held-out data remains an empirical question.

## Skill to build now
Choose one narrow scientific prediction task with historical examples and known outcomes. This week, prototype a verifier that scores a model’s submitted answer against those outcomes, then inspect cases where the score disagrees with expert judgment. If the score is trustworthy, use a held-out split to compare the base model with a small fine-tuning run before investing in a larger RL pipeline. NVIDIA’s example makes the threshold explicit for distillation: a Tanimoto score of at least 0.7 selected traces for its SFT corpus, but each domain needs its own justified criterion.

## Reader takeaway
A scientific agent should be trained and judged against evidence that represents the task’s real outcome. NVIDIA’s recipe shows how experimental records can become an automated reward loop, while also making clear that a useful score and held-out evaluation are prerequisites—not details to add after training.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Claude](https://newruntime.com/topics/claude.md): Explore the claude topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)
