Papers › Iterative Random Forests to detect predictive and stable high-order interactions

Iterative Random Forests to detect predictive and stable high-order interactions

26 Jun 2017arXiv:1706.08457archive 2025-07-28

Sumanta Basu, Karl Kumbier, James B. Brown, Bin Yu

Genomics has revolutionized biology, enabling the interrogation of whole transcriptomes, genome-wide binding sites for proteins, and many other molecular processes. However, individual genomic assays measure elements that interact in vivo as components of larger molecular machines. Understanding how these high-order interactions drive gene expression presents a substantial statistical challenge. Building on Random Forests (RF), Random Intersection Trees (RITs), and through extensive, biologically inspired simulations, we developed the iterative Random Forest algorithm (iRF). iRF trains a feature-weighted ensemble of decision trees to detect stable, high-order interactions with same order of computational cost as RF. We demonstrate the utility of iRF for high-order interaction discovery in two prediction problems: enhancer activity in the early Drosophila embryo and alternative splicing of primary transcripts in human derived cell lines. In Drosophila, among the 20 pairwise transcription factor interactions iRF identifies as stable (returned in more than half of bootstrap replicates), 80% have been previously reported as physical interactions. Moreover, novel third-order interactions, e.g. between Zelda (Zld), Giant (Gt), and Twist (Twi), suggest high-order relationships that are candidates for follow-up experiments. In human-derived cells, iRF re-discovered a central role of H3K36me3 in chromatin-mediated splicing regulation, and identified novel 5th and 6th order interactions, indicative of multi-valent nucleosomes with specific roles in splicing regulation. By decoupling the order of interactions from the computational cost of identification, iRF opens new avenues of inquiry into the molecular mechanisms underlying genome biology.

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 11 code samples harvested from 4 repositories linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 7 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 7 where our contract draft was wrong; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: community (archive-listed): 11 samples from 4 repositories, 7 ran (0 with no instrument failure; 7 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-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

Yu-Group/iterative-Random-Forest mentioned on GitHubSyntology: 3 samples, 2 ran (2 instrument-failed) · 1 unverified report
bpark738/iRF mentioned on GitHubSyntology: 3 samples, 3 ran (3 instrument-failed) · 0 unverified report
ishoxo/irf mentioned on GitHubSyntology: 3 samples, 1 ran (1 instrument-failed) · 2 unverified report
shifwang/irf mentioned on GitHubSyntology: 2 samples, 1 ran (1 instrument-failed) · 1 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

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

7ran · our draft was wrong
4unverified

Licence: 11 of the 11 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 4 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

Yu-Group/iterative-Random-Forest community (archive-listed) 3 samples, 2 ran (2 instrument-failed) · 1 unverified
filter_leaves_classifier irf/irf_utils.py ran · our draft was wrong licence not identified · pointer only · 74487807104d4ef3 · report fixture: signature dtree_data:dict/0/?, bin_class_type:int/0/int · returned dict · level recorded 2026-09-22
generate_rit_samples irf/irf_utils.py ran · our draft was wrong licence not identified · pointer only · f3cb399edc5cb695 · report fixture: signature all_rf_tree_data:dict/0/?, bin_class_type:int/0/int · returned generator · level recorded 2026-09-22
get_rit_tree_data irf/irf_utils.py unverified licence not identified · pointer only · b7ab93c439f6346b · report
bpark738/iRF community (archive-listed) 3 samples, 3 ran (3 instrument-failed) · 0 unverified
filter_leaves_classifier irf/irf_utils.py ran · our draft was wrong licence not identified · pointer only · 3f5d96cefb7d165d · report fixture: signature dtree_data:dict/0/?, bin_class_type:int/0/int · returned dict · level recorded 2026-09-22
generate_rit_samples irf/irf_utils.py ran · our draft was wrong licence not identified · pointer only · 1b3853ec1401d104 · report fixture: signature all_rf_tree_data:dict/0/?, bin_class_type:int/0/int · returned generator · level recorded 2026-09-22
get_rit_tree_data irf/irf_utils.py ran · our draft was wrong licence not identified · pointer only · 8c3459a1553ad720 · report fixture: signature all_rf_tree_data:dict/0/?, bin_class_type:int/0/int · returned dict · level recorded 2026-09-22
ishoxo/irf community (archive-listed) 3 samples, 1 ran (1 instrument-failed) · 2 unverified
get_validation_metrics irf/irf_utils.py ran · our draft was wrong licence not identified · pointer only · 627753c508a398e3 · report fixture: signature inp_class_reg_obj:RandomForestClassifier/0/?, y_true:ndarray/1/int, X_test:ndarray/2/float · returned dict · level recorded 2026-09-22
all_tree_paths irf/irf_utils.py unverified licence not identified · pointer only · 102bd9c4261017ef · report
get_tree_data irf/irf_utils.py unverified licence not identified · pointer only · f5c2c72ec22787ee · report
shifwang/irf community (archive-listed) 2 samples, 1 ran (1 instrument-failed) · 1 unverified
get_validation_metrics irf/irf_utils.py ran · our draft was wrong no licence file found · pointer only · 6eea6f59de6f28de · report fixture: signature inp_class_reg_obj:RandomForestClassifier/0/?, y_true:ndarray/1/int, X_test:ndarray/2/float · returned dict · level recorded 2026-09-22
all_tree_signed_paths irf/irf_utils.py unverified no licence file found · pointer only · cc79532ba9a31b16 · report

Tasks

Vocal Bursts Intensity Prediction

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