ci.yml: check doxygen on 24.04 (#519)

tutorials: change heading depth

Signed-off-by: Steve Peters <[email protected]>

Author: scpeters

.github/workflows/ci.yml

@@ -20,9 +20,6 @@ jobs:
         uses: gazebo-tooling/action-gz-ci@jammy
         with:
           codecov-enabled: true
-          cppcheck-enabled: true
-          cpplint-enabled: true
-          doxygen-enabled: true
   noble-ci:
     runs-on: ubuntu-latest
     name: Ubuntu Noble CI
@@ -33,5 +30,7 @@ jobs:
         id: ci
         uses: gazebo-tooling/action-gz-ci@noble
         with:
+          # codecov-enabled: true
           cppcheck-enabled: true
           cpplint-enabled: true
+          doxygen-enabled: true

tutorials/boundingbox_camera.md

@@ -241,7 +241,7 @@ gz sim boundingbox_camera.sdf
 
 you will find that the dataset is saved in the given path
 
-#### Dataset Demo
+### Dataset Demo
 
 ![dataset_generation](files/boundingbox_camera/object_detection_dataset.gif)
 

tutorials/segmentation_camera.md

@@ -96,7 +96,7 @@ As we can see, we define a sensor with the following SDF elements:
 * `<visualize>`: Whether the sensor should be visualized in the GUI (indicated by true) or not (indicated by false). This is currently unused by Gazebo.
 * `<topic>`: The name of the topic which will be used to publish the sensor data.
 
-#### Label map & Colored map
+### Label map & Colored map
 The segmentation sensor creates 2 maps (or images):
 
 - The `label map`: For semantic segmentation, each pixel contains the object's label. For panoptic segmentation, each pixel contains the label and object's instance count.
@@ -271,7 +271,7 @@ To save the output of the sensor as segmentation dataset samples, we add the `<s
 In the example world we just ran (`segmentation_camera.sdf`), you'll notice that the panoptic camera is saving data to `segmentation_data/instance_camera`, while the semenatic camera is saving data to
 `segmentation_data/semantic_camera` (these are relative paths).
 
-#### Dataset Demo
+### Dataset Demo
 
 Up to this point, we have left simulation paused.
 Go ahead and start simulation by pressing the play button at the bottom-left part of the GUI.