icalp-artifact-evaluationUse 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
icalp-author-responseUse when writing an ICALP (EATCS) Track B rebuttal in response to initial reviews, or when handling a Track A correctness query — correcting reviewer misreadings of a proof, pointing to the exact lemma or step that answers an objection, conceding real gaps honestly, and staying within the lightweigh
icalp-camera-readyUse when preparing an accepted ICALP (EATCS) paper for the LIPIcs open-access camera-ready — converting to the lipics-v2021 document class, de-anonymizing (restoring authors, affiliations, ORCIDs, acknowledgements, and funding), completing LIPIcs metadata (ACM CCS, keywords, DOI cross-references), r
icalp-experimentsUse when matching the argument of an ICALP (EATCS) theory paper to its claim — choosing the proof strategy for an upper or lower bound, deciding when supporting computation (SAT/SMT-verified base cases, computer-assisted case analysis, exhaustive small-case checks) legitimately backs a theorem, and
icalp-related-workUse when writing the related-work and positioning of an ICALP (EATCS) theory paper — comparing against the best known bounds in the TCS literature, crediting the right prior venues (STOC/FOCS/SODA/LICS/CCC and TCS journals), stating the delta precisely, and keeping self-citations third-person under
icalp-reproducibilityUse 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 IC
icalp-review-processUse when reasoning about how an ICALP (EATCS) submission is evaluated, covering lightweight double-blind review, the separate Track A and Track B program committees, the asymmetric author interaction (Track B rebuttal vs Track A correctness-only contact), correctness-driven acceptance, the single ac
icalp-submissionUse when auditing an ICALP (EATCS) Track A or Track B submission for HotCRP readiness, covering the correct-track submission server, abstract registration before the full-paper deadline, the 15-page extended-abstract page budget with a clearly labelled appendix / full version, lightweight double-bli
icalp-supplementaryUse when splitting an ICALP (EATCS) theory paper between the 15-page main body and the clearly labelled appendix / full version — deciding what a referee must see in the body versus what may be deferred, ensuring every deferred proof is actually present and findable, and keeping the split consistent
icalp-topic-selectionUse when deciding whether a theoretical computer science result belongs at ICALP (EATCS) and, if so, whether it is a Track A (algorithms, complexity, games) or Track B (automata, logic, semantics, theory of programming) paper, and when distinguishing ICALP from the US theory venues STOC, FOCS, and S
icalp-workflowUse when planning an ICALP (EATCS) campaign backward from its single annual February deadline, through abstract registration, the anonymous submission, the Track B rebuttal window, the April notification, and the LIPIcs camera-ready and presentation, and when coordinating a full-version (arXiv/ECCC)
icalp-writing-styleUse when shaping the exposition of an ICALP (EATCS) theory paper — stating the model before the theorem, putting a legible theorem statement and its improvement over prior bounds on the first page, structuring the 15-page body around the argument while full proofs live in the appendix/full version,