Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Recommend paper-backed diagnostics for PyTorch and Hugging Face training problems.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"traintools": {
"command": "uvx",
"args": [
"traintools",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add traintools -- uvx traintools mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"traintools": {
"command": "uvx",
"args": [
"traintools",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"traintools": {
"type": "stdio",
"command": "uvx",
"args": [
"traintools",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 AparajeetS 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.6.2)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Paper-backed ML training diagnostics for PyTorch. Small tools that answer practical questions while a run is still alive.
Have a real run or false alarm to share? Use the diagnostic report template.
pip install traintools
Not sure which tool fits the problem?
traintools recommend "my loss became NaN and gradients explode"
traintools integration gradient-health --framework pytorch
Agents can use the JSON CLI, the agent guide, llms.txt, or the optional local MCP server:
pip install "traintools[mcp]"
traintools-mcp
The same local, read-only server is discoverable through the official MCP Registry and can be launched without a persistent install:
uvx --with mcp traintools mcp
For AI coding assistants: start with traintools recommend " " --json, then insert the smallest diagnostic snippet into the user's existing loop. The agent-facing entrypoints are AGENTS.md, llms.txt, JSON schemas, and the optional MCP server.
| Tool | Question it answers |
|---|---|
| Gradient Noise Scale (GNS) | Is my batch size wasting compute? |
| GradientAccumulationGNS | Can I get GNS for free during gradient accumulation? |
| PlasticityProbe | Is my network losing the ability to learn? |
| TrainGuard | Should I stop training yet? |
| BatchInspector | Is this batch broken, imbalanced, or out of scale? |
| GradientHealthMonitor | Are gradients finite, clipped, vanished, exploded, or too large for the weights? |
| ExampleDynamicsTracker | Which examples are forgotten, hard, ambiguous, or likely mislabeled? |
| GradientConfusionMonitor | Are micro-batch gradients fighting each other and slowing SGD? |
| AUMTracker | Which examples look mislabeled by margin dynamics? |
| EL2NTracker | Which examples are important or pruneable early in training? |
| NeuralCollapseMonitor | Has the classifier entered neural-collapse geometry? |
from traintools import BatchInspector, GradientHealthMonitor
from traintools.callbacks.pytorch import TraintoolsTracker
tracker = TraintoolsTracker(model, loss_fn) batch_inspector = BatchInspector(expected_num_classes=10) grad_health = GradientHealthMonitor(max_grad_norm=1.0)
for step, (x, y) in enumerate(dataloader): batch_report = batch_inspector.inspect(x, y, step=step) if not batch_report.ok: print(batch_report)
loss = loss_fn(model(x), y) loss.backward()
grad_report = grad_health.inspect(model, step=step, lr=optimizer.param_groups0) if not grad_report.ok: print(grad_report)
optimizer.step() optimizer.zero_grad()
decision = tracker.step(step=step, inputs=x, targets=y, val_loss=val_loss) if decision and decision.should_stop: break
HuggingFace Trainer:
from transformers import Trainer
from traintools.callbacks.huggingface import TraintoolsCallback
trainer = Trainer(model=model, ..., callbacks=[TraintoolsCallback()])
GNS is the ratio of per-example gradient variance to gradient signal:
GNS = tr(Sigma) / ||G||^2
It estimates the critical batch size B*: the point where larger batches stop buying much more optimization progress.
GNS > B: under-batched, larger batches can helpGNS < B: over-batched, the batch may be larger than neededGNS ~= B: near the efficient frontiertraintools uses the unbiased estimators from McCandlish et al. 2018 (Bessel-corrected variance, bias-corrected signal) and tracks GNS as EMA(tr(Sigma)) / EMA(||G||^2).
[step 500] GNS=5010.7 (EMA) critical_batch=5011 current=64 regime=under-batched
Batch size 64 is ~78x below the critical batch (~5011). Larger batches would give cleaner gradients per step.
If you already use gradient accumulation, the per-micro-batch gradients you compute anyway are exactly the samples GNS needs.
from traintools import GradientAccumulationGNS
gns = GradientAccumulationGNS(model, micro_batch_size=B_micro)
for step in range(num_steps): for xm, ym in micro_batches: (loss_fn(model(xm), ym) / accum_steps).backward() gns.record_microbatch() optimizer.step() result = gns.compute(step=step) optimizer.zero_grad() gns.reset_accumulation()
PlasticityProbe measures activations directly:
Those are combined into a plasticity score in [0, 1].
[step 200] Plasticity Score: 0.706
All layers healthy.
TrainGuard fits a power-law or exponential curve to validation loss, bootstraps uncertainty, and only stops when continuing looks unlikely to matter.
[step 400] STOP
current loss: 0.6536 predicted final: 0.6119 expected improvement: 0.0417 (90% CI: [0.0012, 0.0821]) estimated plateau at step: 3200 reason: No improvement in 300 steps (best=0.6350 at step 93).
BatchInspector catches bad tensors and labels before they quietly poison a run.
from traintools import BatchInspector
inspector = BatchInspector(expected_num_classes=10, max_abs_value=1e4) report = inspector.inspect(inputs=x, targets=y, step=step) if not report.ok: print(report)
It checks for empty tensors, NaNs/infs, extreme scales, constant tensors, labels outside the expected class range, and severe batch imbalance.
GradientHealthMonitor is called after backward() and before optimizer.step().
from traintools import GradientHealthMonitor
monitor = GradientHealthMonitor(max_grad_norm=1.0) loss.backward() report = monitor.inspect(model, step=step, lr=optimizer.param_groups0) if not report.ok: print(report)
It reports global and per-layer gradient norms, non-finite gradients, likely vanishing/exploding gradients, clipping coefficient, and update-to-weight ratio.
ExampleDynamicsTracker implements two underused training-dynamics probes:
Use stable dataset ids, logits, and labels during a normal classification run.
from traintools import ExampleDynamicsTracker
dynamics = ExampleDynamicsTracker()
for step, (ids, x, y) in enumerate(dataloader): logits = model(x) loss = loss_fn(logits, y) dynamics.update(ids, logits, y, step=step) loss.backward() optimizer.step() optimizer.zero_grad()
print(dynamics.summary()) print("likely noisy or brittle:", [ex.example_id for ex in dynamics.most_forgotten(20)]) print("ambiguous:", [ex.example_id for ex in dynamics.cartography_region("ambiguous")])
A forgetting event is a transition from correct classification to incorrect classification for the same example. Repeatedly forgotten examples are often ambiguous, mislabeled, or distribution-edge cases. Unforgettable examples can be useful candidates for pruning or curriculum experiments.
GradientConfusionMonitor estimates whether micro-batch gradients are aligned or fighting each other, following the gradient-confusion idea from Sankararaman et al. 2019.
from traintools import GradientConfusionMonitor
confusion = GradientConfusionMonitor(n_splits=4) report = confusion.estimate(model, loss_fn, x, y, step=step) if not report.ok: print(report)
It reports mean/min/max pairwise gradient cosine, the fraction of negative gradient pairs, and a compact conflict score. High conflict can point to noisy labels, incompatible samples, depth/initialization issues, or a need for a different batching/curriculum strategy.
AUMTracker implements the Area Under the Margin statistic from Pleiss et al. 2020. For each example, it averages:
true_class_logit - max(other_class_logits)
Low-AUM examples are candidates for label audit or ambiguity review.
from traintools import AUMTracker
aum = AUMTracker(low_aum_threshold=0.0) for step, (ids, x, y) in enumerate(dataloader): logits = model(x) aum.update(ids, logits, y, step=step)
print([ex.example_id for ex in aum.lowest_aum(20)])
EL2NTracker implements the cheap example-importance score from Paul et al. 2021:
||softmax(logits) - one_hot(label)||_2
High EL2N examples tend to be important, hard, noisy, or distribution-edge examples. Low EL2N examples can be candidates for data-pruning experiments.
from traintools import EL2NTracker
el2n = EL2NTracker() el2n.update(ids, logits, y, step=step) important = el2n.highest(100) prune_candidates = el2n.lowest(100)
NeuralCollapseMonitor measures late-stage classifier geometry from Papyan, Han, and Donoho 2020:
from traintools import NeuralCollapseMonitor
collapse = NeuralCollapseMonitor() report = collapse.measure(features, labels, classifier_weight=model.fc.weight) print(report)
# Core: PyTorch only
pip install traintools
pip install traintools[full]
pip install traintools[hf]
pip install traintools[mcp]
pip install -e ".[dev]"
traintools is alpha software. The diagnostics are intentionally small and well-tested, but thresholds are heuristics and should be interpreted as training signals, not automatic truth. Bug reports, benchmark traces, and real-world failure cases are especially welcome.
Problem-oriented guides live in the documentation. Diagnostic objects can be written as versioned JSON with write_json_report.
只显示了开头部分;其余内容请在仓库中阅读