[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-25.7, 115.74, 20.04, -43.92, 25.46, 0.0]
  Target bbox: [624.61, 289.22, 662.43, 359.19]

Frame 2:
  Drone pose: [-24.95, 116.0, 19.98, -38.35, 29.81, 0.0]
  Target bbox: [582.88, 386.56, 616.31, 452.57]

Frame 3:
  Drone pose: [-24.63, 116.44, 20.0, -40.11, 27.57, 0.0]
  Target bbox: [608.69, 351.15, 644.86, 419.91]

Frame 4:
  Drone pose: [-23.97, 116.8, 19.98, -41.94, 27.07, 0.0]
  Target bbox: [625.91, 327.36, 653.89, 392.07]

Frame 5 (current):
  Drone pose: [-23.64, 117.11, 19.82, -45.62, 31.28, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 572.91, "ymin": 255.41, "xmax": 605.96, "ymax": 324.35}, "waypoint_deltas": [{"dx": 0.42, "dy": 0.45, "dz": 0.18, "dpitch": 4.08, "dyaw": -3.93, "droll": 0.0}, {"dx": 0.88, "dy": 0.82, "dz": 0.18, "dpitch": 4.2, "dyaw": -3.67, "droll": 0.0}, {"dx": 1.34, "dy": 1.18, "dz": 0.18, "dpitch": 4.04, "dyaw": -4.59, "droll": 0.0}, {"dx": 1.8, "dy": 1.55, "dz": 0.18, "dpitch": 3.87, "dyaw": -5.51, "droll": 0.0}, {"dx": 2.27, "dy": 1.91, "dz": 0.18, "dpitch": 3.99, "dyaw": -5.22, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [77.45, 88.33, 22.0, -46.42, -63.43, 0.0]
  Target bbox: [622.44, 324.82, 657.8, 394.55] (model-predicted box)

Frame 2:
  Drone pose: [80.65, 85.33, 21.2, -50.92, -69.53, 0.0]
  Target bbox: [619.18, 321.4, 661.13, 397.63] (model-predicted box)

Frame 3:
  Drone pose: [84.83, 83.33, 20.67, -54.63, -83.56, 0.0]
  Target bbox: [618.97, 321.45, 661.47, 397.19]

Frame 4:
  Drone pose: [89.48, 81.97, 20.65, -55.76, -103.32, 0.0]
  Target bbox: [616.76, 318.87, 663.42, 399.6]

Frame 5 (current):
  Drone pose: [93.85, 81.04, 20.62, -53.77, -118.92, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 619.47, "ymin": 322.5, "xmax": 660.79, "ymax": 396.15}, "waypoint_deltas": [{"dx": 3.4, "dy": -0.75, "dz": -0.03, "dpitch": 2.63, "dyaw": -9.69, "droll": 0.0}, {"dx": 5.6, "dy": -1.44, "dz": -0.05, "dpitch": 4.35, "dyaw": -14.65, "droll": 0.0}, {"dx": 6.88, "dy": -2.1, "dz": -0.07, "dpitch": 5.7, "dyaw": -18.03, "droll": 0.0}, {"dx": 7.68, "dy": -2.7, "dz": -0.09, "dpitch": 5.98, "dyaw": -18.92, "droll": 0.0}, {"dx": 8.3, "dy": -3.25, "dz": -0.2, "dpitch": 6.23, "dyaw": -19.29, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [104.53, 73.65, 20.19, -47.5, -138.29, 0.0]
  Target bbox: [616.93, 319.61, 663.02, 399.49]

Frame 2:
  Drone pose: [104.52, 73.12, 20.17, -47.53, -138.34, 0.0]
  Target bbox: [615.61, 318.93, 664.41, 400.28]

Frame 3:
  Drone pose: [104.5, 72.6, 20.15, -47.54, -138.36, 0.0]
  Target bbox: [618.96, 321.5, 660.92, 397.54]

Frame 4:
  Drone pose: [104.49, 72.09, 20.14, -47.53, -138.37, 0.0]
  Target bbox: [617.42, 320.84, 662.51, 398.32]

Frame 5 (current):
  Drone pose: [104.51, 71.6, 20.12, -47.25, -138.37, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 616.27, "ymin": 319.7, "xmax": 663.71, "ymax": 399.51}, "waypoint_deltas": [{"dx": 0.02, "dy": -0.48, "dz": -0.01, "dpitch": 0.07, "dyaw": 0.01, "droll": 0.0}, {"dx": 0.05, "dy": -0.95, "dz": -0.03, "dpitch": 0.15, "dyaw": 0.02, "droll": 0.0}, {"dx": 0.08, "dy": -1.42, "dz": -0.04, "dpitch": 0.24, "dyaw": 0.03, "droll": 0.0}, {"dx": 0.11, "dy": -1.89, "dz": -0.05, "dpitch": 0.33, "dyaw": 0.03, "droll": 0.0}, {"dx": 0.13, "dy": -2.36, "dz": -0.06, "dpitch": 0.4, "dyaw": 0.04, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [104.67, 64.8, 20.01, -46.68, -138.26, 0.0]
  Target bbox: [618.82, 321.34, 661.06, 397.75]

Frame 2:
  Drone pose: [104.71, 64.27, 20.01, -46.66, -138.4, 0.0]
  Target bbox: [616.18, 319.82, 663.8, 399.45]

Frame 3:
  Drone pose: [104.71, 63.78, 20.01, -46.64, -138.36, 0.0]
  Target bbox: [616.57, 319.79, 663.4, 399.44]

Frame 4:
  Drone pose: [104.69, 63.3, 20.01, -46.64, -138.29, 0.0]
  Target bbox: [616.16, 319.17, 663.83, 400.05]

Frame 5 (current):
  Drone pose: [104.6, 62.85, 20.01, -46.69, -137.96, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 619.1, "ymin": 321.05, "xmax": 660.77, "ymax": 397.99}, "waypoint_deltas": [{"dx": -0.14, "dy": -0.4, "dz": 0.0, "dpitch": -0.07, "dyaw": 0.54, "droll": 0.0}, {"dx": -0.94, "dy": -0.62, "dz": -0.01, "dpitch": -0.69, "dyaw": 3.0, "droll": 0.0}, {"dx": -2.14, "dy": -0.74, "dz": -0.01, "dpitch": -1.59, "dyaw": 6.81, "droll": 0.0}, {"dx": -3.62, "dy": -0.74, "dz": -0.01, "dpitch": -2.51, "dyaw": 11.89, "droll": 0.0}, {"dx": -5.27, "dy": -0.67, "dz": -0.01, "dpitch": -3.24, "dyaw": 17.96, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [91.5, 60.45, 20.0, -48.81, -90.37, 0.0]
  Target bbox: [624.12, 322.58, 655.63, 396.34]

Frame 2:
  Drone pose: [91.46, 59.93, 20.0, -48.85, -90.24, 0.0]
  Target bbox: [621.97, 321.82, 657.87, 397.0]

Frame 3:
  Drone pose: [91.42, 59.4, 20.0, -48.9, -90.1, 0.0]
  Target bbox: [622.75, 322.72, 657.18, 396.18]

Frame 4:
  Drone pose: [91.38, 58.88, 20.0, -48.94, -89.97, 0.0]
  Target bbox: [628.54, 321.74, 651.48, 397.08]

Frame 5 (current):
  Drone pose: [91.32, 58.35, 20.0, -48.98, -89.76, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 627.42, "ymin": 321.53, "xmax": 652.74, "ymax": 397.28}, "waypoint_deltas": [{"dx": -0.05, "dy": -0.5, "dz": 0.0, "dpitch": 0.0, "dyaw": 0.18, "droll": 0.0}, {"dx": -0.07, "dy": -0.94, "dz": 0.0, "dpitch": 0.1, "dyaw": 0.27, "droll": 0.0}, {"dx": -0.08, "dy": -1.34, "dz": 0.0, "dpitch": 0.28, "dyaw": 0.28, "droll": 0.0}, {"dx": -0.08, "dy": -1.77, "dz": 0.0, "dpitch": 0.39, "dyaw": 0.29, "droll": 0.0}, {"dx": -0.08, "dy": -2.25, "dz": 0.0, "dpitch": 0.43, "dyaw": 0.28, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [91.26, 51.68, 20.0, -48.42, -89.56, 0.0]
  Target bbox: [626.31, 322.31, 653.97, 396.57]

Frame 2:
  Drone pose: [91.26, 51.25, 20.0, -48.52, -89.56, 0.0]
  Target bbox: [625.42, 322.58, 654.87, 396.31]

Frame 3:
  Drone pose: [91.27, 50.83, 20.0, -48.4, -89.59, 0.0]
  Target bbox: [620.34, 322.69, 659.92, 396.2]

Frame 4:
  Drone pose: [91.26, 50.4, 20.0, -48.28, -89.55, 0.0]
  Target bbox: [628.55, 321.78, 651.74, 397.06]

Frame 5 (current):
  Drone pose: [91.29, 49.97, 20.0, -48.16, -89.67, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 622.58, "ymin": 322.87, "xmax": 657.63, "ymax": 396.05}, "waypoint_deltas": [{"dx": 0.02, "dy": -0.46, "dz": 0.0, "dpitch": 0.06, "dyaw": -0.05, "droll": 0.0}, {"dx": 0.01, "dy": -0.94, "dz": 0.0, "dpitch": 0.1, "dyaw": -0.02, "droll": 0.0}, {"dx": 0.01, "dy": -1.43, "dz": 0.0, "dpitch": 0.11, "dyaw": -0.02, "droll": 0.0}, {"dx": -0.03, "dy": -1.95, "dz": 0.0, "dpitch": 0.08, "dyaw": 0.12, "droll": 0.0}, {"dx": -0.03, "dy": -2.5, "dz": 0.0, "dpitch": 0.0, "dyaw": 0.12, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [90.61, 41.05, 20.0, -51.07, -79.57, 0.0]
  Target bbox: [618.71, 320.65, 661.2, 398.09]

Frame 2:
  Drone pose: [90.65, 40.42, 20.0, -51.13, -77.8, 0.0]
  Target bbox: [619.02, 319.54, 660.8, 399.14]

Frame 3:
  Drone pose: [90.61, 39.56, 20.0, -51.55, -75.49, 0.0]
  Target bbox: [616.4, 319.08, 663.45, 399.68]

Frame 4:
  Drone pose: [90.59, 38.7, 20.0, -51.93, -73.21, 0.0]
  Target bbox: [619.12, 320.25, 660.71, 398.36]

Frame 5 (current):
  Drone pose: [90.05, 37.76, 20.0, -52.08, -68.88, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 619.39, "ymin": 321.07, "xmax": 660.41, "ymax": 397.55}, "waypoint_deltas": [{"dx": -0.7, "dy": -0.78, "dz": 0.0, "dpitch": 0.41, "dyaw": 4.68, "droll": 0.0}, {"dx": -1.24, "dy": -1.48, "dz": 0.0, "dpitch": 0.97, "dyaw": 8.51, "droll": 0.0}, {"dx": -1.39, "dy": -1.97, "dz": 0.0, "dpitch": 1.59, "dyaw": 10.54, "droll": 0.0}, {"dx": -1.4, "dy": -2.42, "dz": 0.0, "dpitch": 2.15, "dyaw": 12.02, "droll": 0.0}, {"dx": -1.42, "dy": -2.88, "dz": 0.0, "dpitch": 2.72, "dyaw": 13.45, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [91.13, 31.62, 20.0, -46.89, -52.81, 0.0]
  Target bbox: [622.75, 323.01, 656.92, 395.96]

Frame 2:
  Drone pose: [91.67, 31.18, 20.0, -46.85, -53.02, 0.0]
  Target bbox: [622.68, 324.94, 657.07, 393.92]

Frame 3:
  Drone pose: [92.22, 30.74, 20.0, -46.83, -53.26, 0.0]
  Target bbox: [624.16, 323.85, 655.56, 395.08]

Frame 4:
  Drone pose: [92.77, 30.3, 20.0, -46.8, -53.5, 0.0]
  Target bbox: [621.29, 323.8, 658.37, 395.24]

Frame 5 (current):
  Drone pose: [93.29, 29.86, 20.0, -46.74, -53.67, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 620.61, "ymin": 322.73, "xmax": 659.02, "ymax": 396.3}, "waypoint_deltas": [{"dx": 0.48, "dy": -0.43, "dz": 0.0, "dpitch": 0.11, "dyaw": -0.08, "droll": 0.0}, {"dx": 0.91, "dy": -0.85, "dz": 0.0, "dpitch": 0.28, "dyaw": -0.04, "droll": 0.0}, {"dx": 1.27, "dy": -1.26, "dz": 0.0, "dpitch": 0.05, "dyaw": -1.15, "droll": 0.0}, {"dx": 1.6, "dy": -1.67, "dz": 0.0, "dpitch": -0.11, "dyaw": -2.17, "droll": 0.0}, {"dx": 1.88, "dy": -2.07, "dz": 0.0, "dpitch": -0.23, "dyaw": -3.12, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [97.32, 24.19, 20.0, -47.42, -64.32, 0.0]
  Target bbox: [621.21, 320.05, 659.1, 399.01]

Frame 2:
  Drone pose: [97.54, 23.77, 20.0, -47.46, -65.09, 0.0]
  Target bbox: [615.96, 318.96, 664.33, 400.22]

Frame 3:
  Drone pose: [97.76, 23.35, 20.0, -47.49, -65.83, 0.0]
  Target bbox: [620.88, 320.73, 659.43, 398.42]

Frame 4:
  Drone pose: [97.96, 22.92, 20.0, -47.51, -66.55, 0.0]
  Target bbox: [617.24, 319.86, 663.08, 399.35]

Frame 5 (current):
  Drone pose: [98.16, 22.49, 20.0, -47.53, -67.24, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 622.91, "ymin": 320.6, "xmax": 657.4, "ymax": 398.44}, "waypoint_deltas": [{"dx": 0.19, "dy": -0.43, "dz": 0.0, "dpitch": -0.02, "dyaw": -0.67, "droll": 0.0}, {"dx": 0.37, "dy": -0.86, "dz": 0.0, "dpitch": -0.03, "dyaw": -1.31, "droll": 0.0}, {"dx": 0.55, "dy": -1.3, "dz": 0.0, "dpitch": -0.04, "dyaw": -1.92, "droll": 0.0}, {"dx": 0.72, "dy": -1.74, "dz": 0.0, "dpitch": -0.04, "dyaw": -2.52, "droll": 0.0}, {"dx": 0.88, "dy": -2.18, "dz": 0.0, "dpitch": -0.05, "dyaw": -3.09, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [100.25, 16.22, 20.0, -47.52, -74.53, 0.0]
  Target bbox: [618.74, 320.91, 661.66, 398.26]

Frame 2:
  Drone pose: [100.36, 15.76, 20.0, -47.51, -74.91, 0.0]
  Target bbox: [622.16, 320.69, 658.19, 398.35]

Frame 3:
  Drone pose: [100.46, 15.3, 20.0, -47.5, -75.27, 0.0]
  Target bbox: [622.89, 320.36, 657.47, 398.65]

Frame 4:
  Drone pose: [100.56, 14.83, 20.0, -47.49, -75.62, 0.0]
  Target bbox: [621.23, 321.01, 659.14, 398.08]

Frame 5 (current):
  Drone pose: [100.66, 14.36, 20.0, -47.47, -75.95, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 622.64, "ymin": 320.41, "xmax": 657.73, "ymax": 398.6}, "waypoint_deltas": [{"dx": 0.09, "dy": -0.47, "dz": 0.0, "dpitch": 0.01, "dyaw": -0.32, "droll": 0.0}, {"dx": 0.18, "dy": -0.94, "dz": 0.0, "dpitch": 0.02, "dyaw": -0.63, "droll": 0.0}, {"dx": 0.27, "dy": -1.41, "dz": 0.0, "dpitch": 0.04, "dyaw": -0.92, "droll": 0.0}, {"dx": 0.35, "dy": -1.88, "dz": 0.0, "dpitch": 0.05, "dyaw": -1.2, "droll": 0.0}, {"dx": 0.43, "dy": -2.35, "dz": 0.0, "dpitch": 0.07, "dyaw": -1.47, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [101.67, 7.7, 20.0, -47.29, -79.41, 0.0]
  Target bbox: [623.83, 320.89, 656.53, 398.11]

Frame 2:
  Drone pose: [101.72, 7.22, 20.0, -47.27, -79.59, 0.0]
  Target bbox: [622.32, 320.84, 658.07, 398.18]

Frame 3:
  Drone pose: [101.77, 6.73, 20.0, -47.26, -79.76, 0.0]
  Target bbox: [620.76, 321.37, 659.64, 397.69]

Frame 4:
  Drone pose: [101.82, 6.25, 20.0, -47.25, -79.93, 0.0]
  Target bbox: [621.55, 321.87, 658.85, 397.26]

Frame 5 (current):
  Drone pose: [101.86, 5.77, 20.0, -47.24, -80.09, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 622.31, "ymin": 321.75, "xmax": 658.07, "ymax": 397.33}, "waypoint_deltas": [{"dx": 0.05, "dy": -0.49, "dz": 0.0, "dpitch": 0.01, "dyaw": -0.15, "droll": 0.0}, {"dx": 0.09, "dy": -0.98, "dz": 0.0, "dpitch": 0.02, "dyaw": -0.29, "droll": 0.0}, {"dx": 0.13, "dy": -1.46, "dz": 0.0, "dpitch": 0.03, "dyaw": -0.43, "droll": 0.0}, {"dx": 0.17, "dy": -1.95, "dz": 0.0, "dpitch": 0.04, "dyaw": -0.56, "droll": 0.0}, {"dx": 0.21, "dy": -2.44, "dz": 0.0, "dpitch": 0.05, "dyaw": -0.69, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [77.45, 88.33, 22.0, -46.42, -63.43, 0.0]
  Target bbox: [619.43, 323.59, 660.79, 395.79] (model-predicted box)

Frame 2:
  Drone pose: [80.73, 85.38, 21.11, -50.76, -69.84, 0.0]
  Target bbox: [620.24, 321.24, 660.08, 397.72] (model-predicted box)

Frame 3:
  Drone pose: [84.83, 83.33, 20.67, -52.83, -81.28, 0.0]
  Target bbox: [602.84, 350.89, 632.34, 428.65]

Frame 4:
  Drone pose: [89.48, 81.97, 20.65, -60.57, -108.32, 0.0]
  Target bbox: [663.57, 240.64, 712.85, 319.39]

Frame 5 (current):
  Drone pose: [93.85, 81.04, 20.62, -48.77, -123.92, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 670.1, "ymin": 410.4, "xmax": 710.78, "ymax": 479.84}, "waypoint_deltas": [{"dx": 3.4, "dy": -0.75, "dz": -0.03, "dpitch": -2.37, "dyaw": -4.69, "droll": 0.0}, {"dx": 5.6, "dy": -1.44, "dz": -0.05, "dpitch": -0.65, "dyaw": -9.65, "droll": 0.0}, {"dx": 6.88, "dy": -2.1, "dz": -0.07, "dpitch": 0.7, "dyaw": -13.03, "droll": 0.0}, {"dx": 7.68, "dy": -2.7, "dz": -0.09, "dpitch": 0.98, "dyaw": -13.92, "droll": 0.0}, {"dx": 8.3, "dy": -3.25, "dz": -0.2, "dpitch": 1.23, "dyaw": -14.29, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [104.53, 73.65, 20.19, -48.55, -143.29, 0.0]
  Target bbox: [672.5, 304.42, 722.13, 383.29]

Frame 2:
  Drone pose: [104.61, 73.28, 20.16, -51.51, -140.49, 0.0]
  Target bbox: [645.76, 249.28, 688.69, 326.64]

Frame 3:
  Drone pose: [104.4, 72.48, 20.18, -44.32, -136.46, 0.0]
  Target bbox: [592.95, 377.74, 641.39, 459.87]

Frame 4:
  Drone pose: [104.49, 72.09, 20.14, -48.35, -133.37, 0.0]
  Target bbox: [555.88, 305.8, 609.48, 389.61]

Frame 5 (current):
  Drone pose: [104.51, 71.6, 20.12, -47.25, -138.37, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 614.42, "ymin": 318.52, "xmax": 665.64, "ymax": 400.82}, "waypoint_deltas": [{"dx": 0.02, "dy": -0.48, "dz": -0.01, "dpitch": 0.07, "dyaw": 0.01, "droll": 0.0}, {"dx": 0.05, "dy": -0.95, "dz": -0.03, "dpitch": 0.15, "dyaw": 0.02, "droll": 0.0}, {"dx": 0.08, "dy": -1.42, "dz": -0.04, "dpitch": 0.24, "dyaw": 0.03, "droll": 0.0}, {"dx": 0.11, "dy": -1.89, "dz": -0.05, "dpitch": 0.33, "dyaw": 0.03, "droll": 0.0}, {"dx": 0.13, "dy": -2.36, "dz": -0.06, "dpitch": 0.4, "dyaw": 0.04, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [104.67, 64.8, 20.01, -46.68, -138.26, 0.0]
  Target bbox: [618.8, 321.47, 661.1, 397.65]

Frame 2:
  Drone pose: [104.59, 64.39, 19.94, -45.9, -132.85, 0.0]
  Target bbox: [557.43, 332.51, 605.96, 412.81]

Frame 3:
  Drone pose: [104.69, 63.75, 20.15, -50.02, -135.61, 0.0]
  Target bbox: [586.07, 268.82, 628.8, 346.9]

Frame 4:
  Drone pose: [104.83, 63.18, 20.04, -45.52, -138.51, 0.0]
  Target bbox: [610.88, 336.97, 660.68, 419.92]

Frame 5 (current):
  Drone pose: [104.6, 62.85, 20.01, -46.69, -137.96, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 617.8, "ymin": 319.98, "xmax": 662.11, "ymax": 399.1}, "waypoint_deltas": [{"dx": -0.14, "dy": -0.4, "dz": 0.0, "dpitch": -0.07, "dyaw": 0.54, "droll": 0.0}, {"dx": -0.94, "dy": -0.62, "dz": -0.01, "dpitch": -0.69, "dyaw": 3.0, "droll": 0.0}, {"dx": -2.14, "dy": -0.74, "dz": -0.01, "dpitch": -1.59, "dyaw": 6.81, "droll": 0.0}, {"dx": -3.62, "dy": -0.74, "dz": -0.01, "dpitch": -2.51, "dyaw": 11.89, "droll": 0.0}, {"dx": -5.27, "dy": -0.67, "dz": -0.01, "dpitch": -3.24, "dyaw": 17.96, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [91.5, 60.45, 20.0, -50.35, -95.37, 0.0]
  Target bbox: [675.04, 297.68, 716.06, 373.4]

Frame 2:
  Drone pose: [91.45, 59.92, 20.07, -48.96, -90.21, 0.0]
  Target bbox: [628.64, 321.61, 651.22, 397.19]

Frame 3:
  Drone pose: [91.42, 59.4, 20.0, -45.88, -90.5, 0.0]
  Target bbox: [625.57, 372.52, 663.22, 447.84]

Frame 4:
  Drone pose: [91.38, 58.88, 20.0, -47.24, -91.85, 0.0]
  Target bbox: [642.65, 351.17, 679.29, 425.29]

Frame 5 (current):
  Drone pose: [91.41, 58.29, 20.03, -45.59, -86.98, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 592.66, "ymin": 381.25, "xmax": 619.19, "ymax": 457.76}, "waypoint_deltas": [{"dx": -0.14, "dy": -0.44, "dz": -0.03, "dpitch": -3.39, "dyaw": -2.6, "droll": 0.0}, {"dx": -0.16, "dy": -0.88, "dz": -0.03, "dpitch": -3.29, "dyaw": -2.51, "droll": 0.0}, {"dx": -0.17, "dy": -1.28, "dz": -0.03, "dpitch": -3.11, "dyaw": -2.5, "droll": 0.0}, {"dx": -0.17, "dy": -1.71, "dz": -0.03, "dpitch": -3.0, "dyaw": -2.49, "droll": 0.0}, {"dx": -0.17, "dy": -2.19, "dz": -0.03, "dpitch": -2.96, "dyaw": -2.5, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [91.38, 51.62, 19.86, -47.63, -87.37, 0.0]
  Target bbox: [596.27, 333.77, 626.0, 408.79]

Frame 2:
  Drone pose: [91.38, 51.26, 20.04, -45.68, -88.07, 0.0]
  Target bbox: [605.8, 370.12, 631.87, 445.88]

Frame 3:
  Drone pose: [91.21, 50.77, 20.16, -51.69, -84.4, 0.0]
  Target bbox: [569.0, 273.4, 599.73, 349.6]

Frame 4:
  Drone pose: [91.26, 50.4, 20.0, -51.02, -84.55, 0.0]
  Target bbox: [566.92, 276.8, 600.79, 353.64]

Frame 5 (current):
  Drone pose: [91.26, 49.8, 20.05, -51.97, -93.89, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 670.25, "ymin": 265.65, "xmax": 706.68, "ymax": 339.86}, "waypoint_deltas": [{"dx": 0.05, "dy": -0.29, "dz": -0.05, "dpitch": 3.87, "dyaw": 4.17, "droll": 0.0}, {"dx": 0.04, "dy": -0.77, "dz": -0.05, "dpitch": 3.91, "dyaw": 4.2, "droll": 0.0}, {"dx": 0.04, "dy": -1.26, "dz": -0.05, "dpitch": 3.92, "dyaw": 4.2, "droll": 0.0}, {"dx": 0.0, "dy": -1.78, "dz": -0.05, "dpitch": 3.89, "dyaw": 4.34, "droll": 0.0}, {"dx": 0.0, "dy": -2.33, "dz": -0.05, "dpitch": 3.81, "dyaw": 4.34, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [90.57, 40.92, 19.92, -50.17, -84.33, 0.0]
  Target bbox: [671.18, 338.78, 715.12, 416.93]

Frame 2:
  Drone pose: [90.54, 40.49, 19.96, -54.85, -73.43, 0.0]
  Target bbox: [573.4, 254.34, 620.3, 334.17]

Frame 3:
  Drone pose: [90.51, 39.66, 19.95, -47.52, -70.24, 0.0]
  Target bbox: [564.61, 385.47, 608.84, 462.39]

Frame 4:
  Drone pose: [90.59, 38.62, 19.86, -51.87, -73.13, 0.0]
  Target bbox: [619.2, 319.61, 660.6, 398.97]

Frame 5 (current):
  Drone pose: [90.08, 37.59, 20.07, -57.5, -68.36, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 615.65, "ymin": 236.04, "xmax": 656.2, "ymax": 314.27}, "waypoint_deltas": [{"dx": -0.73, "dy": -0.61, "dz": -0.07, "dpitch": 5.83, "dyaw": 4.16, "droll": 0.0}, {"dx": -1.27, "dy": -1.31, "dz": -0.07, "dpitch": 6.39, "dyaw": 7.99, "droll": 0.0}, {"dx": -1.42, "dy": -1.8, "dz": -0.07, "dpitch": 7.01, "dyaw": 10.02, "droll": 0.0}, {"dx": -1.43, "dy": -2.25, "dz": -0.07, "dpitch": 7.57, "dyaw": 11.5, "droll": 0.0}, {"dx": -1.45, "dy": -2.71, "dz": -0.07, "dpitch": 8.14, "dyaw": 12.93, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [91.12, 31.61, 19.8, -47.09, -52.01, 0.0]
  Target bbox: [614.87, 315.8, 647.73, 386.85]

Frame 2:
  Drone pose: [91.73, 31.07, 19.87, -46.11, -57.11, 0.0]
  Target bbox: [668.38, 336.49, 707.46, 410.44]

Frame 3:
  Drone pose: [92.2, 30.74, 19.96, -46.75, -53.19, 0.0]
  Target bbox: [623.06, 325.1, 656.67, 393.84]

Frame 4:
  Drone pose: [92.77, 30.3, 20.0, -46.8, -53.5, 0.0]
  Target bbox: [624.53, 323.47, 655.19, 395.46]

Frame 5 (current):
  Drone pose: [93.28, 30.0, 20.07, -46.66, -53.91, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 620.59, "ymin": 322.87, "xmax": 659.05, "ymax": 396.18}, "waypoint_deltas": [{"dx": 0.49, "dy": -0.57, "dz": -0.07, "dpitch": 0.03, "dyaw": 0.16, "droll": 0.0}, {"dx": 0.92, "dy": -0.99, "dz": -0.07, "dpitch": 0.2, "dyaw": 0.2, "droll": 0.0}, {"dx": 1.28, "dy": -1.4, "dz": -0.07, "dpitch": -0.03, "dyaw": -0.91, "droll": 0.0}, {"dx": 1.61, "dy": -1.81, "dz": -0.07, "dpitch": -0.19, "dyaw": -1.93, "droll": 0.0}, {"dx": 1.89, "dy": -2.21, "dz": -0.07, "dpitch": -0.31, "dyaw": -2.88, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [97.32, 24.19, 20.0, -47.39, -59.32, 0.0]
  Target bbox: [559.95, 322.29, 605.7, 401.76]

Frame 2:
  Drone pose: [97.54, 23.77, 20.0, -43.69, -60.09, 0.0]
  Target bbox: [558.42, 383.45, 607.01, 466.11]

Frame 3:
  Drone pose: [97.76, 23.35, 20.0, -47.49, -65.83, 0.0]
  Target bbox: [616.49, 319.74, 663.82, 399.51]

Frame 4:
  Drone pose: [97.98, 22.81, 20.01, -47.7, -66.46, 0.0]
  Target bbox: [622.75, 320.27, 657.56, 398.73]

Frame 5 (current):
  Drone pose: [98.04, 22.4, 19.89, -51.75, -61.75, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 558.33, "ymin": 248.37, "xmax": 606.87, "ymax": 329.29}, "waypoint_deltas": [{"dx": 0.31, "dy": -0.34, "dz": 0.11, "dpitch": 4.2, "dyaw": -6.16, "droll": 0.0}, {"dx": 0.49, "dy": -0.77, "dz": 0.11, "dpitch": 4.19, "dyaw": -6.8, "droll": 0.0}, {"dx": 0.67, "dy": -1.21, "dz": 0.11, "dpitch": 4.18, "dyaw": -7.41, "droll": 0.0}, {"dx": 0.84, "dy": -1.65, "dz": 0.11, "dpitch": 4.18, "dyaw": -8.01, "droll": 0.0}, {"dx": 1.0, "dy": -2.09, "dz": 0.11, "dpitch": 4.17, "dyaw": -8.58, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [100.25, 16.22, 20.0, -47.89, -73.98, 0.0]
  Target bbox: [618.36, 314.71, 649.27, 391.92]

Frame 2:
  Drone pose: [100.35, 15.67, 20.06, -47.73, -74.82, 0.0]
  Target bbox: [618.7, 320.87, 661.69, 398.27]

Frame 3:
  Drone pose: [100.46, 15.3, 20.0, -51.05, -77.5, 0.0]
  Target bbox: [643.69, 260.81, 688.54, 339.48]

Frame 4:
  Drone pose: [100.56, 14.83, 20.0, -47.49, -75.62, 0.0]
  Target bbox: [618.2, 320.93, 662.21, 398.24]

Frame 5 (current):
  Drone pose: [100.54, 14.3, 19.94, -47.43, -75.52, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 616.93, "ymin": 319.96, "xmax": 663.48, "ymax": 399.13}, "waypoint_deltas": [{"dx": 0.21, "dy": -0.41, "dz": 0.06, "dpitch": -0.03, "dyaw": -0.75, "droll": 0.0}, {"dx": 0.3, "dy": -0.88, "dz": 0.06, "dpitch": -0.02, "dyaw": -1.06, "droll": 0.0}, {"dx": 0.39, "dy": -1.35, "dz": 0.06, "dpitch": 0.0, "dyaw": -1.35, "droll": 0.0}, {"dx": 0.47, "dy": -1.82, "dz": 0.06, "dpitch": 0.01, "dyaw": -1.63, "droll": 0.0}, {"dx": 0.55, "dy": -2.29, "dz": 0.06, "dpitch": 0.03, "dyaw": -1.9, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [101.67, 7.7, 20.0, -42.99, -79.15, 0.0]
  Target bbox: [616.78, 393.62, 657.57, 469.91]

Frame 2:
  Drone pose: [101.72, 7.22, 20.0, -51.02, -84.52, 0.0]
  Target bbox: [674.5, 260.4, 719.44, 336.08]

Frame 3:
  Drone pose: [101.86, 6.63, 19.91, -48.13, -79.9, 0.0]
  Target bbox: [624.54, 308.15, 654.0, 383.69]

Frame 4:
  Drone pose: [101.89, 6.11, 19.91, -46.54, -78.39, 0.0]
  Target bbox: [602.45, 334.56, 638.39, 412.68]

Frame 5 (current):
  Drone pose: [101.86, 5.77, 20.0, -47.24, -80.09, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 624.38, "ymin": 321.25, "xmax": 655.97, "ymax": 397.75}, "waypoint_deltas": [{"dx": 0.05, "dy": -0.49, "dz": 0.0, "dpitch": 0.01, "dyaw": -0.15, "droll": 0.0}, {"dx": 0.09, "dy": -0.98, "dz": 0.0, "dpitch": 0.02, "dyaw": -0.29, "droll": 0.0}, {"dx": 0.13, "dy": -1.46, "dz": 0.0, "dpitch": 0.03, "dyaw": -0.43, "droll": 0.0}, {"dx": 0.17, "dy": -1.95, "dz": 0.0, "dpitch": 0.04, "dyaw": -0.56, "droll": 0.0}, {"dx": 0.21, "dy": -2.44, "dz": 0.0, "dpitch": 0.05, "dyaw": -0.69, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-130.39, -1.02, 22.0, -54.41, 11.35, 0.0]
  Target bbox: [622.77, 326.04, 657.15, 392.72]

Frame 2:
  Drone pose: [-130.14, -1.02, 21.2, -52.71, 12.97, 0.0]
  Target bbox: [621.7, 321.42, 658.66, 397.42]

Frame 3:
  Drone pose: [-129.89, -1.01, 20.67, -51.54, 12.74, 0.0]
  Target bbox: [621.85, 324.8, 658.12, 393.98]

Frame 4:
  Drone pose: [-129.65, -1.01, 20.64, -50.87, 14.26, 0.0]
  Target bbox: [619.12, 320.95, 660.67, 397.95]

Frame 5 (current):
  Drone pose: [-129.4, -1.0, 20.62, -50.18, 15.72, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 623.89, "ymin": 328.72, "xmax": 656.2, "ymax": 390.08}, "waypoint_deltas": [{"dx": 0.25, "dy": 0.01, "dz": -0.03, "dpitch": 0.45, "dyaw": -0.25, "droll": 0.0}, {"dx": 0.5, "dy": 0.01, "dz": -0.05, "dpitch": 0.89, "dyaw": -0.5, "droll": 0.0}, {"dx": 0.74, "dy": 0.02, "dz": -0.07, "dpitch": 1.32, "dyaw": -0.74, "droll": 0.0}, {"dx": 0.99, "dy": 0.02, "dz": -0.09, "dpitch": 1.76, "dyaw": -0.97, "droll": 0.0}, {"dx": 1.24, "dy": 0.03, "dz": -0.2, "dpitch": 2.31, "dyaw": -1.2, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-125.69, -0.92, 20.15, -43.76, 12.56, 0.0]
  Target bbox: [623.95, 324.35, 656.36, 395.0]

Frame 2:
  Drone pose: [-125.44, -0.91, 20.14, -43.38, 12.39, 0.0]
  Target bbox: [624.67, 324.22, 655.68, 395.27]

Frame 3:
  Drone pose: [-124.95, -1.0, 20.12, -43.32, 12.63, 0.0]
  Target bbox: [623.57, 323.54, 656.78, 395.88]

Frame 4:
  Drone pose: [-124.46, -1.12, 20.1, -43.26, 12.94, 0.0]
  Target bbox: [625.83, 328.75, 654.31, 390.43]

Frame 5 (current):
  Drone pose: [-123.95, -1.25, 20.09, -43.21, 13.31, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 626.37, "ymin": 329.62, "xmax": 653.72, "ymax": 389.47}, "waypoint_deltas": [{"dx": 0.52, "dy": -0.15, "dz": -0.01, "dpitch": 0.05, "dyaw": 0.43, "droll": 0.0}, {"dx": 1.05, "dy": -0.32, "dz": -0.02, "dpitch": 0.08, "dyaw": 0.89, "droll": 0.0}, {"dx": 1.59, "dy": -0.48, "dz": -0.03, "dpitch": 0.1, "dyaw": 1.37, "droll": 0.0}, {"dx": 2.13, "dy": -0.64, "dz": -0.04, "dpitch": 0.1, "dyaw": 1.82, "droll": 0.0}, {"dx": 2.69, "dy": -0.76, "dz": -0.05, "dpitch": 0.09, "dyaw": 2.21, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-115.06, -1.1, 20.01, -43.15, 24.84, 0.0]
  Target bbox: [627.71, 326.66, 652.12, 392.57]

Frame 2:
  Drone pose: [-114.44, -0.91, 20.01, -43.12, 25.77, 0.0]
  Target bbox: [626.74, 328.24, 653.14, 390.99]

Frame 3:
  Drone pose: [-113.84, -0.7, 20.0, -43.07, 26.64, 0.0]
  Target bbox: [624.64, 328.31, 655.23, 390.97]

Frame 4:
  Drone pose: [-113.24, -0.47, 20.0, -43.01, 27.45, 0.0]
  Target bbox: [622.84, 324.4, 656.88, 395.0]

Frame 5 (current):
  Drone pose: [-112.65, -0.23, 20.0, -42.95, 28.2, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 620.77, "ymin": 325.12, "xmax": 658.98, "ymax": 394.27}, "waypoint_deltas": [{"dx": 0.58, "dy": 0.26, "dz": 0.0, "dpitch": 0.05, "dyaw": 0.69, "droll": 0.0}, {"dx": 1.17, "dy": 0.55, "dz": 0.0, "dpitch": 0.09, "dyaw": 1.33, "droll": 0.0}, {"dx": 1.76, "dy": 0.86, "dz": 0.0, "dpitch": 0.12, "dyaw": 1.92, "droll": 0.0}, {"dx": 2.34, "dy": 1.17, "dz": 0.0, "dpitch": 0.15, "dyaw": 2.49, "droll": 0.0}, {"dx": 2.93, "dy": 1.49, "dz": 0.0, "dpitch": 0.17, "dyaw": 3.04, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-104.02, 4.37, 20.0, -42.53, 35.52, 0.0]
  Target bbox: [622.07, 326.15, 657.62, 393.24]

Frame 2:
  Drone pose: [-103.47, 4.73, 20.0, -42.47, 35.91, 0.0]
  Target bbox: [624.75, 325.2, 654.93, 394.21]

Frame 3:
  Drone pose: [-102.93, 5.11, 20.0, -42.42, 36.25, 0.0]
  Target bbox: [623.32, 326.54, 656.39, 392.84]

Frame 4:
  Drone pose: [-102.4, 5.51, 20.0, -42.37, 36.53, 0.0]
  Target bbox: [626.84, 328.7, 652.97, 390.58]

Frame 5 (current):
  Drone pose: [-101.88, 5.92, 20.0, -42.31, 36.75, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 622.86, "ymin": 326.56, "xmax": 656.84, "ymax": 392.82}, "waypoint_deltas": [{"dx": 0.51, "dy": 0.42, "dz": 0.0, "dpitch": 0.05, "dyaw": 0.18, "droll": 0.0}, {"dx": 1.02, "dy": 0.86, "dz": 0.0, "dpitch": 0.09, "dyaw": 0.34, "droll": 0.0}, {"dx": 1.54, "dy": 1.3, "dz": 0.0, "dpitch": 0.12, "dyaw": 0.5, "droll": 0.0}, {"dx": 2.07, "dy": 1.74, "dz": 0.0, "dpitch": 0.13, "dyaw": 0.67, "droll": 0.0}, {"dx": 2.61, "dy": 2.19, "dz": 0.0, "dpitch": 0.13, "dyaw": 0.86, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-93.64, 12.25, 20.0, -42.12, 40.51, 0.0]
  Target bbox: [624.4, 327.9, 655.32, 391.41]

Frame 2:
  Drone pose: [-93.11, 12.68, 20.0, -42.08, 40.7, 0.0]
  Target bbox: [625.18, 325.89, 654.49, 393.47]

Frame 3:
  Drone pose: [-92.6, 13.13, 20.0, -42.05, 40.83, 0.0]
  Target bbox: [623.43, 327.62, 656.27, 391.69]

Frame 4:
  Drone pose: [-92.09, 13.6, 20.0, -42.03, 40.9, 0.0]
  Target bbox: [629.64, 326.93, 650.15, 392.35]

Frame 5 (current):
  Drone pose: [-91.59, 14.09, 20.0, -42.02, 40.92, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 628.65, "ymin": 330.15, "xmax": 651.2, "ymax": 389.07}, "waypoint_deltas": [{"dx": 0.49, "dy": 0.5, "dz": 0.0, "dpitch": 0.02, "dyaw": -0.02, "droll": 0.0}, {"dx": 0.96, "dy": 1.01, "dz": 0.0, "dpitch": 0.03, "dyaw": -0.08, "droll": 0.0}, {"dx": 1.43, "dy": 1.54, "dz": 0.0, "dpitch": 0.04, "dyaw": -0.2, "droll": 0.0}, {"dx": 1.88, "dy": 2.08, "dz": 0.0, "dpitch": 0.05, "dyaw": -0.38, "droll": 0.0}, {"dx": 2.32, "dy": 2.65, "dz": 0.0, "dpitch": 0.05, "dyaw": -0.61, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-85.34, 22.63, 20.0, -41.76, 35.54, 0.0]
  Target bbox: [625.13, 327.86, 654.85, 391.45]

Frame 2:
  Drone pose: [-84.99, 23.05, 20.0, -41.91, 34.39, 0.0]
  Target bbox: [620.24, 323.16, 659.99, 396.46]

Frame 3:
  Drone pose: [-84.64, 23.43, 20.0, -42.03, 33.31, 0.0]
  Target bbox: [620.42, 323.22, 659.79, 396.36]

Frame 4:
  Drone pose: [-84.28, 23.78, 20.0, -42.13, 32.28, 0.0]
  Target bbox: [624.5, 326.97, 655.56, 392.36]

Frame 5 (current):
  Drone pose: [-83.92, 24.12, 20.0, -42.21, 31.3, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 620.85, "ymin": 323.49, "xmax": 659.4, "ymax": 396.11}, "waypoint_deltas": [{"dx": 0.37, "dy": 0.31, "dz": 0.0, "dpitch": -0.06, "dyaw": -0.94, "droll": 0.0}, {"dx": 0.74, "dy": 0.62, "dz": 0.0, "dpitch": -0.12, "dyaw": -1.85, "droll": 0.0}, {"dx": 1.12, "dy": 0.91, "dz": 0.0, "dpitch": -0.17, "dyaw": -2.71, "droll": 0.0}, {"dx": 1.5, "dy": 1.18, "dz": 0.0, "dpitch": -0.2, "dyaw": -3.53, "droll": 0.0}, {"dx": 1.89, "dy": 1.44, "dz": 0.0, "dpitch": -0.23, "dyaw": -4.3, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-77.47, 26.17, 20.0, -42.49, 24.93, 0.0]
  Target bbox: [621.31, 323.01, 658.98, 396.51]

Frame 2:
  Drone pose: [-76.93, 26.07, 20.0, -42.48, 25.24, 0.0]
  Target bbox: [622.55, 324.43, 657.68, 395.06]

Frame 3:
  Drone pose: [-76.38, 25.95, 20.0, -42.48, 25.6, 0.0]
  Target bbox: [621.58, 323.53, 658.68, 395.99]

Frame 4:
  Drone pose: [-75.8, 25.83, 20.0, -42.5, 25.98, 0.0]
  Target bbox: [625.27, 328.14, 654.78, 391.11]

Frame 5 (current):
  Drone pose: [-75.21, 25.72, 20.0, -42.54, 26.38, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 620.82, "ymin": 322.53, "xmax": 659.47, "ymax": 397.02}, "waypoint_deltas": [{"dx": 0.61, "dy": -0.12, "dz": 0.0, "dpitch": -0.07, "dyaw": 0.43, "droll": 0.0}, {"dx": 1.25, "dy": -0.26, "dz": 0.0, "dpitch": -0.15, "dyaw": 0.95, "droll": 0.0}, {"dx": 1.91, "dy": -0.43, "dz": 0.0, "dpitch": 0.09, "dyaw": 2.78, "droll": 0.0}, {"dx": 2.59, "dy": -0.62, "dz": 0.0, "dpitch": -0.24, "dyaw": 5.38, "droll": 0.0}, {"dx": 3.3, "dy": -0.82, "dz": 0.0, "dpitch": -0.54, "dyaw": 8.11, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-64.91, 25.48, 20.0, -43.41, 52.39, 0.0]
  Target bbox: [623.56, 326.29, 656.39, 393.05]

Frame 2:
  Drone pose: [-64.45, 25.71, 20.0, -43.48, 53.88, 0.0]
  Target bbox: [619.64, 323.33, 660.3, 396.08]

Frame 3:
  Drone pose: [-64.03, 25.97, 20.0, -43.55, 55.26, 0.0]
  Target bbox: [618.82, 323.42, 661.17, 396.0]

Frame 4:
  Drone pose: [-63.65, 26.25, 20.0, -43.6, 56.53, 0.0]
  Target bbox: [618.91, 322.9, 661.02, 396.5]

Frame 5 (current):
  Drone pose: [-63.28, 26.54, 20.0, -43.63, 57.72, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 623.27, "ymin": 325.46, "xmax": 656.63, "ymax": 393.84}, "waypoint_deltas": [{"dx": 0.34, "dy": 0.32, "dz": 0.0, "dpitch": -0.04, "dyaw": 1.12, "droll": 0.0}, {"dx": 0.67, "dy": 0.66, "dz": 0.0, "dpitch": -0.09, "dyaw": 2.17, "droll": 0.0}, {"dx": 1.0, "dy": 1.0, "dz": 0.0, "dpitch": -0.12, "dyaw": 3.22, "droll": 0.0}, {"dx": 1.32, "dy": 1.32, "dz": 0.0, "dpitch": -0.1, "dyaw": 4.28, "droll": 0.0}, {"dx": 1.63, "dy": 1.65, "dz": 0.0, "dpitch": -0.1, "dyaw": 5.29, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-58.93, 31.76, 20.0, -43.33, 71.75, 0.0]
  Target bbox: [624.33, 326.12, 655.49, 393.12]

Frame 2:
  Drone pose: [-58.7, 32.16, 20.0, -43.3, 72.47, 0.0]
  Target bbox: [627.3, 327.1, 652.53, 392.15]

Frame 3:
  Drone pose: [-58.48, 32.57, 20.0, -43.27, 73.14, 0.0]
  Target bbox: [627.0, 327.75, 652.85, 391.5]

Frame 4:
  Drone pose: [-58.27, 32.99, 20.0, -43.25, 73.78, 0.0]
  Target bbox: [627.9, 326.42, 651.9, 392.86]

Frame 5 (current):
  Drone pose: [-58.07, 33.43, 20.0, -43.24, 74.37, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 624.57, "ymin": 326.39, "xmax": 655.23, "ymax": 392.85}, "waypoint_deltas": [{"dx": 0.19, "dy": 0.44, "dz": 0.0, "dpitch": 0.01, "dyaw": 0.55, "droll": 0.0}, {"dx": 0.36, "dy": 0.9, "dz": 0.0, "dpitch": 0.0, "dyaw": 1.04, "droll": 0.0}, {"dx": 0.51, "dy": 1.36, "dz": 0.0, "dpitch": 0.0, "dyaw": 1.47, "droll": 0.0}, {"dx": 0.64, "dy": 1.84, "dz": 0.0, "dpitch": -0.01, "dyaw": 1.85, "droll": 0.0}, {"dx": 0.74, "dy": 2.31, "dz": 0.0, "dpitch": -0.01, "dyaw": 2.17, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-57.17, 40.44, 20.0, -42.89, 77.16, 0.0]
  Target bbox: [629.64, 327.37, 650.19, 391.89]

Frame 2:
  Drone pose: [-57.2, 40.93, 20.0, -42.87, 77.08, 0.0]
  Target bbox: [627.98, 328.23, 651.86, 391.02]

Frame 3:
  Drone pose: [-57.22, 41.44, 20.0, -42.88, 77.03, 0.0]
  Target bbox: [629.66, 327.29, 650.17, 391.97]

Frame 4:
  Drone pose: [-57.22, 41.97, 20.0, -42.91, 77.01, 0.0]
  Target bbox: [627.83, 327.02, 652.0, 392.19]

Frame 5 (current):
  Drone pose: [-57.19, 42.52, 20.0, -42.99, 77.04, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 620.0, "ymin": 324.04, "xmax": 660.13, "ymax": 395.45}, "waypoint_deltas": [{"dx": 0.05, "dy": 0.57, "dz": 0.0, "dpitch": 0.05, "dyaw": -1.27, "droll": 0.0}, {"dx": 0.12, "dy": 1.17, "dz": 0.0, "dpitch": -0.11, "dyaw": -1.13, "droll": 0.0}, {"dx": 0.22, "dy": 1.78, "dz": 0.0, "dpitch": -0.3, "dyaw": -0.93, "droll": 0.0}, {"dx": 0.34, "dy": 2.4, "dz": 0.0, "dpitch": -0.31, "dyaw": -2.08, "droll": 0.0}, {"dx": 0.45, "dy": 2.99, "dz": 0.0, "dpitch": -0.48, "dyaw": -1.84, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-130.39, -1.02, 22.0, -54.41, 11.35, 0.0]
  Target bbox: [619.66, 323.37, 660.2, 395.48]

Frame 2:
  Drone pose: [-130.16, -0.9, 21.26, -53.7, 7.54, 0.0]
  Target bbox: [675.27, 315.88, 707.12, 376.5]

Frame 3:
  Drone pose: [-129.89, -1.01, 20.67, -50.66, 7.74, 0.0]
  Target bbox: [668.22, 336.83, 717.31, 415.36]

Frame 4:
  Drone pose: [-129.62, -1.12, 20.61, -50.81, 14.7, 0.0]
  Target bbox: [622.76, 326.21, 657.22, 392.62]

Frame 5 (current):
  Drone pose: [-129.35, -0.9, 20.48, -50.11, 15.43, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 625.05, "ymin": 328.31, "xmax": 655.06, "ymax": 390.48}, "waypoint_deltas": [{"dx": 0.2, "dy": -0.09, "dz": 0.11, "dpitch": 0.38, "dyaw": 0.04, "droll": 0.0}, {"dx": 0.45, "dy": -0.09, "dz": 0.09, "dpitch": 0.82, "dyaw": -0.21, "droll": 0.0}, {"dx": 0.69, "dy": -0.08, "dz": 0.07, "dpitch": 1.25, "dyaw": -0.45, "droll": 0.0}, {"dx": 0.94, "dy": -0.08, "dz": 0.05, "dpitch": 1.69, "dyaw": -0.68, "droll": 0.0}, {"dx": 1.19, "dy": -0.07, "dz": -0.06, "dpitch": 2.24, "dyaw": -0.91, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-125.69, -0.92, 20.15, -43.76, 12.56, 0.0]
  Target bbox: [624.32, 323.75, 656.02, 395.68]

Frame 2:
  Drone pose: [-125.44, -0.91, 20.14, -43.38, 12.39, 0.0]
  Target bbox: [626.36, 329.0, 653.76, 390.1]

Frame 3:
  Drone pose: [-124.95, -1.0, 20.12, -40.68, 16.61, 0.0]
  Target bbox: [575.24, 370.4, 607.03, 440.13]

Frame 4:
  Drone pose: [-124.54, -1.21, 20.06, -43.04, 13.14, 0.0]
  Target bbox: [625.87, 329.93, 654.23, 389.21]

Frame 5 (current):
  Drone pose: [-123.93, -1.3, 20.24, -43.43, 13.45, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 624.96, "ymin": 324.79, "xmax": 655.34, "ymax": 394.61}, "waypoint_deltas": [{"dx": 0.5, "dy": -0.1, "dz": -0.16, "dpitch": 0.27, "dyaw": 0.29, "droll": 0.0}, {"dx": 1.03, "dy": -0.27, "dz": -0.17, "dpitch": 0.3, "dyaw": 0.75, "droll": 0.0}, {"dx": 1.57, "dy": -0.43, "dz": -0.18, "dpitch": 0.32, "dyaw": 1.23, "droll": 0.0}, {"dx": 2.11, "dy": -0.59, "dz": -0.19, "dpitch": 0.32, "dyaw": 1.68, "droll": 0.0}, {"dx": 2.67, "dy": -0.71, "dz": -0.2, "dpitch": 0.31, "dyaw": 2.07, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-115.06, -1.1, 20.01, -44.73, 29.84, 0.0]
  Target bbox: [564.11, 302.98, 592.7, 367.13]

Frame 2:
  Drone pose: [-114.35, -0.89, 19.96, -43.18, 25.85, 0.0]
  Target bbox: [621.19, 325.13, 658.59, 394.27]

Frame 3:
  Drone pose: [-113.75, -0.74, 20.16, -43.38, 26.84, 0.0]
  Target bbox: [625.67, 325.65, 654.12, 393.62]

Frame 4:
  Drone pose: [-113.08, -0.41, 20.05, -43.98, 28.96, 0.0]
  Target bbox: [607.22, 317.79, 636.19, 379.51]

Frame 5 (current):
  Drone pose: [-112.74, -0.17, 20.0, -44.42, 23.49, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 676.17, "ymin": 300.67, "xmax": 714.03, "ymax": 370.08}, "waypoint_deltas": [{"dx": 0.67, "dy": 0.2, "dz": 0.0, "dpitch": 1.52, "dyaw": 5.4, "droll": 0.0}, {"dx": 1.26, "dy": 0.49, "dz": 0.0, "dpitch": 1.56, "dyaw": 6.04, "droll": 0.0}, {"dx": 1.85, "dy": 0.8, "dz": 0.0, "dpitch": 1.59, "dyaw": 6.63, "droll": 0.0}, {"dx": 2.43, "dy": 1.11, "dz": 0.0, "dpitch": 1.62, "dyaw": 7.2, "droll": 0.0}, {"dx": 3.02, "dy": 1.43, "dz": 0.0, "dpitch": 1.64, "dyaw": 7.75, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-104.06, 4.44, 19.97, -44.08, 39.13, 0.0]
  Target bbox: [574.75, 301.64, 609.29, 366.94]

Frame 2:
  Drone pose: [-103.47, 4.73, 20.0, -42.47, 35.91, 0.0]
  Target bbox: [623.88, 325.11, 655.81, 394.25]

Frame 3:
  Drone pose: [-102.93, 5.11, 20.0, -39.22, 38.2, 0.0]
  Target bbox: [599.42, 382.69, 631.47, 444.57]

Frame 4:
  Drone pose: [-102.54, 5.62, 19.95, -40.51, 41.05, 0.0]
  Target bbox: [564.52, 356.97, 590.41, 423.55]

Frame 5 (current):
  Drone pose: [-101.88, 5.92, 20.0, -42.31, 36.75, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 624.93, "ymin": 328.07, "xmax": 654.86, "ymax": 391.19}, "waypoint_deltas": [{"dx": 0.51, "dy": 0.42, "dz": 0.0, "dpitch": 0.05, "dyaw": 0.18, "droll": 0.0}, {"dx": 1.02, "dy": 0.86, "dz": 0.0, "dpitch": 0.09, "dyaw": 0.34, "droll": 0.0}, {"dx": 1.54, "dy": 1.3, "dz": 0.0, "dpitch": 0.12, "dyaw": 0.5, "droll": 0.0}, {"dx": 2.07, "dy": 1.74, "dz": 0.0, "dpitch": 0.13, "dyaw": 0.67, "droll": 0.0}, {"dx": 2.61, "dy": 2.19, "dz": 0.0, "dpitch": 0.13, "dyaw": 0.86, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-93.67, 12.16, 19.87, -42.94, 37.08, 0.0]
  Target bbox: [671.41, 309.42, 697.7, 373.73]

Frame 2:
  Drone pose: [-93.18, 12.73, 20.07, -42.16, 40.47, 0.0]
  Target bbox: [627.83, 326.88, 651.93, 392.41]

Frame 3:
  Drone pose: [-92.6, 13.13, 20.0, -42.5, 37.29, 0.0]
  Target bbox: [667.17, 320.18, 701.25, 386.11]

Frame 4:
  Drone pose: [-92.09, 13.6, 20.0, -39.68, 40.57, 0.0]
  Target bbox: [631.17, 370.01, 657.03, 428.07]

Frame 5 (current):
  Drone pose: [-91.64, 14.07, 20.12, -41.85, 44.45, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 580.35, "ymin": 332.17, "xmax": 609.85, "ymax": 398.34}, "waypoint_deltas": [{"dx": 0.54, "dy": 0.52, "dz": -0.12, "dpitch": -0.15, "dyaw": -3.55, "droll": 0.0}, {"dx": 1.01, "dy": 1.03, "dz": -0.12, "dpitch": -0.14, "dyaw": -3.61, "droll": 0.0}, {"dx": 1.48, "dy": 1.56, "dz": -0.12, "dpitch": -0.13, "dyaw": -3.73, "droll": 0.0}, {"dx": 1.93, "dy": 2.1, "dz": -0.12, "dpitch": -0.12, "dyaw": -3.91, "droll": 0.0}, {"dx": 2.37, "dy": 2.67, "dz": -0.12, "dpitch": -0.12, "dyaw": -4.14, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-85.27, 22.52, 19.87, -40.14, 40.91, 0.0]
  Target bbox: [560.17, 351.73, 593.56, 418.22]

Frame 2:
  Drone pose: [-84.99, 23.05, 20.0, -42.0, 34.58, 0.0]
  Target bbox: [623.57, 326.8, 651.62, 389.71]

Frame 3:
  Drone pose: [-84.46, 23.4, 20.03, -42.25, 33.64, 0.0]
  Target bbox: [625.0, 327.86, 654.97, 391.41]

Frame 4:
  Drone pose: [-84.46, 23.74, 20.03, -41.95, 32.12, 0.0]
  Target bbox: [622.13, 324.19, 658.05, 395.3]

Frame 5 (current):
  Drone pose: [-84.09, 24.11, 20.1, -42.15, 31.08, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 620.85, "ymin": 323.46, "xmax": 659.38, "ymax": 396.12}, "waypoint_deltas": [{"dx": 0.54, "dy": 0.32, "dz": -0.1, "dpitch": -0.12, "dyaw": -0.72, "droll": 0.0}, {"dx": 0.91, "dy": 0.63, "dz": -0.1, "dpitch": -0.18, "dyaw": -1.63, "droll": 0.0}, {"dx": 1.29, "dy": 0.92, "dz": -0.1, "dpitch": -0.23, "dyaw": -2.49, "droll": 0.0}, {"dx": 1.67, "dy": 1.19, "dz": -0.1, "dpitch": -0.26, "dyaw": -3.31, "droll": 0.0}, {"dx": 2.06, "dy": 1.45, "dz": -0.1, "dpitch": -0.29, "dyaw": -4.08, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-77.47, 26.17, 20.0, -42.49, 24.93, 0.0]
  Target bbox: [621.81, 324.08, 658.42, 395.39]

Frame 2:
  Drone pose: [-76.93, 25.99, 20.01, -41.79, 21.68, 0.0]
  Target bbox: [671.07, 340.33, 702.6, 403.71]

Frame 3:
  Drone pose: [-76.38, 25.95, 20.0, -44.53, 26.49, 0.0]
  Target bbox: [612.25, 290.88, 645.39, 359.88]

Frame 4:
  Drone pose: [-75.91, 25.73, 20.11, -41.36, 21.64, 0.0]
  Target bbox: [677.93, 345.17, 713.48, 414.75]

Frame 5 (current):
  Drone pose: [-75.17, 25.9, 19.98, -41.32, 25.29, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 634.08, "ymin": 351.34, "xmax": 663.66, "ymax": 413.58}, "waypoint_deltas": [{"dx": 0.57, "dy": -0.3, "dz": 0.02, "dpitch": -1.29, "dyaw": 1.52, "droll": 0.0}, {"dx": 1.21, "dy": -0.44, "dz": 0.02, "dpitch": -1.37, "dyaw": 2.04, "droll": 0.0}, {"dx": 1.87, "dy": -0.61, "dz": 0.02, "dpitch": -1.13, "dyaw": 3.87, "droll": 0.0}, {"dx": 2.55, "dy": -0.8, "dz": 0.02, "dpitch": -1.46, "dyaw": 6.47, "droll": 0.0}, {"dx": 3.26, "dy": -1.0, "dz": 0.02, "dpitch": -1.76, "dyaw": 9.2, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-64.82, 25.45, 19.97, -43.4, 52.64, 0.0]
  Target bbox: [622.33, 324.51, 657.57, 394.82]

Frame 2:
  Drone pose: [-64.5, 25.71, 20.14, -43.65, 53.78, 0.0]
  Target bbox: [618.69, 323.82, 661.32, 395.65]

Frame 3:
  Drone pose: [-64.11, 26.04, 19.86, -42.62, 55.72, 0.0]
  Target bbox: [613.83, 337.04, 647.51, 406.99]

Frame 4:
  Drone pose: [-63.61, 26.13, 20.09, -43.88, 51.79, 0.0]
  Target bbox: [681.04, 322.17, 721.25, 392.12]

Frame 5 (current):
  Drone pose: [-63.35, 26.59, 19.83, -43.37, 57.49, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 618.89, "ymin": 323.66, "xmax": 661.06, "ymax": 395.79}, "waypoint_deltas": [{"dx": 0.41, "dy": 0.27, "dz": 0.17, "dpitch": -0.3, "dyaw": 1.35, "droll": 0.0}, {"dx": 0.74, "dy": 0.61, "dz": 0.17, "dpitch": -0.35, "dyaw": 2.4, "droll": 0.0}, {"dx": 1.07, "dy": 0.95, "dz": 0.17, "dpitch": -0.38, "dyaw": 3.45, "droll": 0.0}, {"dx": 1.39, "dy": 1.27, "dz": 0.17, "dpitch": -0.36, "dyaw": 4.51, "droll": 0.0}, {"dx": 1.7, "dy": 1.6, "dz": 0.17, "dpitch": -0.36, "dyaw": 5.52, "droll": 0.0}]}


[System]
You are a drone navigation expert. Given five sequential observation frames and the drone ego-state history, predict the target bounding box for the current frame and relative waypoint offsets for the next five frames.

Input format:
- Frames 1-4 (history): each provides the drone pose and a 2D axis-aligned target bounding box [xmin, ymin, xmax, ymax] in image-plane pixel coordinates.
- Frame 5 (current): only the drone pose is provided; target bounding-box observations for this timestep are omitted (e.g., detection not yet applied).
- Drone pose: [x, y, z, pitch, yaw, roll] in the world frame (position in meters, Euler angles in degrees).
- Target bounding-box semantics: when the target is visible in the camera view, the box denotes ground-truth image-plane localization; when the target is not visible, the box encodes a trajectory-inferred localization and is explicitly annotated in the frame text (e.g., as a model-predicted box).

Output:
1. current_bbox: the predicted target bounding box [xmin, ymin, xmax, ymax] for the current frame (Frame 5).
2. waypoint_deltas: five waypoint deltas relative to the current drone pose.
   - Each delta: [dx, dy, dz, dpitch, dyaw, droll]

Respond ONLY with a JSON object.

[User]
<image>
<image>
<image>
<image>
<image>
Flight state history (t-4 to t):

Frame 1:
  Drone pose: [-58.87, 31.68, 20.09, -39.38, 70.37, 0.0]
  Target bbox: [641.28, 393.73, 678.79, 461.23]

Frame 2:
  Drone pose: [-58.85, 32.14, 20.11, -40.66, 67.09, 0.0]
  Target bbox: [684.46, 373.72, 718.13, 440.47]

Frame 3:
  Drone pose: [-58.57, 32.72, 20.04, -43.5, 72.76, 0.0]
  Target bbox: [627.6, 327.1, 652.23, 392.13]

Frame 4:
  Drone pose: [-58.17, 32.93, 19.87, -38.88, 72.74, 0.0]
  Target bbox: [645.43, 396.26, 667.73, 462.33]

Frame 5 (current):
  Drone pose: [-58.07, 33.43, 20.0, -42.45, 70.58, 0.0]

Predict the target bounding box for the current frame and the next 5 waypoint deltas from current pose.

[Assistant] {"current_bbox": {"xmin": 672.44, "ymin": 340.89, "xmax": 700.64, "ymax": 406.94}, "waypoint_deltas": [{"dx": 0.19, "dy": 0.44, "dz": 0.0, "dpitch": -0.78, "dyaw": 4.34, "droll": 0.0}, {"dx": 0.36, "dy": 0.9, "dz": 0.0, "dpitch": -0.79, "dyaw": 4.83, "droll": 0.0}, {"dx": 0.51, "dy": 1.36, "dz": 0.0, "dpitch": -0.79, "dyaw": 5.26, "droll": 0.0}, {"dx": 0.64, "dy": 1.84, "dz": 0.0, "dpitch": -0.8, "dyaw": 5.64, "droll": 0.0}, {"dx": 0.74, "dy": 2.31, "dz": 0.0, "dpitch": -0.8, "dyaw": 5.96, "droll": 0.0}]}