Model Explainability
Inspect explanation files after training a model to investigate input-column sensitivity and the sampled graph context used for selected examples. These files describe the selected model on a bounded set of test examples. They do not establish that a feature caused an outcome or explain every later prediction.
Use your prediction task to identify which explanation methods are eligible:
Eligibility does not guarantee that a file is generated. Availability also depends on model compatibility, whether explanations are enabled, and whether the explanation step completes. Check the fit logs if an eligible explanation is missing.
Find the Selected Experiment
For supported tasks, Trainer.fit() requests gradient scores, column analysis, and sampled subgraphs unless trainer.model_plan.training_job.disable_explain is enabled. The files remain in local scratch and are not part of the published model bundle.
Continue in the process that produced fit_result. Resolve the selected experiment instead of reading every experiment directory under scratch:
When training refits the selected experiment on the combined training and validation data, test explanations are written under the matching _refit_trainval directory. Otherwise, they remain under the selected version_N directory.
Explanation availability depends on the task and model. An explanation failure is logged without discarding a successfully trained model. If a file is absent, check disable_explain and the fit logs. A missing score does not mean that a column was excluded from training.
Inspect Gradient Scores
scores.csv contains one gradient attribution score for each reported input column. Its columns are table, column, and score.
Plot the highest scores to compare columns within this explanation. Run the examples below with pandas, numpy, and matplotlib installed in your notebook or Python environment. Continue from the paths dictionary above.

Illustrative data, not results from a customer model. Scores are shown as reported, without converting them to percentages.
Plot the column ranking from scores.csv
Use the table and column names to check whether the leading signals make sense for your task. A high score shows model sensitivity in the examples used for explanation, not a causal effect or a guarantee of predictive value on future data.
These scores concern input features. They are different from the AutoML setting analysis in Training Diagnostics.
Inspect Column Cohorts
Column analysis groups feature values into cohorts and reports their population share, average predictions, and average observed targets when available. Each record identifies a column by table_name, hop, and col_name. The same column can appear at more than one graph hop, so select all three fields together.

Illustrative regression data for customers.purchase_count at hop 0. These values do not describe a trained customer model.
The upper panel compares averages in the prediction target’s units. For a selected classification class, it compares predicted probabilities with observed class proportions. The lower panel shows each cohort’s relative population. Differences describe associations in the explanation sample, not the effect of changing a feature. A small population share warrants caution and does not provide an absolute sample count or uncertainty interval.
Select a Column and Class
List the available records first. Replace column_key with a (table_name, hop, col_name) tuple from this output. For class dictionaries, the example selects and prints the first available class; set class_name to another listed key to inspect that class. Regression uses a single list and needs no class selection.
Plot Predictions and Population Share
Run this after selecting the record above. The plot omits observed targets when targets is absent or null. It rejects missing classes, invalid numbers, and mismatched cohort lengths rather than plotting misaligned values.
Plot the selected cohort record
Inspect Sampled Graph Context
The subgraph collector saves a bounded selection of test examples. Each file can contain a root entity, sampled nodes and relationships, and feature values. Inspect the structure before building a visualization or sharing the file:
The subgraph is a sampled view of model context, not the complete source graph. It can contain entity identifiers and feature values. Review that data before exporting an image or sharing the JSON. The local Python API does not provide a graph visualization call for these files.
Preserve the Explanation Files
Retain the selected explanation files with the model version, predictive query, graph definition, snapshot identity, and Kumo package version used for training. Publishing a model does not copy these files.
On Linux, copy the complete AutoML directory to storage that survives the machine so the selected experiment and any refit explanations remain together. In a Snowflake notebook, use Preserve the Selected History to archive that directory to a restricted internal stage. Keep access limited when the files contain source derived values. In a Databricks notebook, use the same history guide to copy the selected AutoML directory to a restricted Unity Catalog volume before the cluster stops. The model bundle does not include explanation files.