# 📦 WP-064 — `release: v0.3.0 oriented detection`

> Research log · [Phase 8 — Oriented detection, v0.3.0](https://borda.github.io/lucid-YOLO/research/phase-08-oriented-detection/)
>
> 🔗 Depends on [WP-063](https://borda.github.io/lucid-YOLO/work_packages/wp-063/) · Needed by [WP-091](https://borda.github.io/lucid-YOLO/work_packages/wp-091/), [WP-107](https://borda.github.io/lucid-YOLO/work_packages/wp-107/), [WP-065](https://borda.github.io/lucid-YOLO/work_packages/wp-065/), [WP-111](https://borda.github.io/lucid-YOLO/work_packages/wp-111/)
>
> ⬅️ [WP-105](https://borda.github.io/lucid-YOLO/work_packages/wp-105/) · [Roadmap](https://borda.github.io/lucid-YOLO/ROADMAP/) · [WP-089](https://borda.github.io/lucid-YOLO/work_packages/wp-089/) ➡️


## WP-064 — shipping a figure that compares to nothing

<a id="wp-064"></a>

0.3.0's oriented numbers are **per tile**. R1 and R18 report whole-image DOTA figures, so nothing this release published is comparable to anything outside it, and the release's own disclosure is what keeps that gap from reading as an omission: the reproduction report, the oriented model card and the README each say so.

The row also owned the whole-image tile merge and did not deliver it. It moved to [WP-107](https://borda.github.io/lucid-YOLO/work_packages/wp-107/#wp-107) rather than being marked done — a package that reports itself complete while a clause of its scope is unbuilt is how a roadmap stops describing the code, and this is the third time the merge had slipped, after [WP-063](https://borda.github.io/lucid-YOLO/work_packages/wp-063/) deferred it and [WP-088](https://borda.github.io/lucid-YOLO/work_packages/wp-088/)'s scope never took it up.