---
name: experiment-reporting
description: Mandatory for any request to report, review, summarize, compare, or check progress of machine-learning experiments, including phrases like "实验进度", "跑到哪", "结果如何", "结束了么", "预计多久", "baseline", "因子筛选", "训练队列", "test IC/UIC", "复盘". Always explain experiment purpose, design, results, conclusions, and next steps; never only list run names or short status.
metadata:
  short-description: Structured ML experiment reports
---

# Experiment Reporting

When the user asks for experiment progress, completed results, comparisons, expected finish time, queue status, or a research recap, this skill is mandatory.

Do not answer experiment-status questions with only "currently running X" or raw run names. Even a short progress answer must identify the research purpose, why the current run exists, what is queued next, and what conclusion can or cannot be drawn yet.

## Trigger Phrases

Use this skill for any user message containing or implying:

- `实验进度`, `目前进度`, `跑到哪`, `现在在跑什么`, `结束了么`, `出结果了么`
- `结果`, `汇报`, `复盘`, `总结`, `对比`, `baseline`, `test IC`, `test UIC`
- `因子筛选`, `selector`, `gate`, `shuffle`, `MLP`, `GRU`, `Transformer`
- `预计多久`, `什么时候跑完`, `队列`, `g03`, `g47`, `16-6`

## Required Report Shape

1. **Current State**
   - Say what is running now, what is queued next, and what has not started.
   - Include resource context if relevant: lane, GPUs, queue position, expected remaining time.
   - Explain what research question the currently running job belongs to.

2. **Experiment Map**
   - Group runs by research question, not by raw run name.
   - For each group, explain:
     - **Motivation**: why this experiment exists.
     - **Hypothesis**: what it is trying to verify.
     - **Design**: model, feature set, selector/gate/control, seed/repeat count, train/eval split, and metric.
     - **Result**: strict test metrics first; include mean, best, worst, and n where possible.
     - **Conclusion**: what the result implies.

3. **Progress Interpretation**
   - For a running queue, translate the current run into plain language.
   - Say whether it is a selector experiment, a baseline replay, a factor-set validation, or a model-family comparison.
   - Say what result is still missing before a firm conclusion can be made.

4. **Naming Translation**
   - If run names are shown, translate each important token into plain language.
   - Avoid presenting opaque names without explanation.

5. **Metric Discipline**
   - Use strict test metrics for conclusions unless explicitly discussing validation behavior.
   - Label validation metrics as validation; never let best-val be mistaken for test.
   - Prefer `test.global_uic` / strict test UIC for factor/model comparisons.
   - For factor-set quality comparisons after 2026-07-02, use the main weighted score
     `score = (MLP + 2 * Transformer + 2 * GRU) / 5` when all three model families
     are available. Linear is auxiliary unless the user explicitly requests it.
   - If GRU is not yet available and a temporary proxy is used for candidate generation,
     state that clearly and do not present the proxy as the final factor-set ranking.

6. **Logical Summary**
   - End with a ranked or grouped conclusion:
     - what worked,
     - what did not work,
     - what remains uncertain,
     - what should be run next.

## Visual Report Style

The user expects experiment reports to be visually scannable, not just plain
tables. Use explicit colored/status labels when the UI supports HTML/Markdown.
If color rendering is uncertain, keep the label text anyway.

Default labels:

- <span style="color:#16a34a;font-weight:700">[结论]</span> for confirmed, useful findings.
- <span style="color:#2563eb;font-weight:700">[进行中]</span> for currently running or incomplete queues.
- <span style="color:#d97706;font-weight:700">[待验证]</span> for plausible but not yet fully confirmed hypotheses.
- <span style="color:#dc2626;font-weight:700">[风险]</span> for failed, unstable, misleading, or leakage-risk results.
- <span style="color:#6b7280;font-weight:700">[证据]</span> for run names, counts, and metric details.

Every substantial report should start with a short "一句话总览" using these
labels, then a "研究地图" that groups experiments by question. For each group,
write in this order:

1. Why this group exists.
2. What hypothesis it tests.
3. What was actually run.
4. What strict test UIC/IC says.
5. What conclusion follows and what should be done next.

Do not make the user infer meaning from run names. Run names may appear only as
evidence after the plain-language explanation.

## Default Table Columns

For completed experiment groups, prefer:

| 实验组 | 目的/假设 | 具体做法 | n | 平均 test UIC | 最好 | 最差 | 结论 |

For queue/progress reports, prefer:

| 阶段 | 当前状态 | 内容 | 预计剩余 | 备注 |

## Minimum Progress Report

If the user only asks "进度怎么样", still include at least:

1. **现在在跑什么**: current run translated into plain language.
2. **为什么跑它**: the hypothesis or comparison it serves.
3. **已经完成什么**: completed result count or latest completed group.
4. **后面排什么**: queued experiments and their purpose.
5. **预计多久**: start/finish estimate when possible.
6. **当前结论边界**: what can and cannot be concluded yet.

## Style Rules

- Write in Chinese unless the user asks otherwise.
- Be explicit and concrete. The user should not need to remember old run names.
- Keep raw run names secondary; they are evidence, not the report itself.
- Never make raw run names the main report. Translate every important run name into purpose/design.
- When reporting progress, do not omit the research purpose just because no new results have finished.
- If results are incomplete, say exactly which part is complete and which is still pending.
- If a conclusion is weak because the sample size is small or seeds are incomplete, say that directly.
