Papers › PipelineProfiler: A Visual Analytics Tool for the Exploration of AutoML Pipelines

PipelineProfiler: A Visual Analytics Tool for the Exploration of AutoML Pipelines

1 May 2020arXiv:2005.00160links table onlyarchive 2025-07-28

Jorge Piazentin Ono, Sonia Castelo, Roque Lopez, Enrico Bertini, Juliana Freire, Claudio Silva

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

In recent years, a wide variety of automated machine learning (AutoML) methods have been proposed to search and generate end-to-end learning pipelines. While these techniques facilitate the creation of models for real-world applications, given their black-box nature, the complexity of the underlying algorithms, and the large number of pipelines they derive, it is difficult for their developers to debug these systems. It is also challenging for machine learning experts to select an AutoML system that is well suited for a given problem or class of problems. In this paper, we present the PipelineProfiler, an interactive visualization tool that allows the exploration and comparison of the solution space of machine learning (ML) pipelines produced by AutoML systems. PipelineProfiler is integrated with Jupyter Notebook and can be used together with common data science tools to enable a rich set of analyses of the ML pipelines and provide insights about the algorithms that generated them. We demonstrate the utility of our tool through several use cases where PipelineProfiler is used to better understand and improve a real-world AutoML system. Furthermore, we validate our approach by presenting a detailed analysis of a think-aloud experiment with six data scientists who develop and evaluate AutoML tools.

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 22 code samples harvested from 1 repository linked to this paper: 18 ran (of which 0 constructed an object rather than computing a result; 18 with no instrument failure: 0 honoured, 0 violated, 18 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 22 samples from 1 repository, 18 ran (18 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

VIDA-NYU/PipelineVis officialmentioned in papermentioned on GitHubBSD-3-ClauseSyntology: 22 samples, 18 ran (0 instrument-failed) · 4 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

22 samples harvested: 18 ran (of which 0 constructed an object rather than computing a result; 18 with no instrument failure: 0 honoured, 0 violated, 18 with no contract checked; 0 where Syntology's instrument failed) · 4 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.

18ran
4unverified

Licence: 0 of the 22 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 VIDA-NYU/PipelineVis. “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.

VIDA-NYU/PipelineVis official repository 22 samples, 18 ran (0 instrument-failed) · 4 unverified
comm_export_pipelines PipelineProfiler/_plot_pipeline_matrix.py ran BSD-3-Clause (permissive) · cb700fb13b74cafb · report fixture: signature msg:dict/0/? · returned dict · level recorded 2026-09-25
compute_edge_type PipelineProfiler/_similarity_flooding.py ran BSD-3-Clause (permissive) · 468aa06640e32104 · report fixture: signature g:DiGraph/0/?, edge:tuple/1/int · returned str · level recorded 2026-09-25
create_pairwise_conn_graph PipelineProfiler/_similarity_flooding.py ran BSD-3-Clause (permissive) · 093743a6ad664cab · report fixture: signature g1:DiGraph/0/?, g2:DiGraph/0/? · returned DiGraph · level recorded 2026-09-25
extract_coef_matrix PipelineProfiler/Experimental/FeatureWeights.py ran BSD-3-Clause (permissive) · 981f88dd9636a989 · report fixture: signature pipelines:list/1/dict · returned tuple · level recorded 2026-09-25
extract_primitive_matrix PipelineProfiler/_powerset_analysis.py ran BSD-3-Clause (permissive) · 02b0b27a25321f61 · report fixture: signature pipelines:list/1/dict · returned tuple · level recorded 2026-09-25
extract_primitive_names PipelineProfiler/_powerset_analysis.py ran BSD-3-Clause (permissive) · 8f8cace5414ad119 · report fixture: signature pipeline:dict/0/? · returned list · level recorded 2026-09-25
extract_primitive_names PipelineProfiler/Experimental/FeatureWeights.py ran BSD-3-Clause (permissive) · e83e9f9bff219c2f · report fixture: signature pipeline:dict/0/? · returned list · level recorded 2026-09-25
extract_scores in 16 papers PipelineProfiler/_powerset_analysis.py ran BSD-3-Clause (permissive) · 2bdd440663e3b6c7 · report fixture: signature pipelines:list/1/dict · returned list · level recorded 2026-09-25
find_ensemble_weights PipelineProfiler/_import_autosklearn.py ran BSD-3-Clause (permissive) · 78e46d80267263a0 · report fixture: signature all_params:list/1/dict, models_with_weights:list/1/tuple · returned ndarray · level recorded 2026-09-25
find_metric_name PipelineProfiler/_import_autosklearn.py ran BSD-3-Clause (permissive) · af652d3f85cb2cd0 · report fixture: signature automl:MockAutoML/0/? · returned str · level recorded 2026-09-25
find_pipeline_digest PipelineProfiler/_helpers.py ran BSD-3-Clause (permissive) · 02ed464496dd4171 · report fixture: signature pipelines:list/1/dict, digest:str/0/str · returned list · level recorded 2026-09-25
graph_data_accessor PipelineProfiler/_graph_matching.py ran BSD-3-Clause (permissive) · 171e8b337efff784 · report fixture: signature node:dict/0/?, graph_name:str/0/str · returned dict · level recorded 2026-09-25
id_generator in 8 papers PipelineProfiler/_plot_pipeline_node_link.py ran fingerprinted BSD-3-Clause (permissive) · 9e6f0e878723c786 · report fixture: signature size:int/0/int · returned str · level recorded 2026-09-25
import_autosklearn PipelineProfiler/_import_autosklearn.py ran BSD-3-Clause (permissive) · bbed82fca7a991d2 · report fixture: signature automl:MockAutoML/0/?, source:str/0/str · returned list · level recorded 2026-09-25
merge_pipeline_files PipelineProfiler/pipeline_merge.py ran BSD-3-Clause (permissive) · cdf74ce85a1cf951 · report fixture: signature pipelines_file:str/0/str, pipeline_runs_file:str/0/str, n:int/0/int, verbose:bool/0/bool · returned list · level recorded 2026-09-25
node_type PipelineProfiler/_similarity_flooding.py ran BSD-3-Clause (permissive) · e257df5f0fbcb877 · report fixture: signature g:DiGraph/0/?, node:str/0/str · returned str · level recorded 2026-09-25
pipeline_to_graph PipelineProfiler/_graph_matching.py ran BSD-3-Clause (permissive) · 5d81e8b2d80be745 · report fixture: signature pipeline:dict/0/?, name:str/0/str · returned DiGraph · level recorded 2026-09-25
python_path_similarity PipelineProfiler/_graph_matching.py ran fingerprinted BSD-3-Clause (permissive) · 64cc10732a5bf54b · report fixture: signature python_path1:str/0/str, python_path2:str/0/str · returned float · level recorded 2026-09-25
comm_merge_graphs PipelineProfiler/_plot_pipeline_matrix.py unverified BSD-3-Clause (permissive) · fd412c5826f4338f · report
comm_powerset_analysis PipelineProfiler/_plot_pipeline_matrix.py unverified BSD-3-Clause (permissive) · ce3a9407ef5f2b82 · report
make_html PipelineProfiler/_plot_pipeline_node_link.py unverified BSD-3-Clause (permissive) · f03844004cdb90bc · report
setup_comm_colab PipelineProfiler/_comm_api.py unverified BSD-3-Clause (permissive) · 1996a25026aaf84a · report

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