Description
DVC params commands help you track and compare parameters (hyperparameters, configuration values) across different experiments and commits. Parameters are typically stored in YAML, JSON, TOML, or Python files and define model training configurations.Subcommands
params diff
Show changes in params between commits in the DVC repository, or between a commit and the workspace.Arguments
Old Git commit to compare (defaults to HEAD).
New Git commit to compare (defaults to the current workspace).
Options
Specific params file(s) to compare (even if not found as
params in dvc.yaml). Shows all tracked params by default.Show unchanged params as well.
Show only params that are stage dependencies.
Show output in JSON format.
Show tabulated output in the Markdown format (GFM).
Don’t show params path.
Examples
Basic Parameter Comparison
Compare Specific Files
Show Only Changed Parameters (Default)
Include Unchanged Parameters
JSON Output for Automation
Show Only Stage Dependencies
The
--deps flag is useful when you have many parameters but only want to see those that affect pipeline execution.Parameter File Formats
DVC supports multiple parameter file formats:YAML
YAML
params.yaml
JSON
JSON
params.json
TOML
TOML
params.toml
Python
Python
params.py
Use Cases
Hyperparameter Tracking
Track how hyperparameters change across experiments and their impact on metrics.
Experiment Comparison
Compare parameter configurations between different experiment runs.
Reproducibility
Ensure exact parameter values are recorded for reproducing results.
Configuration Management
Manage different configurations for development, staging, and production.
Related Commands
dvc metrics- Compare metrics across experimentsdvc plots- Visualize how parameters affect outcomesdvc exp show- Show both params and metrics together