Papers › RuleMatrix: Visualizing and Understanding Classifiers with Rules

RuleMatrix: Visualizing and Understanding Classifiers with Rules

17 Jul 2018arXiv:1807.06228archive 2025-07-28

Yao Ming, Huamin Qu, Enrico Bertini

With the growing adoption of machine learning techniques, there is a surge of research interest towards making machine learning systems more transparent and interpretable. Various visualizations have been developed to help model developers understand, diagnose, and refine machine learning models. However, a large number of potential but neglected users are the domain experts with little knowledge of machine learning but are expected to work with machine learning systems. In this paper, we present an interactive visualization technique to help users with little expertise in machine learning to understand, explore and validate predictive models. By viewing the model as a black box, we extract a standardized rule-based knowledge representation from its input-output behavior. We design RuleMatrix, a matrix-based visualization of rules to help users navigate and verify the rules and the black-box model. We evaluate the effectiveness of RuleMatrix via two use cases and a usability study.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 17 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 0 honoured, 0 violated, 11 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 17 samples from 1 repository, 11 ran (11 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

rulematrix/rule-matrix-py mentioned on GitHubMITSyntology: 17 samples, 11 ran (0 instrument-failed) · 6 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

17 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 0 honoured, 0 violated, 11 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

11ran
6unverified

Licence: 0 of the 17 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from rulematrix/rule-matrix-py. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

rulematrix/rule-matrix-py community (archive-listed) 17 samples, 11 ran (0 instrument-failed) · 6 unverified
accuracy in 872 papers
census: 8 implementations from 7 papers, 7 distinct outputs across 6 buckets, one shared input per bucket
rulematrix/metrics.py ran MIT (permissive) · 1eeee0ccaf141825 · report fixture: signature y_true:ndarray/1/int, y_pred:ndarray/1/int, weights:ndarray/1/float · returned float64 · level recorded 2026-09-26
auc_score in 5 papers rulematrix/metrics.py ran MIT (permissive) · d3542621aac4348e · report fixture: signature y_true:ndarray/1/int, y_pred:ndarray/2/float, average:NoneType/0/? · returned ndarray · level recorded 2026-09-26
check_input_constraints rulematrix/surrogate/sample.py ran MIT (permissive) · 02e591dd6b1e1576 · report fixture: signature n_features:int/0/int, is_continuous:ndarray/1/bool, is_categorical:ndarray/1/bool, is_integer:ndarray/1/bool · returned tuple · level recorded 2026-09-26
compute_mdlp_all_intervals rulematrix/surrogate/discretize.py ran MIT (permissive) · c79736ac5b0a2bd0 · report fixture: signature mdlp_discretizer:MockMDLPDiscretizer/0/? · returned list · level recorded 2026-09-26
create_constraint rulematrix/surrogate/sample.py ran MIT (permissive) · bbcc1d105e0a0c8d · report fixture: signature feature_type:str/0/str, range_:list/1/int · returned IntegerConstraint · level recorded 2026-09-26
create_constraints rulematrix/surrogate/sample.py ran MIT (permissive) · c103faf7972f2e5c · report fixture: signature n_features:int/0/int, is_continuous:ndarray/1/bool, is_categorical:ndarray/1/bool, is_integer:ndarray/1/bool, ranges:list/1/tuple · returned list · level recorded 2026-09-26
discretizer2json rulematrix/utils.py ran MIT (permissive) · 677a4296cd9b867b · report fixture: signature discretizer:MockDiscretizer/0/? · returned list · level recorded 2026-09-26
dumps rulematrix/utils.py ran MIT (permissive) · b9ed416dd712f887 · report fixture: signature obj:dict/0/? · returned str · level recorded 2026-09-26
filter_data in 19 papers rulematrix/utils.py ran MIT (permissive) · a8c4c235c66db7be · report fixture: signature is_categorical:list/1/bool, x:ndarray/2/float, y:ndarray/1/int, query:list/1/list · returned tuple · level recorded 2026-09-26
label2binary rulematrix/metrics.py ran fingerprinted MIT (permissive) · c01c1c0f3dfdaf67 · report fixture: signature y:ndarray/1/int · returned ndarray · level recorded 2026-09-26
prepare_streams rulematrix/visualization/data_model.py ran MIT (permissive) · db1fedad319eeca0 · report fixture: signature model:callable/0/?, dataset:DummyDataset/0/?, conditional:bool/0/bool, bins:int/0/int · returned str · level recorded 2026-09-26
compute_support_matrix rulematrix/visualization/data_model.py unverified MIT (permissive) · 242f789db4a0fa0a · report
get_discretizer rulematrix/surrogate/discretize.py unverified MIT (permissive) · 010eba1abe819f5a · report
obj2pkl rulematrix/server/utils.py unverified MIT (permissive) · 4b9339c331a65eff · report
pkl2obj rulematrix/server/utils.py unverified MIT (permissive) · a0dd49cfc5f36cb2 · report
prepare_rule_list_json rulematrix/visualization/data_model.py unverified MIT (permissive) · 4671b211694e13a6 · report
surrogate rulematrix/surrogate/surrogate.py unverified MIT (permissive) · 32847a5f07b51596 · report

Tasks

BIG-bench Machine LearningNavigate

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections