domains / families / research / mlsys-workflow

mlsys-workflow

separate

Use when planning an MLSys submission cycle end to end, from venue-fit and track choice through evaluation freeze, the October deadline, the four-day January response, notification, camera-ready, the March artifact-evaluation submission, and the May conference, with backward planning built around scarce GPU time and team ownership.

When to use

• planning an MLSys submission cycle
• venue-fit and track choice
• evaluation freeze planning
• October deadline management
• January response preparation
• notification and camera-ready planning
• March artifact-evaluation submission
• May conference logistics

When not to use

• ML-venue planning without shared hardware constraints

Skill page

Source