Overview
This page documents all available command-line options for theheartmap command. All options are optional unless marked as required.
Positional Arguments
Path to the input single-cell data file.Supported formats:
.h5ad- AnnData format (recommended).h5- HDF5 format
Optional Arguments
—analysis-type
Type of analysis pipeline to run.Choices:
basic- Basic preprocessing, clustering, and annotationadvanced- Advanced communication analysis with ligand-receptor interactionsmulti_chamber- Multi-chamber specific analysis for cardiac datacomprehensive- Complete analysis with all components
comprehensiveExample:—output-dir
Output directory for saving analysis results.The directory will be created if it doesn’t exist. All output files including processed data, plots, and analysis results will be saved here.Default:
resultsExample:—config
Path to a custom configuration file in YAML format.If not provided, default configuration will be used. The config file allows you to customize analysis parameters such as filtering thresholds, normalization methods, and clustering parameters.Default: Uses built-in default configurationExample:Sample config file:
-h, —help
Show help message and exit.Example:Output:
Usage Examples
Minimal Command
Run with all default settings:- Run comprehensive analysis (default)
- Save results to
./results(default) - Use default configuration
Complete Command
Specify all options:Analysis Type Comparison
Basic Analysis
- Duration: ~5-10 minutes (for typical dataset)
- Includes: QC, normalization, clustering, basic annotation
- Output size: ~100-500 MB
Advanced Analysis
- Duration: ~15-30 minutes
- Includes: Basic analysis + cell-cell communication analysis
- Output size: ~500 MB - 1 GB
Multi-Chamber Analysis
- Duration: ~20-40 minutes
- Includes: Chamber-specific marker identification and composition analysis
- Output size: ~500 MB - 1 GB
Comprehensive Analysis
- Duration: ~30-60 minutes
- Includes: All analysis components (basic + advanced + multi-chamber)
- Output size: 1-2 GB
Configuration File Format
The--config option accepts YAML configuration files. Here’s a complete example:
Environment Variables
HeartMAP CLI respects the following environment variables:HEARTMAP_CONFIG: Default configuration file pathHEARTMAP_DATA_DIR: Default data directoryHEARTMAP_CACHE_DIR: Cache directory for downloaded resources
Common Issues
File Not Found
FileNotFoundError: nonexistent.h5ad not found
Solution: Verify the file path is correct and the file exists.
Invalid Analysis Type
error: argument --analysis-type: invalid choice: 'invalid'
Solution: Use one of the valid choices: basic, advanced, multi_chamber, or comprehensive.
Invalid Configuration
ConfigurationError: Invalid configuration file
Solution: Check your YAML syntax and ensure all required fields are present.
See Also
- CLI Commands - Overview of CLI commands and examples
- Python API - Using HeartMAP from Python
- Configuration Reference - Complete configuration documentation