Usage: Copy this template when creating new modules. Replace placeholder text with actual content.
Brief description of what this module does and its role in the FUSION project.
Example: This module handles network topology generation and management for optical network simulations.
core.py: [Description of main functionality]utils.pyorutils/: [Description of utility functions]constants.py: [Module-specific constants]errors.py: [Custom exceptions for this module]
registry.py: [Component registry - only if needed for multi-component modules]config.py: [Module-specific configuration handling]
from fusion.[module_name] import [main_class_or_function]
# Example usage
example = MainClass(config_params)
result = example.primary_method()# More complex examplesfusion.core.config: Configuration managementfusion.utils.logging: Logging utilities- [Other internal modules]
numpy: [Why this is needed]pathlib: Path handling- [Other external packages]
# Example configuration structure
config = {
"module_setting": "value",
"another_setting": 42
}FUSION_MODULE_DEBUG: Enable debug mode for this module- [Other environment variables]
Unit tests are located in tests/ directory:
# Run module tests
pytest fusion/[module_name]/tests/
# Run with coverage
pytest --cov=fusion.[module_name] fusion/[module_name]/tests/MainClass: [Brief description]HelperClass: [Brief description]
primary_function(): [Brief description]utility_function(): [Brief description]
# Code example showing typical usage# Code example showing complex scenarios- [Important design choices and rationale]
- [Why certain patterns were chosen]
- [Current limitations or constraints]
- [Future improvement areas]
- [Performance tips or warnings]
- [Memory usage considerations]
- Replace [Module Name] with actual module name
- Purpose section: 2-3 sentences max, be specific
- Key Components: List only files that actually exist
- Usage examples: Real, working code examples
- Dependencies: Only list actual dependencies with reasons
- Remove template notes section when done
- Architecture: For complex modules with multiple components
- Algorithms: For modules implementing specific algorithms
- Integration: How this module integrates with others
- Troubleshooting: Common issues and solutions
- Concise: Each section should be scannable
- Examples: Always include working code examples
- AI-friendly: Clear structure for Claude to understand
- Actionable: Tell readers exactly what they can do