<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rotated-Fcos on DeepLearning.Earth</title><link>https://deeplearning.earth/tags/rotated-fcos/</link><description>Recent content in Rotated-Fcos on DeepLearning.Earth</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 03 Sep 2026 12:30:00 +0700</lastBuildDate><atom:link href="https://deeplearning.earth/tags/rotated-fcos/index.xml" rel="self" type="application/rss+xml"/><item><title>Rotated FCOS vs Oriented R-CNN on macOS</title><link>https://deeplearning.earth/posts/2026-09-02_rotated_fcos_vs_oriented_rcnn_on_macos/</link><pubDate>Wed, 02 Sep 2026 15:00:00 +0700</pubDate><guid>https://deeplearning.earth/posts/2026-09-02_rotated_fcos_vs_oriented_rcnn_on_macos/</guid><description>In June we ran Oriented R-CNN on a MacBook with --device mps — no CUDA toolchain, one CLI command, rotated boxes on a real aerial tile. v0.2.0 added a fourth detector family: Rotated FCOS, an anchor-free single-stage model with a decoded-rIoU 3× Hub checkpoint.
This post puts both on the same Mac and the same images. Same canvas, same NMS, same score floor — Apple M1 Max, PyTorch MPS, Hub 3× weights.</description></item><item><title>Oriented-Det v0.2.0 — Rotated FCOS, decoded rIoU, and a four-family zoo</title><link>https://deeplearning.earth/posts/2026-08-28_oriented-det_v0_2_0_rotated_fcos_decoded_riou_and_the_updated_zoo/</link><pubDate>Fri, 28 Aug 2026 09:00:00 +0700</pubDate><guid>https://deeplearning.earth/posts/2026-08-28_oriented-det_v0_2_0_rotated_fcos_decoded_riou_and_the_updated_zoo/</guid><description>Six weeks after v0.1.1, Oriented-Det v0.2.0 is on PyPI and tagged on GitHub. The headline is a new detector family: Rotated FCOS, an anchor-free single-stage model that sits in the zoo as the balanced pick — close to Rotated Faster R-CNN accuracy, without a region proposal network.
This post is the release note: what landed, which Hub slug to download, and how the loss recipe (not the architecture name) is what moved the number.</description></item></channel></rss>