experiment-bridge

Execute research experiment plans through DSH background jobs with run tracking.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill experiment-bridge-nitrogen216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment-bridge
Source: https://github.com/Nitrogen216/awesome-dsh-mods/tree/main/modes/dsh-autoresearch/skills/experiment-bridge
Command: npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill experiment-bridge-nitrogen216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running machine learning experiments requires coordinating code changes, compute backends, run IDs, and result collection, and doing this manually leads to lost runs, duplicated IDs, and untraceable results. ## Core Features & Use Cases - Backend Detection and Sanity Checks: Detects the configured local CUDA, MPS, CPU, SSH, Vast.ai, or Modal backend and runs a bounded sanity command before any full training launch. - Attributable Run Management: Reserves stable run IDs from canonical state, launches training as DSH background jobs, and records both job ID and run ID for full traceability. - Result Collection and Routing: Collects terminal job results, recomputes declared metrics from raw outputs, appends factual records to research/RESULTS.jsonl, and hands evidence to experiment-run for routing. - Use Case: During a screening phase of an autonomous research project, use this Skill to implement the selected candidate, launch a seeded training run on the configured GPU backend, and route the completed comparison according to the precommitted decision rule. ## Quick Start Use the experiment-bridge skill to implement the current candidate and launch the planned screening run as a background job on the configured backend.

Frequently Asked Questions about experiment-bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run ML training experiments as background jobs?▼

Launch long training work with the DSH bash tool using run_in_background set to true, then record the returned job ID beside the scientific run ID. Completion notices wake the session so you never need to busy-poll for results.

How do I track experiment run IDs across training runs?▼

Reserve the run ID from canonical state with transition_guard.py reserve-run immediately before launch, then use that ID in the config, log name, raw output path, and RESULTS.jsonl record. Never invent IDs or compute hashes separately.

Which compute backends does experiment-bridge support?▼

It supports local CUDA, MPS, or CPU devices, explicit SSH hosts with remote working directories, and Vast.ai or Modal when the project supplies that configuration and the required CLI is available. It never silently switches backends.

What happens when a training run fails before producing results?▼

Infrastructure failure before a scientific result keeps the same candidate and decision rule, and the failure is diagnosed from its primary log. An unchanged deterministic failure is never blindly rerun, and a valid negative result never triggers an automatic Oracle call.

Can I run multiple experiment candidates at the same time?▼

Only one active candidate runs at a time, but seeds or fixed confirmation replicas for that candidate may run concurrently when the plan and available devices permit it. Mixing candidate mechanisms in one launch wave is not allowed.