Menu

Individual skill

icde-experiments

0upvotes

Use when designing or auditing IEEE ICDE experiments for a data-engineering paper: workload realism, tuned baselines, scale curves over single points, throughput and tail-latency with declared variance, mechanism-isolating ablations, cost/loss disclosure, and hardware reporting that satisfies a builder-heavy committee.

ICDE-Skills/skills/icde-experiments/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,413
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# ICDE Experiments

Use this before submission when the evaluation is not yet locked. At ICDE, the experiments are
where a systems paper is won or lost; a builder-heavy committee reads them adversarially.

## Experiment audit

- Map each performance claim to a **figure, table, or measured crossover** — no orphan claims.
- Run **tuned baselines**, not straw men. Document the tuning budget you gave each competitor;
  an untuned baseline is the single most common ICDE reject trigger.
- Prefer **curves over points**: show behavior across scale factors, data sizes, or contention
  levels, not one operating point where you happen to win.
- Report **throughput and tail latency with variance** — multiple runs, and captions that say
  whether bars are standard deviations, confidence intervals, or percentiles. A p99 that hides
Back to top