Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug #112: window size identification fixed for trend change detection #114

Merged
merged 1 commit into from
Sep 29, 2022

Conversation

papaemman
Copy link
Contributor

The current approach for trend detection in the Data exploration module (/luminaire/exploration/data_exploration.py) was enabled only for daily ('D') and hourly ('H) time series.
I added a fix to trigger the computation of window sizes for weekly ('W') frequency, using a value of 4.
Also, I added a fix to support all the other frequencies.

@papaemman
Copy link
Contributor Author

Hey @sayanchk, @shahsmit14, @snazzyfox

I opened this PR to solve the bug regarding the data exploration module for time series with Weekly frequency.
This is intended to replace the previous PR (#113).

I'm kindly asking you to review it and approve it.

Thank you very much.

Panos

@sayanchk
Copy link
Collaborator

sayanchk commented Sep 15, 2022

Hi @papaemman, I think the example in the other PR (also adding here as reference) is comprehensive. My point is the assumption of monthly seasonality for weekly data could be little stringent. That being said, based on the example you shared, I think it's fare to go with your changes and see how it works out for your and other use cases. A better solution would be to check the _detect_window_size method within DataExploration and optimize the method to detect the window sizes automatically for weekly data. I'll create an issue and tag you to it for visibility.

Thanks for your contribution to Luminaire!

@sayanchk
Copy link
Collaborator

Here's the link to the related issue i just created: #115

@sayanchk sayanchk requested a review from shahsmit14 September 15, 2022 23:52
@sayanchk
Copy link
Collaborator

@shahsmit14 I added you as a reviewer to this issue as well. Looks like I don't have permission to merge it. Please approve and merge if it looks okay on your end. Thanks!

@sayanchk sayanchk requested a review from snazzyfox September 28, 2022 15:18
@sayanchk
Copy link
Collaborator

sayanchk commented Sep 28, 2022

@shahsmit14 @snazzyfox Following up for updates. Can anyone take a look?

@shahsmit14
Copy link
Collaborator

Sorry for the delayed response. Merging this.

@shahsmit14 shahsmit14 merged commit 0af6a34 into zillow:master Sep 29, 2022
@shahsmit14
Copy link
Collaborator

I will do a release this with this MR since it has the code to release for v0.4.1 in setup.py

@shahsmit14
Copy link
Collaborator

Pending one more merge before releasing #118

@shahsmit14
Copy link
Collaborator

@papaemman v0.4.1 is now available to use. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants