"include/git@developer.sourcefind.cn:tianlh/lightgbm-dcu.git" did not exist on "f3037c184365606cfd1476ba4d86d4bbc5e2f079"
Commit 51bceaaa authored by Pierre PACI's avatar Pierre PACI Committed by Guolin Ke
Browse files

better log for "Check max_depth and num_leaves" (#931)

* better log for "Check max_depth and num_leaves"

The default log said "[LightGBM] [Warning] Accuarcy may be bad since you didn't set num_leaves." but the case max_depth²>num_leaves could also trigger this log.
Correction of a typo too : Accuarcy > Accuracy

* Update config.cpp
parent 9c57793e
...@@ -230,7 +230,7 @@ void OverallConfig::CheckParamConflict() { ...@@ -230,7 +230,7 @@ void OverallConfig::CheckParamConflict() {
int full_num_leaves = static_cast<int>(std::pow(2, boosting_config.tree_config.max_depth)); int full_num_leaves = static_cast<int>(std::pow(2, boosting_config.tree_config.max_depth));
if (full_num_leaves > boosting_config.tree_config.num_leaves if (full_num_leaves > boosting_config.tree_config.num_leaves
&& boosting_config.tree_config.num_leaves == kDefaultNumLeaves) { && boosting_config.tree_config.num_leaves == kDefaultNumLeaves) {
Log::Warning("Accuarcy may be bad since you didn't set num_leaves."); Log::Warning("Accuracy may be bad since you didn't set num_leaves and max_depth² > num_leaves.");
} }
} }
} }
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment