/// RESEARCH TRAINING
Research Training
I am using this section to practise the parts of research that a job does not usually teach: framing a question, building a model small enough to understand, reading the literature without pretending I have read everything, and writing a paper that states its own limits.
The rule is one topic at a time. Right now that topic is computation offloading at the edge.
/// CURRENT PROJECT / WORKING PAPER 01
Offload or Not?
A simulation study of latency- and energy-aware computation offloading for IoT devices. The question is not whether the edge is faster. It is when moving work to the edge stops helping and starts building a queue.
The model compares three policies: run everything locally, send everything to a shared edge server, and a deadline/energy-aware heuristic that decides per task. The simulator, the data, and the figures are in the repository.
Python NumPy Matplotlib Monte Carlo Queueing Edge computing
27simulation points
20replications each
3policies compared
0.75 stask deadline
Why this exists
I am preparing for a PhD after my degree. A PhD is not a longer version of a software project. It is a habit of asking a question that can survive being wrong, building evidence that someone else can reproduce, and writing down what the evidence does not show.
This notebook is where I practise that habit in public. The work here is early. It is not peer reviewed, and it is not a claim of novelty. It is a record of the method I am learning: choose a narrow question, build a transparent model, run the experiment, report the result, then attack the result before someone else does.
The rules
- One topic at a time. The current question gets the attention. Old notes stay online so the mistakes remain visible.
- Code has to run. Every figure comes from a script in
scripts/research/. The seed is fixed. The data is published. - No invented citations. If a reference is listed, it should be a real paper I have opened. The reading list will grow slowly.
- State the limitation before the conclusion. A simulation is an argument about assumptions, not a measurement of the world.
- Write for a reader who is not me. The paper should explain the model without requiring the reader to run the code first.
Writing log
2026-10-27
Draft 01: edge offloading paper and thesis plan
- Built the first Python simulator: 20 devices, shared edge queue, three offloading policies.
- Ran a 27-point sweep with 20 replications per point and generated three figures.
- Wrote the first journal-style draft and a four-year thesis outline for the same topic.
- Next: replace the synthetic workload with a trace from a real ESP32 and a local edge server.
Reading list
These are the papers I am using to orient the topic, not a complete survey.
- Mao et al., “A Survey on Mobile Edge Computing: The Communication Perspective,” IEEE Communications Surveys & Tutorials, 2017.
- Satyanarayanan, “The Emergence of Edge Computing,” Computer, 2017.
- Mach and Becvar, “Mobile Edge Computing: A Survey on Architecture and Computation Offloading,” IEEE Communications Surveys & Tutorials, 2017.
- Mao, Zhang, and Letaief, “Dynamic Computation Offloading for Mobile-Edge Computing with Energy Harvesting Devices,” IEEE JSAC, 2016.
- Chen et al., “Efficient Multi-User Computation Offloading for Mobile-Edge Cloud Computing,” IEEE/ACM Transactions on Networking, 2016.
- Zhang et al., “Energy-Optimal Mobile Cloud Computing under Stochastic Wireless Channel,” IEEE Transactions on Wireless Communications, 2013.
What comes next
The next version should be less synthetic. I want to collect a small trace from an ESP32 running a fixed workload, measure the Wi-Fi transfer time and energy for that workload, and replace the lognormal assumptions with the measured distribution. If the conclusion changes, that is the useful result.
The longer thesis direction is in the thesis plan. It extends the same question to multiple edge servers, variable channels, and a testbed, with the simulation used to choose which policies are worth testing on real hardware.
WORKING PAPER / DRAFT 01
Simulation study
A working paper on when battery-powered IoT devices should compute locally or send work to a shared edge server. Includes a reproducible Python simulator, a load sweep, and the limits of the model.
`Edge computing` `Computation offloading` `IoT` `Latency`
>>> READ THE DRAFTTHESIS PLAN / DRAFT 01
Proposal outline
A four-year thesis outline that extends the first simulation study into a trace-driven, multi-edge, testbed-validated investigation of computation offloading.
`Edge computing` `Computation offloading` `IoT` `Uncertainty`
>>> READ THE DRAFT