How trisycl/path_tracer works
Project type and purpose
• This is a standalone, compute-heavy CLI application: an experimental C++20 path tracer accelerated via SYCL (triSYCL by default) targeting GPUs or FPGAs.
• Its goal is to render images by simulating light paths (“path tracing”) and to explore replacing dynamic polymorphism with std::variant/std::visit in a heterogeneous context.
File structure
• Top-level:
• CMakeLists.txt + cmake/… → build system and custom FindTriSYCL module.
• src/main.cpp → host entry point compiling scene, invoking SYCL kernels, writing output.
• doc/ + images/ → documentation and example render.
• No separate “frontend/backend” folders: it’s a monolithic host/device compute engine.
• Dependencies: triSYCL (or other SYCL implementations), stb image library.
README
• Specifies features (motion blur, depth of field, various materials/geometry), build instructions (CMake + triSYCL or other SYCL), and run producing out.png.
• Emphasizes modern C++ constructs over classic dynamic polymorphism.
Detail
• std::variant layer sitting between Scene Data and Device Kernels, indicating compile-time dispatch.
• Call out optional FPGA mode vs. GPU mode (single_task vs. parallel_for).