Apollo is a comprehensive autonomous driving platform developed by Baidu, providing a full software stack for self-driving vehicles. The repository contains a modular architecture built on Cyber RT, a high-performance runtime framework optimized for autonomous driving scenarios with low latency and high throughput. Key modules include perception (camera, LiDAR, radar, sensor fusion), planning (scenario-based with multiple planners), control (PID, LQR, MPC controllers), localization (RTK, NDT, MSF), prediction, routing, and V2X communication. The system integrates with hardware through extensive driver support for various sensors (Velodyne, Hesai, Continental radar, Mobileye, etc.) and vehicle platforms (Lincoln, Lexus, Geely, etc.). Dreamview provides a web-based visualization and monitoring interface. The codebase demonstrates strong engineering practices with clear module boundaries, extensive configuration management, comprehensive testing infrastructure, and support for both x86_64 and ARM64 (Orin) platforms. Recent versions introduce package management for easier deployment, Dreamview Plus for enhanced developer experience, and cloud-based model training services (Apollo Fuel).
FishNet is a comprehensive Unity multiplayer networking framework providing a full client-server architecture with RPCs, sync types, prediction, scene management, observer conditions, and multiple transport backends (LiteNetLib, Synapse, Yak). It employs IL code generation via Mono.Cecil to auto-generate serializers and RPC stubs, achieving high performance and low bandwidth usage. The codebase is well-structured with extensive use of partial classes, pools, and utility patterns. It includes demos for authentication, prediction, collider rollback, and scene management. While the framework is tightly coupled to Unity, many utility components (e.g., object pooling, ring buffers, quaternion compression) are reusable in isolation and demonstrate strong engineering craftsmanship. The project is actively maintained with a large community and regular commits.
BatteryRecorder is an Android application for precise battery power recording and battery life prediction. It consists of a main app module with Jetpack Compose UI and a native server daemon that reads battery data directly from sysfs and dumpsys via JNI. The architecture follows a multi-module structure (app, server, shared) with AIDL-based IPC between the app and the privileged background server. The app provides real-time monitoring, historical charts, per-app and per-scenario battery endurance predictions, calibration settings, and export/import capabilities. It is a sophisticated tool aimed at power users and developers, but it relies on device-specific sysfs paths and hidden Android APIs, making it fragile across different devices and Android versions. The codebase demonstrates solid use of modern Android patterns (ViewModel, StateFlow, UseCase, Repository) and custom Compose components, though it lacks automated tests and has mixed-language documentation.
This repository implements an end-to-end predictive modeling pipeline for Premier League football match outcomes (home win, draw, away win). It ingests raw match statistics from the api-football.com REST API, processes JSON data into structured DataFrames, engineers features using rolling averages (5- and 10-game windows) and team-vs-opponent differentials, trains multiple classifiers (Random Forest, SVM, KNN, MLP) with hyperparameter tuning, and serves live predictions via a Flask web application. The dominant character is data research: the primary deliverable is a set of trained models and an analytical pipeline, with the web server being a secondary deployment artifact. The best-performing model is a Random Forest achieving ~50-51% test accuracy, demonstrating that football outcomes are modestly predictable from historical statistics. The codebase includes modular helper modules for feature engineering, data scaling, and evaluation plotting that are reusable for other sports or time-series classification tasks. However, the project suffers from hardcoded absolute paths, outdated dependencies (Python 3.7, sklearn 0.23.1), plain-text API keys in the repository, and a static dataset that will drift over time.