domains / families / research / icalp-reproducibility

icalp-reproducibility

separate

Use when making an ICALP (EATCS) theory result independently checkable — writing complete, self-contained proofs in the appendix and a full version (arXiv/ECCC/HAL), pinning any computational steps to reproducible certificates, and (optionally) formalizing key theorems in Coq/Lean/Isabelle, since ICALP has no runnable-artifact track and proof verifiability is the analogue of reproducibility.

When to use

• writing complete, self-contained proofs in the appendix
• creating a full version on arXiv/ECCC/HAL
• pinning computational steps to reproducible certificates
• formalizing key theorems in Coq/Lean/Isabelle
• ensuring proof verifiability for ICALP submissions

When not to use

• runnable-system artifacts
• Docker images of implementations
• benchmark harnesses
• providing proofs only upon request
• satisfying reproducibility with an arXiv link that defers hard steps

Skill page

Source