dotnet/machinelearning-samples

ML.NET Forcasting Light Switches on and off using TimeSerie or Regression once a week [Question]

Open

#846 opened on Sep 2, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)PowerShell (2,681 forks)batch import
P3help wantedquestion

Repository metrics

Stars
 (4,683 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Question: i have data that has light IDs and when a light of a particular ID is switched on the data is captured now the next step is to try and figure out which light will be on for a particular week in the future. Can anyone let me know how this can be done either using Time series or regression link to the data

all i need to predict is an On or Off like a for the next week or 2

Key Light ID: this is a light represented ad an ID LightDate: this is data captured once a week over the course of 2 n half years OnOff: If the light for a particular ID was on on that time or off On being 1 and off Being 0 WeightByMonth: how many times the light was on for that month max can only be 4 since the data is captured once a week WeightByYear: how many times the light was on for that year TotalWeightOverTheYears: how many times the light was on for the entirety of the data being captured

Contributor guide

Research direction
This issue is a question about forecasting light switches using ML.NET time series or regression. To contribute, first clarify the acceptance criteria with maintainers, as the current description lacks a specific request. Then, explore ML.NET's time series methods (e.g., Singular Spectrum Analysis) and suitable regression approaches. Review existing samples at dotnet/machinelearning samples for similar patterns. Implement a solution that predicts On/Off for a given week using the provided dataset. The deliverable could be a sample notebook or code snippet.
Tech stack
csharp
Domain
machine learningdata
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Unclear
Prerequisites
basic machine learning conceptsC# programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20