Repository reference
File by file breakdown of the repo. This reference turns the cuda-doctor repository into navigable documentation. Each file gets its own explanation, its role in the system, its neighbors, and the search terms that should surface it when users are hunting for edge cases.
Implemented
24
Files with executable logic or active configuration already present.
Meta
3
Product, packaging, or repo-level files that define the project contract.
Placeholders
28
Empty files that still matter because they document planned architecture.
Reference map
Browse the repository by subsystem. Each group expands into repo-specific subsections, then down to the tracked files that power that part of the system.
Project root
Product contract, build metadata, and repo-wide policy files.
5 files ▾
Overview
Start with the product brief and repository contract.
1 ▾
Build and packaging
Native build graph and Python packaging entry points.
2 ▾
Repository policy
Ignore rules and licensing metadata for the whole project.
2 ▾
Python wrapper
The Python CLI entry point, config surface, and output formatting layer.
6 files ▾
Entry points
Package marker and the Python CLI command surface.
2 ▾
Configuration
Default values and runtime settings for the Python wrapper.
2 ▾
Output
Terminal printing and report shaping for Python-facing flows.
2 ▾
Native commands
CLI routing plus the implemented and planned command handlers.
8 files ▾
Entry point
Top-level native executable dispatch.
1 ▾
Check command
Interface and implementation for inspection-only checks.
2 ▾
Doctor command
Interface and implementation for diagnosis and repair flows.
2 ▾
Planned commands
Reserved files for build, setup, and validate behaviors.
3 ▾
Native core
System probing, process execution, compatibility logic, and build helpers.
16 files ▾
Reporting and process
Core report types and subprocess execution primitives.
3 ▾
Platform and hardware detection
Host, driver, GPU, and CUDA environment discovery.
8 ▾
Repair and build helpers
Configuration, repo patching, and builder orchestration.
5 ▾
Kernels and UI
CUDA smoke workloads plus the terminal-facing reporting layer.
9 files ▾
Elementwise kernel
Simple elementwise CUDA sample and shared declarations.
2 ▾
Memory benchmark
Memory transfer benchmarking kernels and declarations.
2 ▾
Reduction kernel
Reduction sample kernels and matching headers.
2 ▾
UI layer
Terminal placeholders and native report rendering.
3 ▾
Automation and tests
Bootstrap scripts, reproducible environments, tests, and vendor placeholders.
11 files ▾
Automation
Bootstrap helpers and Docker environments for local reproduction.
3 ▾
C++ tests
Native coverage for CUDA environment, driver, and GPU probes.
3 ▾
Python tests
CLI, configuration, and report-output verification in Python.
3 ▾
Vendored placeholders
Reserved directories for future third-party dependencies.
2 ▾