Skip to content

Commit 87c3a01

Browse files
authored
Add FAQ to README.md 3 (corrected links 2)
[skip ci]
1 parent 18eeebc commit 87c3a01

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -282,7 +282,7 @@ You can also find some winning stacking architectures on [Kaggle blog](http://bl
282282

283283
***Note:*** Always remember that higher number of levels or models does NOT guarantee better result. The key to success in stacking (blending) is diversity - low correlation between models.
284284

285-
For some example configurations see [Q16](https://github.com/vecxoz/vecstack#16-how-many-models-should-i-use-on-a-given-level)
285+
For some example configurations see [Q16](https://github.com/vecxoz/vecstack#16-how-many-models-should-i-use-on-a-given-stacking-level)
286286

287287
### 18. How do I choose models for stacking?
288288

@@ -354,15 +354,15 @@ You can find out only by experiment. Default choice is variant ***A***, because
354354

355355
### 25. How to choose number of folds?
356356

357-
***Note:*** Remember that higher number of folds substantially increase training time (and RAM consumption for StackingTransformer). See [Q23](https://github.com/vecxoz/vecstack#23-how-to-estimate-training-time-and-number-of-models-which-will-be-built).
357+
***Note:*** Remember that higher number of folds substantially increase training time (and RAM consumption for StackingTransformer). See [Q23](https://github.com/vecxoz/vecstack#23-how-to-estimate-stacking-training-time-and-number-of-models-which-will-be-built).
358358

359359
* Standard approach: 4 or 5 folds.
360360
* If data is big: 3 folds.
361361
* If data is small: you can try more folds like 10 or so.
362362

363363
### 26. When I transform train set I see 'Train set was detected'. What does it mean?
364364

365-
Due to its nature stacking procedure treats train set and any other set differently. It means that transformation is different for train set and any other set. So if you are transforming `X_train` and see 'Train set was detected' everything is OK. If you meant to transform train set but you don't see this message then something went wrong. Possibly your train set was changed (it is not allowed). In this case you have to retrain `StackingTransformer`. For more details see [stacking tutorial](https://github.com/vecxoz/vecstack/blob/master/examples/00_stacking_concept_pictures_code.ipynb) or [Q8](https://github.com/vecxoz/vecstack#8-why-do-i-need-complicated-stacking-procedure)
365+
Due to its nature stacking procedure treats train set and any other set differently. It means that transformation is different for train set and any other set. So if you are transforming `X_train` and see 'Train set was detected' everything is OK. If you meant to transform train set but you don't see this message then something went wrong. Possibly your train set was changed (it is not allowed). In this case you have to retrain `StackingTransformer`. For more details see [stacking tutorial](https://github.com/vecxoz/vecstack/blob/master/examples/00_stacking_concept_pictures_code.ipynb) or [Q8](https://github.com/vecxoz/vecstack#8-why-do-i-need-complicated-inner-procedure-for-stacking)
366366

367367
***Note 1:*** It is NOT allowed to (substantially) change train set after training on it.
368368
***Note 2:*** To be correctly detected train set does not necessarily have to be identical (exactly the same). It must have the same shape and all values must be *close* (`np.isclose` is used for checking). So if you somehow regenerate your train set you should not worry.

0 commit comments

Comments
 (0)