domains / families / research / pods-experiments

pods-experiments

separate

Use when designing or auditing the analytical "evidence" of an ACM PODS paper — worst-case and average-case analyses, matching upper and lower bounds, dichotomy completeness, correct complexity assumptions, and the occasional empirical validation when a theory paper claims practicality — matching the rigor to the shape of each theoretical claim.

When to use

• designing analytical evidence for PODS papers
• auditing worst-case and average-case analyses
• matching upper and lower bounds
• checking dichotomy completeness
• verifying complexity assumptions
• validating empirical claims of practicality

When not to use

• systems submissions
• using benchmarks to substitute for missing proofs

Skill page

Source