dashboard
Route Plexe's dashboard and workdir inspection workflow.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- dashboard
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Route Plexe's dashboard and workdir inspection workflow.
- disable-model-invocation
- true
02 资源文件 2
- 参考文档references/dashboard-workflow.md2.6 KB
- 参考文档references/troubleshooting.md2.5 KB
03 SKILL.md 正文
dashboard
Use this sub-skill for Plexe's Streamlit dashboard and saved-run inspection workflow. It is the right route when the user wants to browse experiment history, checkpoints, search trees, evaluation reports, or packaged model files.
Typical triggers
- "Open the Plexe dashboard"
- "What does this workdir contain?"
- "Why isn't my saved run showing up?"
- "Inspect the checkpoints or model package for this experiment"
- "How does Plexe discover experiments in
workdir/?"
What belongs here
python -m plexe.viz --work-dir ...plexe.viz.mainplexe.utils.dashboard.app- experiment discovery and metadata extraction
- checkpoint and report loading
- dashboard tabs and model package presentation
- workdir structure assumptions for saved runs
What stays out
- Training, retraining, Spark setup, and packaging decisions belong in model-building.
- Repository maintenance and release automation stay outside this skill.
Read these references first when needed
references/dashboard-workflow.mdfor the launch command, environment variables, experiment discovery, tabs, and workdir layout.references/troubleshooting.mdfor missing workdirs, empty dashboards, malformed checkpoints, and dependency problems.../../scripts/inspect_workdir.pywhen you need a quick read-only summary without opening the Streamlit UI.
How to work this route
- Confirm the workdir path and whether the user wants the dashboard or a text summary.
- Check that the run has checkpoints and a packaged model before blaming the UI.
- Use the dashboard reference to map a question to the correct tab or file.
- Use the troubleshooting reference when the workdir is empty, corrupt, or incomplete.
What the dashboard expects
- Saved experiment directories grouped by dataset name and timestamp.
checkpoints/*.jsonfiles for phase progress and search state..build/reports/*.yamlfiles for generated reports.model/andmodel.tar.gzfor packaged model inspection.model/model.yamlplusschemas/andsrc/files for the package tab.
If those files are missing, the dashboard may still open but will show warnings or empty panes.
Common questions this route answers
- Which phase did the run reach?
- Why is a run marked failed, paused, or running?
- What did the best search node look like?
- Did the package get written and what files does it contain?
- Which saved runs exist for a given dataset?
Decision points
- If the path exists but no experiments appear, check the depth and naming convention first.
- If the run exists but a tab is empty, inspect whether the corresponding checkpoint or report file was written.
- If the package tab is missing fields, confirm the final packaging phase completed.
- If you only need a text summary, use the bundled workdir inspector instead of opening Streamlit.
Bundle ownership
This sub-skill owns the dashboard workflow reference and its troubleshooting notes. The root skill should only route here, not duplicate the tab-by-tab behavior.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).