gt3-backside-route-policy

Étoiles8

Forks3

Mis à jour8 mars 2026 à 03:05

Apply and validate GT3 backside routing policy in Innovus. Use when configuring CTS/PDN/signal layer usage, submitting GT3 consistency runs, diagnosing zero-backside-nets, or enforcing BPR-reserved-for-PDN constraints.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

Mr-Fang-VLSI

Mr-Fang-VLSI/EDAgent

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

5 fichiers

SKILL.md

readonly

name	gt3-backside-route-policy
description	Apply and validate GT3 backside routing policy in Innovus. Use when configuring CTS/PDN/signal layer usage, submitting GT3 consistency runs, diagnosing zero-backside-nets, or enforcing BPR-reserved-for-PDN constraints.

GT3 Backside Route Policy

Apply this policy for GT3 experiments unless the task brief explicitly overrides it.

Policy defaults

Keep CTS route on M4/M5.
Keep PDN on high layers (BSPDN_HI => M6/M7).
Reserve BPR for PDN.
Allow backside signal routing on BM2/BM1 only (index 1..2).
Treat BM2 -> BM1 -> M0 -> M1 as the current working signal-entry hypothesis until disproved by a topology-validity gate.
Do not assume direct BM1 -> M1 connectivity without explicit tool or techlef evidence.

Submit controlled run

ROOT=/mnt/research/Hu_Jiang/Students/Fang_Donghao/TAMU-ASAP07-BSPDN-BPR-V0.00
cd "$ROOT"

TASK_BRIEF=<task_brief_md> \
BACKSIDE_SIGNAL_NET_FILE=<net_list_txt> \
BACKSIDE_SIGNAL_NET_BOTTOM_INDEX=1 \
BACKSIDE_SIGNAL_NET_TOP_INDEX=2 \
bash scripts/debug/submit_gt3_route_rc_consistency.sh <design> <run_tag>

Monitor outputs:

slurm_logs/04_delay_modeling/<run_tag>.monitor.md
slurm_logs/04_delay_modeling/<run_tag>.monitor.history.tsv

Post-run checks

Verify backside signal occupancy appears on BM layers.
Verify signal occupancy does not use BPR.
Verify CTS remains on M4/M5 window.
Verify the run does not rely on an unproven shortcut such as direct BM1-M1.

Load references/policy_checks.md for quick command snippets.

Plus depuis ce dépôt

même dépôt

academic-presentation-crafter

Mr-Fang-VLSI/EDAgent

Creates and refines academic presentations from research papers. Use this skill for tasks involving the conversion of scientific or technical documents into slide decks for conferences, seminars, lectures, thesis defenses, or academic reviews. Supports beamer LaTeX (.tex), PowerPoint (.pptx), and Markdown output formats.

2026-04-288

delay-model-gate-evaluator

Mr-Fang-VLSI/EDAgent

Execute delay-model validation gates against HPWL baselines. Use when evaluating model consistency, running Gate-0 contract checks, building Gate-1 bucketed scorecards, performing wirelength-aware correlation checks, or deciding readiness for active optimization.

2026-04-288

workflow-research-chain

Mr-Fang-VLSI/EDAgent

Run a full EDA research chain from knowledge exploration and paper triage to idea debate, hypothesis experiment design, implementation, git versioning, validation, and retrospective. Use when the user requests an end-to-end EDA research workflow rather than a single isolated execution step.

2026-04-288

academic-writing-quality-assessor

Mr-Fang-VLSI/EDAgent

Audit and refine academic manuscripts for structure, terminology consistency, LaTeX hygiene, and high-signal grammar fixes. Use this skill for theses, papers, proposals, and technical reports when the task is manuscript writing rather than experiment execution.

2026-03-278

backside-routing-realization-specialist

Mr-Fang-VLSI/EDAgent

Diagnose and implement backside-routing realization paths, including targeted reroute, local DEF/OpenDB patching, and OpenROAD-backed net-level rerouter bring-up, when theory predicts benefit but the current flow does not realize BM2/BM1 usage.

2026-03-088

bspdn-physical-contract-auditor

Mr-Fang-VLSI/EDAgent

Audit whether the local BSPDN physical contract is coherent across paper assumptions, GT3 tech collateral, layer/via topology, and current flow policy before promotion or expensive attribution experiments.

2026-03-088

name	gt3-backside-route-policy
description	Apply and validate GT3 backside routing policy in Innovus. Use when configuring CTS/PDN/signal layer usage, submitting GT3 consistency runs, diagnosing zero-backside-nets, or enforcing BPR-reserved-for-PDN constraints.

GT3 Backside Route Policy

Apply this policy for GT3 experiments unless the task brief explicitly overrides it.

Policy defaults

Keep CTS route on M4/M5.
Keep PDN on high layers (BSPDN_HI => M6/M7).
Reserve BPR for PDN.
Allow backside signal routing on BM2/BM1 only (index 1..2).
Treat BM2 -> BM1 -> M0 -> M1 as the current working signal-entry hypothesis until disproved by a topology-validity gate.
Do not assume direct BM1 -> M1 connectivity without explicit tool or techlef evidence.

Submit controlled run

ROOT=/mnt/research/Hu_Jiang/Students/Fang_Donghao/TAMU-ASAP07-BSPDN-BPR-V0.00
cd "$ROOT"

TASK_BRIEF=<task_brief_md> \
BACKSIDE_SIGNAL_NET_FILE=<net_list_txt> \
BACKSIDE_SIGNAL_NET_BOTTOM_INDEX=1 \
BACKSIDE_SIGNAL_NET_TOP_INDEX=2 \
bash scripts/debug/submit_gt3_route_rc_consistency.sh <design> <run_tag>

Monitor outputs:

slurm_logs/04_delay_modeling/<run_tag>.monitor.md
slurm_logs/04_delay_modeling/<run_tag>.monitor.history.tsv

Post-run checks

Verify backside signal occupancy appears on BM layers.
Verify signal occupancy does not use BPR.
Verify CTS remains on M4/M5 window.
Verify the run does not rely on an unproven shortcut such as direct BM1-M1.

Load references/policy_checks.md for quick command snippets.