How orcasound/orcanode works
Main Components
a. Hardware Layer:
• Sound Input Devices (Hydrophones)
• Computing Platforms (Raspberry Pi/AMD64 systems)
• Sound Cards (e.g., Pisound HAT)
b. Container Infrastructure:
• Docker containers for different services
• Base images for different architectures (ARM32v7, AMD64)
c. Audio Processing Pipeline:
• Audio Capture (ALSA/Jack)
• FFmpeg Processing
• File Generation Systems
d. Storage Systems:
• Local Storage (/tmp and /mnt directories)
• Cloud Storage (AWS S3 buckets)
e. Monitoring & Logging:
• LogDNA integration
• System monitoring
[Hardware Layer]
• ↓
[Container Layer]
• ↓
[Audio Processing]
• ↓
[Storage Layer]
• ↓
[Monitoring Layer]
Key Relationships
• Data Flow:
• Audio input → FFmpeg processing
• Processed audio → Local storage
• Local storage → S3 bucket synchronization
• System logs → LogDNA
• Component Integration:
• Docker container relationships
• Storage system interactions
• Monitoring system connections
Technical Details
• FFmpeg pipeline configuration
• AWS S3 integration points
• Docker container relationships
• Audio format conversion paths
The monitoring and logging infrastructure
Use standardized symbols:
• Rectangles for processing components
• Hexagons for input/output points
• Clouds for external services
This system design should capture both the current implementation and allow for future expansions, such as new audio format support or additional node types.