Skill UI

A comprehensive guide for optimizing computer science manuscripts targeting the USENIX Annual Technical Conference (ATC). It covers core systems research fields (OS, networking, storage, security), defining the required evidence bar (built artifacts, clean evaluation), and re-framing the paper's contribution to align with top-tier systems venue expectations.

This skill provides a comprehensive guide for authors targeting the USENIX Symposium on Operating Systems Design and Implementation (OSDI). It helps in positioning complex systems research, covering core scope areas like operating systems, distributed systems, and cloud infrastructure. It details how to frame the contribution, build evidence (artifacts, baselines), and distinguish the work from similar top-tier venues like SOSP and NSDI.

A comprehensive guide detailing the mandatory and optional evaluation phases for academic security artifacts, such as those required for USENIX Security. It covers Phase-1 (availability) checks and Phase-2 (functionality, reproducibility) requirements. Provides best practices for structuring code, managing technical hazards (e.g., dangerous-by-default behavior), and ensuring verifiable, reproducible results for peer review.

Outlines the mandatory, multi-stage process for authors preparing final, camera-ready papers for USENIX Security. This guide covers critical post-acceptance steps, including de-anonymizing the manuscript, ensuring all mandated artifacts are permanently available (Open Science policy), updating ethical considerations, and meeting publication standards before final submission deadlines.

This guide covers the mandatory Open Science appendix for high-level security research. It instructs authors on enumerating all artifacts (code, datasets, configurations), documenting data withholding decisions, and implementing engineering controls (like environment pinning and version tracking) to ensure that published results are independently and reliably reproducible.

This guide outlines the strict formatting and structural guidelines for submitting security conference papers (like USENIX Security). It helps authors determine which material—core mechanisms, proofs, or supplementary data—must remain in the main body to guarantee review visibility, versus what can be safely demoted to optional appendices or external artifacts.

This detailed guide helps researchers determine the optimal top-tier venue (e.g., USENIX Security, IEEE S&P, ACM CCS) for their security research paper. It emphasizes that venue selection must be based on the committee's core expertise and the existence of reusable artifacts, measurements, or systems evidence, ensuring the work has the necessary technical depth to succeed.

A comprehensive guide detailing the standards for scientific reproducibility in visualization research, particularly for IEEE VIS submissions. It outlines the Graphics Replicability Stamp Initiative (GRSI) requirements, covering how independent volunteers must reproduce results using provided code, data, and environments (e.g., Docker containers). Learn how to package your work—including determinism aids, mapping tables, and licensed data—to pass rigorous, clean-machine testing.

This guide outlines the methodology for preparing research artifacts for rigorous academic reproducibility evaluations, such as those run by VLDB/SIGMOD. It details the required components—including prototype code, input data, workloads, and analysis scripts—to structure a comprehensive package. The goal is to ensure that any external evaluator can independently and flawlessly rebuild and validate all claimed results, maximizing the chances of winning reproducibility awards.

This comprehensive guide outlines the rigorous, multi-step process required for authors to finalize and submit their accepted papers for VLDB proceedings. It covers essential technical compliance points, including using the correct volume template, ensuring PDF/A compliance with embedded fonts, adhering to figure legibility rules, and detailing the permanent storage of research artifacts (DOI-backed). It also outlines the associated conference presentation obligations.

A comprehensive guide for creating the two required artifacts for a WACV paper: an anonymous package for double-blind review, and a public release post-acceptance. It emphasizes reproducing deployed system claims (latency, power, robustness) and maintaining consistency across revision rounds.

Provides comprehensive guidelines for packaging and submitting research artifacts (datasets, models, code) for major conferences. It details the difference between mere 'existence' (badge verification) and true academic 'reproducibility,' covering archival strategies, web data licensing, takedown resilience, and minimal viable package structure for long-term scholarly impact.