Skip to main content

cirron plan

Generate execution plans for Cirron operations (compile, build) and save, compare, or replay them. Plans show what will be executed, estimated resources, and potential issues without running anything.

Usage

Commands

CommandDescription
compileGenerate compilation plan for ML models
buildGenerate build plan for ML projects
diffCompare two saved plans
saveSave plans for future reference
replayExecute a saved plan from file

Options (compile / build)

OptionDescriptionDefault
--arch, -aTarget architecture (cpu, cuda, gpu)Auto-detected
--indexPath to index/manifest filenull
--validateRun validation checks during planningfalse
--saveSave plan to filefalse
--jsonOutput plan in JSON formatfalse
--verboseShow detailed plan informationfalse
-i, --interactiveEnhanced planning with save optionsfalse

Plan compile / build

Validation covers required files (src/model.py, requirements.txt), architecture-specific checks (e.g. CUDA availability), framework compatibility, and dependency resolution. The plan reports environment setup, dependency resolution, model compilation/build, architecture-specific optimization, and artifact generation steps.

Plan diff

Compare two saved plans to identify added/removed/changed/unchanged configurations and dependencies.
Example diff:

Plan save

OptionDescriptionDefault
--allSave all plan types (compile, build)false
--name <filename>Custom filenameAuto-generated
--description <desc>Description for the plan-
--tags <tags>Comma-separated tags-
--listList all saved plansfalse
--cleanup [days]Remove plans older than N days30
--verboseDetailed save outputfalse
--jsonJSON outputfalse
Plans are stored in ~/.cirron/plans/ with timestamp, description, tags, command type, and framework metadata.

Plan replay

OptionDescriptionDefault
--plan <file>Plan file to replay (required)-
--validateValidate environment compatibilitytrue
--dry-runShow what would be executed without runningfalse
--verboseDetailed execution informationfalse
--forceForce replay despite compatibility warningsfalse

Examples

Output Formats

Troubleshooting

ErrorResolution
No cirron.yaml foundcirron init my-project
Invalid plan filesRegenerate with cirron plan compile --save new-plan.json
Use descriptive names and tags, save baselines before major changes, and clean up old plans regularly with --cleanup. Use --json for programmatic processing in CI/CD pipelines.