Route Threshold Optimization Does Not Change Default Threshold Values

[vdemchenko3]

Hi,

What's the best way to interpret unchanged threshold values after optimization? I've ran into a few situations where running route_layer.fit() did not alter the thresholds at all.

Does this mean more data or more iterations are needed or something else entirely?

On a separate note, are there any plans to introduce other optimization methods in the future?

Thanks!

[jess-lord]

also curious about this. Would be nice to see a report on accuracy per class too.

[prawiraelang]

I also noticed this behavior, as discussed in #299. It's been a while since I did the threshold tuning, but seeing many people still talking about this, I suspect it might be a bug in the optimization mechanism.