Papers › Universal Non-Intrusive Load Monitoring (UNILM) Using Filter Pipelines, Probabilistic...
Universal Non-Intrusive Load Monitoring (UNILM) Using Filter Pipelines, Probabilistic Knapsack, and Labelled Partition Maps
Alejandro Rodriguez-Silva, Stephen Makonin
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
Being able to track appliances energy usage without the need of sensors can help occupants reduce their energy consumption to help save the environment all while saving money. Non-intrusive load monitoring (NILM) tries to do just that. One of the hardest problems NILM faces is the ability to run unsupervised -- discovering appliances without prior knowledge -- and to run independent of the differences in appliance mixes and operational characteristics found in various countries and regions. We propose a solution that can do this with the use of an advanced filter pipeline to preprocess the data, a Gaussian appliance model with a probabilistic knapsack algorithm to disaggregate the aggregate smart meter signal, and partition maps to label which appliances were found and how much energy they use no matter the country/region. Experimental results show that relatively complex appliance signals can be tracked accounting for 93.7% of the total aggregate energy consumed.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections