@@ -18,11 +18,19 @@ in future iterations of your trained model.
1818
1919You can see the average magnitude of the {feat-imp} values for each field across
2020all the training data in {kib} or by using the
21- {ref}/get-inference.html[get trained model API]. For example:
21+ {ref}/get-inference.html[get trained model API]. For example, {kib} shows the
22+ total feature importance for each field in {regression} or binary
23+ {classanalysis} results as follows:
2224
2325[role="screenshot"]
2426image::images/flights-regression-total-importance.png["Total {feat-imp} values for a {regression} {dfanalytics-job} in {kib}"]
2527
28+ If the {classanalysis} involves more than two classes, {kib} uses colors to show
29+ how the impact of each field varies by class. For example:
30+
31+ [role="screenshot"]
32+ image::images/diamonds-classification-total-importance.png["Total {feat-imp} values for a {classification} {dfanalytics-job} in {kib}"]
33+
2634You can also examine the feature importance values for each individual
2735prediction. In {kib}, you can see these values in JSON objects or decision plots:
2836
@@ -41,8 +49,7 @@ value is positive, it increases the prediction value.
4149By default, {feat-imp} values are not calculated. To generate this information,
4250when you create a {dfanalytics-job} you must specify the
4351`num_top_feature_importance_values` property. For example, see
44- <<flightdata-regression>>.
45- //and <<flightdata-classification>>.
52+ <<flightdata-regression>> and <<flightdata-classification>>.
4653
4754The {feat-imp} values are stored in the {ml} results field for each document in
4855the destination index. The number of {feat-imp} values for each document might
0 commit comments