← all publishers

brycewang-stanford

@brycewang-stanford source repo

Report this profile Claim this profile

• 5.3k skills
• 0 followers
• 1k repo stars
• 2 weeks ago last updated

1. ▌
   Cre Heterogeneity · brycewang-stanford

   Use when designing or writing heterogeneity analysis for a 《中国农村经济》 manuscript. Enforces rural-relevant cut dimensions and theoretical-justification discipline.
   1k repo stars
2. ▌
   Csj Workflow · brycewang-stanford

   在需要《计算机科学》(Computer Science, JSJKX) 从选题到见刊的全流程时间线与技能编排时调用。本刊是计算机全学科中文综合月刊(CCF 会刊、B 类、T2 级)，单盲审稿、期刊式多轮修回，见刊周期约 13 个月(待核实)。技能把 12 个 csj-* 技能串成一条端到端流水线：选题定位→写作体例→相关工作→实验→可复现/补充/可用性→投稿→审稿→修回→定稿，标明每阶段产出、依赖顺序与关口检查。适用于统筹整段投稿旅程、决定下一步该调用哪个技能的场景。
   1k repo stars
3. ▌
   CI Theory And Method · brycewang-stanford

   Use to choose and deploy the theoretical framework and critical method of a Critical Inquiry (CI) essay so theory does real analytic work on objects. CI is a leading theory journal across the humanities; this skill helps select a lens (hermeneutic, deconstructive, psychoanalytic, materialist, postcolonial, media-theoretical, etc.), use concepts precisely, and avoid jargon-as-decoration. It guides theoretical craft; it does not invent sources.
   1k repo stars
4. ▌
   Ecta Replication Package · brycewang-stanford

   Use when assembling the code and data deposit for an Econometrica manuscript under the journal's Data and Code Availability Policy, including reproducible Monte Carlo and (for empirical work) data provenance. Builds and audits the replication package; it does not design the simulations (use ecta-robustness) or format exhibits (use ecta-tables-figures).
   1k repo stars
5. ▌
   Ecopol Identification · brycewang-stanford

   Use when the identification argument is the bottleneck for an Economic Policy (EP) manuscript — causal identification of a policy effect, or parameter identification in a quantitative policy model. Stress-tests it to the EP bar (credible to an academic discussant, legible to a policy discussant) before exhibits are finalized.
   1k repo stars
6. ▌
   Ecopol Tables Figures · brycewang-stanford

   Use when an Economic Policy (EP) manuscript's exhibits are too technical for a policy reader or do not carry the policy message. Redesigns tables and figures for the EP dual audience; it does not invent evidence or citations.
   1k repo stars
7. ▌
   Er Abstract · brycewang-stanford

   Use when drafting or revising the 中文内容提要 (~300 字, official) or English 梗概/Summary for an 《经济研究》 manuscript. Enforces the five-sentence Chinese pattern, the five-element English Summary, and forbids empty-significance phrases. 本技能服务于《经济研究》(Economic Research Journal, ERJ)。
   1k repo stars
8. ▌
   Er Rebuttal · brycewang-stanford

   Use when responding to reviewer and editorial-board reports for an 《经济研究》 (Economic Research Journal) R&R — sequencing manuscript revision before letter writing, drafting point-by-point replies in the accept / partial-accept / decline modes, prioritizing 编委 theory-positioning comments, and deciding whether new results go in the body or an appendix. 使用时机：收到《经济研究》外审或编委意见、准备修订正文并撰写逐条回复信、或多轮修改中回复与正文出现不一致时。
   1k repo stars
9. ▌
   Er Workflow · brycewang-stanford

   Use when deciding which er-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for 《经济研究》 (Economic Research Journal). Routes — does not replace — the specialized skills.
   1k repo stars
10. ▌
    Optica · brycewang-stanford

    Use when targeting Optica or deciding whether an optics-and-photonics manuscript fits this venue. Encodes the journal's fit, the high-impact concise-advance bar, measurement and characterization rigor, house style, the Optica-vs-specialty-journal routing, official-submission re-check, and desk-reject heuristics.
    1k repo stars
11. ▌
    Matter · brycewang-stanford

    Use when targeting Matter (Matter) or deciding whether a materials manuscript fits this Cell Press primary-research venue spanning atoms to systems with societal relevance. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
    1k repo stars
12. ▌
    Nature · brycewang-stanford

    Use when targeting Nature or deciding whether a manuscript fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
    1k repo stars
13. ▌
    Neuron · brycewang-stanford

    Use when targeting Neuron or deciding whether a neuroscience manuscript fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
    1k repo stars
14. ▌
    Eer Rebuttal · brycewang-stanford

    Use when a European Economic Review (EER) decision letter arrives (R&R or reject-with-appeal grounds) and a response strategy and letter are needed. Plans the revision and drafts the point-by-point response; it does not run new estimation or rewrite the whole paper.
    1k repo stars
15. ▌
    Eer Workflow · brycewang-stanford

    Use when deciding which eer-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a European Economic Review (EER) submission. Routes — it does not replace — the specialized skills.
    1k repo stars
16. ▌
    Fcr Cover Letter · brycewang-stanford

    Use when writing the cover letter for a Field Crops Research (FCR) submission to the Editors-in-Chief. The letter must establish scope fit (field-based, multi-season/-environment, a field crop, generally significant), state the novel contribution and article type, and confirm originality and data availability. Drafts the letter; it does not contact editors or invent claims.
    1k repo stars
17. ▌
    Cte Style · brycewang-stanford

    Use when polishing the language and rhetoric of a 《财贸经济》 manuscript — eliminating empty-significance phrases, fixing the "加强完善推进" policy formula, replacing method-flexing with identifiable mechanism, and aligning tense / person / hedging with CSSCI house style. 本技能服务于《财贸经济》(Finance & Trade Economics, CTE)。
    1k repo stars
18. ▌
    Humrel Review Process · brycewang-stanford

    Use when calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen, double-anonymous developmental review, decision types, timelines, and when a sibling journal is the better route. Sets expectations; it does not draft the rebuttal (see humrel-rebuttal).
    1k repo stars
19. ▌
    Humrel Tables Figures · brycewang-stanford

    Use when building and auditing the exhibits for a Human Relations (HR) manuscript — qualitative data-structure and evidence tables, process models, and quantitative tables/figures. Improves the exhibits; it does not change the analysis or theory.
    1k repo stars
20. ▌
    Hrm Methods · brycewang-stanford

    Use when the research design is the bottleneck for a Human Resource Management (Wiley "HRM") manuscript — matching multilevel structure, multi-source/multi-wave timing, construct validity, and common-method-bias defenses to the theoretical claim. Designs the study; it does not run the estimation (hrm-data-analysis).
    1k repo stars
21. ▌
    Interspeech Supplementary · brycewang-stanford

    Use when deciding what accompanies an INTERSPEECH paper beyond its 4 pages — audio sample pages and multimedia for listening-based judgment, what reviewers may ignore versus must see, the references-and-acknowledgments page's strict scope, and packaging extra analyses when no reviewed appendix exists.
    1k repo stars
22. ▌
    Interspeech Writing Style · brycewang-stanford

    Use when writing or compressing an INTERSPEECH paper into its 4 content pages — the abstract-and-index-terms opening, task-first framing for a mixed science/engineering readership, table and figure economy, protocol one-liners that preserve rigor under compression, and the cuts that shrink pages without shrinking claims.
    1k repo stars
23. ▌
    Joc Rebuttal · brycewang-stanford

    Use when revising a Journal of Communication (JoC) manuscript after a revise-and-resubmit. The hard problem at JoC is that communication is a multi-paradigm field, so a single R&R can carry post-positivist, interpretive, critical, and computational reviewers who want incompatible things — inside a fixed 35-page cap. Plans the revision and response memo; it does not fabricate new results.
    1k repo stars
24. ▌
    Joc Workflow · brycewang-stanford

    Use as the entry point for any Journal of Communication (JoC) manuscript. Routes to the right JoC sub-skill based on where you are in the lifecycle and which format (original research article, JoC Forum, special issue) fits. It dispatches; it does not draft content.
    1k repo stars
25. ▌
    Jf Topic Selection · brycewang-stanford

    Use when judging whether a research question is general-interest and economically significant enough for The Journal of Finance (JF), and when sharpening the framing. Tests fit and contribution; it does not design the empirics.
    1k repo stars
26. ▌
    Icassp Review Process · brycewang-stanford

    Use when reasoning about ICASSP peer review — the IEEE Signal Processing Society technical-committee pipeline, EDICS-based assignment, single-blind reviewing, the recently added short rebuttal, oral-versus-poster allocation, the roughly-even acceptance rate, and how a signal-processing decision is actually made and should be decoded.
    1k repo stars
27. ▌
    Ieeesp Supplementary · brycewang-stanford

    Use when deciding what goes in an IEEE S&P (Oakland) paper's appendix versus the 13-page body, including the 5-page references-and-appendices allowance, the rule that reviewers need not read appendices, marking requirements past page 13, and what must never be relegated out of the reviewed body.
    1k repo stars
28. ▌
    Ieeesp Writing Style · brycewang-stanford

    Use when writing or revising an IEEE S&P (Oakland) paper's prose, including the threat-model-first structure, calibrating security claims to evaluated boundaries, the first-round survival test for introductions, SoK voice, and fitting the argument into 13 compsoc pages.
    1k repo stars
29. ▌
    Infocom Camera Ready · brycewang-stanford

    Use when preparing an accepted IEEE INFOCOM paper for its IEEE Xplore camera-ready, covering de-anonymization, the IEEEtran final format and page budget, the IEEE electronic Copyright Form (eCF), PDF eXpress validation, the author-registration requirement, integrating reviewer-required changes without scope creep, and permanentizing any released artifact links.
    1k repo stars
30. ▌
    Infocom Related Work · brycewang-stanford

    Use when positioning an IEEE INFOCOM submission against the networking literature across INFOCOM, SIGCOMM, NSDI, MobiCom, ICNP, and the journals (IEEE/ACM ToN, IEEE JSAC/TMC), writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind on EDAS, and handling concurrent, preprint, and prior-version overlap.
    1k repo stars
31. ▌
    Lancet Figures Tables · brycewang-stanford

    Use to build and check The Lancet's clinical display items — the Table 1 baseline characteristics, Kaplan–Meier curves with numbers at risk, forest plots for subgroups/meta-analyses, the CONSORT/study-flow diagram, and maps for multi-country studies — all with confidence intervals shown.
    1k repo stars
32. ▌
    Mind Citation And Style · brycewang-stanford

    Use when formatting references and applying the MIND house style to a Mind article. Mind provides a MIND Stylesheet and requires accepted papers to be prepared in its house style; line numbering is required for review. Handles citation mechanics and formatting; it does not write the argument.
    1k repo stars
33. ▌
    Mobicom Camera Ready · brycewang-stanford

    Use when preparing an accepted MobiCom paper for publication — de-anonymizing into the double-column final version, discharging every rebuttal and revision promise, completing ACM rights and metadata, coordinating the artifact-badge timeline, and planning the in-person presentation for the Austin program.
    1k repo stars
34. ▌
    Mobicom Related Work · brycewang-stanford

    Use when building or auditing the related-work of a MobiCom paper — sweeping the SIGMOBILE and networking literature lanes, proving each citation's venue on dblp/ACM DL against the INFOCOM/SIGCOMM/NSDI misattribution traps, positioning against the current rolling-cohort cohort, and self-citing without breaking double-blind.
    1k repo stars
35. ▌
    Mobisys Camera Ready · brycewang-stanford

    Use when preparing an accepted MobiSys paper for the ACM Digital Library camera-ready — de-anonymization, the ACM double-column final layout and 12-page budget, ACM rights and CCS metadata, delivering any results promised in the rebuttal, coordinating the three artifact badges, registration, and the June in-person talk and demo in Cambridge.
    1k repo stars
36. ▌
    Mobisys Related Work · brycewang-stanford

    Use when positioning a MobiSys submission against the mobile-systems literature — offload, on-device ML, mobile OS and runtimes, sensing services, and energy — covering the right lanes, handling concurrent work, verifying that cited "MobiSys papers" are MobiSys rather than MobiCom/SenSys/OSDI, and self-citing without breaking double-blind.
    1k repo stars
37. ▌
    Neurips Camera Ready · brycewang-stanford

    Use when preparing accepted NeurIPS papers for camera-ready upload, de-anonymization, final checklist, code/data release, OpenReview metadata, and post-acceptance obligations.
    1k repo stars
38. ▌
    Neurips Related Work · brycewang-stanford

    Use when positioning a NeurIPS submission against current-cycle ML literature, contemporaneous work, preprints, neighboring conferences, and the exact technical delta from prior methods.
    1k repo stars
39. ▌
    Oopsla Review Process · brycewang-stanford

    Use when explaining or strategizing around OOPSLA's two-round review machinery — double-anonymous multi-stage reviewing, the four outcomes (Accept, Minor Revision, Major Revision, Reject), reviewer continuity across rounds, round-hopping a Major Revision, and how acceptance flows into a PACMPL issue and the SPLASH talk.
    1k repo stars
40. ▌
    Percom Review Process · brycewang-stanford

    Use 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.
    1k repo stars
41. ▌
    Pmla Citation And Style · brycewang-stanford

    Use when formatting a PMLA (Publications of the Modern Language Association) essay in MLA style — in-text parenthetical citations keyed to a Works Cited list built from the MLA Handbook's template of core elements, plus quotation, translation, and discursive-note conventions. PMLA requires the most recent MLA Handbook. Handles citation mechanics; it does not write the argument.
    1k repo stars
42. ▌
    Pnasnexus Figures · brycewang-stanford

    Use to finalize PNAS Nexus display items — count figures and tables against the graphical-element budget, size to journal column widths, set legible fonts, show-the-data with n and defined error bars, scale bars, colorblind-safe palettes, legend structure, and image integrity (raw, unprocessed images must be retained). Enforces figure rigor before submission.
    1k repo stars
43. ▌
    Pnasnexus Writing · brycewang-stanford

    Use to choose the PNAS Nexus article type, structure the main text, and hold the page-based length budget — Research Report / Brief Report / Perspective / Review / Registered Report — keep Materials and Methods in the main text, and select the required research-area classification at submission.
    1k repo stars
44. ▌
    Recsys Review Process · brycewang-stanford

    Use when explaining or planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer, the rebuttal phase, how the reproducibility-crisis culture shapes reviewer priorities, the offline-versus-online evaluation lens, and how acceptance leads to ACM Digital Library publication.
    1k repo stars
45. ▌
    Rt Workflow · brycewang-stanford

    Use to sequence a manuscript across venues — which cross-journal toolkit skill to invoke next, from picking a target journal through execution, submission-readiness, simulated review, rebuttal, and the replication package. Routes; it does not replace the per-journal depth packs or the specialized toolkit skills.
    1k repo stars
46. ▌
    Sensys Review Process · brycewang-stanford

    Use when interpreting SenSys's two-deadline, self-contained review model — what a first-deadline outcome means, that a reject may return at the second deadline only with a substantive revision and Response to Reviewers, how systems reviewers weigh energy and deployment evidence, and how to classify a notification before drafting a response.
    1k repo stars
47. ▌
    Sigcomm Camera Ready · brycewang-stanford

    Use when preparing an accepted ACM SIGCOMM paper for the TAPS proceedings — clearing shepherd sign-off in HotCRP, uploading the final PDF plus source under acmart, de-anonymizing author and deployment identity, keeping the 12-page body under ACM two-column reflow, appendix-necessity approval, and releasing the public artifact by the badge deadline.
    1k repo stars
48. ▌
    Sigcomm Related Work · brycewang-stanford

    Use when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each placement via dblp and the ACM Digital Library, distinguishing main-track papers from CCR editorials, handling concurrent work, and keeping self-citation double-blind-safe.
    1k repo stars
49. ▌
    Siggraph Submission · brycewang-stanford

    Use when auditing an ACM SIGGRAPH / SIGGRAPH Asia Technical Papers submission for Linklings readiness, covering the two-step form-then-upload deadline, the acmart (>=2.16) format and the 7-page conference-track budget, the dual-track vs Journal-only choice, the mandatory representative image and supplemental video, and desk-risk triage before the UTC cutoff.
    1k repo stars
50. ▌
    Sigmod Review Process · brycewang-stanford

    Use when reasoning about how a SIGMOD research paper moves through a PACMMOD round, covering double-anonymous CMT reviewing, the author feedback phase, accept/reject/revision verdicts, the one-month revision window, the 12-month rejection embargo, and how database PC members actually weigh evidence.
    1k repo stars
51. ▌
    Wp Submission · brycewang-stanford

    Use when running the final pre-submission preflight for World Politics via ScholarOne — article-type selection, triple-blind anonymization, the 12,500-word limit (including notes and references), the 150-word abstract, double-spacing, the 15-page online-supplement cap, house-style formatting, the APSA human-subjects affirmation, and prior-publication rules. Final checks; it does not draft content.
    1k repo stars
52. ▌
    Aaai Artifact Evaluation · brycewang-stanford

    Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
    1k repo stars
53. ▌
    Aistats Supplementary · brycewang-stanford

    Use when preparing AISTATS supplementary material, appendices, proof details, code/data archives, simulation scripts, additional tables, and anonymized artifacts under deadline, size, anonymity, and reviewer-discretion constraints, including how to split a theory-plus-experiments paper between body and supplement.
    1k repo stars
54. ▌
    Aistats Writing Style · brycewang-stanford

    Use when revising an AISTATS paper for concise AI-statistics framing, theorem-and-experiment clarity, 8-page two-column compression, double-blind wording, reproducibility clarity, statistically careful claims, and assumption-labeling discipline that survives statistician reviewers.
    1k repo stars
55. ▌
    Asplos Author Response · brycewang-stanford

    Use when drafting an ASPLOS author response inside the short fixed window — triaging reviews into factual errors versus questions versus disagreements, budgeting for the ~800 words reviewers are expected to read, arguing only from evidence already in the submission, and positioning the paper for the Accept / Major Revision / Reject decision.
    1k repo stars
56. ▌
    Asplos Reproducibility · brycewang-stanford

    Use when hardening an ASPLOS paper's results for independent repetition — pinning simulator versions and configs, recording kernel/firmware/BIOS state, packaging FPGA bitstreams and RTL, documenting hardware dependencies an evaluator may lack, and writing availability statements that match what the ACM badges will later require.
    1k repo stars
57. ▌
    Asplos Topic Selection · brycewang-stanford

    Use when deciding whether a project belongs at ASPLOS or at a single-community venue — applying the cross-layer deletion test, matching against ASPLOS's architecture/PL/OS intersection identity, routing to ISCA/MICRO/HPCA, PLDI/POPL, SOSP/OSDI/EuroSys, SC, or MLSys instead, and choosing between the April and September deadlines.
    1k repo stars
58. ▌
    Cc Figures Tables · brycewang-stanford

    Use when building or auditing multi-panel mechanistic figures and tables for a Cancer Cell (Cell Press) manuscript — quantification of images, panel logic, image integrity, and legends. It shapes display items; it does not choose statistical tests or write the abstract.
    1k repo stars
59. ▌
    Cre Style · brycewang-stanford

    Use when polishing the language and rhetoric of a 《中国农村经济》 manuscript — eliminating empty-significance phrases, fixing the "加强完善推进" policy formula, replacing method-flexing with household mechanism, and aligning tense / person / hedging with CSSCI house style. 本技能服务于《中国农村经济》(China Rural Economy, CRE)。
    1k repo stars
60. ▌
    Cikm Artifact Evaluation · brycewang-stanford

    Use when packaging the code, datasets, knowledge graphs, prompts, and demo systems around a CIKM paper — choosing the artifact form per track (research, applied, resource, demo), meeting the resource track's reuse-and-documentation bar, and staging anonymous review artifacts into citable public releases.
    1k repo stars
61. ▌
    Colm Artifact Evaluation · brycewang-stanford

    Use when packaging the artifacts of a COLM paper — model weights, training data, prompts, evaluation sets, and cached model outputs — for anonymous review and public post-acceptance release, navigating licenses, API terms-of-service limits, and the absence of a formal COLM artifact track.
    1k repo stars
62. ▌
    Colt Artifact Evaluation · brycewang-stanford

    Use when deciding what evidence package a COLT (Conference on Learning Theory) paper needs, given that COLT runs no artifact-evaluation track or badges — the proof appendix is the artifact. Covers proof-verification passes, optional code companions for numerics, formalization aids, and post-acceptance release of scripts.
    1k repo stars
63. ▌
    Conext Author Response · brycewang-stanford

    Use when drafting ACM CoNEXT author responses, covering the initial-review rebuttal and — distinctively — the one-shot "major" revision response letter that must stay double-anonymous, map every "minimum necessary change" to a concrete tracked edit, and survive a single re-review by the original reviewers and a shepherd under PACMNET.
    1k repo stars
64. ▌
    Conext Reproducibility · brycewang-stanford

    Use when building the reproducibility story for an ACM CoNEXT paper — pinned traces and configs, a runnable artifact, an honest data-availability posture, and the one-page artifact description the CoNEXT reproducibility committee needs — remembering that the ACM badge opt-in is due before the submission deadline.
    1k repo stars
65. ▌
    Conext Topic Selection · brycewang-stanford

    Use when deciding whether a networking project belongs at ACM CoNEXT or should be routed to SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, or HotNets, and when using CoNEXT's two-cycles-per-year calendar and PACMNET journal-style fit to choose the venue and the cycle by contribution shape and evidence maturity.
    1k repo stars
66. ▌
    Corl Artifact Evaluation · brycewang-stanford

    Use when packaging the artifacts of a CoRL paper — code, training configs, demonstration datasets, policy checkpoints, simulation environments, and benchmark definitions — as anonymous review-time evidence and as durable public releases after acceptance, in a venue with no formal artifact-badging track.
    1k repo stars
67. ▌
    Cscw Artifact Evaluation · brycewang-stanford

    Use when packaging what stands behind a CSCW paper — systems, analysis pipelines, codebooks, instruments, datasets from real communities — for review-time scrutiny and post-acceptance release, where community-data ethics constrain release more than any badge checklist.
    1k repo stars
68. ▌
    Cvpr Artifact Evaluation · brycewang-stanford

    Use when packaging code, models, datasets, or demo videos for a CVPR paper at either review time or release time, covering anonymous supplement packaging under the external-link ban, the dataset-release-by-camera-ready rule, model-weight and license decisions, and making a vision artifact runnable by a skeptical stranger.
    1k repo stars
69. ▌
    Eacl Artifact Evaluation · brycewang-stanford

    Use when packaging code, data, prompts, model outputs, and annotation materials for an EACL submission, first as an anonymized ACL Rolling Review supplement aligned with the Responsible NLP checklist, then as a public post-acceptance ACL Anthology release, with attention to licensing, dataset documentation, and reproduction instructions.
    1k repo stars
70. ▌
    Ecai Artifact Evaluation · brycewang-stanford

    Use when planning the reproducibility/artifact story for an ECAI paper — noting that ECAI/FAIA has NO ACM/IEEE-style artifact-badging committee, so credibility is carried by the paper and its supplement and judged by the same reviewers, and adapting an ML-style reproducibility package (or a complete proof appendix for theory work) to that reality.
    1k repo stars
71. ▌
    Eccv Artifact Evaluation · brycewang-stanford

    Use when packaging code, models, and data around an ECCV paper — the anonymous review-time archive under the trailing supplement deadline, the do-not-cite-your-own-repo rule, and the June-to-September post-acceptance runway for a public release aligned with the ECVA and Springer copies of the paper.
    1k repo stars
72. ▌
    Edbt Artifact Evaluation · brycewang-stanford

    Use when preparing an EDBT database-systems artifact and reproducibility package, covering what evaluators check first for systems papers, a turnkey run path, pinned workloads and environments, DOI-issuing archival for the open-access OpenProceedings record, and the higher stakes for Experiments & Analysis papers.
    1k repo stars
73. ▌
    Eurosys Supplementary · brycewang-stanford

    Use when deciding what lives outside a EuroSys paper's 12 technical pages — free reference pages, whether the current round permits appendices or supplementary uploads, anonymized artifact repositories linked from the submission, and extended technical reports — without moving decision-critical evidence out of the reviewed pages.
    1k repo stars
74. ▌
    Eurosys Writing Style · brycewang-stanford

    Use when drafting or revising EuroSys prose — building the problem-to-mechanism arc systems reviewers expect, budgeting the 12 technical pages across design and evaluation, writing figure-first evaluation sections, keeping claims measurement-scoped, and maintaining double-blind voice in the acmart sigplan format.
    1k repo stars
75. ▌
    Fast Artifact Evaluation · brycewang-stanford

    Use when packaging a USENIX FAST artifact for the USENIX Artifact Evaluation scheme (Artifacts Available, Artifacts Functional, Results Reproduced), covering what a storage AEC checks first, DOI-issuing archives, the artifact appendix, and the special challenges of storage artifacts that need specific devices, large traces, or long endurance runs on the separate post-acceptance timeline.
    1k repo stars
76. ▌
    Focs Artifact Evaluation · brycewang-stanford

    Use when planning the durable evidence objects around a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue with no artifact track where the public arXiv/ECCC full version is the artifact of record, plus proof certificates, checker code, and the IEEE Xplore version's supporting role.
    1k repo stars
77. ▌
    Icassp Author Response · brycewang-stanford

    Use when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already know you, answering signal-processing reviewers from the four-page record without a revised PDF, and writing for the technical-committee decision rather than for tone.
    1k repo stars
78. ▌
    Icassp Reproducibility · brycewang-stanford

    Use when strengthening ICASSP reproducibility across signal-processing modalities — pinning the scoring ruler for the paper's metric, dataset versions and splits, front-end/DSP settings, seeds, and compute, and mapping each claim to a checkable location, since ICASSP has no reviewed appendix and the four pages plus a public release must carry it.
    1k repo stars
79. ▌
    Icassp Topic Selection · brycewang-stanford

    Use when deciding whether a project fits ICASSP, the IEEE Signal Processing Society flagship spanning all signal processing, and specifically for the ICASSP-versus-Interspeech routing decision for speech work, plus routing to ICIP, EUSIPCO, WASPAA, SPS journals, or ML venues by identifying the signal-processing primitive of the contribution.
    1k repo stars
80. ▌
    Iccv Artifact Evaluation · brycewang-stanford

    Use when packaging code, models, or data for an ICCV paper at review or release time, covering anonymous in-archive code under the do-not-cite-your-repo rule, the June-to-October release runway after acceptance, weight and license decisions in a field whose landmark releases became infrastructure, and reuse-grade packaging.
    1k repo stars
81. ▌
    Icde Artifact Evaluation · brycewang-stanford

    Use when packaging IEEE ICDE code, data, workload generators, and logs as supplemental material whose availability reviewers score, and for any post-acceptance reproducibility or badge process the edition runs. Covers what a builder-heavy committee inspects first, making a data-systems benchmark turnkey, and single-blind packaging.
    1k repo stars
82. ▌
    Icdm Artifact Evaluation · brycewang-stanford

    Use when packaging code, data, and logs for an ICDM (IEEE International Conference on Data Mining) paper - building the anonymized, history-scrubbed repository that the PDF must cite for a triple-blind Research Track submission, how the single-blind Applied Track changes what may be revealed, and the smoke checks that make an ICDM artifact reviewer-usable.
    1k repo stars
83. ▌
    Icdt Artifact Evaluation · brycewang-stanford

    Use when preparing the "artifact" of an ICDT (International Conference on Database Theory) paper, which at a pure-theory venue is the complete-proofs full version rather than a code package — covering why ICDT has no ACM-style artifact-badging or code-artifact track, what the marked appendix and the archived arXiv full version must contain, and (only for the rare algorithmic paper) how any code should be handled.
    1k repo stars
84. ▌
    Iclr Artifact Evaluation · brycewang-stanford

    Use when packaging ICLR code, data, checkpoints, demos, logs, and reproduction instructions for reviewers or post-acceptance release, including anonymized links and private OpenReview discussion-period sharing. Use when a reviewer asks for a missing repro path, when a public comment questions whether claims can be verified, or when converting an anonymous supplement into a durable post-acceptance release for the permanent ICLR record.
    1k repo stars
85. ▌
    Icml Artifact Evaluation · brycewang-stanford

    Use when packaging ICML artifacts - code, data, model weights, simulators, benchmarks, proof scripts, notebooks, anonymous repositories, and supplementary code/data ZIPs - for both the double-blind review package and the public release that accompanies accepted PMLR papers. Use when checking anonymity, decision relevance, licensing, and the OpenReview code URL field under current ICML rules.
    1k repo stars
86. ▌
    Icra Artifact Evaluation · brycewang-stanford

    Use when packaging the artifacts behind an ICRA paper — ROS packages, controllers, simulation environments, trained policies, CAD and PCB files, datasets, and trial logs — into something a robotics reviewer or reader can actually run or audit, given that ICRA has no formal artifact-badging track to certify it for you.
    1k repo stars
87. ▌
    Icse Artifact Evaluation · brycewang-stanford

    Use when preparing an artifact for the ICSE Artifact Evaluation track after paper acceptance, covering the ACM badge system (Available, Reusable, Results Reproduced/Replicated), evaluator-proof packaging, archival requirements, open licensing, and the January-window timeline anchored to recent cycles.
    1k repo stars
88. ▌
    Ieeesp Review Process · brycewang-stanford

    Use when reasoning about IEEE S&P (Oakland) peer review, including the rounds inside each cycle, early-reject notices, the rebuttal for second-round papers, the Accept/Revise/Reject decision set, the Research Ethics Committee, shepherding of accepted papers, and the one-year resubmission embargo.
    1k repo stars
89. ▌
    Infocom Supplementary · brycewang-stanford

    Use when deciding what fits inside an IEEE INFOCOM paper's tight IEEEtran budget, covering the rule that appendices count toward the nine pages of text, the absence of a separate supplementary channel at review time, double-blind handling of any released material, and how to split an analytical or systems networking paper between the body and an optional external release.
    1k repo stars
90. ▌
    Infocom Writing Style · brycewang-stanford

    Use when revising an IEEE INFOCOM paper for a networking problem and system model stated up front, theorems or protocol design that pay off, evaluation proportional to the claim, defensive writing that pre-empts objections (because there is no rebuttal), double-blind wording, and disciplined use of the tight IEEEtran two-column page budget.
    1k repo stars
91. ▌
    Ipsn Artifact Evaluation · brycewang-stanford

    Use when packaging an IPSN-lineage artifact for the ACM badges and the IPSN Best Research Artifact Award, covering hardware-plus-software artifacts (firmware, board files, datasets), what sensor-systems evaluators check first, DOI-issuing archives, evaluator-proof documentation for a physical system, and the separate post-acceptance timing.
    1k repo stars
92. ▌
    Iros Artifact Evaluation · brycewang-stanford

    Use when packaging IROS evidence for a skeptical reviewer even though IROS runs no formal artifact track — the robotics artifact stack of hardware ledger, logs, configs, code, and data, what an embodied-systems reviewer opens first, review-time anonymity versus acceptance-time public release, and making a claim auditable not asserted.
    1k repo stars
93. ▌
    Isca Artifact Evaluation · brycewang-stanford

    Use when preparing an accepted ISCA paper's artifact for evaluation under the ACM Review and Badging policy — scoping which results are reproducible within evaluator budgets, packaging simulator-heavy workflows others can run, writing the evaluator-facing appendix, and earning badges that print on the paper.
    1k repo stars
94. ▌
    Itcs Artifact Evaluation · brycewang-stanford

    Use to adapt the idea of an "artifact" to a pure-theory venue — at ITCS there is no artifact-evaluation track, no code, and no badges; the analogue is making every claim independently verifiable through complete proofs in the submitted PDF and a matching public full version, plus checkable finite objects for any computational content.
    1k repo stars
95. ▌
    Jama Ethics Registration · brycewang-stanford

    Use when verifying trial registration, IRB/ethics approval, informed consent, ICMJE authorship and conflict-of-interest disclosures, and the data-sharing statement for a JAMA manuscript. Confirms compliance; it does NOT design the study or write the abstract.
    1k repo stars
96. ▌
    Jama Reporting Standards · brycewang-stanford

    Use when selecting and completing the EQUATOR-network reporting checklist and flow diagram for a JAMA manuscript (CONSORT, STROBE, PRISMA, STARD, and design-specific guidelines). Maps design to checklist; it does NOT design the study or write the statistics.
    1k repo stars
97. ▌
    Jama Structured Abstract · brycewang-stanford

    Use when writing or auditing the JAMA structured abstract and the Key Points box for a JAMA manuscript. Enforces the exact JAMA heading set and quantified results; it does NOT design the study or run statistics.
    1k repo stars
98. ▌
    Misq Submission · brycewang-stanford

    Use for the final pre-submission preflight of a MIS Quarterly manuscript — confirming the ScholarOne workflow, Word-file format, double-anonymous compliance, the correct manuscript category and its page limit, the pluralistic transparency commitment uploaded at Step 2, and the reviewer-service agreement. Verifies submission readiness; it does not polish prose (misq-writing-style) or interpret decisions (misq-review-process).
    1k repo stars
99. ▌
    Mobicom Supplementary · brycewang-stanford

    Use when deciding what goes in the MobiCom 12-page double-column body versus references, optional appendices, and HotCRP fields — placing channel-model derivations, full protocols, and extended measurements outside the cap, keeping the contribution self-contained, and ensuring rebuttal and revision packets stay off the page count.
    1k repo stars
100. ▌
     Mobicom Writing Style · brycewang-stanford

     Use when drafting or revising a MobiCom paper for house style — putting the wireless/mobile mechanism and its operating regime on the first page, pairing every claim with over-the-air measurement, replacing superlatives with percentiles and intervals, and fitting the argument into the double-column 12-page body.
     1k repo stars