domains / families / documents / wacv-artifact-evaluation

wacv-artifact-evaluation

separate

Use when packaging code, data, and models for a WACV paper, covering the anonymous review artifact versus the public post-acceptance release, reproducing constraint-based applications claims (latency, power, robustness) not just accuracy, dataset licensing and release, and keeping the artifact in sync across the two-round Revise-and-Resubmit lap.

When to use

• packaging code, data, and models for a WACV paper
• creating anonymous review artifact
• creating public post-acceptance release
• reproducing constraint-based applications claims
• dataset licensing and release
• keeping artifact in sync across two-round Revise-and-Resubmit

When not to use

• shipping review artifact with link to named GitHub repo
• shipping review artifact with project page
• reproducing only accuracy number without systems result
• deferring license decision to the last day

Skill page

Source