PerCom Skills
A 12-skill depth pack for IEEE PerCom (International Conference on Pervasive Computing and Communications), the IEEE flagship for human-centric ubiquitous computing: routing among the ubicomp venues, the double-blind HotCRP submission on the IEEEtran 9+1 budget, the single-round rebuttal review with early rejection, activity-recognition and cross-subject evaluation of human-subjects sensing data,
Skills in this plugin
12- ▌ Percom Workflow · brycewang-stanfordUse when planning an IEEE PerCom project timeline from venue fit through paper registration, the September submission, the early-rejection gate, the bounded rebuttal, the IEEE Xplore camera-ready, and in-person presentation, with backward-planning offsets for a human-subjects sensing paper and honest handling of the single-annual-deadline cycle.
- ▌ Percom Submission · brycewang-stanfordUse when auditing an IEEE PerCom research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the IEEEtran 9+1 two-column page budget, double-blind anonymization, the open-data / human-subjects plan, IEEE Xplore publication, and desk-reject triage before the AoE cutoff.
- ▌ Percom Experiments · brycewang-stanfordUse when designing or auditing IEEE PerCom empirical evaluations, covering real human subjects, leave-one-subject-out / cross-subject evaluation, F1 and event-level metrics on imbalanced activity classes, deployment realism (free-living vs. lab), fair baselines, contamination-aware model ablations, and matching evidence to the shape of each pervasive-computing claim.
- ▌ Percom Camera Ready · brycewang-stanfordUse when preparing an accepted IEEE PerCom paper for its IEEE Xplore camera-ready, covering de-anonymization, the IEEEtran compsocconf template and page budget, IEEE Xplore metadata (PDF eXpress, eCopyright, ORCID, index terms), integrating reviewer-required changes without scope creep, permanentizing the dataset links, and IEEE production checks.
- ▌ Percom Related Work · brycewang-stanfordUse when positioning an IEEE PerCom submission against the pervasive/ubiquitous-computing literature across PerCom, ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, and IPSN, writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind, and handling concurrent, preprint, and prior-version overlap.
- ▌ Percom Supplementary · brycewang-stanfordUse when deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix, covering the tight IEEEtran 9+1 page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-blind supplementary material, and how to split a human-subjects sensing paper between body and dataset.
- ▌ Percom Writing Style · brycewang-stanfordUse when revising an IEEE PerCom paper for a pervasive-computing contribution on the first page, cross-subject claims stated precisely, a limitations section that argues rather than recites, evidence proportional to the claim, double-blind wording, and disciplined use of the tight IEEEtran 9-page budget.
- ▌ Percom Review Process · brycewang-stanfordUse when reasoning about how an IEEE PerCom research submission is evaluated, covering double-blind review, the three-TPC-member model, the early-rejection stage, the single-round bounded rebuttal gated by a "weak accept," the accept/reject decision, and how PerCom's process differs from ACM UbiComp/IMWUT's journal revise cycle.
- ▌ Percom Author Response · brycewang-stanfordUse when drafting an IEEE PerCom rebuttal after being invited following the initial reviews, covering the bounded single-round reply that answers explicit reviewer questions, corrects misreadings, points to evidence already in the paper without promising new experiments, and preserves double-blindness.
- ▌ Percom Reproducibility · brycewang-stanfordUse when strengthening IEEE PerCom reproducibility and open-data evidence for human-subjects sensing, covering the dataset-availability statement, de-identified datasets with IRB/consent handling, sensing provenance (devices, sampling, labeling), cross-subject reproducibility, honest degrees of reproducibility, and consistency between what the paper says and what the dataset contains.
- ▌ Percom Topic Selection · brycewang-stanfordUse when deciding whether a pervasive-computing project belongs at IEEE PerCom or should be routed to ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, or IPSN, and when distinguishing PerCom's human-centric ubicomp focus from networked-sensor-systems venues by contribution shape, the human-centricity test, and the IEEE-conference vs. IMWUT-journal model.
- ▌ Percom Artifact Evaluation · brycewang-stanfordUse when packaging an IEEE PerCom sensing artifact and dataset for reproducibility and any badging (IEEE Open Research Objects / Results Reproduced, IEEE DataPort or Zenodo deposit), covering what a ubicomp evaluator checks first for human-subjects sensing data, cross-subject reproduction, de-identification, and honest degrees of reproducibility.