跳到主要内容
知仓学习社ZHICANG

mobicom-writing-style

Use when drafting or revising a MobiCom paper for house style — putting the wireless/mobile mechanism and its operating regime on the first page, pa…

不碰外部(只输出文字)无严重或高危命中brycewang-stanford/Awesome-Journal-Skills

它会碰到什么

扫了多少1 个文本文件,5 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

MobiCom Writing Style

A MobiCom paper reads as a mechanism justified by measurement. The first page states a

wireless or mobile-networking problem, the mechanism that addresses it, and the measured

evidence — before any implementation detail. The double-column 12-page body is for the core

argument; derivations, protocols, and extra results go to references and appendices.

The first-page arc

Put this in the abstract and first page, in order:

  1. The wireless/mobile pain — the concrete condition that breaks existing designs

(a fade under mobility, interference, a spectrum constraint, an energy limit).

  1. Why existing mechanisms fall short — each prior approach gets a specific, named

failure tied to the condition, not "prior work is limited."

  1. The mechanism — what is new, stated as a networking/PHY-MAC/routing/sensing

mechanism, with its operating regime named (distance, mobility, channel, power).

  1. The measured evidence — the headline result with its condition and its uncertainty,

not a bare "up to N×."

  1. Why it matters for mobile networking — the community-level payoff.

See [../../resources/worked-examples/01-introduction.md](../../resources/worked-examples/01-introduction.md)

for a before→after that executes this arc.

Name the operating regime

The single most common wireless-writing failure is a claim with an unstated envelope. Every

headline claim carries its regime:

| Vague | MobiCom-calibrated |

|---|---|

| "achieves high throughput" | "sustains X at 1-4 m NLOS under pedestrian mobility" |

| "low power" | "energy-per-bit within the harvested budget at Y% duty cycle" |

| "robust to interference" | "holds delivery above threshold at Z dB co-channel interference" |

| "works in real settings" | "measured over the air in a furnished room with walkers" |

A reviewer cannot fault — or reward — a claim whose conditions are hidden. Stating the

regime is not hedging; it is the claim.

Claims are paired with evidence

Every major claim maps to a proof, a figure, a measured condition, or a reproducibility

location. Build the map before submitting:

Claim -> evidence pairing (fill for each headline sentence):
  "decodable through fades"  -> Fig. 3 (delivery vs walker path) + channel traces
  "within energy budget"     -> Fig. 4 (energy-per-bit) + instrument note (App. B)
  "no dedicated carrier"     -> system description Sec. 3 + power measurement
An unpaired claim is either cut or demoted to future work.

Percentiles, not superlatives

  • Report distributions and confidence intervals, not single best runs or unqualified

maxima. "Up to N×" without the spread behind it is a review risk (mobicom-experiments).

  • Prefer the median and a tail over the mean alone when the metric is delivery or

latency; wireless distributions are skewed.

  • Avoid "significantly" as prose; show the interval and let it speak.

Fitting the double-column 12 pages

  • Figures and tables count against the 12; a radio-testbed diagram and three CDFs is

real page budget. Triage content, never geometry (mobicom-submission).

  • The body carries the mechanism and its headline evidence; channel-model derivations,

full protocols, extended sweeps, and instrument details go to **appendices after the

references**, outside the cap (mobicom-supplementary).

  • Keep the introduction's roadmap to one or two sentences; over-signposting substitutes for

argument.

  • Do not put the strongest result only in an appendix — reviewers should not reconstruct the

contribution from supplementary material.

Prose discipline

  • Lead sections with the finding, then the method — not a chronological lab diary.
  • Name the abstraction or mechanism once and use the name consistently.
  • Separate engineering effort from research contribution: building a testbed is

work, but the contribution is the mechanism it demonstrates.

Revision checklist

  • [ ] Mechanism and operating regime on the first page.
  • [ ] Each prior-work line has a specific, named failure.
  • [ ] Every headline claim paired to a figure, condition, or appendix.
  • [ ] Distributions/intervals replace superlatives throughout.
  • [ ] Figures/tables budgeted against the 12 double-column pages.
  • [ ] Strongest result in the body, not only the appendix.

Output format

[First page] mechanism + regime present? y/n — what is missing
[Regime] which headline claims lack a stated envelope
[Claim map] unpaired claims listed for cut-or-support
[Superlatives] flagged phrases -> distribution/interval replacement
[Page budget] over/under 12; what to move to appendix

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。