Papers › IGL-Bench: Establishing the Comprehensive Benchmark for Imbalanced Graph Learning

IGL-Bench: Establishing the Comprehensive Benchmark for Imbalanced Graph Learning

14 Jun 2024arXiv:2406.09870archive 2025-07-28

Jiawen Qin, Haonan Yuan, Qingyun Sun, Lyujin Xu, Jiaqi Yuan, Pengfeng Huang, Zhaonan Wang, Xingcheng Fu, Hao Peng, JianXin Li, Philip S. Yu

Deep graph learning has gained grand popularity over the past years due to its versatility and success in representing graph data across a wide range of domains. However, the pervasive issue of imbalanced graph data distributions, where certain parts exhibit disproportionally abundant data while others remain sparse, undermines the efficacy of conventional graph learning algorithms, leading to biased outcomes. To address this challenge, Imbalanced Graph Learning (IGL) has garnered substantial attention, enabling more balanced data distributions and better task performance. Despite the proliferation of IGL algorithms, the absence of consistent experimental protocols and fair performance comparisons pose a significant barrier to comprehending advancements in this field. To bridge this gap, we introduce IGL-Bench, a foundational comprehensive benchmark for imbalanced graph learning, embarking on 16 diverse graph datasets and 24 distinct IGL algorithms with uniform data processing and splitting strategies. Specifically, IGL-Bench systematically investigates state-of-the-art IGL algorithms in terms of effectiveness, robustness, and efficiency on node-level and graph-level tasks, with the scope of class-imbalance and topology-imbalance. Extensive experiments demonstrate the potential benefits of IGL algorithms on various imbalanced conditions, offering insights and opportunities in the IGL field. Further, we have developed an open-sourced and unified package to facilitate reproducible evaluation and inspire further innovative research, which is available at https://github.com/RingBDStack/IGL-Bench.

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 9 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 2 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 4 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 8 ran (3 with no instrument failure; 5 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 between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

ringbdstack/igl-bench officialmentioned in papermentioned on GitHubjaxMITSyntology: 9 samples, 8 ran (5 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

9 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 2 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures 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.

2ran · violated contract
4ran · our draft was wrong
1ran; the contract check could not run
1ran
1unverified

Licence: 0 of the 9 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 ringbdstack/igl-bench. “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.

ringbdstack/igl-bench official repository 9 samples, 8 ran (5 instrument-failed) · 1 unverified
AcontainsB IGL_Bench/algorithm/COLDBREW/norm_tricks.py ran · violated contract MIT (permissive) · 19511295442b8b8a · report fixture: signature A:str/0/str, listB:list/1/str · returned bool · level recorded 2026-09-24
adj2edgeindex IGL_Bench/algorithm/DPGNN/utils.py ran · our draft was wrong fingerprinted MIT (permissive) · 742082b98cf22cc4 · report fixture: signature adj:Tensor/2/int · returned Tensor · level recorded 2026-09-25
random_mask in 13 papers IGL_Bench/algorithm/COLDBREW/utils.py ran · violated contract MIT (permissive) · 4d6df03aa2af1f80 · report fixture: signature L:int/0/int, true_prob:float/0/float · returned ndarray · level recorded 2026-09-24
reset_weight_GroupNorm IGL_Bench/algorithm/COLDBREW/norm_tricks.py ran · our draft was wrong MIT (permissive) · a5483c4f44a5f81a · report fixture: signature args:SimpleArgs/0/? · returned SimpleArgs · level recorded 2026-09-24
run_norm_if_any IGL_Bench/algorithm/COLDBREW/norm_tricks.py ran MIT (permissive) · 429df79768882322 · report fixture: signature net:callable/0/?, x:Tensor/2/float, ilayer:int/0/int · returned Tensor · level recorded 2026-09-24
sample_mask in 39 papers
census: 4 implementations from 5 papers, 4 distinct outputs on one shared input
IGL_Bench/algorithm/DEMONet/util.py ran · our draft was wrong MIT (permissive) · 03c26d27b6d12de7 · report fixture: signature idx:ndarray/1/int, l:int/0/int · returned ndarray · level recorded 2026-09-24
sparse_to_tuple in 22 papers IGL_Bench/algorithm/DEMONet/util.py ran · our draft was wrong MIT (permissive) · eaa82e9c7a22e930 · report fixture: signature sparse_mx:coo_matrix/2/float · returned tuple · level recorded 2026-09-24
tonp in 10 papers IGL_Bench/algorithm/COLDBREW/GCN.py ran; the contract check could not run (RAISES) MIT (permissive) · 18d569c66cbe1eda · report fixture: signature arr:Tensor/2/float · returned ndarray · level recorded 2026-09-24
test in 377 papers IGL_Bench/algorithm/DPGNN/learn.py unverified MIT (permissive) · 41233a7e838d93ea · report

Tasks

Graph Learning

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