Skill UI

This guide provides expert principles for designing and auditing system-level experiments in computer architecture (e.g., for ASPLOS-level conferences). It details the proper usage of various instruments—from real silicon and FPGAs to cycle-level simulators and analytical models—ensuring that every claim is matched to a valid, stated error model. It emphasizes workload selection, establishing strong baselines, performing rigorous ablation studies, and honestly reporting measurement noise and limitations to maintain scientific credibility.

This guide outlines the rigorous methodology for ensuring that computational research results, especially those involving hardware architecture and simulation, are fully reproducible. It emphasizes pinning the entire result chain—from simulator commits and configuration files to workloads, sampling recipes, and statistics scripts—and mandates creating a manifest for every figure. Key practices include recording machine state for silicon runs and containerizing the environment to prevent data drift.

A comprehensive guide on achieving scientific reproducibility for complex computer architecture and system simulations. It details how to manage and pin all dependencies—including simulator commit hashes, local patches, workload binaries, hardware states, and post-processing scripts—to ensure that every reported figure and number can be accurately regenerated, regardless of time or environment changes.

This guide details the process of preparing complex research artifacts (simulators, configurations, traces, and scripts) for post-acceptance evaluation, especially for microarchitecture papers. It outlines best practices for achieving ACM badges like 'Available' and 'Reproducible,' focusing on structuring the code base with tiered entry points (smoke, key, full) and handling dependencies, licensed data, and simulation time constraints.

A comprehensive guide for microarchitecture researchers on achieving rigorous scientific reproducibility. It mandates tracking every critical artifact—including simulator commits, workload traces, power/area models, and RTL toolchains—and compiling them into a single run manifest, ensuring any reported result can be verified by a third party.