OpenParable
Skip to content
← Back to skills

Infocom Artifact Evaluation

Development
infocom-artifact-evaluation

Infocom Artifact Evaluation is an Agent Skill for development published in the brycewang-stanford/Awesome-Journal-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when packaging IEEE INFOCOM code, simulators, and datasets for credibility and optional IEEE reproducibility badges, given that INFOCOM runs no standing artifact-evaluation track, covering DOI-issuing archives, evaluator-proof documentation, what the absence of a formal track changes, and how a released package strengthens a no-rebuttal submission.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/brycewang-stanford/Awesome-Journal-Skills/blob/HEAD/INFOCOM-Skills/skills/infocom-artifact-evaluation/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/infocom-artifact-evaluation, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

INFOCOM Artifact Evaluation

Use this when you want to release an artifact. The first thing to internalize: INFOCOM has no standing artifact-evaluation track and no mandatory badge process (as of 2026-07-09; 待核实 whether a cycle introduces one). Unlike SIGCOMM/NSDI/USENIX ATC — where a separate committee runs your artifact and awards badges — an INFOCOM artifact is entirely optional and self-directed. That changes the goal: you package not to pass an evaluator, but to make a large, skeptical, no-rebuttal reviewer pool believe your numbers.

What the absence of a formal track changes

At an artifact-track venue (SIGCOMM/NSDI/ATC)At INFOCOM
A committee runs your artifact on a deadlineNo one is required to run it
Badges (Available/Functional/Reproduced) are awardedNo INFOCOM badge exists (待核实 per cycle)
Packaging is a graded deliverablePackaging is a credibility investment you choose
The artifact can lift a borderline decisionA released package pre-empts "I don't believe this" in the PDF

Because no evaluator is guaranteed, the payoff of a release is reviewer trust and post-publication impact, not a badge. Optimize for a reader who might look, and for the researchers who will build on your simulator after publication.

IEEE reproducibility options you can opt into

  • IEEE DataPort — deposit datasets/traces with a DOI and a license.
  • DOI-issuing archives — Zenodo, figshare, or Software Heritage for a simulator or code release with a permanent identifier and an OSI-approved license.
  • Some IEEE venues offer code/data availability badges; INFOCOM does not mandate them — confirm the current cycle's specifics before claiming one (待核实).

What a credible networking release contains

Contribution typeFirst thing a reader checksCommon failure to avoid
An algorithm/protocolA README and one run command on a small exampleOnly-runs-on-authors'-cluster; undocumented deps
A simulation studyThe scripts that regenerate the paper's figures from logged runsNumbers in the PDF no script reproduces
A dataset/traceThe data plus its provenance and preprocessingQuery shipped, data missing; source unstated
A learning-for-networking resultCached inputs/outputs, model IDs, seedsRequires live API keys; not reproducible

Packaging plan (optional but persuasive)

[Container]   a Dockerfile or a pinned environment (requirements/lockfile) for the simulator/tool
[README]      one screen: what it is, how to install, how to run a small demo, how to regenerate
              each figure, expected runtime and outputs
[Mapping]     an explicit table: paper claim/figure -> script -> expected result
[Config]      the exact topology, traffic model, seeds, and parameters used in the paper
[Data]        the trace/dataset (or documented access), not just the generator
[License]     an OSI-approved license so others can build on it
[Archive]     deposit in a DOI-issuing repository (Zenodo/DataPort/Software Heritage)

Double-blind timing

  • At submission: if you link an artifact for reviewers, anonymize it — no owner strings, cluster paths, lab names, or identifying repo — and host it behind an anonymizing service. Nothing decision-critical may live only there (reviewers need not open it).
  • After acceptance: replace anonymized placeholders with the public, licensed, DOI-issuing archive, and make the camera-ready's statements match it.

Vignette: releasing a scheduling simulator + trace

A paper contributes an edge-scheduling algorithm evaluated by trace-driven simulation. A credible optional release: a Docker image with the custom simulator pre-built; a run_demo.sh that runs one small scenario in under a minute; a figures/ directory whose scripts regenerate each plot from logged runs; a claim-to-script table in the README; the request trace (or documented access) with its provenance; and an MIT/Apache license with a Zenodo DOI. State honestly which figures are turnkey and which need the full (slow) trace.

Calibration

  • There is no artifact deadline because there is no artifact track — do not invent one; the only related deadline is the IEEE Xplore camera-ready (infocom-camera-ready).
  • If a future cycle adds an artifact/badge process, confirm its rules, timing, and anonymity model on the current call before advising (待核实).

Output format

[Release decision] release / no release, with reason
[Target] credibility only / IEEE DataPort / DOI archive / (badge if a cycle offers one, 待核实)
[Contents] <simulator/tool + config + data + license>
[Ten-minute test] does install + demo succeed on a clean machine? yes/no
[Figure mapping] <figure -> script -> expected result present? yes/no>
[Anonymity] anonymized for review; de-anonymized DOI archive for camera-ready? yes/no