From ef359c8eeaf83102dcfe996f15afdbd943c6b6f2 Mon Sep 17 00:00:00 2001 From: Gahow Wang Date: Tue, 12 May 2026 21:40:19 +0800 Subject: [PATCH] Document profile-driven harness run --- .../profile-driven-harness-implementation-20260512.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/harness-ablation/profile-driven-harness-implementation-20260512.md b/docs/harness-ablation/profile-driven-harness-implementation-20260512.md index f85b9e4..12b886b 100644 --- a/docs/harness-ablation/profile-driven-harness-implementation-20260512.md +++ b/docs/harness-ablation/profile-driven-harness-implementation-20260512.md @@ -71,3 +71,13 @@ Run the same qwen3.5-27b chat 0-8k setup as the current ablation baseline: The no-harness min-prompt baseline is already available and only needs to be reused for comparison unless the setup changes. +## Experiment Started + +Started on `dash0` (`11.73.2.172`) at commit `17e9681`. + +- tmux session: `qwen27b-profileplanner-harness-20260512` +- spec: `.aituner-tight/specs/dash0-qwen27b-chat-0-8k-ttft4s-tpot25-gpu3skip-12iter-harness-profileplanner-20260512.json` +- study id: `dash0-qwen27b-chat-0-8k-ttft4s-tpot25-gpu3skip-12iter-harness-profileplanner-20260512` +- log: `.aituner-tight/logs/qwen27b-profileplanner-harness-20260512.log` +- status at launch check: `trial-0001` baseline is running under AITuner; no manual intervention in the tuning loop. +