메뉴
이 저장소의 skills
SkillsMP는 brycewang-stanford/Awesome-Journal-Skills에서 3,969개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
brycewang-stanford/Awesome-Journal-Skills수집된 skill 3,969개 중 40개를 표시합니다.
Use when preparing or auditing a SODA (ACM-SIAM Symposium on Discrete Algorithms) submission — the no-page-limit full-version norm, the title-page abstract, 11-point single-column letter format, lightweight double-blind rules, HotCRP entry, and the July AoE…
원문 언어: 영어
Use when organizing the back matter of a SODA (ACM-SIAM Symposium on Discrete Algorithms) submission — there is no supplementary channel, so appendix architecture inside the single no-page-limit PDF does the supplement's job; covers front/back matter split,…
원문 언어: 영어
Use when deciding whether a result is SODA-shaped (ACM-SIAM Symposium on Discrete Algorithms) — concrete algorithmic problems, data structures, and discrete mathematics with quantitative progress — versus routing to STOC/FOCS, ESA, ICALP, ITCS, SOSA, ALENEX,…
원문 언어: 영어
Use when planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between STOC and FOCS deadlines, the September rebuttal and October decision, satellite…
원문 언어: 영어
Use when writing or revising a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly, the title-page abstract that wins bidding, a first-ten-pages overview for triage readers, prior-bound comparison tables, and prose…
원문 언어: 영어
Use when preparing a PVLDB artifact for the pVLDB Reproducibility Evaluation or the ACM availability badge, covering the mandatory participation rule for EA&B papers, the four artifact surfaces evaluators rebuild, packaging for a rerun by strangers, and…
원문 언어: 영어
Use when a PVLDB paper receives a revision verdict and the response package must be built, covering the one-shot revision rule, the three-month window, reading the reviewers' required-changes list, planning new experiments against the clock, and writing the…
원문 언어: 영어
Use when producing the final PVLDB version of an accepted VLDB paper, covering the volume-specific template, PDF/A compliance and font embedding, figure legibility floors, the availability paragraph and artifact URL, proceedings file naming and copyright…
원문 언어: 영어
Use when designing or auditing the evaluation of a VLDB paper, covering workload and dataset realism at scale, competitor tuning fairness, scalability curves versus single points, tail-latency and throughput reporting, ablations that isolate the mechanism,…
원문 언어: 영어
Use when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood, concurrent work under rolling monthly deadlines, industrial and open-source systems as…
원문 언어: 영어
Use when engineering reproducibility into a VLDB paper before submission, covering hardware and configuration disclosure, dataset and workload provenance, run-to-run variance in systems measurements, competitor-version pinning, figure-to-raw-data…
원문 언어: 영어
Use when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome space, the one-shot revision's odds, single-blind dynamics, the volume review board,…
원문 언어: 영어
Use when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and page-budget choice, single-blind cover-page requirements, the per-month and…
원문 언어: 영어
Use when deciding what lives outside a PVLDB paper's page budget, covering the rule that appendices count against the limit, the extended technical report on arXiv under single-blind review, proof and algorithm placement, artifact repositories as the…
원문 언어: 영어
Use when deciding whether a project belongs at VLDB and in which PVLDB category, applying the data-management-primitive test, choosing among Regular, EA&B, Scalable Data Science, and Vision papers, and routing against SIGMOD, ICDE, CIDR, EDBT, PODS, KDD,…
원문 언어: 영어
Use when planning a VLDB project on the PVLDB rolling calendar, covering month-picking strategy, the volume-to-conference mapping and acceptance cutoff, budgeting a possible three-month revision, coordinating author caps across a group, and backward planning…
원문 언어: 영어
Use when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of hiding them, terminology and notation discipline across a 12-page budget, and the…
원문 언어: 영어
Use when positioning a SIGMOD submission against the data-management literature, covering coverage across SIGMOD/PACMMOD, PVLDB, ICDE, TODS, and PODS lines, decades-deep systems history, concurrent papers in rolling venues, industrial-system citations, and…
원문 언어: 영어
Use when hardening the reproducibility story of a SIGMOD submission, covering PACMMOD's expectation that code, data, scripts, and notebooks be shared, experiment provenance from config to figure, dataset and workload disclosure, variance reporting for systems…
원문 언어: 영어
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…
원문 언어: 영어
Use when deciding what accompanies a SIGMOD submission beyond the 12 pages, covering extended technical reports, anonymized code and data links that survive multi-round review, appendix placement relative to the unlimited reference pages, and what reviewers…
원문 언어: 영어
Use when planning a SIGMOD project calendar under the PACMMOD round system, covering round selection and hopping, backward planning from abstract and paper cutoffs, the feedback and revision windows, embargo-aware contingencies, and coordinating a…
원문 언어: 영어
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…
원문 언어: 영어
Use when drafting an ECCV rebuttal — the optional one-page, two-column PDF answering three-plus reviews inside a nine-day window (reviews May 2, rebuttal due May 11 in 2026), with references counted inside the page, no venue-forbidden extras, and arguments…
원문 언어: 영어
Use when preparing an accepted ECCV paper for Springer LNCS publication — the enlarged final page budget, Springer author kit and licensing, the June 30 AoE camera-ready cutoff in 2026, registration as a publication condition, ECVA open-access mirroring about…
원문 언어: 영어
Use when designing or auditing the experimental program of an ECCV paper — benchmark selection that survives a September conference, matched-substrate baseline fairness in the foundation-model era, ablations that isolate the claimed mechanism, qualitative…
원문 언어: 영어
Use when positioning an ECCV submission in the literature — covering the two intervening CVPR/ICCV cycles since the last ECCV, March-deadline concurrent-work conventions, the no-self-repo citation rule, Springer-vs-CVF venue attribution hygiene, and turning a…
원문 언어: 영어
Use when hardening the reproducibility story of an ECCV paper — training recipes and schedules readers can re-run, dataset versioning and split provenance, pinned foundation-model dependencies, compute disclosure, and seed/variance honesty for benchmark…
원문 언어: 영어
Use when modeling how ECCV review actually works — the OpenReview pipeline from March registration to June decisions, the 2026 reviewer-duty enforcement that desk-rejects authors of late or LLM-written reviews, rebuttal-to-AC-discussion dynamics, and what the…
원문 언어: 영어
Use when auditing an ECCV submission for the two-step registration-then-paper deadline chain, the 14-page LNCS single-column limit, CET (not AoE) cutoffs, the trailing supplementary deadline, double-blind rules, the four-page dual-submission definition, the…
원문 언어: 영어
Use when assembling ECCV supplementary material under its own deadline one week after the paper (March 12 in 2026) — deciding what belongs in the extra week's upload, video and qualitative-result packaging, anonymity scrubbing of archives, and keeping the…
원문 언어: 영어
Use when deciding whether a computer-vision project should target ECCV — weighing the two-year even-year cadence against CVPR, ICCV, WACV, BMVC, ACCV, NeurIPS, and journal routes, testing whether the work matches ECCV's breadth from geometry to…
원문 언어: 영어
Use when running an ECCV campaign end to end — the even-year calendar from February registration to the September conference, the retargeting triangle to CVPR and ICCV seen from the ECCV seat, where the 2026 cycle stands today, and backward planning a 2028…
원문 언어: 영어
Use when writing or revising an ECCV paper in the Springer LNCS single-column format — spending the 14-page budget (figures and tables included), LNCS-specific layout craft, first-page architecture for a mixed European panel, numbered-citation hygiene, and…
원문 언어: 영어
Use when packaging datasets, models, prompts, or annotation materials for a NAACL-bound submission — building the artifact around the Responsible NLP checklist's artifact questions, documenting provenance and licensing for language data, and handling…
원문 언어: 영어
Use when writing the ARR author response for a paper headed to NAACL — deciding which reviewer objections to spend the window on, drafting replies that give the action editor a citable meta-review sentence, and protecting the score record that NAACL's…
원문 언어: 영어
Use when converting a paper accepted to NAACL Main or Findings into its final ACL Anthology version — merging promised revisions, restoring identity and community acknowledgements, applying the extra-page allowance, fixing Anthology metadata, and planning…
원문 언어: 영어
Use when designing or auditing the experimental program of a NAACL submission — matching evidence to language-coverage claims, keeping cross-lingual comparisons budget-fair, testing on natively authored rather than translated data where the claim requires it,…
원문 언어: 영어
Use when building the related-work and positioning story for a NAACL submission — covering the ACL Anthology lineages reviewers expect, citing Findings, workshop, and regional venues correctly, handling resubmission histories and concurrent preprints under…
원문 언어: 영어
Use when hardening the reproducibility story of a NAACL submission — treating the Responsible NLP checklist as a binding contract, pinning model versions and API access dates, making multilingual evaluation re-runnable, and stating an honest release level…
원문 언어: 영어