Fix HUBDatasetStats for no-label edge cases (#4583)

docs/datasets/detect/index.md

@@ -93,11 +93,15 @@ If you have your own dataset and would like to use it for training detection mod
 
 You can easily convert labels from the popular COCO dataset format to the YOLO format using the following code snippet:
 
-```python
-from ultralytics.data.converter import convert_coco
+!!! example ""
 
-convert_coco(labels_dir='../coco/annotations/')
-```
+    === "Python"
+
+        ```python
+        from ultralytics.data.converter import convert_coco
+        
+        convert_coco(labels_dir='path/to/coco/annotations/')
+        ```
 
 This conversion tool can be used to convert the COCO dataset or any dataset in the COCO format to the Ultralytics YOLO format.
 

docs/datasets/obb/index.md

@@ -69,11 +69,15 @@ For those looking to introduce their own datasets with oriented bounding boxes,
 
 Transitioning labels from the DOTA dataset format to the YOLO OBB format can be achieved with this script:
 
-```python
-from ultralytics.data.converter import convert_dota_to_yolo_obb
+!!! example ""
 
-convert_dota_to_yolo_obb('path/to/DOTA')
-```
+    === "Python"
+
+        ```python
+        from ultralytics.data.converter import convert_dota_to_yolo_obb
+        
+        convert_dota_to_yolo_obb('path/to/DOTA')
+        ```
 
 This conversion mechanism is instrumental for datasets in the DOTA format, ensuring alignment with the Ultralytics YOLO OBB format.
 

docs/datasets/pose/index.md

@@ -10,9 +10,7 @@ keywords: Ultralytics, YOLO, pose estimation, datasets, training, YAML, keypoint
 
 ### Ultralytics YOLO format
 
-** Label Format **
-
-The dataset format used for training YOLO pose models is as follows:
+The dataset label format used for training YOLO pose models is as follows:
 
 1. One text file per image: Each image in the dataset has a corresponding text file with the same name as the image file and the ".txt" extension.
 2. One row per object: Each row in the text file corresponds to one object instance in the image.
@@ -119,10 +117,14 @@ If you have your own dataset and would like to use it for training pose estimati
 
 Ultralytics provides a convenient conversion tool to convert labels from the popular COCO dataset format to YOLO format:
 
-```python
-from ultralytics.data.converter import convert_coco
+!!! example ""
 
-convert_coco(labels_dir='../coco/annotations/', use_keypoints=True)
-```
+    === "Python"
+
+        ```python
+        from ultralytics.data.converter import convert_coco
+        
+        convert_coco(labels_dir='path/to/coco/annotations/', use_keypoints=True)
+        ```
 
 This conversion tool can be used to convert the COCO dataset or any dataset in the COCO format to the Ultralytics YOLO format. The `use_keypoints` parameter specifies whether to include keypoints (for pose estimation) in the converted labels.

docs/datasets/segment/index.md

@@ -10,9 +10,7 @@ keywords: Ultralytics, YOLO, Instance Segmentation, Dataset, YAML, COCO, Auto-An
 
 ### Ultralytics YOLO format
 
-** Label Format **
-
-The dataset format used for training YOLO segmentation models is as follows:
+The dataset label format used for training YOLO segmentation models is as follows:
 
 1. One text file per image: Each image in the dataset has a corresponding text file with the same name as the image file and the ".txt" extension.
 2. One row per object: Each row in the text file corresponds to one object instance in the image.
@@ -28,16 +26,16 @@ The format for a single row in the segmentation dataset file is as follows:
 
 In this format, `<class-index>` is the index of the class for the object, and `<x1> <y1> <x2> <y2> ... <xn> <yn>` are the bounding coordinates of the object's segmentation mask. The coordinates are separated by spaces.
 
-Here is an example of the YOLO dataset format for a single image with two object instances:
+Here is an example of the YOLO dataset format for a single image with two objects made up of a 3-point segment and a 5-point segment.
 
 ```
-0 0.6812 0.48541 0.67 0.4875 0.67656 0.487 0.675 0.489 0.66
-1 0.5046 0.0 0.5015 0.004 0.4984 0.00416 0.4937 0.010 0.492 0.0104
+0 0.681 0.485 0.670 0.487 0.676 0.487
+1 0.504 0.000 0.501 0.004 0.498 0.004 0.493 0.010 0.492 0.0104
 ```
 
 !!! tip "Tip"
 
-      - The length of each row does not have to be equal.
+      - The length of each row does **not** have to be equal.
       - Each segmentation label must have a **minimum of 3 xy points**: `<class-index> <x1> <y1> <x2> <y2> <x3> <y3>`
 
 ### Dataset YAML format
@@ -103,11 +101,15 @@ If you have your own dataset and would like to use it for training segmentation
 
 You can easily convert labels from the popular COCO dataset format to the YOLO format using the following code snippet:
 
-```python
-from ultralytics.data.converter import convert_coco
+!!! example ""
 
-convert_coco(labels_dir='../coco/annotations/', use_segments=True)
-```
+    === "Python"
+
+        ```python
+        from ultralytics.data.converter import convert_coco
+        
+        convert_coco(labels_dir='path/to/coco/annotations/', use_segments=True)
+        ```
 
 This conversion tool can be used to convert the COCO dataset or any dataset in the COCO format to the Ultralytics YOLO format.
 
@@ -121,11 +123,15 @@ Auto-annotation is an essential feature that allows you to generate a segmentati
 
 To auto-annotate your dataset using the Ultralytics framework, you can use the `auto_annotate` function as shown below:
 
-```python
-from ultralytics.data.annotator import auto_annotate
+!!! example ""
 
-auto_annotate(data="path/to/images", det_model="yolov8x.pt", sam_model='sam_b.pt')
-```
+    === "Python"
+
+        ```python
+        from ultralytics.data.annotator import auto_annotate
+         
+        auto_annotate(data="path/to/images", det_model="yolov8x.pt", sam_model='sam_b.pt')
+        ```
 
 | Argument   | Type                | Description                                                                                             | Default      |
 |------------|---------------------|---------------------------------------------------------------------------------------------------------|--------------|

docs/modes/predict.md

@@ -264,7 +264,7 @@ Below are code examples for using each source type:
         ```
 
     === "Streams"
-        Run inference on remote streaming sources using RTSP, RTMP, and IP address protocols. If mutliple streams are provided in a `*.streams` text file then batched inference will run, i.e. 8 streams will run at batch-size 8, otherwise single streams will run at batch-size 1.
+        Run inference on remote streaming sources using RTSP, RTMP, and IP address protocols. If multiple streams are provided in a `*.streams` text file then batched inference will run, i.e. 8 streams will run at batch-size 8, otherwise single streams will run at batch-size 1.
         ```python
         from ultralytics import YOLO
 

docs/quickstart.md

@@ -41,7 +41,7 @@ Ultralytics provides various installation methods including pip, conda, and Dock
 
         !!! note
         
-            If you are installing in a CUDA environment best practice is to install `ultralytics`, `pytorch` and `pytorch-cuda` in the same command to allow the conda package manager to resolve any conflicts, or else to install `pytorch-cuda` last to allow it override the CPU-specific `pytorch` package if necesary.
+            If you are installing in a CUDA environment best practice is to install `ultralytics`, `pytorch` and `pytorch-cuda` in the same command to allow the conda package manager to resolve any conflicts, or else to install `pytorch-cuda` last to allow it override the CPU-specific `pytorch` package if necessary.
             ```bash
             # Install all packages together using conda
             conda install -c conda-forge -c pytorch -c nvidia ultralytics pytorch torchvision pytorch-cuda=11.8