Problems with sample_period>30min in disaggregation
See original GitHub issueI have been working with the REDD dataset and with a dataset created by me (with a sample_period=1s in all meters). In both cases, when I try to disaggregate (CO and FHMM) the mains with a sample_period greater than 30 minutes, no process is performed, and the output.h5 file is empty.
This function I am using without problems for periods less than 30 minutes:
disaggregate(test_elec.mains(), output, sample_period=3600)
Does anyone know why this happens?
Thanks
Issue Analytics
- State:
- Created 3 years ago
- Comments:9
Top Results From Across the Web
Non-intrusive load disaggregation solutions for very low-rate ...
An unsupervised approach based on semi-binary non-negative matrix fac- torization (SBNMF) is proposed in [43] for the 30-min NILM problem, where.
Read more >Disaggregating Time Series Data for Energy Consumption by ...
This dissertation generalizes the problem of disaggregating time series data ... 1.6 Example customer consumption and temperature for temperature-sensitive.
Read more >Aggregation and disaggregation features of the human ... - NCBI
A control sample was collected (pre‐shock) prior to partitioning cells for heat treatment. The cells were treated either with heat shock (44°C) ...
Read more >Algorithms for Energy Disaggregation - UPCommons
However, they currently send readings at very low sampling rates (between 15 minutes and 1 hour), which seems incompatible with most disaggregation algorithms....
Read more >Temporal rainfall disaggregation using a micro-canonical ...
While for the calibration period the autocorrelation was ... lutions of t = {4 h, 2 h, 1 h, 30 min, 15 min,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I believe the main issue is the check for the minimum number of samples (defaults to 100). Try something like
There could be warnings about number of clusters (with such a low sample rate, sometimes there is only one, that is, no events for some appliances), otherwise it seems to work fine. Using
.disaggregate_chunk()
and iterating the chunks much like in the old example notebooks also seems to work as expected.Mathematically, I don’t see any inherit limitation for the methods. I don’t recall anything else related to the sample period or resampling that limits the upper range of the sample period, but it’s a possibility.
I’ll try to check this on the weekend. Should be easy to check. If you want to give it a go, try stepping through the code with a debugger.