PaulWestenthanner

Hi, do I see this correct, that with this update it's possible to show percent values in the flow-charts? This would be a great feature as well. Cheers, Paul

I also ran into this error. In my case, the problem was a column that only had NULL values. Changing NULL to empty strings solved the problem.

> Is that really desired in general? That's a good question. I've read trough the target-encoder paper and there is no hard rule saying single-value categories should be assigned the...

From a technical point I agree with @bmreiniger that making a hard cut between once-observed labels and twice (or more often) observed labels does not make too much sense. So...

Hi guys, I'm planning to do a release shortly and add the FutureWarnings for those who use the default parameters at the moment. As for new default parameters I just...

Hi, yes the best values will depend on the used estimator. The thing we're discussing in this issue is that the default values for smoothing and min_samples_leaf are just selected...

That's because the new defaults might be bad for some encoders but the current ones are bad for pretty much all encoders. The current behaviour is that if a category...

I chose it because I think the values for lambda make sense > I would suggest k=20 and f=10 as new default parameters This gives 95% global mean for n=1...

Hi @Pacman1984 I understand that this technique can improve model quality and that you want to contribute it to a bigger framework. Both of these points make absolute sense. I'm...

Hi Will, I recently commited to the repo for the first time and I'd be definitely be interested in doing more. @janmotl @wdm0006 What would be the way to go...