Skill UI

This comprehensive guide provides strict structural and technical guidelines for authors submitting papers to ACM SoCC. It mandates focusing on cloud-scale problems recognized by operators, emphasizing contributions at the intersection of systems and data. Key requirements include reporting tail latency (p95/p99) and concrete cost models, grounding every claim in measured, real-world evidence, and explicitly stating external limitations.

This guide provides a rigorous methodology for achieving scientific reproducibility in technical and user experience papers (e.g., UIST). It details three essential 'ledgers': the Build Ledger (pinning software, hardware, and environment dependencies), the Measurement Ledger (defining precise protocols for metrics like latency and accuracy), and the Study Ledger (documenting human evaluation tasks). Following these protocols ensures that external researchers can accurately rebuild the artifact and validate reported results.

This comprehensive guide provides researchers with structured methodologies for designing and auditing Computer Vision (CV) experiments for major conferences like WACV. It details the critical differences between the Applications and Algorithms tracks, emphasizing the need to report performance under real deployment constraints (e.g., power, latency) and ensuring fair, rigorous comparisons with baselines. Ideal for revising submissions to meet high review standards.

A comprehensive guide for strengthening the reproducibility of academic papers, especially those involving systems claims (e.g., power usage, latency). It details maintaining a 'recipe ledger' for all reported metrics, ensuring constraint-aware measurement of environmental variables, and managing data/artifact consistency across the entire two-round revision process.

This skill provides a methodical approach to system performance troubleshooting and root-cause analysis using Brendan Gregg's USE and TSA methodologies. It guides users through evidence-backed investigation steps, from initial triage to detailed thread state analysis, ensuring every claim is supported by metrics. Ideal for SREs and DevOps engineers debugging latency, CPU, memory, or network issues on Linux systems, culminating in structured RCA reports or postmortems.