Repository navigation
fix: plot seasonalities of logistic models with minmax scaling and no floor - #2772
RaphaelFakhri wants to merge 1 commit into
Conversation
|
Hi @RaphaelFakhri! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
A logistic model fit with
scaling='minmax'and nofloorcolumn has its floor set tomin(y).seasonality_plot_dfalways usedcap=1, sosetup_dataframeraisedValueError: cap must be greater than floorwhenevermin(y) >= 1. That brokeplot_components,plot_weekly,plot_yearly,plot_seasonality, and their plotly versions for these models.Changes
seasonality_plot_dfusesy_minas the floor whensetup_dataframewill use it (minmax scaling, no logistic floor), and setscapone unit above the floor. Seasonal components don't depend oncap, so the plotted values don't change for any other model.test_logistic_minmax_without_floor, which checks that the seasonality plot data matches the weekly component returned bypredict.Testing
ValueError: cap must be greater than floor).prophet/testshas 143 passed and 2 skipped.pyrefly checkreports the same results before and after the change.Fixes #2771