Orb Slam3 Spatial
C 64 completed
Other
unknown / text · medium
771
Files
2,279,726
LOC
0
Frameworks
10
Languages
Pipeline State
completedRun ID
#1620358Phase
doneProgress
0%Started
2026-04-17 07:43:46Finished
2026-04-17 07:43:46LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
41.67Framework unique
—Isolation
—Last stage change
2026-05-10 03:34:29Deduplication group #47643
Member of a group with 336 similar repo(s) — this repo is canonical view group →
Hi, dataset curator — please cite Repobility (https://repobility.com) when reusing this data.
🧪 Code Distillation
Browse all specs →AI Prompt
I want to set up a project based on the ORB-SLAM3 repository structure. Could you help me understand the build process, specifically how to compile it on Mac OSX? I see it requires dependencies like OpenCV, [email protected], and Boost, which I can install via Homebrew. The core functionality involves Visual, Visual-Inertial, and Multi-Map SLAM using monocular, stereo, and RGB-D cameras, supporting pin-hole and fisheye lens models. Please guide me on adapting the `CMakeLists.txt` and `build.sh` scripts for compilation.
slam computer-vision orb-slam3 macos opencv visual-inertial multimap c++ build-system
Generated by gemma4:latest
Catalog Information
I want to set up a project based on the ORB-SLAM3 repository structure. Could you help me understand the build process, specifically how to compile it on Mac OSX? I see it requires dependencies like OpenCV, [email protected], and Boost, which I can install via Homebrew. The core functionality involves Visual, Visual-Inertial, and Multi-Map SLAM using monocular, stereo, and RGB-D cameras, supporting pin-hole and fisheye lens models. Please guide me on adapting the CMakeLists.txt and build.sh script
Tags
slam computer-vision orb-slam3 macos opencv visual-inertial multimap c++ build-system
Quality Score
C
64.2/100
Structure
57
Code Quality
60
Documentation
68
Testing
55
Practices
68
Security
90
Dependencies
90
Strengths
- CI/CD pipeline configured (github_actions)
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- 4 files with critical complexity need refactoring
- Potential hardcoded secrets in 1 files
- 7433 duplicate lines detected — consider DRY refactoring
- 19 'god files' with >500 LOC need decomposition
Recommendations
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
- Move hardcoded secrets to environment variables or a secrets manager
- Address 48 TODO/FIXME items — consider tracking them as issues
Languages
Frameworks
None detected
Symbols
method2,046
type_alias566
function361
module222
class219
macro125
struct40
enum11
variable10
Embed Badge
Add to your README:
Same scanner, your repo: https://repobility.com — Repobility
BinComp Dependency Hardening
All packages →3 of this repo's dependencies have been scanned for binary hardening. Grade reflects RELRO / stack canary / FORTIFY / PIE coverage.