domains / families / research / eurosys-reproducibility

eurosys-reproducibility

separate

Use when hardening the reproducibility story of a EuroSys paper — recording hardware and software provenance for every number, taming performance variance with repeated runs and dispersion reporting, versioning workloads and traces, and writing an availability statement that survives both double-blind review and the sysartifacts AEC.

When to use

• recording hardware and software provenance
• taming performance variance with repeated runs
• versioning workloads and traces
• writing availability statements for double-blind review
• preparing for sysartifacts AEC
• automating figure regeneration
• handling restricted evidence with synthetic substitutes
• running pre-deadline reproducibility drills

When not to use

• retrofitting reproducibility in deadline week

Skill page

Source