domains / families / research / icalp-artifact-evaluation

icalp-artifact-evaluation

separate

Use to understand why ICALP (EATCS) has no artifact-evaluation track or badge scheme, and what plays the equivalent role for a pure-theory paper — the full version with complete proofs, reproducible computational certificates, and optional machine formalization — so authors coming from a systems/ML venue do not waste effort building an artifact ICALP does not evaluate.

When to use

• understanding why ICALP has no artifact-evaluation track
• identifying what plays the equivalent role of an artifact for ICALP
• guiding authors from systems or ML venues on ICALP submission requirements
• determining if software is the actual contribution requiring venue reconsideration

When not to use

• building an artifact-evaluation package for ICALP
• importing ACM/IEEE badge language into the paper
• importing ML reproducibility-checklist artifacts into the paper

Skill page

Source