save command saves the current project state by creating a checkpoint that includes models, configurations, and optionally data and logs.
Usage
Options
| Option | Type | Default | Description |
|---|---|---|---|
--name | string | checkpoint_{timestamp} | Name for the checkpoint |
--include-data | flag | false | Include data directory in the checkpoint |
--include-logs | flag | false | Include logs directory in the checkpoint |
--output-dir | string | checkpoints | Output directory for checkpoints |
Checkpoint Contents
A checkpoint always includes:- models/: All saved model files
- configs/: Configuration files (or
config.jsonif it exists) - metadata.json: Checkpoint information (timestamp, name, Neurenix version, options)
- data/: Training/validation data (with
--include-data) - logs/: Training logs (with
--include-logs)
Examples
Save basic checkpoint
Save with custom name
Save with data and logs
Save to custom directory
Full backup before deployment
Checkpoint Metadata
Each checkpoint includes ametadata.json file with information about the save:
Use Cases
1. Save training milestones
Save checkpoints at key training milestones:2. Version control for models
Create versioned checkpoints for model iterations:3. Pre-deployment backup
Create a full backup before deploying to production:4. Experiment tracking
Save results of different experiments:Restoring from Checkpoint
To restore a project from a checkpoint, copy the contents back to your project directory:Best Practices
1. Use descriptive names
Give checkpoints meaningful names that indicate their purpose:2. Regular checkpoints during long training
Save periodic checkpoints during extended training sessions:3. Include data for reproducibility
When saving experiment results, include data to ensure reproducibility:4. Clean up old checkpoints
Regularly remove outdated checkpoints to save disk space:See Also
- Run command - Train models
- Export command - Export to different formats
- Optimize command - Optimize saved models