API Reference
This section provides comprehensive API documentation for all modules, classes, and functions in ibleatools.
Package Overview
ibleatools is organized into several core modules, each providing specific functionality for electrophysiological data analysis:
ephysatlas: Main package containing all modules
features: Feature extraction and computation
plots: Visualization and plotting utilities
reveal: High-level analysis and figure generation
utils: Utility functions and data management
anatomy: Brain region classification
regionclassifier: Machine learning models
data: Data loading and management
Module Documentation
Core Modules
Quick Reference
Common Functions
Feature Extraction:
ephysatlas.feature_computation.compute_features_from_pid()/compute_features_from_file()OOP calculators:
ephysatlas.feature_calculators.IBLPIDFeatureCalculator,SpikeGLXFileFeatureCalculatorVisualization:
ephysatlas.reveal.AtlasRevealData Loading:
ephysatlas.data.load_raw_data()Utilities:
ephysatlas.utils.setup_output_directory()
Data Types
Features:
ephysatlas.features.ModelRawFeaturesParameters:
ephysatlas.features.DartParametersTransformers:
ephysatlas.features.EphysTransformer
Configuration
Schemas: Pandera-based data validation schemas
Parameters: Configurable parameters for all major functions
Defaults: Sensible defaults for common use cases
Usage Patterns
Basic Workflow:
Load data using a PID
Extract features using appropriate functions
Visualize results with plotting functions
Save outputs for further analysis
Advanced Workflow:
Customize parameters for specific needs
Use transformers for data preprocessing
Generate comprehensive figures with AtlasReveal
Apply machine learning models for classification
Data Management:
Set up output directories with utilities
Manage metadata and file organization
Aggregate results across multiple experiments
Export data in various formats
Examples
For practical examples and step-by-step guides, see the How-to Guides section.
Getting Help
Documentation: This reference guide
Examples: Code examples in the How-to Guides section
Source Code: Full source code with detailed docstrings
Issues: Report bugs or request features on the project repository
Contributing
Code Style: Follow PEP 8 and use Google Style docstrings
Documentation: Keep docstrings up to date with code changes
Testing: Add tests for new functionality
Examples: Provide examples for new features