메뉴
이 저장소의 skills
SkillsMP는 brycewang-stanford/Awesome-Journal-Skills에서 3,969개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
brycewang-stanford/Awesome-Journal-Skills수집된 skill 3,969개 중 40개를 표시합니다.
Use when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the design-automation contribution as a measured delta, fitting a complete argument into six…
원문 언어: 영어
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,…
원문 언어: 영어
Use when drafting EDBT author responses across the two turns of a cycle — the short author-feedback reply on the initial reviews, and the in-cycle revise-and-resubmit change letter that maps every reviewer request to a concrete revision re-read by the…
원문 언어: 영어
Use when preparing an accepted EDBT paper for its OpenProceedings camera-ready, covering the host/OpenProceedings LaTeX template, the CC-BY-NC-ND open-access license and copyright form, ISBN/volume metadata, integrating reviewer-required changes without scope…
원문 언어: 영어
Use when designing or auditing EDBT empirical evaluations for database-systems work, covering real workloads and datasets, fair and tuned baselines, honest measurement across realistic scales, reproducible harnesses, and the higher bar of the Experiments &…
원문 언어: 영어
Use when positioning an EDBT submission against the data-management literature across SIGMOD, VLDB/PVLDB, ICDE, EDBT, the co-located ICDT, and the database journals (VLDBJ, TODS, TKDE), writing delta-first contrast rather than a citation catalog, and handling…
원문 언어: 영어
Use when strengthening EDBT reproducibility for a database-systems paper, covering a runnable artifact, pinned environments and workloads, dataset and query-log provenance, claim-to-evidence mapping, honest degrees of reproducibility, and consistency between…
원문 언어: 영어
Use when reasoning about how an EDBT research submission is evaluated, covering Microsoft CMT reviewing, the author-feedback phase, the accept / revise / reject decision, the in-cycle revise-and-resubmit second read by the original reviewers, the…
원문 언어: 영어
Use when auditing an EDBT research-track submission for Microsoft CMT readiness, covering the cycle choice, the paper shape (Regular / Experiments-&-Analysis / Vision), the OpenProceedings/host LaTeX template and per-shape page budget, the 12-month…
원문 언어: 영어
Use when deciding what belongs in an EDBT paper body versus its artifact and appendices, covering the per-shape page budget with unlimited references, the rule that decision-critical evidence stays inside the reviewed pages, and how to split a…
원문 언어: 영어
Use when deciding whether a data-management project belongs at EDBT or should be routed to SIGMOD, VLDB/PVLDB, ICDE, the co-located ICDT theory venue, or a database journal, and when choosing the EDBT paper shape (Regular / Experiments-&-Analysis / Vision)…
원문 언어: 영어
Use when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for…
원문 언어: 영어
Use when revising an EDBT paper for a data-management contribution on the first page, a reproducibly described mechanism, an evaluation that survives a database-systems reviewer, honest scope, and disciplined use of the per-shape page budget (Regular /…
원문 언어: 영어
Use when packaging the artifacts of an accepted ACM/IEEE HRI paper — code, robot behaviors, de-identified data, and study materials — for openness and any ACM badges the edition offers, while being honest about the limits of reproducing an embodied…
원문 언어: 영어
Use when writing the single ACM/IEEE HRI full-paper rebuttal that responds to three external reviewers and two area chairs — triaging study-design and statistics critiques, correcting misreadings, promising only what a camera-ready can deliver, staying…
원문 언어: 영어
Use when preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically, completing ACM+IEEE dual-publication metadata (CCS concepts, ORCID, rights/eRights form), delivering every rebuttal promise within the 8-page budget,…
원문 언어: 영어
Use when designing or auditing the human-subjects study at the heart of an ACM/IEEE HRI full paper — choosing between/within-subjects designs, running Wizard-of-Oz honestly, powering the sample, reporting statistics with effect sizes and qualitative rigor,…
원문 언어: 영어
Use when writing or auditing the related-work and positioning of an ACM/IEEE HRI full paper — covering HRI's crossing literatures (robotics, HCI, psychology, design), writing a delta-first argument that credits each community, and keeping self-citation…
원문 언어: 영어
Use when building the openness and replicability story for an ACM/IEEE HRI full paper — sharing study materials, robot-behavior specifications, de-identified data, and analysis code; reporting Wizard-of-Oz and pre-registration; and stating honestly what can…
원문 언어: 영어
Use to understand and navigate the ACM/IEEE HRI full-paper review pipeline — the initial desk check and track assignment, the 1AC/2AC plus three external reviewers, the double-blind two-phase model, the author rebuttal, the online reviewer discussion, the…
원문 언어: 영어
Use when auditing an ACM/IEEE HRI full-paper submission for PCS readiness — the mandatory abstract-then-paper two-step deadline, choosing the correct one of the five tracks, the 8-page acmart anonymous format, the double-blind sweep across PDF and video, the…
원문 언어: 영어
Use when planning the supplementary materials for an ACM/IEEE HRI full paper — above all the video figure that shows the embodied interaction, plus study instruments, extended results, and appendices — deciding what a reviewer must see to judge the…
원문 언어: 영어
Use when deciding whether a human-robot-interaction project belongs at the ACM/IEEE HRI conference versus CHI, ICRA/IROS, RO-MAN, CoRL, HAI, or the THRI/JHRI journals, and then which of HRI's five full-paper tracks (User Studies, Technical, Design, Theory and…
원문 언어: 영어
Use to plan an ACM/IEEE HRI campaign backward from the full-paper deadline through the abstract-then-paper two-step, the rebuttal, the program-committee meeting, camera-ready, and the March conference, coordinating the parallel alt.HRI, Late-Breaking Reports,…
원문 언어: 영어
Use when drafting or revising an ACM/IEEE HRI full paper's structure and prose for an interdisciplinary audience — leading with the human-robot contribution and research questions, making hypotheses and measures explicit, describing the robot embodiment,…
원문 언어: 영어
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…
원문 언어: 영어
Use when handling the IEEE INFOCOM post-submission reality — that the venue has traditionally offered no author rebuttal — covering how to write a self-defending submission, how to read and act on an early-reject, what to do after a final reject, and how to…
원문 언어: 영어
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,…
원문 언어: 영어
Use when designing or auditing IEEE INFOCOM evaluations, covering analytical results with stated and justified assumptions, simulation with a named simulator and logged seeds, testbed and measurement studies with real traffic, honest and tuned baselines, and…
원문 언어: 영어
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…
원문 언어: 영어
Use when strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track, covering pinned simulator setups, released code and datasets where possible, complete proofs and parameters within the page budget, IEEE…
원문 언어: 영어
Use when reasoning about how an IEEE INFOCOM submission is evaluated, covering the large-scale double-blind pipeline, automated paper-reviewer assignment, the two-tier TPC and early-reject phase, the (traditional) absence of an author rebuttal, TPC…
원문 언어: 영어
Use when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column 10-page/9-page-of-text budget, double-blind anonymization of the PDF and metadata, the…
원문 언어: 영어
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…
원문 언어: 영어
Use when deciding whether a networking project belongs at IEEE INFOCOM or should be routed to SIGCOMM, NSDI, MobiCom, ICNP, or an IEEE/ACM networking journal (ToN, JSAC), distinguishing INFOCOM by its breadth, its analytical/optimization tradition alongside…
원문 언어: 영어
Use when planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration, the early-reject checkpoint, the December notification, the IEEE Xplore camera-ready with PDF eXpress and eCF, and presentation, with…
원문 언어: 영어
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),…
원문 언어: 영어
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…
원문 언어: 영어
Use to operate under the reality that ITCS has no rebuttal or author-response phase — pre-empting reviewer objections inside the submission, then handling the post-decision situation (camera-ready window on accept, or rerouting and reusing the reviews on…
원문 언어: 영어
Use when preparing an accepted ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class, de-anonymizing, completing LIPIcs metadata (ACM CCS, keywords, funding), folding in reviewer-noted fixes, and passing the Schloss…
원문 언어: 영어