How yashkarthik/where_is_my_ion works
Project type and purpose
• The software side parses static GTFS schedules and realtime GTFS‑RT feeds (via Protocol Buffers), computes LED on/off or count per segment, and sends commands to the hardware.
• The hardware side is a KiCad‑designed driver board (EDA/gerbers, .kicad_sch) with LED drivers and connectors for station and inter‑station LEDs.
File structure
─ Top level:
• GRT GTFS/…txt – raw schedule (static) data.
• eda/… – PCB design files and Gerber outputs.
• src/ – C++ application: CMakeLists.txt, main.cpp, GTFS‑PROTO, loader header, and generated .pb.cc/.pb.h files.
─ Build & config:
• Root CMakeLists.txt and src/Makefile drive compilation.
• .clangd hints at IDE integration.
• gtfs-realtime.proto → generates gtfs-realtime.pb.cc/.h.
─ Outputs:
• src/a.out, main.o, out.txt suggest a CLI tool that produces test logs or output.
README for additional insights
─ The README lists LED‑to‑driver assignments, counts for station and inter‑station LEDs, and a logical network topology.
─ It defines the mapping between physical rails/stations and drivers on the board.
Detail
• Number of LEDs per segment alongside the hardware outputs.