Começar

Estimativa de pose com Ultralytics YOLO

Ultralytics YOLO pose estimation with human body keypoint detection

A estimativa de pose é uma tarefa que envolve identificar a localização de pontos específicos em uma imagem, geralmente chamados de pontos-chave. Os pontos-chave podem representar várias partes do objeto, como articulações, marcos anatômicos ou outras características distintivas. As localizações dos pontos-chave geralmente são representadas por um conjunto de coordenadas 2D [x, y], opcionalmente com uma indicação de visibilidade [x, y, visible].

A saída de um modelo de estimativa de pose é um conjunto de pontos que representa os pontos-chave de um objeto na imagem, geralmente acompanhado pelas pontuações de confiança de cada ponto. A estimativa de pose é uma boa opção quando você precisa identificar partes específicas de um objeto em uma cena e a localização delas em relação umas às outras.



Assista: Como executar estimativa de pose em tempo real com Ultralytics YOLO26 | Rastreamento e extração de pontos-chave 🕺
Dica

Os modelos Pose do YOLO26 usam o sufixo -pose, por exemplo, yolo26n-pose.pt, e são pré-treinados nos pontos-chave do COCO.

Modelos#

Abaixo estão os modelos YOLO26 Pose pré-treinados no conjunto de dados pontos-chave COCO.

Os modelos são transferidos automaticamente da versão mais recente do Ultralytics na primeira utilização.

Modelotamanho
(pixels)
mAPpose50-95
(e2e)
mAPpose50
(e2e)
Velocidade
CPU ONNX
(ms)
Velocidade
T4 TensorRT10
(ms)
parâmetros
(M)
FLOPs
(B)
YOLO26n-pose64057.283.340.3 ± 0.51.8 ± 0.02.97.6
YOLO26s-pose64063.086.685.3 ± 0.92.7 ± 0.010.424.1
YOLO26m-pose64068.889.6218.0 ± 1.55.0 ± 0.121.573.3
YOLO26l-pose64070.490.5275.4 ± 2.46.5 ± 0.125.991.7
YOLO26x-pose64071.691.6565.4 ± 3.012.2 ± 0.257.6202.3
  • Os valores de mAPval são para um único modelo e uma única escala no conjunto de dados COCO Keypoints val2017.
    Reproduza com yolo pose val data=coco-pose.yaml device=0 nms=False
  • Velocidade média nas imagens de COCO val com ONNX em CPU e TensorRT10 numa GPU NVIDIA T4.
    Reproduz os resultados com yolo pose val data=coco-pose.yaml batch=1 device=0|cpu nms=False
  • Os valores de Params e FLOPs referem-se a modelos fundidos após a fusão de Conv/BatchNorm e a remoção do ramo de deteção não utilizado. Os pontos de controlo pré-treinados mantêm a arquitetura de treino completa e podem apresentar contagens superiores.

Consulte a prévia não lançada do YOLO27 para ver resultados preliminares de pontos-chave COCO.

Treinar#

Treina um modelo YOLO26n-pose no conjunto de dados COCO8-pose durante 100 épocas, com tamanho de imagem 640.

Exemplo
from ultralytics import YOLO

# Carregar um modelo
model = YOLO("yolo26n-pose.yaml")  # crie um novo modelo a partir de YAML
model = YOLO("yolo26n-pose.pt")  # carregue um modelo pré-treinado (recomendado para treinamento)
model = YOLO("yolo26n-pose.yaml").load("yolo26n-pose.pt")  # crie a partir de YAML e transfira os pesos

# Treinar o modelo
results = model.train(data="coco8-pose.yaml", epochs=100, imgsz=640)

Consulte a página Treinar para ver todos os detalhes do modo train. Os modelos de pose também podem ser treinados com o treinamento na nuvem da Ultralytics Platform.

Formato do conjunto de dados#

Você encontra detalhes sobre o formato do conjunto de dados de pose YOLO no Guia do conjunto de dados. Para converter um conjunto de dados JSON existente de pontos-chave COCO para o formato YOLO, use a função integrada convert_coco com use_keypoints=True, conforme descrito no guia de conversão de COCO para YOLO. A anotação da Ultralytics Platform também oferece suporte a rótulos de pose com modelos de esqueleto integrados para pessoas, mãos, rostos e configurações personalizadas de pontos-chave.

Para tarefas personalizadas de estimativa de pose, você também pode explorar conjuntos de dados especializados, como Tiger-Pose para estimativa de pose animal, Hand Keypoints para rastreamento de mãos ou Dog-Pose para análise de pose canina.

Validar#

Valide a precisão do modelo YOLO26n-pose treinado, medida como precisão média (mAP). Não são necessários argumentos, pois model mantém seus dados de treinamento data e argumentos como atributos do modelo: path/to/best.pt do exemplo de treinamento valida o modelo em COCO8-pose. Os pesos oficiais registram um caminho para o conjunto de dados de treinamento que não existe na sua máquina; por isso, eles recorrem ao valor padrão da tarefa coco8-pose.yaml e exibem um aviso. Passe data para validar em outro conjunto de dados.

Exemplo
from ultralytics import YOLO

# Carregar um modelo
model = YOLO("yolo26n-pose.pt")  # carrega um modelo oficial
model = YOLO("path/to/best.pt")  # carregar um modelo personalizado

# Valida o modelo
metrics = model.val()  # não são necessários argumentos; o conjunto de dados e as definições são guardados
metrics.box.map  # map50-95
metrics.box.map50  # map50
metrics.box.map75  # map75
metrics.box.maps  # mAP50-95 por classe; as classes ausentes do conjunto de validação recebem o mAP geral
metrics.box.ap_class_index  # índices das classes que foram efetivamente avaliadas
metrics.box.image_metrics  # dicionário de métricas por imagem para caixas, com precisão, revocação, 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) por classe; as classes ausentes do conjunto de validação recebem o mAP(P) geral
metrics.pose.ap_class_index  # índices das classes que foram efetivamente avaliadas
metrics.pose.image_metrics  # dicionário de métricas por imagem para pose, com precisão, revocação, F1, TP, FP e FN

Prever#

Use um modelo YOLO26n-pose treinado para fazer previsões em imagens.

Exemplo
from ultralytics import YOLO

# Carregar um modelo
model = YOLO("yolo26n-pose.pt")  # carrega um modelo oficial
model = YOLO("path/to/best.pt")  # carregar um modelo personalizado

# Faz previsões com o modelo
results = model("https://ultralytics.com/images/bus.jpg")  # faz uma previsão numa imagem

# Acede aos resultados
for result in results:
    xy = result.keypoints.xy  # coordenadas x e y
    xyn = result.keypoints.xyn  # normalized
    kpts = result.keypoints.data  # x, y, visibilidade (se disponível)

Consulta os detalhes completos do modo predict na página Previsão.

Saída dos resultados#

A estimativa de pose retorna um objeto Results por imagem. Os principais campos de previsão são result.keypoints, para as coordenadas da pose, e result.boxes, para as instâncias detectadas às quais esses pontos-chave pertencem.

AtributoTipoFormatoDescrição
result.keypointsKeypoints(N)Pontos-chave.
result.keypoints.datatorch.float32(N,K,2/3)x,y mais visibilidade/confiança opcional.
result.keypoints.xytorch.float32(N,K,2)Pontos-chave em pixels.
result.keypoints.xyntorch.float32(N,K,2)Pontos-chave normalizados.
result.boxesBoxes(N)Caixas de instância.

Para ver os campos Results específicos de cada tarefa, consulta a secção Resultados da previsão por tarefa.

Mapa de índices dos pontos-chave#

Os modelos YOLO26 Pose padrão preveem os 17 pontos-chave COCO; portanto, o índice k em result.keypoints.xy[:, k] corresponde a:

  1. Nariz
  2. Olho esquerdo
  3. Olho direito
  4. Orelha esquerda
  5. Orelha direita
  6. Ombro esquerdo
  7. Ombro direito
  8. Cotovelo esquerdo
  9. Cotovelo direito
  10. Pulso esquerdo
  11. Pulso direito
  12. Quadril esquerdo
  13. Quadril direito
  14. Joelho esquerdo
  15. Joelho direito
  16. Tornozelo esquerdo
  17. Tornozelo direito

Exportar#

Exporte um modelo YOLO26n-pose para outro formato, como ONNX, CoreML etc.

Exemplo
from ultralytics import YOLO

# Carregar um modelo
model = YOLO("yolo26n-pose.pt")  # carrega um modelo oficial
model = YOLO("path/to/best.pt")  # carregar um modelo personalizado

# Exporta o modelo
model.export(format="onnx")

Os formatos de exportação disponíveis para YOLO26-pose estão na tabela abaixo. Você pode exportar para qualquer formato usando o argumento format, por exemplo, format='onnx' ou format='engine'. Você pode executar previsões ou validações diretamente nos modelos exportados, por exemplo, yolo predict model=yolo26n-pose.onnx. Após a conclusão da exportação, são exibidos exemplos de uso do modelo.

FormatoArgumento formatModeloMetadadosArgumentos
PyTorch-yolo26n-pose.pt✅-
TorchScripttorchscriptyolo26n-pose.torchscript✅imgsz, quantize, dynamic, nms, batch, device
ONNXonnxyolo26n-pose.onnx✅imgsz, quantize, dynamic, simplify, opset, nms, batch, data, fraction, device
OpenVINOopenvinoyolo26n-pose_openvino_model/✅imgsz, quantize, dynamic, nms, batch, data, fraction, device
TensorRTengineyolo26n-pose.engine✅imgsz, quantize, dynamic, simplify, opset, workspace, nms, batch, data, fraction, device
CoreMLcoremlyolo26n-pose.mlpackage✅imgsz, dynamic, quantize, nms, batch, device
Apple Core AIcoreaiyolo26n-pose.aimodel✅imgsz, batch, quantize
TF SavedModelsaved_modelyolo26n-pose_saved_model/✅imgsz, quantize, opset, nms, batch, data, fraction, device
TF GraphDefpbyolo26n-pose.pb❌imgsz, opset, batch, device
TF Edge TPUedgetpuyolo26n-pose_edgetpu.tflite✅imgsz, quantize, opset, data, fraction, device
LiteRTlitertyolo26n-pose.tflite✅imgsz, quantize, batch, data, fraction, device
PaddlePaddlepaddleyolo26n-pose_paddle_model/✅imgsz, batch, device
MNNmnnyolo26n-pose.mnn✅imgsz, batch, dynamic, quantize, simplify, opset, nms, device
NCNNncnnyolo26n-pose_ncnn_model/✅imgsz, quantize, device
IMX500imxyolo11n_imx_model/✅imgsz, quantize, data, fraction, nms, device
RKNNrknnyolo26n-pose_rknn_model/✅imgsz, batch, name, quantize, simplify, opset, data, fraction, device
ExecuTorchexecutorchyolo26n-pose_executorch_model/✅imgsz, quantize, batch, data, fraction, device
Axeleraaxelerayolo26n-pose_axelera_model/✅imgsz, batch, quantize, data, fraction, device
DEEPXdeepxyolo26n-pose_deepx_model/✅imgsz, quantize, simplify, opset, data, optimize, device
Qualcomm QNNqnnyolo26n-pose_qnn.onnx✅imgsz, batch, name, quantize, simplify, opset, data, fraction, device
Hailohailoyolo26n-pose_hailo_model/✅imgsz, name, quantize, data, fraction, simplify, conf, iou, device
Huawei Ascendascendyolo26n-pose_ascend_model/✅imgsz, batch, name, quantize, opset, simplify, nms, device
AMD Xilinxxilinxyolo26n-pose_xilinx_model/✅imgsz, name, quantize, data, fraction, opset, simplify, device
NXPnxpyolo26n-pose_nxp.tflite✅imgsz, quantize, data, fraction, device
ST Edge AIstedgeaiyolo26n-pose_stedgeai.onnx✅imgsz, quantize, data, fraction, opset, simplify, device

nms=None usa por padrão saídas brutas para NMS externo (YOLO26 mantém sua cabeça sem NMS na Axelera). Define nms=False para selecionar uma cabeça sem NMS disponível; os formatos não compatíveis recorrem ao caminho de saída nativo. As entradas nms acima identificam os formatos que podem incorporar NMS com nms=True.

Consulte os detalhes completos de export na página Exportação.

Perguntas frequentes#

  • A estimativa de pose com Ultralytics YOLO26 envolve identificar pontos específicos, conhecidos como pontos-chave, em uma imagem. Esses pontos-chave geralmente representam articulações ou outras características importantes do objeto. A saída inclui as coordenadas [x, y] e as pontuações de confiança de cada ponto. Os modelos YOLO26-pose foram projetados especificamente para essa tarefa e usam o sufixo -pose, como yolo26n-pose.pt. Esses modelos são pré-treinados em conjuntos de dados como os pontos-chave do COCO e podem ser usados em várias tarefas de estimativa de pose. Os modelos padrão preveem os 17 pontos-chave do COCO.

  • Para treinar um modelo YOLO26-pose em um conjunto de dados personalizado, carregue um modelo, que pode ser um modelo novo definido por um arquivo YAML ou um modelo pré-treinado. Em seguida, você pode iniciar o processo de treinamento usando o conjunto de dados e os parâmetros especificados.

    Exemplo
    from ultralytics import YOLO
    
    # Carregar um modelo
    model = YOLO("yolo26n-pose.yaml")  # crie um novo modelo a partir de YAML
    model = YOLO("yolo26n-pose.pt")  # carregue um modelo pré-treinado (recomendado para treinamento)
    
    # Treinar o modelo
    results = model.train(data="your-dataset.yaml", epochs=100, imgsz=640)

    Para ver todos os detalhes sobre treinamento, consulte a seção Treinar. Você também pode usar o treinamento na nuvem da Ultralytics Platform para treinar modelos personalizados de estimativa de pose sem escrever código.

  • A validação de um modelo YOLO26-pose consiste em avaliar sua precisão usando os mesmos parâmetros de conjunto de dados mantidos durante o treinamento. Veja um exemplo:

    Exemplo
    from ultralytics import YOLO
    
    # Carregar um modelo
    model = YOLO("yolo26n-pose.pt")  # carrega um modelo oficial
    model = YOLO("path/to/best.pt")  # carregar um modelo personalizado
    
    # Valida o modelo
    metrics = model.val()  # não são necessários argumentos; o conjunto de dados e as definições são guardados

    Para mais informações, acesse a seção Val.

  • Sim, você pode exportar um modelo YOLO26-pose para vários formatos, como ONNX, CoreML, TensorRT e outros. Isso pode ser feito usando Python ou a interface de linha de comando (CLI).

    Exemplo
    from ultralytics import YOLO
    
    # Carregar um modelo
    model = YOLO("yolo26n-pose.pt")  # carrega um modelo oficial
    model = YOLO("path/to/best.pt")  # carregar um modelo personalizado
    
    # Exporta o modelo
    model.export(format="onnx")

    Consulte a seção Exportar para mais detalhes. Os modelos exportados podem ser implantados em dispositivos de borda para aplicações em tempo real, como monitoramento de atividades físicas, análise esportiva ou robótica.

  • A Ultralytics YOLO26 oferece vários modelos de pose pré-treinados, como YOLO26n-pose, YOLO26s-pose, YOLO26m-pose, entre outros. Esses modelos variam em tamanho, precisão (mAP) e velocidade. Para ver a lista completa com mAP de pontos-chave COCO, velocidade, parâmetros e FLOPs por modelo, consulte a seção Modelos.

Comentários465

Faz uma pergunta, partilha os teus resultados ou ajuda alguém.

  1. 3300299472GitHub

    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
    1. Glenn JocherUltralytics(editado)

      @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 results object 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! 😊

  2. AdadAlShababGitHub

    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
    1. Glenn JocherUltralytics

      Hi! 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, y2 with 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! 😊

  3. Pakorn-02GitHub(editado)

    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
    1. Paula DerrengerUltralytics

      Hi 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! 🚀

  4. Pakorn-02GitHub(editado)

    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
    1. Glenn JocherUltralytics

      Converting 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:

      1. Using stereo vision techniques if you have images from multiple angles.
      2. Applying a separate depth estimation model that can predict the z-coordinate based on the 2D image.
      3. 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. 🎮🕵️‍♂️

    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 p2 formed by the line segments p1p2 and p2p3. Hope this helps! Let me know if you have any other questions. 😊

      1
    2. leonidasavilaGitHub

      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

    3. Paula DerrengerUltralytics

      Hey 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 need

      This 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! 😊

    4. ozankavcu38GitHub

      By the way sir after loading the model how could we dissapear the pose estimatet lines like boxes=False argument

    5. Paula DerrengerUltralytics(editado)

      Hey there! 😊 To hide the pose estimation lines (similar to using boxes=False for 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. 🚀

      1
    6. KindstepGitHub

      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.

      1
    7. Glenn JocherUltralytics

      To access specific keypoints in YOLO11 pose estimation, you can index the keypoints array directly using the indices corresponding to each body part. For example, to calculate the angle at the right elbow, you can use keypoints[6], keypoints[8], and keypoints[10] for the right shoulder, right elbow, and right wrist, respectively. Let me know if you need further assistance!

    8. KindstepGitHub

      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!

      1
    9. leonidasavilaGitHub

      @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!

  5. CosophiaGitHub

    What task does line annotation correspond to? what I know is : rectangle -> detection point -> pose polygon -> Segment

    1. Paula DerrengerUltralytics

      A 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.

    1. Glenn JocherUltralytics

      Yes — 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.

  6. JC3GitHub

    Ok... but where is the documentation on how to actually run the model and access the results? Seems to be missing.

    1. Glenn JocherUltralytics

      You can run a pose model via Python or CLI; the returned results objects 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
  7. shayan-mesdaghiGitHub

    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.

    1. 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 for kpt_line see Annotator.kpts, and the dataset YAML fields for pose (e.g., kpt_shape) are shown in the Pose datasets overview.

  8. mobin3399GitHub

    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:

    1. The OKS-based keypoint loss being scale-dependent (large objects are penalized less for the same absolute error).
    2. The receptive field or feature resolution in the pose head being insufficient for very large objects.
    3. 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!

    1. pratikbariyaGitHub

      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
    2. Glenn JocherUltralytics(editado)

      @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.5

      See 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)

      1
    3. mobin3399GitHub

      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.