메뉴
이 저장소의 skills
SkillsMP는 brycewang-stanford/Awesome-Journal-Skills에서 3,969개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
brycewang-stanford/Awesome-Journal-Skills수집된 skill 3,969개 중 40개를 표시합니다.
Use when positioning an ISCA submission against prior art — covering five decades of architecture literature across ACM DL, IEEE Xplore, and dblp, differentiating by mechanism rather than metric, handling self-citations and arXiv preprints under double-blind…
원문 언어: 영어
Use when making an ISCA paper's results regenerable — pinning simulator versions and local patches, archiving per-figure configuration manifests, recording workload provenance and sampling seeds, quantifying run-to-run variation on real hardware, and keeping…
원문 언어: 영어
Use when reasoning about how an ISCA submission is evaluated — the two-round review structure with December and February reviewer waves, what the combined rebuttal-and-revision window means for decisions, PC-meeting dynamics at a flagship architecture venue,…
원문 언어: 영어
Use when running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart, the 11-page text limit with unlimited references, the template check, the double-blind sweep including PDF metadata and anonymized…
원문 언어: 영어
Use when deciding what accompanies an ISCA submission beyond the 11 reviewed pages — what must live inside the page budget because reviewers see nothing else, how to use fully anonymized artifact links under the double-blind rules, staging material for the…
원문 언어: 영어
Use when deciding whether a project belongs at ISCA, the ACM/IEEE flagship architecture symposium — testing whether the machine itself is the contribution, choosing between ISCA's November gate and the MICRO, HPCA, and ASPLOS seats in the architecture year,…
원문 언어: 영어
Use when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and…
원문 언어: 영어
Use when drafting or revising an ISCA paper's prose — organizing 11 pages around one architectural insight, writing the motivation section from measured data, describing mechanisms at reviewer-checkable precision with figures that carry the design, and…
원문 언어: 영어
Use when preparing a MICRO artifact for post-acceptance evaluation — packaging simulators, configs, traces, and scripts so evaluators can regenerate the paper's figures, targeting the ACM Available/Functional/Reproducible badges, handling licensed workloads…
원문 언어: 영어
Use when a MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle, de-anonymization and acknowledgments restoration, keeping the all-author reference rule, integrating rebuttal promises, the optional…
원문 언어: 영어
Use when designing or auditing the evaluation of a MICRO paper — choosing the right instrument on the ladder from analytical model to cycle-level simulator to RTL to silicon, tuning baselines the PC will respect, selecting workload suites, running ablations…
원문 언어: 영어
Use when building a MICRO paper's related-work coverage and positioning — sweeping the four-venue architecture literature plus journals and industry disclosures, differentiating by mechanism structure and cost rather than by numbers, obeying MICRO's…
원문 언어: 영어
Use when hardening a MICRO paper's results for re-derivation — pinning simulator commits and configs, recording workload trace provenance and SimPoint recipes, versioning power/area models, capturing RTL toolchain state, and writing the run manifests that…
원문 언어: 영어
Use when reasoning about how a MICRO submission is judged — the double-blind HotCRP pipeline from the April deadline through the June rebuttal/revision window to the early-July notification, what reviewers score in a microarchitecture paper, the…
원문 언어: 영어
Use when auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the abstract-registration gate a week before the paper, minimum 9pt fonts, mandatory page numbers,…
원문 언어: 영어
Use when deciding where a MICRO paper's supporting material lives, because MICRO allows no appendix at all — triaging content into the 11 reviewed pages, the unlimited references, an anonymized artifact repository, or the post-acceptance two-page artifact…
원문 언어: 영어
Use when deciding whether a project belongs at MICRO (IEEE/ACM International Symposium on Microarchitecture) or should route to ISCA, HPCA, ASPLOS, DAC/ICCAD, SC, or MLSys — testing whether the mechanism truly lives inside the machine, gauging the MICRO…
원문 언어: 영어
Use when planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock, the four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICRO's October seat, resubmission lattices after each outcome, and starting the MICRO 2027…
원문 언어: 영어
Use when drafting or revising a MICRO paper's prose and structure — building the characterization-motivated introduction, budgeting 11 appendix-free pages, drawing the mechanism walkthrough a microarchitect can re-implement, and pairing every speedup claim…
원문 언어: 영어
Use when packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code, trained policies, trial ledgers, hardware documentation, and footage — first as anonymous review-time evidence and then as the public release the venue's free…
원문 언어: 영어
Use when converting an accepted RSS (Robotics: Science and Systems) paper into its public form — de-anonymization and platform-attribution restoration, adding the external links the CFP reserves for this stage, publication in the free roboticsproceedings.org…
원문 언어: 영어
Use when designing or auditing the experimental campaign for an RSS (Robotics: Science and Systems) paper — hypothesis-shaped robot experiments, trial protocols and per-condition counts, mechanism-isolating ablations, simulation-versus-hardware evidence…
원문 언어: 영어
Use when positioning an RSS (Robotics: Science and Systems) submission within the literature — covering the robotics-conference lanes (RSS/ICRA/IROS/CoRL) plus journals and ML venues, handling fast-moving arXiv concurrency in robot learning, keeping…
원문 언어: 영어
Use when strengthening the reproducibility of an RSS (Robotics: Science and Systems) paper whose evidence lives partly on hardware — platform disclosure ledgers, log-backed trial claims, seeds and configs for the computational half, honest replication tiers,…
원문 언어: 영어
Use when auditing an RSS (Robotics: Science and Systems) submission for OpenReview readiness — the abstract/paper/supplement deadline cascade, the 8-page-excluding-references ceiling, double-blind compliance, PDF self-containment, the…
원문 언어: 영어
Use when assembling RSS (Robotics: Science and Systems) supplementary material under the separate one-week-later deadline — deciding what leaves the self-contained main PDF, cutting robot video that functions as evidence rather than promotion, anonymizing…
원문 언어: 영어
Use when judging whether a robotics project fits RSS (Robotics: Science and Systems), the single-track selective venue whose bar is a scientific claim about robotics, and when routing instead toward ICRA, IROS, CoRL, HRI, WAFR, T-RO, or IJRR based on claim…
원문 언어: 영어
Use when planning an RSS (Robotics: Science and Systems) campaign end to end — the late-January abstract/paper/supplement cascade, the invited-rebuttal window, late-April decisions, July conference week — and when placing RSS inside the year-round…
원문 언어: 영어
Use when revising an RSS (Robotics: Science and Systems) draft to meet the science-first bar — a falsifiable claim about robotics up front, evidence sized to claim scope, honest failure reporting, concision under an 8-page ceiling that rewards brevity, and…
원문 언어: 영어
Use when packaging the artifacts behind a UIST paper — code, toolkits, hardware design files, and datasets — first as anonymous review-time evidence that the system is real, then as a public release engineered for reuse, in a venue with no formal badge…
원문 언어: 영어
Use when writing the UIST rebuttal — budgeting the 5,000-character self-contained response, prioritizing factual corrections and novelty defenses over taste disputes, promising only camera-ready changes you can deliver, and writing for the PC discussion that…
원문 언어: 영어
Use when converting a conditional UIST acceptance into a published paper — delivering the rebuttal-promised changes by the July deadline, working the ACM TAPS pipeline with alt text for every figure and table, de-anonymizing correctly, finalizing the video…
원문 언어: 영어
Use when designing or auditing the evaluation of a UIST paper — choosing among technical benchmarks, controlled comparisons, usability walkthroughs, expert sessions, and demonstration applications, matching evaluation shape to the systems claim, and avoiding…
원문 언어: 영어
Use when positioning a UIST submission against prior art — organizing by capability delta rather than paper lists, covering the technique lineage, toolkit ancestry, and commercial systems reviewers know, citing your own work in the third person, and verifying…
원문 언어: 영어
Use when making a UIST paper's results replicable — reporting implementation parameters and measurement protocols so a lab could rebuild the system, specifying hardware down to parts and calibration, logging technical evaluations deterministically, and…
원문 언어: 영어
Use when interpreting the UIST review pipeline — anonymous PC-plus-external review of papers and videos, the rebuttal's role, PC-meeting decisions, conditional acceptance mechanics, reading systems-reviewer psychology, and choosing the demo/poster fallback or…
원문 언어: 영어
Use when performing the final pre-upload audit of a UIST paper in PCS — the abstract-then-paper deadline pair, 10-page/5-page two-column limits with desk-reject enforcement, anonymous acmart options, video-figure and supplementary uploads, the prior-work…
원문 언어: 영어
Use when producing the video figure and supplementary materials for a UIST submission — treating the 3-minute video as near-mandatory evidence in a demo-culture venue, scripting it around claims, meeting the 1080p/4K H.264 spec, anonymizing frames and audio,…
원문 언어: 영어
Use when deciding whether a project belongs at UIST — testing it against the interface-systems contribution bar (novel technique, toolkit, or hardware that works), making the CHI-vs-UIST routing call explicitly, and re-routing to CSCW, IMWUT, TEI, ISMAR, IUI,…
원문 언어: 영어
Use when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional acceptance, the July camera-ready, adjunct-track parallel lanes, and the November…
원문 언어: 영어