How naveens007/slalom works
SLALOM is a fixed-time radiosity benchmark: it reads box and optical properties, subdivides the box into patches, builds and solves the radiosity system, writes patch radiosities, and reports timing and operation counts. The frozen C reference is accompanied by Python, Java, and TypeScript ports; the optional C++ scaffold does not yet run the benchmark. The Java timing orchestrator and several of its calls are visible in the excerpts. Other language-level connections are limited to README documentation and the SOURCE INDEX, so the graph avoids guessing at their internal call flow.
Main entry points: Meter.java Benchmark meter · Geometry.java Patch geometry · slalom.c C benchmark · Slalom.java Java entry
Components 23
C reference
- C driver
src/sl-driver.c - C benchmark
src/slalom.c - Machine report
src/system_info.c
Java port
- Java entry
src/java/Slalom.java - Benchmark meter
src/java/Meter.java - Problem reader
src/java/Problem.java - Patch geometry
src/java/Geometry.java - Box faces
src/java/Face.java - Surface patches
src/java/Patch.java - Radiosity solver
src/java/RadiositySystem.java - Answer writer
src/java/Storer.java - Machine report
src/java/MachineReport.java
Other implementations
- Python benchmark
src/slalom.py - TypeScript entry
src/ts/Slalom.ts - TypeScript driver
src/ts/driver.ts - TypeScript benchmark
src/ts/benchmark.ts - TypeScript geometry
src/ts/geometry.ts - TypeScript solver
src/ts/solver.ts - Machine report
src/ts/machineInfo.ts - C++ scaffold
src/cpp/slalom-cxx.cpp
Benchmark data
- geom input
src/geom - answer output
Other components
- Benchmark user
Connections 29
- Benchmark user → C driver: runs benchmark
README.md - Benchmark user → Python benchmark: runs port
README.md - Benchmark user → Java entry: runs port
README.md - Benchmark user → TypeScript entry: runs port
README.md - Benchmark user → C++ scaffold: builds scaffold
README.md - C driver → C benchmark: starts benchmark
- C benchmark → geom input: reads geometry
README.md - C benchmark → answer output: writes results
README.md - Java entry → Benchmark meter: runs measurement
src/java/Slalom.java - Java entry → Machine report: reports machine
src/java/Slalom.java - Benchmark meter → Problem reader: reads problem
src/java/Meter.java - Benchmark meter → Patch geometry: decomposes patches
src/java/Meter.java - Benchmark meter → Radiosity solver: builds and solves
src/java/Meter.java - Benchmark meter → Answer writer: stores result
src/java/Meter.java - Benchmark meter → answer output: writes answer
- Problem reader → geom input: reads geometry
src/java/Problem.java - Patch geometry → Box faces: creates faces
src/java/Geometry.java - Patch geometry → Surface patches: creates patches
src/java/Geometry.java - Radiosity solver → Patch geometry: uses geometry
src/java/RadiositySystem.java - Answer writer → Patch geometry: writes patch layout
src/java/Storer.java - TypeScript entry → TypeScript driver: delegates to
src/ts/Slalom.ts - TypeScript driver → TypeScript benchmark: uses benchmark
src/ts/driver.ts - TypeScript driver → Machine report: uses report
src/ts/driver.ts - TypeScript solver → TypeScript geometry: uses geometry
src/ts/solver.ts - Python benchmark → geom input: reads geometry
README.md - Python benchmark → answer output: writes results
README.md - Java entry → answer output: produces results
README.md - TypeScript entry → answer output: produces results
README.md - C benchmark → Machine report: uses system report
src/slalom.c