Connect

ICALP Artifact Evaluation Guidance

brycewang-stanfordbybrycewang-stanford
•
1.1k
•
Learning & Documentation

Guides theoretical computer science researchers on ICALP submission norms regarding software artifacts, complete proofs, and computational certificates.

Designed for researchers transitioning from systems or machine learning venues to theoretical computer science conferences like ICALP (EATCS), this skill clarifies why ICALP does not feature an artifact evaluation track or badge system. It explains what replaces conventional software artifacts in pure theory submissions—specifically complete proofs in full versions, checkable computational certificates, and optional machine-checked formalizations (Coq, Lean, Isabelle)—ensuring authors do not waste time packaging unneeded Docker containers or misroute papers where software is the primary contribution.

Key Features

01Maps systems/ML artifact concepts (e.g., badges, capsules) to theoretical computer science equivalents
02Standardizes review outputs for proof completeness and anonymity-preserving code references
03Clarifies ICALP submission standards regarding the absence of artifact evaluation and badges
04Advises on proper handling of computational certificates and computer-assisted proofs
05Provides venue routing checks to identify when empirical software belongs in experimental tracks like ALENEX or ESA
061,079 GitHub stars

Use Cases

01Formatting computational certificates and supplementary proofs for ICALP submissions and full-version preprints
02Evaluating whether an implementation-heavy paper should be routed to ICALP or an experimental algorithms venue
03Transitioning from systems or ML venues to theoretical computer science conferences without building unnecessary artifact packages