-
Notifications
You must be signed in to change notification settings - Fork 3
Contributing
Joel Morin - VE1ATM edited this page Nov 14, 2025
·
1 revision
Thank you for your interest in contributing to DVOACAP-Python! This guide will help you get started with contributing to the project.
- Development Setup
- How to Contribute
- Development Workflow
- Code Style Guidelines
- Testing Guidelines
- Reporting Bugs
- Maintain numerical accuracy with the original VOACAP/DVOACAP
- Provide clear, well-documented code
- Enable integration with the Python scientific ecosystem
- Make HF propagation modeling accessible to developers and researchers
git clone https://github.com/skyelaird/dvoacap-python.git
cd dvoacap-pythonpython -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activate
# Install core library pip install -e . # Install development dependencies pip install pytest pytest-cov # Or install everything at once pip install -e ".[all]"
# Test import python -c "from dvoacap import FourierMaps; print('Success!')" # Run tests pytest tests/ -v
Priority 1: Phase 5 Completion (Current Focus)
- Signal strength calculations
- Reliability calculation bug fixes
- Path loss modeling
- Noise and SNR calculations
- End-to-end integration testing
Priority 2: Testing
- Unit tests for existing modules
- Integration tests
- Validation against reference VOACAP data
- Edge case testing
- Increase code coverage to >80%
Priority 3: Documentation
- Code comments and docstrings
- Usage examples
- Tutorial notebooks
- API reference improvements
- Wiki page enhancements
Priority 4: Performance Optimization
- Profiling and bottleneck identification
- NumPy vectorization
- Caching strategies
- Memory optimization
Priority 5: Dashboard and Web Interface
- Dashboard UI/UX improvements
- Additional visualization features
- API endpoint enhancements
- Mobile responsiveness
- Multi-user service features
Priority 6: New Features
- Data visualization tools
- Additional antenna models
- Import/export utilities
- Integration with external APIs
- WSPR/PSKReporter validation
Bug Reports
- Found an issue? Open a GitHub issue with details
- See Reporting Bugs section
Bug Fixes
- Submit a pull request with the fix
- Include test case demonstrating the bug
New Features
- Discuss in an issue first
- Get feedback on approach
- Submit PR with implementation
Documentation
- Improvements always welcome
- Docstrings, examples, tutorials
- Wiki page updates
Tests
- Help us increase code coverage
- Add validation test cases
- Edge case testing
Examples
- Show others how to use the library
- Jupyter notebooks
- Real-world use cases
# Fork the repository on GitHub, then: git clone https://github.com/YOUR_USERNAME/dvoacap-python.git cd dvoacap-python git remote add upstream https://github.com/skyelaird/dvoacap-python.git
# For new features git checkout -b feature/your-feature-name # For bug fixes git checkout -b fix/your-bug-fix # For documentation git checkout -b docs/your-doc-update
Code Quality Checklist:
- Write clear, readable code
- Follow existing code style (PEP 8)
- Add docstrings to new functions/classes
- Include type hints where appropriate
- Update documentation if needed
- Add tests for new functionality
- Ensure all tests pass
# Run tests pytest tests/ -v # Check coverage pytest --cov=dvoacap tests/ # Run specific test file pytest tests/test_your_module.py -v
git add . git commit -m "Brief description of changes"
Commit Message Guidelines:
- Use present tense ("Add feature" not "Added feature")
- Keep first line under 72 characters
- Reference issue numbers when applicable
Examples:
Add noise modeling for Phase 5Fix virtual height calculation bug (#123)Update documentation for MUF calculatorRefactor ionospheric profile computation
git push origin feature/your-feature-name
Then open a Pull Request on GitHub with:
- Clear description of changes
- Reference to related issues
- Test results (if applicable)
- Before/after examples (if applicable)
PR Template:
## Description Brief description of what this PR does ## Related Issues Fixes #123 Relates to #456 ## Changes Made - Added feature X - Fixed bug Y - Updated documentation Z ## Testing - [ ] All existing tests pass - [ ] Added new tests - [ ] Validated against reference data ## Checklist - [ ] Code follows style guidelines - [ ] Documentation updated - [ ] Tests added/updated - [ ] All tests passing
We follow PEP 8 with some flexibility:
# β Good: Clear variable names critical_frequency = 10.5 # MHz solar_zenith_angle = 0.3 # radians # β Good: Type hints from typing import List, Tuple, Optional def compute_muf( frequency: float, layer: LayerInfo ) -> float: """Compute Maximum Usable Frequency. Args: frequency: Operating frequency in MHz layer: Ionospheric layer parameters Returns: MUF in MHz """ pass # β Good: Docstrings for classes class IonosphericProfile: """Represents complete ionospheric electron density profile. This class models the electron density as a function of height using quasi-parabolic segments for each ionospheric layer. Attributes: e: E layer parameters f1: F1 layer parameters f2: F2 layer parameters """ pass
Module-level:
"""Path geometry calculations for HF propagation. This module provides utilities for great circle path calculations, geodetic/geocentric conversions, and path midpoint determination. """
Function-level:
def compute_critical_frequency(zenith_angle: float, ssn: int) -> float: """Compute E layer critical frequency. Uses the empirical formula from Davies (1990) to compute foE based on solar zenith angle and solar activity level. Args: zenith_angle: Solar zenith angle in radians (0 = overhead) ssn: Smoothed sunspot number (0-200) Returns: Critical frequency in MHz (typically 1-4 MHz) Raises: ValueError: If zenith_angle > Ο/2 (sun below horizon) Example: >>> compute_critical_frequency(0.3, 100) 3.15 References: Davies, K. (1990). Ionospheric Radio. Chapter 3. """ pass
-
snake_casefor functions and variables -
PascalCasefor classes -
UPPER_CASEfor constants - Descriptive names (avoid single letters except in math formulas)
Examples:
# β Good MAX_FREQUENCY = 50.0 # MHz critical_frequency = compute_fof2(lat, lon) class FourierMaps: pass # β Bad mf = 50.0 cf = calc(x, y) class fourier_maps: pass
# tests/test_your_module.py import pytest from dvoacap import YourModule def test_basic_functionality(): """Test basic functionality of YourModule.""" result = YourModule.compute(input_value) assert result == expected_value def test_edge_case(): """Test edge case handling.""" with pytest.raises(ValueError): YourModule.compute(invalid_input) def test_accuracy(): """Test against reference data.""" reference_value = 10.5 # From VOACAP computed_value = YourModule.compute(test_input) assert abs(computed_value - reference_value) < 0.1
- Aim for >80% code coverage
- Test normal cases
- Test edge cases
- Test error handling
- Test integration points
When porting modules from original VOACAP/DVOACAP:
- Generate reference data from original code
- Run your Python implementation with same inputs
- Compare results and document tolerances
- Add validation tests to test suite
Example:
def test_against_voacap_reference(): """Validate against VOACAP reference data.""" # Load reference data ref_data = load_reference_data("test_cases/muf_reference.csv") # Run our implementation for case in ref_data: result = compute_muf(case.inputs) # Allow 0.1 MHz tolerance assert abs(result - case.expected) < 0.1
When reporting bugs, please include:
- Description: Clear description of the issue
- Steps to Reproduce: Minimal example demonstrating the bug
- Expected Behavior: What should happen
- Actual Behavior: What actually happens
- Environment: Python version, OS, package versions
- Error Messages: Full error traceback if applicable
Example:
## Bug Description MUF calculator returns NaN for high latitude paths ## Steps to Reproduce ```python from dvoacap import MufCalculator, PathGeometry path = PathGeometry() path.set_tx_rx_degrees(80, 0, 85, 10) # Arctic path muf = MufCalculator(path, ...) result = muf.compute_circuit_muf() # Returns NaN
Valid MUF value (e.g., 15.2 MHz)
NaN
- Python 3.9.7
- dvoacap-python 0.5.0
- Linux Ubuntu 20.04
(paste full traceback here)
---
## Code Review Process
All contributions go through code review:
1. **Automated checks**: Tests and linting must pass
2. **Peer review**: At least one maintainer reviews the code
3. **Feedback**: Address review comments
4. **Approval**: Once approved, code is merged
### What Reviewers Look For
- Code correctness and accuracy
- Test coverage
- Documentation quality
- Code style consistency
- Performance considerations
- Integration with existing code
---
## Communication
- **GitHub Issues**: Bug reports, feature requests, questions
- **Pull Requests**: Code contributions and discussions
- **Discussions**: General questions and ideas
---
## License
By contributing, you agree that your contributions will be licensed under the MIT License, consistent with the project's license.
The original DVOACAP code is licensed under Mozilla Public License Version 1.1. Our Python implementation is a clean-room reimplementation released under MIT License.
---
## Resources for New Contributors
### Understanding VOACAP
- [VOACAP Documentation](https://www.voacap.com/)
- [ITU-R P.533 HF Propagation](https://www.itu.int/rec/R-REC-P.533/)
- Davies, K. (1990). "Ionospheric Radio" - Classic reference book
### Understanding the Ionosphere
- [NOAA Space Weather Prediction Center](https://www.swpc.noaa.gov/)
- [IPS Radio and Space Services](https://www.sws.bom.gov.au/)
### Python Scientific Computing
- [NumPy Documentation](https://numpy.org/doc/)
- [SciPy Documentation](https://docs.scipy.org/)
- [pytest Documentation](https://docs.pytest.org/)
### DVOACAP-Python Documentation
- [Architecture](Architecture) - System design and structure
- [API Reference](API-Reference) - Complete API documentation
- [Validation Status](Validation-Status) - Testing and accuracy
- [Troubleshooting](Troubleshooting) - Common issues and solutions
---
## Current Priorities
See [NEXT_STEPS.md](https://github.com/skyelaird/dvoacap-python/blob/main/NEXT_STEPS.md) for the detailed development roadmap.
**Immediate needs:**
1. Fix Phase 5 reliability calculation bug
2. Expand reference test suite
3. Improve documentation
4. Performance optimization
---
## Questions?
If you have questions about contributing:
- Open a GitHub issue with the "question" label
- Check existing issues and documentation first
- Be patient - maintainers are volunteers
---
Thank you for contributing to DVOACAP-Python! Your efforts help make HF propagation modeling accessible to everyone. π» 73!