<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Research Training on Muhammad Nuh</title><link>https://hexrogue.github.io/research/</link><description>Recent content in Research Training on Muhammad Nuh</description><generator>Hugo</generator><language>en-us</language><managingEditor>ikanlemas0@gmail.com (Muhammad Nuh)</managingEditor><webMaster>ikanlemas0@gmail.com (Muhammad Nuh)</webMaster><lastBuildDate>Tue, 27 Oct 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://hexrogue.github.io/research/index.xml" rel="self" type="application/rss+xml"/><item><title>Offload or Not? A Simulation Study of Latency- and Energy-Aware Computation Offloading for IoT Devices</title><link>https://hexrogue.github.io/research/offloading-paper/</link><pubDate>Tue, 27 Oct 2026 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/research/offloading-paper/</guid><description>&lt;h2 id="1-introduction"&gt;1. Introduction&lt;/h2&gt;&#10;&lt;p&gt;A small device with a battery, a radio, and a processor has three ways to handle a compute-heavy task. It can run the task locally, send it to a nearby edge server, or defer it. Local execution avoids the radio but spends time and energy on the device. Offloading can finish sooner and drain less battery, but it adds transmission time, a shared queue, and a dependency on the network.&lt;/p&gt;</description></item><item><title>Thesis Plan: Adaptive Offloading Under Uncertainty at the Edge</title><link>https://hexrogue.github.io/research/thesis-plan/</link><pubDate>Tue, 27 Oct 2026 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/research/thesis-plan/</guid><description>&lt;h2 id="working-title"&gt;Working title&lt;/h2&gt;&#10;&lt;p&gt;&lt;strong&gt;Adaptive Offloading Under Uncertainty at the Edge: From Trace-Driven Simulation to a Multi-Device Testbed&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;The title may change. The question should not.&lt;/p&gt;&#10;&lt;h2 id="the-problem"&gt;The problem&lt;/h2&gt;&#10;&lt;p&gt;Edge offloading is usually framed as a per-task choice: run locally or send the task to a nearby server. That framing hides the difficult part. In a real deployment, the device does not know the next task, the channel changes, the edge server is shared, and other devices are making the same decision at the same time. A policy that is optimal for one device can be bad for the system. A policy that is optimal at low load can fail at high load. A policy that works in simulation can fail on hardware because the radio consumes more energy than the datasheet suggests.&lt;/p&gt;</description></item></channel></rss>