Stima della posa con Ultralytics YOLO
La stima della posa è un'attività che consiste nell'identificare la posizione di punti specifici in un'immagine, solitamente chiamati punti chiave. I punti chiave possono rappresentare diverse parti dell'oggetto, come articolazioni, punti di riferimento o altre caratteristiche distintive. Le loro posizioni sono generalmente rappresentate come un insieme di coordinate 2D [x, y], eventualmente accompagnate da un flag di visibilità [x, y, visible].
L'output di un modello di stima della posa è un insieme di punti che rappresentano i keypoint di un oggetto nell'immagine, solitamente accompagnati dai punteggi di confidenza di ciascun punto. La stima della posa è una buona scelta quando devi individuare parti specifiche di un oggetto in una scena e la loro posizione reciproca.
Guarda: Come eseguire la stima della posa in tempo reale con Ultralytics YOLO26 | Tracciamento ed estrazione dei punti chiave 🕺
I modelli Pose di YOLO26 usano il suffisso -pose, ad esempio yolo26n-pose.pt, e sono preaddestrati sui punti chiave COCO.
Modelli#
Di seguito sono mostrati i modelli YOLO26 Pose pretrained sul dataset dei keypoint COCO.
I modelli vengono scaricati automaticamente dalla più recente release di Ultralytics al primo utilizzo.
| Modello | dimensione (pixel) | mAPpose50-95 (e2e) | mAPpose50 (e2e) | Velocità CPU ONNX (ms) | Velocità T4 TensorRT10 (ms) | parametri (M) | FLOPs (B) |
|---|---|---|---|---|---|---|---|
| YOLO26n-pose | 640 | 57.2 | 83.3 | 40.3 ± 0.5 | 1.8 ± 0.0 | 2.9 | 7.6 |
| YOLO26s-pose | 640 | 63.0 | 86.6 | 85.3 ± 0.9 | 2.7 ± 0.0 | 10.4 | 24.1 |
| YOLO26m-pose | 640 | 68.8 | 89.6 | 218.0 ± 1.5 | 5.0 ± 0.1 | 21.5 | 73.3 |
| YOLO26l-pose | 640 | 70.4 | 90.5 | 275.4 ± 2.4 | 6.5 ± 0.1 | 25.9 | 91.7 |
| YOLO26x-pose | 640 | 71.6 | 91.6 | 565.4 ± 3.0 | 12.2 ± 0.2 | 57.6 | 202.3 |
- I valori mAPval si riferiscono a un singolo modello con scala singola sul dataset COCO Keypoints val2017.
Riproduci conyolo pose val data=coco-pose.yaml device=0 nms=False - Velocità media sulle immagini COCO val con ONNX su CPU e TensorRT10 su una GPU NVIDIA T4.
Riproduci i risultati conyolo pose val data=coco-pose.yaml batch=1 device=0|cpu nms=False - I valori di Parametri e FLOPs si riferiscono ai modelli fusi dopo la fusione di Conv/BatchNorm e la rimozione del ramo di rilevamento inutilizzato. I checkpoint preaddestrati mantengono l’architettura di addestramento completa e possono riportare valori più elevati.
Consulta l'anteprima non ancora rilasciata di YOLO27 per i risultati preliminari sui keypoint COCO.
Addestra#
Addestra un modello YOLO26n-pose sul dataset COCO8-pose per 100 epoche con una dimensione delle immagini di 640.
from ultralytics import YOLO
# Carica un modello
model = YOLO("yolo26n-pose.yaml") # crea un nuovo modello dal file YAML
model = YOLO("yolo26n-pose.pt") # carica un modello preaddestrato (consigliato per l'addestramento)
model = YOLO("yolo26n-pose.yaml").load("yolo26n-pose.pt") # crea dal file YAML e trasferisci i pesi
# Addestra il modello
results = model.train(data="coco8-pose.yaml", epochs=100, imgsz=640)Consulta la pagina Addestramento per i dettagli completi sulla modalità train. Puoi addestrare i modelli di posa anche con l'addestramento cloud di Ultralytics Platform.
Formato del dataset#
Trovi tutti i dettagli sul formato dei dataset YOLO per la posa nella Guida ai dataset. Per convertire un dataset JSON esistente dei keypoint COCO nel formato YOLO, usa la funzione integrata convert_coco con use_keypoints=True, come descritto nella guida alla conversione da COCO a YOLO. Le annotazioni di Ultralytics Platform supportano anche le etichette di posa, con modelli di scheletro integrati per persone, mani e volti, oltre a configurazioni personalizzate di keypoint.
Per attività di stima della posa personalizzate, puoi provare anche dataset specializzati come Tiger-Pose per la stima della posa degli animali, Hand Keypoints per il tracciamento delle mani o Dog-Pose per l'analisi della posa dei cani.
Convalida#
Convalida la precisione del modello YOLO26n-pose addestrato, misurata come precisione media (mAP). Non sono necessari argomenti, poiché model conserva data usati per l'addestramento e gli argomenti come attributi del modello: path/to/best.pt dell'esempio Train esegue la convalida su COCO8-pose. I pesi ufficiali registrano il percorso di un dataset di addestramento che non esiste sul tuo computer, quindi ripiegano sul valore predefinito dell'attività coco8-pose.yaml e mostrano un avviso. Passa data per convalidare il modello su un altro dataset.
from ultralytics import YOLO
# Carica un modello
model = YOLO("yolo26n-pose.pt") # carica un modello ufficiale
model = YOLO("path/to/best.pt") # carica un modello personalizzato
# Convalida il modello
metrics = model.val() # non servono argomenti, il dataset e le impostazioni vengono ricordati
metrics.box.map # map50-95
metrics.box.map50 # map50
metrics.box.map75 # map75
metrics.box.maps # mAP50-95 per classe; le classi assenti nel set di validazione mantengono il mAP complessivo
metrics.box.ap_class_index # indici delle classi effettivamente valutate
metrics.box.image_metrics # dizionario delle metriche per immagine relativo ai riquadri, con precisione, richiamo, F1, TP, FP e FN
metrics.pose.map # map50-95(P)
metrics.pose.map50 # map50(P)
metrics.pose.map75 # map75(P)
metrics.pose.maps # mAP50-95(P) per classe; le classi assenti nel set di validazione mantengono il mAP(P) complessivo
metrics.pose.ap_class_index # indici delle classi effettivamente valutate
metrics.pose.image_metrics # dizionario delle metriche per immagine relativo alla posa, con precisione, richiamo, F1, TP, FP e FNPredici#
Usa un modello YOLO26n-pose addestrato per eseguire previsioni sulle immagini.
from ultralytics import YOLO
# Carica un modello
model = YOLO("yolo26n-pose.pt") # carica un modello ufficiale
model = YOLO("path/to/best.pt") # carica un modello personalizzato
# Esegui previsioni con il modello
results = model("https://ultralytics.com/images/bus.jpg") # esegui una previsione su un’immagine
# Accedi ai risultati
for result in results:
xy = result.keypoints.xy # coordinate x e y
xyn = result.keypoints.xyn # normalized
kpts = result.keypoints.data # x, y, visibilità (se disponibile)Consulta la pagina Previsione per i dettagli completi sulla modalità predict.
Output dei risultati#
La stima della posa restituisce un oggetto Results per immagine. I principali campi della previsione sono result.keypoints per le coordinate della posa e result.boxes per le istanze rilevate a cui appartengono quei keypoint.
| Attributo | Tipo | Forma | Descrizione |
|---|---|---|---|
result.keypoints | Keypoints | (N) | Punti chiave. |
result.keypoints.data | torch.float32 | (N,K,2/3) | x,y più visibilità/confidenza facoltativa. |
result.keypoints.xy | torch.float32 | (N,K,2) | Punti chiave in pixel. |
result.keypoints.xyn | torch.float32 | (N,K,2) | Punti chiave normalizzati. |
result.boxes | Boxes | (N) | Riquadri di istanza. |
Per consultare i campi Results specifici di ogni attività, visita la sezione Risultati delle previsioni per attività.
Mappa degli indici dei keypoint#
I modelli YOLO26 Pose predefiniti prevedono i 17 keypoint COCO, quindi l'indice k in result.keypoints.xy[:, k] corrisponde a:
- Naso
- Occhio sinistro
- Occhio destro
- Orecchio sinistro
- Orecchio destro
- Spalla sinistra
- Spalla destra
- Gomito sinistro
- Gomito destro
- Polso sinistro
- Polso destro
- Anca sinistra
- Anca destra
- Ginocchio sinistro
- Ginocchio destro
- Caviglia sinistra
- Caviglia destra
Esporta#
Esporta un modello YOLO26n-pose in un altro formato, come ONNX, CoreML ecc.
from ultralytics import YOLO
# Carica un modello
model = YOLO("yolo26n-pose.pt") # carica un modello ufficiale
model = YOLO("path/to/best.pt") # carica un modello personalizzato
# Esporta il modello
model.export(format="onnx")I formati di esportazione disponibili per YOLO26-pose sono elencati nella tabella qui sotto. Puoi esportare in qualsiasi formato usando l'argomento format, ad esempio format='onnx' o format='engine'. Puoi eseguire predizioni o convalidare direttamente i modelli esportati, ad esempio con yolo predict model=yolo26n-pose.onnx. Al termine dell'esportazione, vengono mostrati esempi d'uso del modello.
| Formato | Argomento format | Modello | Metadati | Argomenti |
|---|---|---|---|---|
| PyTorch | - | yolo26n-pose.pt | ✅ | - |
| TorchScript | torchscript | yolo26n-pose.torchscript | ✅ | imgsz, quantize, dynamic, nms, batch, device |
| ONNX | onnx | yolo26n-pose.onnx | ✅ | imgsz, quantize, dynamic, simplify, opset, nms, batch, data, fraction, device |
| OpenVINO | openvino | yolo26n-pose_openvino_model/ | ✅ | imgsz, quantize, dynamic, nms, batch, data, fraction, device |
| TensorRT | engine | yolo26n-pose.engine | ✅ | imgsz, quantize, dynamic, simplify, opset, workspace, nms, batch, data, fraction, device |
| CoreML | coreml | yolo26n-pose.mlpackage | ✅ | imgsz, dynamic, quantize, nms, batch, device |
| Apple Core AI | coreai | yolo26n-pose.aimodel | ✅ | imgsz, batch, quantize |
| TF SavedModel | saved_model | yolo26n-pose_saved_model/ | ✅ | imgsz, quantize, opset, nms, batch, data, fraction, device |
| TF GraphDef | pb | yolo26n-pose.pb | ❌ | imgsz, opset, batch, device |
| TF Edge TPU | edgetpu | yolo26n-pose_edgetpu.tflite | ✅ | imgsz, quantize, opset, data, fraction, device |
| LiteRT | litert | yolo26n-pose.tflite | ✅ | imgsz, quantize, batch, data, fraction, device |
| PaddlePaddle | paddle | yolo26n-pose_paddle_model/ | ✅ | imgsz, batch, device |
| MNN | mnn | yolo26n-pose.mnn | ✅ | imgsz, batch, dynamic, quantize, simplify, opset, nms, device |
| NCNN | ncnn | yolo26n-pose_ncnn_model/ | ✅ | imgsz, quantize, device |
| IMX500 | imx | yolo11n_imx_model/ | ✅ | imgsz, quantize, data, fraction, nms, device |
| RKNN | rknn | yolo26n-pose_rknn_model/ | ✅ | imgsz, batch, name, quantize, simplify, opset, data, fraction, device |
| ExecuTorch | executorch | yolo26n-pose_executorch_model/ | ✅ | imgsz, quantize, batch, data, fraction, device |
| Axelera | axelera | yolo26n-pose_axelera_model/ | ✅ | imgsz, batch, quantize, data, fraction, device |
| DEEPX | deepx | yolo26n-pose_deepx_model/ | ✅ | imgsz, quantize, simplify, opset, data, optimize, device |
| Qualcomm QNN | qnn | yolo26n-pose_qnn.onnx | ✅ | imgsz, batch, name, quantize, simplify, opset, data, fraction, device |
| Hailo | hailo | yolo26n-pose_hailo_model/ | ✅ | imgsz, name, quantize, data, fraction, simplify, conf, iou, device |
| Huawei Ascend | ascend | yolo26n-pose_ascend_model/ | ✅ | imgsz, batch, name, quantize, opset, simplify, nms, device |
| AMD Xilinx | xilinx | yolo26n-pose_xilinx_model/ | ✅ | imgsz, name, quantize, data, fraction, opset, simplify, device |
| NXP | nxp | yolo26n-pose_nxp.tflite | ✅ | imgsz, quantize, data, fraction, device |
nms=None restituisce per impostazione predefinita output grezzi per la NMS esterna (YOLO26 mantiene la propria head senza NMS su Axelera). Imposta nms=False per selezionare una head senza NMS disponibile; i formati non supportati usano il proprio percorso di output nativo. Le voci nms qui sopra identificano i formati che possono incorporare la NMS con nms=True.
Consulta i dettagli completi di export nella pagina Esportazione.
Domande frequenti#
La stima della posa con Ultralytics YOLO26 consiste nell'identificare punti specifici, noti come punti chiave, in un'immagine. Questi punti chiave rappresentano in genere le articolazioni o altre caratteristiche importanti dell'oggetto. L'output include le coordinate
[x, y]e i punteggi di confidenza di ciascun punto. I modelli YOLO26-pose sono progettati appositamente per questa attività e usano il suffisso-pose, ad esempioyolo26n-pose.pt. Questi modelli sono preaddestrati su dataset come i punti chiave COCO e possono essere usati per diverse attività di stima della posa. I modelli predefiniti predicono i 17 punti chiave COCO.Per addestrare un modello YOLO26-pose su un dataset personalizzato, carica un modello: puoi definirne uno nuovo tramite un file YAML oppure usare un modello pretrained. Puoi quindi avviare l'addestramento usando il dataset e i parametri specificati.
Esempiofrom ultralytics import YOLO # Carica un modello model = YOLO("yolo26n-pose.yaml") # crea un nuovo modello dal file YAML model = YOLO("yolo26n-pose.pt") # carica un modello preaddestrato (consigliato per l'addestramento) # Addestra il modello results = model.train(data="your-dataset.yaml", epochs=100, imgsz=640)Per informazioni complete sull'addestramento, consulta la sezione Addestramento. Puoi anche usare l'addestramento cloud di Ultralytics Platform per addestrare modelli personalizzati di stima della posa senza scrivere codice.
La convalida di un modello YOLO26-pose consiste nel valutarne l'accuratezza usando gli stessi parametri del dataset conservati durante l'addestramento. Ecco un esempio:
Esempiofrom ultralytics import YOLO # Carica un modello model = YOLO("yolo26n-pose.pt") # carica un modello ufficiale model = YOLO("path/to/best.pt") # carica un modello personalizzato # Convalida il modello metrics = model.val() # non servono argomenti, il dataset e le impostazioni vengono ricordatiPer saperne di più, visita la sezione Val.
Sì, puoi esportare un modello YOLO26-pose in vari formati, come ONNX, CoreML, TensorRT e altri. Puoi farlo con Python oppure tramite l'interfaccia a riga di comando (CLI).
Esempiofrom ultralytics import YOLO # Carica un modello model = YOLO("yolo26n-pose.pt") # carica un modello ufficiale model = YOLO("path/to/best.pt") # carica un modello personalizzato # Esporta il modello model.export(format="onnx")Per maggiori dettagli, consulta la sezione Esportazione. Puoi distribuire i modelli esportati su dispositivi edge per applicazioni in tempo reale, come il monitoraggio dell'attività fisica e l'analisi sportiva, oppure per la robotica.
Ultralytics YOLO26 offre diversi modelli di posa pretrained, tra cui YOLO26n-pose, YOLO26s-pose e YOLO26m-pose. I modelli differiscono per dimensioni, accuratezza (mAP) e velocità. Per l'elenco completo, con mAP sui keypoint COCO, velocità, numero di parametri e FLOPs per modello, consulta la sezione Modelli.
Commenti465
Fai una domanda, condividi i tuoi risultati o aiuta qualcun altro.
3300299472
import pygetwindow as gw import pyautogui from ultralytics import YOLO import cv2
Load the model
model = YOLO("model/best.onnx")
while True: # Get the handle of the application window app_window = gw.getWindowsWithTitle('Chess Game')[0] app_window.activate()
# Move the window to the top-left corner of the screen app_window.moveTo(0, 0) # Set the window size to (929, 721) app_window.resizeTo(929, 721) # Get the window position left, top, width, height = app_window.left, app_window.top, app_window.width, app_window.height # Take a screenshot in the background screenshot = pyautogui.screenshot(region=(left, top, width, height)) screenshot.save('screenshot.png') # Read the screenshot and convert it to OpenCV format img = cv2.imread('screenshot.png') # Perform inference results = model.predict(source=img, show=True)I need help, who will help me? I have successfully identified the object in the program through the ONNX model, but I don't know how to obtain coordinates. I need to obtain coordinates and then control the mouse to move to the coordinates for clicking operations. Can someone show me the reference code? Thank you
1
Glenn JocherUltralytics(modificato)@3300299472 hello! It's great to hear that you've successfully used the ONNX model for object detection. To obtain the coordinates of the detected objects and control the mouse accordingly, you can extract the bounding box coordinates from the
resultsobject and use them to move the mouse. Here's a quick example on how you can do this:from ultralytics import YOLO import pyautogui # Load the model model = YOLO("model/best.onnx") # Perform inference results = model.predict(source=img, show=True) # Get bounding box coordinates for x1, y1, x2, y2 in results[0].boxes.xyxy.tolist(): # detections in the first image # Calculate the center of the bounding box x_center = int((x1 + x2) / 2) y_center = int((y1 + y2) / 2) # Move mouse to the center of the bounding box pyautogui.moveTo(x_center, y_center) # Optionally, perform a click pyautogui.click()This code snippet will move the mouse to the center of each detected object and perform a click. Make sure to adjust the coordinates based on your specific screen resolution and application window size if necessary. Happy coding! 😊
AdadAlShabab
Hi. I want to measure the length of detected line after running the pose detection model. How can I do it? Please let me know.
1
Glenn JocherUltralyticsHi! To measure the length of a detected line after running the pose detection model, you can compute the Euclidean distance between keypoints. If you have keypoints' coordinates, you can use the following Python code example:
import numpy as np def calculate_distance(pt1, pt2): return np.sqrt((pt2[0] - pt1[0])**2 + (pt2[1] - pt1[1])**2) # Example keypoints coordinates keypoint1 = [x1, y1] # Replace x1, y1 with your actual coordinates keypoint2 = [x2, y2] # Replace x2, y2 with your actual coordinates # Calculate distance length = calculate_distance(keypoint1, keypoint2) print('The length of the line is:', length)Just replace
x1, y1, x2, y2with the actual coordinates of your keypoints. This will give you the length between these two points which can represent a line in your use case. Hope this helps! 😊
Pakorn-02(modificato)
Can i only detect the first person entering the camera? And from the source code, can I correctly convert from key point coordinates (x, y) to position coordinates (x, y, z) in Unity?
#My Source Code import requests import cv2 import numpy as np from ultralytics import YOLO model = YOLO('yolov8n-pose.pt') cap = cv2.VideoCapture(0) server_url = 'http://localhost:3000/keypoints' while True: success, frame = cap.read() results = model(frame) # Simulate depth data (replace this with actual depth estimation) depth_data = np.random.rand(frame.shape[0], frame.shape[1]) # Access the xy attribute and convert it to a list keypoints = results[0].keypoints.xy.cpu().numpy().tolist() # data = {'keypoints': keypoints} #Extract only the keypoints for the right hand right_hand_keypoints = [keypoints[0][10]] # Combine 2D keypoints with simulated depth data to obtain 3D keypoints keypoints_3d = [(x, y, depth_data[int(y), int(x)]) for x, y in right_hand_keypoints] data = {'keypoints': keypoints_3d} # Send keypoint data to the Node.js server response = requests.post(server_url, json=data) print(response.text) # Print server response annotated_image = results[0].plot() cv2.imshow('frame', annotated_image) cv2.waitKey(1) cap.release() cv2.destroyAllWindows()1
Paula DerrengerUltralyticsHi there! Regarding your question about detecting only the first person entering the camera, YOLOv8 models by default will detect all instances of persons in each frame. However, you can modify the behavior to track the first detected person by managing the IDs of detected persons and only processing the first ID observed across frames.
As for converting from 2D keypoint coordinates (x, y) to 3D position coordinates (x, y, z) in Unity, the conversion depends on getting a real depth measurement. Your approach of simulating depth data and combining it with the keypoints is a common technique. If you have access to a depth sensor or can derive depth from stereo cameras, that would provide more accurate 3D coordinates. Just ensure that the coordinate system alignment between the AI model output and Unity's coordinate system is correctly calibrated for accurate placements in Unity.
Here's a refined approach considering depth measurements:
# Assuming depth_data contains actual depth measurements keypoints_3d = [(x, y, depth_data[int(y), int(x)]) for x, y in right_hand_keypoints]Keep refining your method to handle actual depth, and ensure coordinate transformations align with Unity's requirements. Good luck! 🚀
Pakorn-02(modificato)
How can i convert 2D Key point value (x, y) to Position (x, y, z) on each bone in the body (3D Model) in Unity? Thanks
1
Glenn JocherUltralyticsConverting 2D keypoints to a 3D model position in Unity requires some form of depth estimation since 2D keypoints captured from images or video only provide information on the x and y axes. To add the z-axis (depth), you'll typically need additional data or a model that can infer depth from the given information.
While Ultralytics YOLOv8 specializes in pose estimation providing 2D [x, y] keypoints, integrating these with a 3D model in Unity to achieve the desired [x, y, z] positioning might involve:
- Using stereo vision techniques if you have images from multiple angles.
- Applying a separate depth estimation model that can predict the z-coordinate based on the 2D image.
- Utilizing additional sensors data (like Lidar or structured light sensors) that provides depth information.
Once you have the depth information, you can map the 2D keypoints [x, y] from YOLOv8 to 3D [x, y, z] coordinates in Unity by aligning the keypoints with the depth information.
Here's a conceptual snippet for understanding:
# Example for converting (x, y) keypoints to (x, y, z) # This assumes you have a method to retrieve 'z' (depth) depth_data = get_depth_information() # Custom method to obtain depth keypoints_2d = [(x, y) for x, y in detected_keypoints] # from YOLOv8 keypoints_3d = [(x, y, depth_data[x, y]) for x, y in keypoints_2d]In Unity, you would then apply these 3D coordinates to position the joints or bones of your model accordingly. Note that exact implementation details would depend on how you're structuring your Unity project and the source of your depth data.
Remember, working with 3D models and real-world positioning introduces complexities, especially concerning coordinate systems alignment and scale adjustments across different frameworks and data sources. 🎮🕵️♂️
leonidasavila
How can i calculate angle position between three points? Thanks
1
Paula DerrengerUltralytics@leonidasavila hey there! 👋 To calculate the angle between three points, you can use the law of cosines. Here's a quick example in Python:
import numpy as np def calculate_angle(p1, p2, p3): # p1, p2, p3 are the points in format [x, y] # Calculate the vectors v1 = np.array(p1) - np.array(p2) v2 = np.array(p3) - np.array(p2) # Calculate the angle in radians angle_rad = np.arccos(np.dot(v1, v2) / (np.linalg.norm(v1) * np.linalg.norm(v2))) # Convert to degrees angle_deg = np.degrees(angle_rad) return angle_deg # Example points p1 = [0, 0] p2 = [1, 0] p3 = [1, 1] angle = calculate_angle(p1, p2, p3) print(f"The angle is {angle} degrees")This calculates the angle at
p2formed by the line segmentsp1p2andp2p3. Hope this helps! Let me know if you have any other questions. 😊1leonidasavila
Thanks @pderrenger, for your quickly response! I´m trying to migrate our startup app from mediapipe to yolo 😍
Do you have any tutorial or short example to define specifics landmarks to make calculates? (4 example push-up)
Best regards! Leonidas
Paula DerrengerUltralyticsHey Leonidas! 🌟
It's awesome to hear about your transition from MediaPipe to YOLO for your startup app! For specific landmark detection like push-ups, you can leverage our YOLOv8 pose models. Here's a quick example to get you started:
from ultralytics import YOLO # Load a pretrained pose model model = YOLO('yolov8n-pose.pt') # Predict keypoints on an image results = model('path/to/your/image.jpg') # Access keypoints keypoints = results[0].keypoints # Now, you can use these keypoints to calculate angles or any other metrics you needThis snippet loads a pretrained YOLOv8 pose model and predicts keypoints on your image. You can then use these keypoints for further calculations, like angles between joints during push-ups.
For more detailed guidance, check out our Pose Estimation page. If you have any more questions or need further assistance, feel free to ask. Happy coding! 😊
ozankavcu38
By the way sir after loading the model how could we dissapear the pose estimatet lines like boxes=False argument
Paula DerrengerUltralytics(modificato)Hey there! 😊 To hide the pose estimation lines (similar to using
boxes=Falsefor bounding boxes), you can simply not plot them. When you're working with the results from the pose estimation model, you have control over what gets visualized. Here's a quick example on how to display the keypoints without drawing the connecting lines:from ultralytics import YOLO # Load your pose model model = YOLO('yolov8n-pose.pt') # Run prediction results = model('path/to/image.jpg') # Access keypoints keypoints = results[0].keypoints # Now, you can visualize keypoints without drawing lines between them # This part depends on how you're visualizing. For example, using OpenCV to plot keypoints: import cv2 image = cv2.imread('path/to/image.jpg') for person in keypoints.xy: # one (17, 2) tensor per detected person for x, y in person.tolist(): cv2.circle(image, (int(x), int(y)), radius=3, color=(0, 255, 0), thickness=-1) cv2.imshow("Keypoints without lines", image) cv2.waitKey(0) cv2.destroyAllWindows()This way, you'll see the keypoints on your image without the estimated pose lines. Hope this helps, and good luck with your app migration! If you have any more questions, feel free to ask. 🚀
1Kindstep
I am currently using Yolo11 for my thesis in software engineering. Regarding the calculation of angles using keypoints, what is the correct way to access the detected keypoints directly in the code? assuming the indexing the same as in:
0: Nose 1: Left Eye 2: Right Eye 3: Left Ear 4: Right Ear 5: Left Shoulder 6: Right Shoulder 7: Left Elbow 8: Right Elbow 9: Left Wrist 10: Right Wrist 11: Left Hip 12: Right Hip 13: Left Knee 14: Right Knee 15: Left Ankle 16: Right Ankle
So assuming i use a similar function as you proposed, to calculate the angle of the right elbow joint a live feed (e.g. webcam) and the code is something like this:
model = YOLO('yolo11x-pose.pt')
results = model(frame, show=True, conf=conf, device=device, save=True)
keypoints = results[0].keypoints
angle = calculate_angle(keypoints6, keypoints8, keypoints10) # print(f"The angle is {angle} degrees")
What is the correct way to access each keypoint? Is it indexed in a array like keypoints[6] or what would be the correct way to go forward?
I hope my question is not too messy. It's getting quite late, but I am enjopying my time working with Yolo11.
1Kindstep
Whoops, was not meant to be edited like that :D
Glenn JocherUltralyticsTo access specific keypoints in YOLO11 pose estimation, you can index the
keypointsarray directly using the indices corresponding to each body part. For example, to calculate the angle at the right elbow, you can usekeypoints[6],keypoints[8], andkeypoints[10]for the right shoulder, right elbow, and right wrist, respectively. Let me know if you need further assistance!Kindstep
Okay, i Already figured it out now that I had time to try it. Seems I was on the right track. :)
Have a great weekend everybody!
1leonidasavila
@kindstep thanks for sharing. Good luck with your thesis, it's will be fine! Currently, we are using YOLO8 and we are studying to migrate YOLO11... I hope the deploy of hand pose very soon!
Cosophia
What task does line annotation correspond to? what I know is : rectangle -> detection point -> pose polygon -> Segment
Paula DerrengerUltralyticsA line annotation does not map to a standalone Ultralytics task. Use pose estimation when the line represents connections between labeled keypoints, or segmentation when you need the line’s pixel-level shape; please continue dropping questions here so the Ultralytics team can assist.
yacinehrb
Is it possible to use byte tracking with YoloPose26 ?
Glenn JocherUltralyticsYes — Ultralytics YOLO26 pose models can be used with ByteTrack through Track mode; feel free to post any follow-up details here so the Ultralytics team can see them, and the pose docs and Track mode docs cover the supported workflow.
JC3
Ok... but where is the documentation on how to actually run the model and access the results? Seems to be missing.
Glenn JocherUltralyticsYou can run a pose model via Python or CLI; the returned
resultsobjects expose keypoints directly—see the usage pattern on the Pose Estimation docs (and feel free to drop any follow-up questions here so the Ultralytics team can see them).from ultralytics import YOLO model = YOLO("yolo26n-pose.pt") results = model("path/to/image.jpg") # or a video path / 0 for webcam r = results[0] xy = r.keypoints.xy # (n, k, 2) pixel coords xyn = r.keypoints.xyn # (n, k, 2) normalized coords kpts = r.keypoints.data # (n, k, 3) x, y, visible/conf (if available)yolo pose predict model=yolo26n-pose.pt source=path/to/image.jpg
shayan-mesdaghi
Hello everyone, I trained a YOLO model on a dataset I created myself. The training went well, but I have a major problem: why isn't the skeleton (landmarks connections) displayed on my images and videos, and only the keypoints are shown? I performed the labelling process using Roboflow. I should mention that when I use a pre-trained YOLO model, the skeleton is displayed, but when I train the dataset myself, only the keypoints are present. Please guide me, thank you.
Glenn JocherUltralytics@shayan-mesdaghi skeleton lines are auto-drawn only for the COCO 17‑keypoint human schema; custom keypoint counts/orders show dots unless you render your own connections. If you’re not using the COCO 17 order, set your skeleton at draw time like this:
from ultralytics import YOLO from ultralytics.utils.plotting import Annotator # 1-based COCO-17 pairs; adjust to your schema as needed skeleton = [(16,14),(14,12),(17,15),(15,13),(12,13),(6,12),(7,13),(6,7), (6,8),(7,9),(8,10),(9,11),(2,3),(1,2),(1,3),(2,4),(3,5),(4,6),(5,7)] model = YOLO("best.pt") for r in model("image_or_video.mp4"): im = r.orig_img.copy() ann = Annotator(im) ann.skeleton = skeleton # 1-based indices for k in r.keypoints.xy: ann.kpts(k, kpt_line=True) im_out = ann.result()If you edited
plotting.py, restart your Python session/notebook so changes load. Method details are in the Annotator.kpts reference, which notes the human‑only default forkpt_linesee Annotator.kpts, and the dataset YAML fields for pose (e.g.,kpt_shape) are shown in the Pose datasets overview.
mobin3399
Hi, I’ve trained a custom YOLOv8-pose model with two object classes. One class occupies more than 80% of the image area (large object), while the other one is much smaller. Interestingly, the smaller object produces much more accurate keypoint predictions, while the large object shows poor keypoint localization — even though both classes have precise annotations, balanced samples, and consistent lighting/camera setup.
I have already tried:
- Careful labeling (pixel-level accurate keypoints)
- Strong data augmentation
- Adjusting loss weights for keypoints and bounding boxes
- Different model scales (YOLOv8n-pose, YOLOv8m-pose)
However, the issue remains: pose accuracy drops significantly for the larger object, despite good detection and validation metrics.
From my analysis, this might be related to:
- The OKS-based keypoint loss being scale-dependent (large objects are penalized less for the same absolute error).
- The receptive field or feature resolution in the pose head being insufficient for very large objects.
- Bounding box coverage (close to image borders) affecting normalized keypoint coordinates.
Has anyone else observed this behavior in YOLOv8-pose or YOLOv9-pose? And is there a recommended way to make keypoint accuracy more scale-invariant (for example, by modifying the OKS loss or normalization strategy)?
Any guidance or similar experiences would be greatly appreciated!
pratikbariya
Ok, you have done proper annotation, augmentation, loss weight adjustments, and tried different models. See, there is an issue regarding YOLOV8-POSE for large objects. I think you have to focus on the KPT loss also. If it is low, then try to improve that by making changes in loss (by overriding or code changes).
If possible, share an image of the object and model matrix. That will help understand the issue.
1
Glenn JocherUltralytics(modificato)@pratikbariya @mobin3399 adding a few concrete levers you can try for the “large object → poorer keypoint localization” case: train/val at higher resolution and lighter augments for pose, e.g.
imgsz=1280 mosaic=0.0 degrees=0 translate=0.05 scale=0.5 fliplr=0.5, and prefer images where the large object isn’t hard‑clipped by borders (pad or pre-crop so it fills the frame); if you’re not using the COCO 17‑kpt schema, note our evaluator defaults to uniform OKS sigmas which can bias big objects—set explicit sigmas for your keypoints or adopt the COCO set; details and usage are in the Pose docs and PoseValidator notes.yolo pose train model=yolo26x-pose.pt data=your.yaml imgsz=1280 mosaic=0.0 degrees=0 translate=0.05 scale=0.5 fliplr=0.5See the Pose Estimation guide for end‑to‑end training tips and keypoint ordering, and the PoseValidator reference for how OKS is computed. Pose Estimation – Ultralytics YOLO • PoseValidator reference (OKS/sigma behavior)
1mobin3399
Thank you for your response. I followed your suggestion, and it helped me resolve the issue to a large extent. I really appreciate your guidance and support.
