“regression”的搜索结果

The measurement surface for ALL Pulp DSP and audio-pipeline work — read it BEFORE writing or gating DSP, not only when something already sounds wrong. Covers the C++ harness (signal generators, metrics, assertions, RenderScenario, contracts), the offline Audio Doctor (magnitude/frequency response, THD/THD+N, phase/group delay), and their Python sibling the Audio Quality Lab (tools/audio/quality-lab — null residual + alignment, LTAS log-spectral distance, spectral flux/centroid, HNR, Theil-Sen drift slope, Kaiser-sinc resampling, license-guarded corpus, regression-net ratchet). TRIGGER on AUTHORING work — "build/design an oscillator/filter/synth/effect", "add a DSP module", "what should the acceptance gate be", "how do I measure aliasing / anti-aliasing / alias floor", "null against a reference", "is this DSP correct", "choose a tolerance", "golden/regression corpus for audio", "measure drift or jitter", "A/B two renders" — AND on DEBUGGING work — "is there sound / no audio / I hear nothing", "does this filter/compressor/synth/delay produce the right signal", "prove the DSP / prove the contract", "measure the frequency response", "what's the THD / is it distorting", "what's the group delay / phase response / measured latency", "magnitude response curve", "render a test tone and assert", "audio regression", "64-frame works but 128 is silent", "sample-rate change pitch-shifted it", "describe what's in this buffer", "audio doctor", "compare before/after a DSP refactor". Reach for this BEFORE hand-rolling any FFT, null test, alias measurement, pitch tracker, or golden-render script — most of it already exists in one of the two lanes. Test/tool layer over HeadlessHost — deterministic, no audio device, no speakers. Off the realtime thread entirely.

中文简介正在准备中。当前显示原文说明。

Set up, format, fix, and clean up LaTeX regression and estimation tables in empirical economics or finance papers. Use when (a) creating a .tex, results.tex, main.tex, or preamble to display regression or estimation output from Python (pyfixest), Stata, or R — including any mention of estout, esttab, estauto, estwide, or table fragments; (b) formatting or repairing estout-style regression tables that overflow the right margin, have cramped or boxed notes, misaligned columns, or poor significance stars, or when asked to match a reference paper, make the note fill the table width, or choose among \estwide, \estauto, and landscape layouts; (c) diagnosing "Misplaced \omit" errors from \input-ed table fragments inside tabular environments. Covers \@@input, \estwide, \estauto, \estautoLT, \specialcell, \sym, minipage notes below tabulars, and the convert-and-verify workflow. Do NOT trigger for general LaTeX documents like beamer presentations, problem sets, letters, or CVs.

中文简介正在准备中。当前显示原文说明。

Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.

中文简介正在准备中。当前显示原文说明。

Use when testing, evaluating, or building regression suites for Agentforce agents: conversation testing in Agent Builder, topic (now subagent) coverage and utterance testing, Testing API and AiEvaluationDefinition metadata, Agentforce DX CLI test runs (sf agent generate test-spec, sf agent test create/run/resume/results/list), evaluation metrics (containment rate, escalation rate, CSAT, topic activation accuracy), and post-deploy analytics via Enhanced Event Logs. Triggers: 'how do I test my Agentforce agent', 'agent routes to wrong subagent', 'write utterance tests', 'regression test after topic change', 'measure agent quality', 'agent containment rate', 'run agent tests from the CLI'. NOT for agent creation, topic design, or action contract design — use agentforce/agentforce-agent-creation, agentforce/agent-topic-design, or agentforce/agent-actions respectively.

中文简介正在准备中。当前显示原文说明。

Diagnose Yuzu bugs and performance regressions with a disciplined reproduce-minimize-hypothesize-instrument-fix-regression-test loop. Use when the user says `/diagnose`, "debug this", reports a failure, flake, broken behavior, or performance regression.

中文简介正在准备中。当前显示原文说明。

Check a change for performance regression against this machine's recorded baseline - decide whether the diff needs checking, run the deck benchmark under the hygiene wrapper, and attribute any regression to an element. Use before opening a PR that touches the simulation hot path.

中文简介正在准备中。当前显示原文说明。

Comprehensive regression model diagnostics and assumption checking. Use when validating regression models, checking assumptions (linearity, homoskedasticity, normality, independence), detecting outliers/influence, testing multicollinearity, or when user mentions residuals, heteroskedasticity, VIF, Cook's distance, or diagnostic plots.

中文简介正在准备中。当前显示原文说明。

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

中文简介正在准备中。当前显示原文说明。

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

中文简介正在准备中。当前显示原文说明。

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

中文简介正在准备中。当前显示原文说明。

Econometrics skill for Regression Discontinuity Design (RDD). Activates when the user asks about: "regression discontinuity", "RDD", "RD design", "sharp RDD", "fuzzy RDD", "running variable", "forcing variable", "cutoff", "bandwidth selection", "local linear regression", "McCrary test", "density test", "RDROBUST", "continuity assumption", "donut hole RDD", "geographic RDD", "断点回归", "回归不连续", "运行变量", "截断值", "带宽选择", "精确断点", "模糊断点", "密度检验", "局部线性回归"

中文简介正在准备中。当前显示原文说明。

Visual regression: production-level screenshots, diff thresholds, anti-flake. Use when implementing, reviewing or testing visual regression for React, Vite, Next.js or Perfect_AI projects.

中文简介正在准备中。当前显示原文说明。

Discover governing equations from data using PySR (evolutionary symbolic regression). Physics-constrained search with dimensional analysis, custom operators, and complexity-accuracy tradeoffs. Use when you need an interpretable equation, not a black-box model.

中文简介正在准备中。当前显示原文说明。

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

中文简介正在准备中。当前显示原文说明。

Implements visual regression testing with screenshot comparison, diff detection, and CI integration using Playwright or Chromatic. Use when users request "visual testing", "screenshot testing", "UI regression", "visual diff", or "Chromatic setup".

中文简介正在准备中。当前显示原文说明。

检查新旧测试实际保护的行为和可检测的缺陷，审视重复检查及对实现细节的依赖。删除前整理依据，保留必要验证，并清理仅供测试使用的代码。

• 判断新增测试是否必要
• 检查重复或依赖实现细节的测试
• 审视仅为测试公开的函数

盘点现有测试及缺口，将需求、业务规则和缺陷关联到稳定的测试编号与执行结果，通过测试台账追踪哪些行为已经验证、哪些仍需检查。

• 盘点现有测试及缺口
• 检查缺陷修复的回归保护
• 核查客户端与服务端的契约验证

在AI开发前定义成功条件，使用代码、规则、模型或人工评估新功能并检查既有功能是否正常，再记录多次尝试的可靠性指标与报告，用于比较提示词、代理或模型版本的变化。

• 在AI实现前确定成功条件
• 检查提示词或代理变更后的回归问题
• 通过多次尝试衡量可靠性

测量网页加载与交互、API响应以及构建和测试的耗时，对比修改前后的结果，并以通过Git共享的基准值检查性能是否下降。

• 比较代码修改前后的性能
• 调查页面缓慢的反馈
• 发布前检查性能目标

审查 Spec Kit 的代码差异和拉取请求，核对设计文档、预期与异常行为测试、缺陷修复的回归测试证据，以及仓库术语的一致性。

• 审查 Spec Kit 拉取请求
• 检查预期与异常行为的测试
• 核对缺陷修复的回归测试

通过代码、近期变更和复现步骤调查错误及异常行为的根本原因，验证假设后进行最小修复，并完成回归测试、结果核验和附有证据的调查报告。

• 调查错误和堆栈跟踪的原因
• 追踪近期变更引入的故障
• 记录修复验证与回归测试

使用真实浏览器测量网页加载时间、内容显示时间和资源传输量，保存性能基准，对比代码修改前后的结果，并查看长期趋势以发现性能下降。

• 保存修改前的性能基准
• 检查代码修改后的页面速度
• 调查耗时资源与大传输量

按复现、定位和最小化的顺序排查测试失败、构建错误及异常行为，修复根本原因，并添加回归测试以防止同类问题再次发生。

• 排查代码修改后的测试失败
• 调查构建错误的原因
• 排查停止工作的功能

调查并修复 Paperclip 中缓慢的 PostgreSQL 查询，在本地复现问题，比较修复前后的速度、结果和权限范围，并整理为通过测试、可供审查的拉取请求。

• 调查疑似由数据库引起的响应延迟
• 降低频繁执行的查询负载
• 比较修复前后的速度与结果