minmax not absmax in docs

This commit is contained in:
Cuong Duong 2023-10-18 18:33:05 +11:00
parent b16d84979f
commit c00f6a2d72
2 changed files with 2 additions and 2 deletions

View file

@ -240,7 +240,7 @@ There are few caveats that should be kept in mind when considering warm-starting
Before model fitting, Prophet scales `y` by dividing by the maximum value in the history. For datasets with very large `y` values, the scaled `y` values may be compressed to a very small range (i.e. `[0.99999... - 1.0]`), which causes a bad fit. This can be fixed by setting `scaling='absmax'` in the Prophet constructor.
Before model fitting, Prophet scales `y` by dividing by the maximum value in the history. For datasets with very large `y` values, the scaled `y` values may be compressed to a very small range (i.e. `[0.99999... - 1.0]`), which causes a bad fit. This can be fixed by setting `scaling='minmax'` in the Prophet constructor.
```python

View file

@ -437,7 +437,7 @@
"source": [
"### minmax scaling (new in 1.1.5)\n",
"\n",
"Before model fitting, Prophet scales `y` by dividing by the maximum value in the history. For datasets with very large `y` values, the scaled `y` values may be compressed to a very small range (i.e. `[0.99999... - 1.0]`), which causes a bad fit. This can be fixed by setting `scaling='absmax'` in the Prophet constructor."
"Before model fitting, Prophet scales `y` by dividing by the maximum value in the history. For datasets with very large `y` values, the scaled `y` values may be compressed to a very small range (i.e. `[0.99999... - 1.0]`), which causes a bad fit. This can be fixed by setting `scaling='minmax'` in the Prophet constructor."
]
},
{