dac-artifact-evaluation
Installation
SKILL.md
DAC Artifact Evaluation
Read the venue reality first. Unlike the software-engineering venues (FSE/ICSE/ISSTA) and the
computer-architecture venues (MICRO/ISCA/HPCA), DAC has historically not operated a standing,
badge-issuing artifact-evaluation track for research manuscripts; whether the current cycle adds
one is 待核实 (resources/official-source-map.md). So do not build for an ACM badge that DAC
does not award. Build instead for the two things that actually matter at DAC: making a skeptical
reviewer trust your QoR numbers and making the community able to reuse and cite your work.
What an EDA artifact is for at DAC
| Goal | What it buys you | How it is earned |
|---|---|---|
| Reviewer credibility | A QoR claim that reads as real, not cherry-picked | Standard benchmarks, disclosed flow, a runnable path |
| Community reuse | Citations and follow-on work built on your tool | Clean open-source release, good docs, a license |
| Contest/leaderboard standing | Recognition on ISPD/TAU/CAD-contest tasks | A tool that runs on the contest harness |
There is no badge to chase, so the design target is a package a stranger can run and a reviewer would believe — not a checklist an evaluator scores.