path-tracing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Path Tracing and Ray Tracing Implementation

Path Tracing与Ray Tracing实现

This skill provides guidance for implementing path tracers and ray tracers, particularly for image reconstruction tasks where a target image must be matched within a similarity threshold.

本技能为Path Tracing与Ray Tracing的实现提供指导，尤其适用于需要将目标图像匹配至相似度阈值内的图像重建任务。

When to Use This Skill

适用场景

Implementing ray tracers or path tracers in C/C++
Reconstructing images by reverse-engineering scene parameters
Building rendering systems with geometric primitives (spheres, planes)
Tasks requiring image similarity matching (L2 norm, cosine similarity)
Rendering scenes with shadows, reflections, or procedural textures

使用C/C++实现光线追踪器或路径追踪器
通过逆向工程场景参数重建图像
构建包含几何基元（球体、平面）的渲染系统
需要图像相似度匹配的任务（L2范数、余弦相似度）
渲染包含阴影、反射或程序化纹理的场景

Workflow: Baseline-First Development

工作流：基准优先开发

Phase 1: Establish a Working Baseline

阶段1：建立可用基准

Before any optimization or parameter tuning, establish a complete working render:

Start with minimal samples - Use S=1 or S=2 to verify the pipeline produces complete output
Verify output file completeness - Check that the output file contains valid, complete image data before proceeding
Test in target environment early - If the task specifies a chroot jail, sandbox, or specific execution environment, test there immediately
Fix all compiler warnings first - Treat warnings as errors; typos like
```
doubled
```
instead of
```
double d
```
cause undefined behavior

在进行任何优化或参数调优前，先构建一个完整可用的渲染程序：

从最小样本量开始 - 使用S=1或S=2验证流水线能否生成完整输出
验证输出文件完整性 - 在继续之前，检查输出文件是否包含有效、完整的图像数据
尽早在目标环境测试 - 如果任务指定了chroot监狱、沙箱或特定执行环境，立即在该环境中测试
先修复所有编译器警告 - 将警告视为错误；诸如
```
doubled
```
而非
```
double d
```
的拼写错误会导致未定义行为

Phase 2: Scene Analysis

阶段2：场景分析

When reconstructing from a reference image:

Read and parse image header - Extract dimensions, format, color depth
Sample key pixels systematically - Sample corners, center, and regions of interest
Identify scene elements - Count all objects (spheres, planes, lights) before implementing
Analyze gradients and patterns - Sample multiple points to derive mathematical relationships for sky gradients, floor patterns
Document derived parameters - Write down calculated values (camera FOV, sphere position/radius, light direction)

当基于参考图像重建时：

读取并解析图像头 - 提取尺寸、格式、颜色深度
系统性采样关键像素 - 采样角落、中心及感兴趣区域
识别场景元素 - 在实现前统计所有物体（球体、平面、光源）
分析渐变与图案 - 采样多个点以推导天空渐变、地面图案的数学关系
记录推导的参数 - 写下计算得到的值（相机视场角、球体位置/半径、光源方向）

Phase 3: Incremental Implementation

阶段3：增量式实现

One feature at a time - Add sphere, then floor, then shadows, then soft shadows
Validate each addition - Render and compare after each feature
Calculate render time before choosing sample count - For a 2400×1800 image at 50 samples, estimate:
```
pixels × samples × rays_per_sample × time_per_ray
```
Never modify code while renders are running - This creates race conditions and confusion about which version produced which output

一次添加一个功能 - 先添加球体，再添加地面，然后是阴影，最后是软阴影
验证每次新增功能 - 每次添加功能后进行渲染并对比
选择样本量前计算渲染时间 - 对于2400×1800的图像，50样本量的渲染时间估算公式：
```
pixels × samples × rays_per_sample × time_per_ray
```
渲染运行时切勿修改代码 - 这会导致竞争条件，混淆哪个版本生成了哪个输出

Phase 4: Validation

阶段4：验证

Use the exact similarity metric - If grading uses normalized L2 or cosine similarity, compute that metric, not RMS error or other proxies
Create a reusable validation script early - Avoid rewriting comparison code repeatedly
Verify output file before submission - Check file size, parse the image, confirm dimensions match expected

使用精确的相似度指标 - 如果评分使用归一化L2或余弦相似度，就计算该指标，而非均方根误差或其他替代指标
尽早创建可复用的验证脚本 - 避免重复编写对比代码
提交前验证输出文件 - 检查文件大小、解析图像、确认尺寸符合预期

Common Scene Elements

常见场景元素

Sky Gradients

天空渐变

Analyze by sampling multiple y-coordinates at a fixed x to derive the vertical gradient formula. Sample multiple x-coordinates at a fixed y to check for horizontal variation.

通过在固定x坐标下采样多个y坐标来推导垂直渐变公式。在固定y坐标下采样多个x坐标以检查是否存在水平变化。

Checkered Floor

棋盘格地面

To match checker patterns:

Sample points across the floor to determine checker scale
Identify the checker color values precisely
Verify pattern origin and orientation

匹配棋盘格图案的方法：

采样地面上的多个点以确定棋盘格比例
精确识别棋盘格颜色值
验证图案的原点与方向

Spheres

球体

Derive sphere parameters by:

Finding the visual center of the sphere in image coordinates
Estimating radius from the sphere's apparent size
Calculating reflection and shadow geometry to verify position

推导球体参数的方法：

在图像坐标系中找到球体的视觉中心
根据球体的表观大小估算半径
计算反射与阴影几何以验证位置

Shadows

阴影

Hard shadows: Single ray to light source
Soft shadows: Multiple samples with jittered light directions
Verify shadow direction matches light position

硬阴影：向光源发射单条光线
软阴影：对光源方向进行抖动采样
验证阴影方向与光源位置匹配

Time Management

时间管理

Calculate Expected Render Time First

先计算预期渲染时间

render_time ≈ (width × height × samples × bounces) / rays_per_second

Typical ray tracer performance: 100K-1M rays/second depending on scene complexity.

For a 2400×1800 image:

S=1: ~4M rays, seconds to complete
S=10: ~40M rays, minutes to complete
S=50: ~200M rays, could take 10+ minutes
S=100: ~400M rays, may exceed time limits

render_time ≈ (width × height × samples × bounces) / rays_per_second

典型光线追踪器性能：每秒10万-100万条光线，具体取决于场景复杂度。

对于2400×1800的图像：

S=1：约400万条光线，数秒完成
S=10：约4000万条光线，数分钟完成
S=50：约2亿条光线，可能需要10分钟以上
S=100：约4亿条光线，可能超出时间限制

Adjust Parameters for Time Budget

根据时间预算调整参数

If the task has a time limit:

Calculate maximum feasible sample count
Start with that limit, not above
Consider rendering at lower resolution first for validation

如果任务有时间限制：

计算最大可行样本量
从该限制开始，不要超过
考虑先以较低分辨率渲染进行验证

Common Pitfalls to Avoid

需避免的常见陷阱

Code Quality Issues

代码质量问题

Typos in type declarations -
```
doubled
```
vs
```
double d
```
causes undefined behavior
Ignoring compiler warnings - Fix all warnings before running long processes
Race conditions - Never edit code while a render is still running

类型声明拼写错误 -
```
doubled
```
与
```
double d
```
会导致未定义行为
忽略编译器警告 - 在运行长时间进程前修复所有警告
竞争条件 - 渲染运行时切勿编辑代码

Validation Mistakes

验证错误

Wrong similarity metric - Match the exact metric used for grading
Incomplete output files - Always verify file completeness before considering done
Downsampled validation - If final output must be full resolution, validate at full resolution

使用错误的相似度指标 - 匹配评分使用的精确指标
输出文件不完整 - 始终在完成前验证文件完整性
降采样验证 - 如果最终输出必须是全分辨率，就以全分辨率进行验证

Time Management Mistakes

时间管理错误

Starting with high sample counts - Always start low (S=1) to verify correctness
Not calculating expected render time - Lead to timeout and wasted iterations
Iterating without completing - Better to have one complete low-quality render than many incomplete high-quality attempts

从高样本量开始 - 始终从低样本量（S=1）开始验证正确性
未计算预期渲染时间 - 导致超时与迭代浪费
未完成就迭代 - 拥有一个完整的低质量渲染比多个不完整的高质量尝试更好

Analysis Mistakes

分析错误

Missing scene elements - Thoroughly identify all objects before implementing
Arbitrary parameter guessing - Derive parameters mathematically from reference image samples
Sign errors in gradients - Double-check gradient direction by sampling multiple points

遗漏场景元素 - 在实现前彻底识别所有物体
随意猜测参数 - 从参考图像采样中通过数学方法推导参数
渐变符号错误 - 通过采样多个点仔细检查渐变方向