domains / families / research / dac-artifact-evaluation

dac-artifact-evaluation

separate

Use when packaging the code, benchmarks, and flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible, reusable artifact — given that DAC has historically run no formal artifact-evaluation or badge-issuing track (verify per cycle), so the goal is reviewer credibility and community reuse via open EDA flows and DOI-archived releases, not an ACM badge.

When to use

• Packaging EDA artifacts for DAC
• Creating reviewer credibility for QoR claims
• Preparing community-reusable open-source releases
• Designing clean-machine bounded-time tests
• Managing anonymized review artifacts
• Mapping paper claims to scripts and benchmarks

When not to use

• Chasing ACM artifact badges
• Assuming DAC has a standing badge-issuing track
• Building for software-engineering venue badges
• Building for computer-architecture venue badges

Skill page

Source