Deployed e056e7e with MkDocs version: 1.5.3

usage/job_description/config_descriptions/object_position/index.html

@@ -585,7 +585,7 @@ <h2 id="example-configuration">Example Configuration</h2>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="s">"obj_pos_1"</span>
 <span class="w">    </span><span class="nt">debug_breakpoint</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">true</span>
 </code></pre></div>
-<p>In the example configuration, the global positions of objects within the scene will be captured with the identifier <code>obj_pos_1</code>. Additionally, if the <a href="/developement/debugging/#visually-debug-a-job-file">scene debugging</a> is active, the scene will break and open in Blender before rendering.</p>
+<p>In the example configuration, the global positions of objects within the scene will be captured with the identifier <code>obj_pos_1</code>. Additionally, if the <a href="../../../../developement/debugging/#visually-debug-a-job-file">scene debugging</a> is active, the scene will break and open in Blender before rendering.</p>
 <h2 id="metadata-output">Metadata Output</h2>
 <p>Along with the output files, a <code>metadata.yaml</code> file is generated in the output folder. This file contains metadata about the keypoint output, including the output type, format, description, expected steps, sensor name, and output ID.</p>
 </article>

usage/job_description/config_descriptions/pixel_annotation/index.html

@@ -663,7 +663,7 @@ <h2 id="example-configuration">Example Configuration</h2>
 <span class="w">      </span><span class="nt">id</span><span class="p">:</span><span class="w"> </span><span class="s">"depth1"</span>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">debug_breakpoint</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">true</span>
 </code></pre></div>
-<p>In the provided configuration, a variety of pixel annotations are set up, each with their unique identifiers. Additionally, if the <a href="/developement/debugging/#visually-debug-a-job-file">scene debugging</a> is active, the scene will break and open in Blender before rendering.</p>
+<p>In the provided configuration, a variety of pixel annotations are set up, each with their unique identifiers. Additionally, if the <a href="../../../../developement/debugging/#visually-debug-a-job-file">scene debugging</a> is active, the scene will break and open in Blender before rendering.</p>
 <h2 id="metadata-output">Metadata Output</h2>
 <p>Along with the output files, a <code>metadata.yaml</code> file is generated in the output folder. This file contains metadata about the keypoint output, including the output type, format, description, expected steps, sensor name, and output ID.</p>
 </article>

usage/job_description/config_descriptions/rgb/index.html

@@ -608,7 +608,7 @@ <h2 id="example-configuration">Example Configuration</h2>
 <span class="w">    </span><span class="nt">samples</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">200</span>
 <span class="w">    </span><span class="nt">debug_breakpoint</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">true</span>
 </code></pre></div>
-<p>In this configuration, the RGB output with the identifier "MainView" will have a quality of 200 samples per pixel. Additionally, if the <a href="/developement/debugging/#visually-debug-a-job-file">scene debugging</a> is active, the scene will break and open in Blender before rendering.</p>
+<p>In this configuration, the RGB output with the identifier "MainView" will have a quality of 200 samples per pixel. Additionally, if the <a href="../../../../developement/debugging/#visually-debug-a-job-file">scene debugging</a> is active, the scene will break and open in Blender before rendering.</p>
 <h2 id="metadata-output">Metadata Output</h2>
 <p>Along with the output files, a <code>metadata.yaml</code> file is generated in the output folder. This file contains metadata about the keypoint output, including the output type, format, description, expected steps, sensor name, and output ID.</p>
 </article>

usage/job_description/config_descriptions/structured_light/index.html

@@ -585,7 +585,7 @@ <h2 id="configuration-parameters">Configuration Parameters</h2>
 <tr>
 <td><code>debug_breakpoint</code></td>
 <td>boolean</td>
-<td>If set to <code>true</code> and the <a href="/developement/debugging/#visually-debug-a-job-file">scene debugging</a> is active, the rendering process will pause and open Blender before proceeding.</td>
+<td>If set to <code>true</code> and the <a href="../../../../developement/debugging/#visually-debug-a-job-file">scene debugging</a> is active, the rendering process will pause and open Blender before proceeding.</td>
 <td>Optional</td>
 </tr>
 </tbody>