Coming from legacy MLLM-Shap¶
mllm-shap replaces the legacy MLLM-Shap
research code. The algorithms are the same family; the configuration, the result
types and a few defaults differ. This page maps the old names to the new ones.
Explainers to estimators¶
legacy MLLM-Shap had one explainer class per estimator and sampling variant. In
mllm-shap the estimator is a name in explanation.estimator and the variant
is expressed with the budget keys:
legacy MLLM-Shap class |
|
Budget keys |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The estimand is a separate key: explanation.estimand is shapley or
banzhaf and every result carries the label (Using estimand aggregators).
Utilities to value functions¶
The legacy MLLM-Shap experiments named their utilities U1 to U4. The corresponding
explanation.value_fn settings:
Label |
legacy MLLM-Shap |
|
|---|---|---|
U1 |
|
|
U2 |
|
|
U3 |
|
|
U4 |
|
|
Behaviour that changed¶
Frozen TF-IDF.
tfidf_cosinefits its IDF weights once on all outputs of the run and scores every coalition with them, instead of refitting per comparison. Scores are therefore comparable across coalitions of one run.Efficiency is verifiable. Results report
base_valueandgrand_value(the empty and grand coalitions), so you can check that the values sum to their difference; the axiom tests enforce it. Nothing checks it at run time. Exact results matchPreciseShapExplaineron additive games.Archives store generations. A run archive keeps the base generation and every coalition output;
reanalyze()recomputes payoffs and attributions with another value function or normalizer without new model calls.Mask hashes are process-independent.
hash_mask()uses BLAKE2b, so hashes written by legacy MLLM-Shap are not comparable with the onesmllm-shapproduces.One configuration object. Model, generation and explanation settings live in one validated
ExplainConfig(Configuration) instead of separate keyword arguments and model config objects.