Rtk Wave Buoy
D 55 completed
Other
unknown / c · tiny
30
Files
6,951
LOC
0
Frameworks
4
Languages
Pipeline State
completedRun ID
#1534294Phase
doneProgress
0%Started
2026-04-16 14:55:50Finished
2026-04-16 14:55:50LLM tokens
0Pipeline Metadata
Stage
SkippedDecision
skip_scaffold_dupNovelty
22.28Framework unique
—Isolation
—Last stage change
2026-04-16 18:15:42Deduplication group #47402
Member of a group with 513 similar repo(s) — canonical #1443114 view group →
Repobility · code-quality intelligence · https://repobility.com
🧪 Code Distillation
Browse all specs →AI Prompt
Create a system for a centimeter-level precision GPS data logging marine buoy. The core functionality needs to handle RTK GPS positioning by receiving corrections via NTRIP over cellular networks using an ESP32 and SIM7000 LTE module. It must log high-precision GPS data and IMU measurements to an SD card using an OpenLog Artemis data logger. The system should interface the ZED-F9P RTK GPS receiver with both the OpenLog Artemis (via I2C at 0x42) and the ESP32. I also need Python scripts to parse UBX files into CSV, and potentially MATLAB scripts for data processing.
c arduino esp32 rtk-gps imu gnss data-logging ntrip python serial
Generated by gemma4:latest
Catalog Information
Create a system for a centimeter-level precision GPS data logging marine buoy. The core functionality needs to handle RTK GPS positioning by receiving corrections via NTRIP over cellular networks using an ESP32 and SIM7000 LTE module. It must log high-precision GPS data and IMU measurements to an SD card using an OpenLog Artemis data logger. The system should interface the ZED-F9P RTK GPS receiver with both the OpenLog Artemis (via I2C at 0x42) and the ESP32. I also need Python scripts to parse
Tags
c arduino esp32 rtk-gps imu gnss data-logging ntrip python serial
Quality Score
D
55.1/100
Structure
43
Code Quality
70
Documentation
59
Testing
0
Practices
68
Security
100
Dependencies
80
Strengths
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No tests found — high risk of regressions
- No CI/CD configuration — manual testing and deployment
- 1 'god files' with >500 LOC need decomposition
Recommendations
- Add a test suite — start with critical path integration tests
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Symbols
function22
macro5
struct5
Embed Badge
Add to your README:
