بنقرة واحدة
query-metrics-db
How to locate and query the deep-cuts pipeline metrics SQLite database
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
How to locate and query the deep-cuts pipeline metrics SQLite database
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | query-metrics-db |
| description | How to locate and query the deep-cuts pipeline metrics SQLite database |
The app maintains a second SQLite database — separate from the main library DB — that records pipeline performance metrics and system lifecycle events. All data stays on the local machine and is never transmitted.
~/Library/Logs/com.rlupi.deep-cuts/metrics.db
Store it in a shell variable to avoid retyping:
MDB="$HOME/Library/Logs/com.rlupi.deep-cuts/metrics.db"
pipeline_metricsOne row per analysis pass execution (success or failure).
| Column | Type | Description |
|---|---|---|
id | INTEGER | Auto-increment PK |
run_id | TEXT | Shared across all passes in a pipeline run (Unix ms timestamp as string) |
track_id | INTEGER | Track ID (no filenames stored) |
pass_name | TEXT | e.g. audio_analysis, clap, essentia, qwen, description_embed |
status | TEXT | success or failed |
duration_ms | INTEGER | Wall-clock time for just this pass on this track |
started_at | INTEGER | Unix timestamp in milliseconds |
ended_at | INTEGER | Unix timestamp in milliseconds |
audio_duration_sec | REAL | Track length in seconds (NULL if unavailable) |
error_message | TEXT | Error string on failure (NULL on success) |
system_eventsPipeline lifecycle events.
| Column | Type | Description |
|---|---|---|
id | INTEGER | Auto-increment PK |
event_type | TEXT | pipeline_start or pipeline_end |
details | TEXT | e.g. run_id=1780559866025 or run_id=... (nothing to do) |
duration_ms | INTEGER | Total pipeline wall-clock time (only on pipeline_end) |
created_at | TIMESTAMP | SQLite wall-clock (CURRENT_TIMESTAMP, UTC) |
sqlite3 "$MDB" ".headers on" ".mode column" \
"SELECT * FROM system_events ORDER BY id DESC LIMIT 20;"
sqlite3 "$MDB" ".headers on" ".mode column" "
SELECT pass_name, status,
COUNT(*) as cnt,
ROUND(AVG(duration_ms)/1000.0, 2) as avg_s,
ROUND(MIN(duration_ms)/1000.0, 2) as min_s,
ROUND(MAX(duration_ms)/1000.0, 2) as max_s
FROM pipeline_metrics
GROUP BY pass_name, status
ORDER BY pass_name, status;"
RUN_ID="1780560383909"
sqlite3 "$MDB" ".headers on" ".mode column" "
SELECT pass_name, track_id, status, duration_ms, audio_duration_sec
FROM pipeline_metrics
WHERE run_id = '$RUN_ID'
ORDER BY started_at;"
sqlite3 "$MDB" ".headers on" ".mode column" "
SELECT pass_name, track_id, error_message, datetime(started_at/1000, 'unixepoch') as started
FROM pipeline_metrics
WHERE status = 'failed'
ORDER BY id DESC LIMIT 20;"
sqlite3 "$MDB" ".headers on" ".mode column" "
SELECT pass_name,
ROUND(AVG(audio_duration_sec / (duration_ms / 1000.0)), 1) as avg_realtime_ratio
FROM pipeline_metrics
WHERE status = 'success' AND audio_duration_sec IS NOT NULL AND duration_ms > 0
GROUP BY pass_name;"
sqlite3 "$MDB" "DELETE FROM pipeline_metrics; DELETE FROM system_events;"
Experimental protocol for Deep Cuts research, prototypes, model evaluations, threshold tuning, ablations, metric comparisons, and claims about accuracy or quality. Use before running or interpreting experiments so bots preserve train/validation/test boundaries, avoid leakage, compare against baselines, and report results honestly.
Guidelines for creating, updating, reorganizing, and reviewing Deep Cuts documentation in the project wiki, including page taxonomy, lifecycle status, protected pages, proposal handling, and link verification.
Pattern for multi-agent collaboration sessions in the deep-cuts fam — forge-first coordination over the botfam substrate (Gitea issues/PRs as the coordination plane, the unified `botfam wait` wake loop, bare-actor worktrees), with IRC opt-in for design sprints, plus session-log conventions
Draft, structure, and finalize a Deep Cuts blog-series post so it conforms to the post template, house voice, and cross-post link rules. Use when writing, drafting, assembling, or editing a "Deep Cuts" blog post (the rlupi.com series), preparing a post for publishing, or adding front matter to one. Covers the template, front matter schema, voice, agent crediting, and the link linter.
Checklist and guide for adding a new analysis pass to the trait-based modular pipeline
Safe pattern for adding SQLite schema migrations in the deep-cuts Rust/rusqlite_migration stack