<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jörn Hees on </title>
    <link>https://mc-lab.de/authors/j%C3%B6rn-hees/</link>
    <description>Recent content in Jörn Hees on </description>
    <generator>Hugo</generator>
    <language>de-DE</language>
    <copyright>© 2025 Mobile Communication Lab der Hochschule Bonn-Rhein-Sieg | Grantham-Allee 20 | 53757 Sankt Augustin</copyright>
    <lastBuildDate>Fri, 02 Oct 2026 16:12:42 +0200</lastBuildDate>
    <atom:link href="https://mc-lab.de/authors/j%C3%B6rn-hees/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Systematic Sample Size Analysis of ML-Based Path Loss Prediction for LPWAN</title>
      <link>https://mc-lab.de/publications/2026-10-systematic-sample-size/</link>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0200</pubDate>
      <guid>https://mc-lab.de/publications/2026-10-systematic-sample-size/</guid>
      <description>&lt;p&gt;Low Power Wide Area Networks like LoRa are increasingly deployed for smart city applications, requiring accurate path loss prediction for effective network planning. Traditional (empirical) propagation models often exhibit limited accuracy in these scenarios. We investigate machine learning models for LoRa path loss prediction, systematically analyzing how prediction accuracy scales with training set size using real-world measurements from an urban deployment.&lt;/p&gt;&#xA;&lt;p&gt;Our approach employs a Random Forest with LiDAR-derived terrain features and k-Nearest Neighbors with coordinate data, comparing their performance against established empirical models and specialized LPWAN models. Under random pooled splits, both ML models consistently outperform the considered baseline models across the evaluated training-set sizes. At maximum training size, they achieve RMSE values below 6.5 dB compared to 9.7 dB for the best baseline, indicating accurate within-deployment interpolation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
