MetaPulsar Troubleshooting Guide
Common Issues
Installation Issues
Import Errors
Problem: ModuleNotFoundError: No module named 'metapulsar'
Solutions:
Check Python path:
import sys print(sys.path)
Reinstall package:
pip uninstall metapulsar pip install -e .
Check virtual environment:
which python pip list | grep metapulsar
Missing Dependencies
Problem: ImportError: No module named 'enterprise'
Solutions:
Install all dependencies:
pip install -e ".[dev,libstempo,analysis]"
Check specific dependency:
import enterprise print(enterprise.__version__)
Runtime Issues
File Not Found
Problem: FileNotFoundError when discovering files
Solutions:
Check PTA registry configuration
Verify file patterns match actual files
Ensure base directories exist
Parameter Consistency Errors
Problem: ParameterInconsistencyError
Solutions:
Check parameter names across PTAs
Verify parameter units
Use composite strategy if consistency not needed
Performance Issues
Slow File Discovery
Solutions:
Use specific PTA names instead of all PTAs
Pre-filter data when possible
Cache frequently used objects
Memory Issues
Solutions:
Use appropriate data types
Clean up large objects
Process data in chunks
Getting Help
Check this troubleshooting guide
Review examples in
examples/directoryCheck API documentation
Report issues on GitHub
FAQ
Q: What’s the difference between composite and consistent strategies?
A: Composite strategy preserves PTA-specific parameter differences, while consistent strategy aligns parameters to a reference PTA for astrophysical consistency.
Q: How do I add a custom PTA?
A: Use the FileDiscoveryService.add_pta() method with a configuration dictionary containing file patterns and settings.
Q: Can I use MetaPulsar without Enterprise?
A: Yes, MetaPulsar is a standalone package. Enterprise integration is optional but recommended for gravitational wave analysis.
Q: How do I handle missing data files?
A: MetaPulsar gracefully handles missing files by filtering out PTAs with no data before creating MetaPulsar objects.
Q: What timing packages are supported?
A: MetaPulsar supports both PINT and TEMPO2 timing packages through the timing_package configuration option.