Papers › A Survey of Information Cascade Analysis: Models, Predictions, and Recent Advances

A Survey of Information Cascade Analysis: Models, Predictions, and Recent Advances

22 May 2020arXiv:2005.11041archive 2025-07-28

Fan Zhou, Xovee Xu, Goce Trajcevski, Kunpeng Zhang

The deluge of digital information in our daily life -- from user-generated content, such as microblogs and scientific papers, to online business, such as viral marketing and advertising -- offers unprecedented opportunities to explore and exploit the trajectories and structures of the evolution of information cascades. Abundant research efforts, both academic and industrial, have aimed to reach a better understanding of the mechanisms driving the spread of information and quantifying the outcome of information diffusion. This article presents a comprehensive review and categorization of information popularity prediction methods, from feature engineering and stochastic processes, through graph representation, to deep learning-based approaches. Specifically, we first formally define different types of information cascades and summarize the perspectives of existing studies. We then present a taxonomy that categorizes existing works into the aforementioned three main groups as well as the main subclasses in each group, and we systematically review cutting-edge research work. Finally, we summarize the pros and cons of existing research efforts and outline the open challenges and opportunities in this field.

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

By repository: community (archive-listed): 17 samples from 3 repositories, 12 ran (10 with no instrument failure; 2 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-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

Xovee/casflow mentioned on GitHubtfSyntology: 2 samples, 2 ran (2 instrument-failed) · 0 unverified report
Xovee/ccgl mentioned on GitHubtfMITSyntology: 13 samples, 8 ran (0 instrument-failed) · 5 unverified report
Xovee/hdgnn mentioned on GitHubpytorchMITSyntology: 2 samples, 2 ran (0 instrument-failed) · 0 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: 12 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 2 where Syntology's instrument failed) · 5 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.

2ran · our draft was wrong
10ran
5unverified

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 3 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.

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.

Xovee/casflow community (archive-listed) 2 samples, 2 ran (2 instrument-failed) · 0 unverified
read_labels in 11 papers gene_emb.py ran · our draft was wrong MIT (permissive) · b8a9341d81c3f6d8 · report fixture: signature filename:str/0/str · returned dict · level recorded 2026-09-22
sequence2list gene_emb.py ran · our draft was wrong MIT (permissive) · ef0b8f55202174f1 · report fixture: signature filename:str/0/str · returned dict · level recorded 2026-09-22
Xovee/ccgl community (archive-listed) 13 samples, 8 ran (0 instrument-failed) · 5 unverified
Invdegree_matrix src/utils/graphwave/utils/graph_tools.py ran fingerprinted MIT (permissive) · c41794102b9f3069 · report fixture: signature adj:ndarray/2/float · returned ndarray · level recorded 2026-09-24
charac_function src/utils/graphwave/characteristic_functions.py ran MIT (permissive) · 74187cbf2bffbbff · report fixture: signature time_points:ndarray/1/float, temp:csr_matrix/2/float · returned ndarray · level recorded 2026-09-24
compute_cheb_coeff src/utils/graphwave/graphwave.py ran MIT (permissive) · 4290905ee7090fdc · report fixture: signature scale:float/0/float, order:int/0/int · returned list · level recorded 2026-09-24
compute_cheb_coeff_basis src/utils/graphwave/graphwave.py ran MIT (permissive) · 0fbc4387afcf2db4 · report fixture: signature scale:float/0/float, order:int/0/int · returned list · level recorded 2026-09-24
degree_matrix src/utils/graphwave/utils/graph_tools.py ran fingerprinted MIT (permissive) · eb7ba08613818849 · report fixture: signature adj:ndarray/2/float · returned ndarray · level recorded 2026-09-24
dot_sim_2 src/utils/tools.py ran fingerprinted MIT (permissive) · de7ad73d28f91ccf · report fixture: signature x:EagerTensor/2/float, y:EagerTensor/2/float · returned EagerTensor · level recorded 2026-09-24
get_negative_mask in 6 papers src/utils/tools.py ran MIT (permissive) · 7ba2d94d446bf525 · report fixture: signature b_size:int/0/int · returned EagerTensor · level recorded 2026-09-24
laplacian in 10 papers src/utils/graphwave/utils/graph_tools.py ran MIT (permissive) · 9858df6684d94526 · report fixture: signature a:csr_matrix/2/float · returned csr_matrix · level recorded 2026-09-24
augmentor_sim src/augmentor.py unverified MIT (permissive) · 4cf1a96acf28df24 · report
charac_function_multiscale src/utils/graphwave/characteristic_functions.py unverified MIT (permissive) · d99ee1ea8c38a2b9 · report
dot_sim_1 src/utils/tools.py unverified MIT (permissive) · f553a8a1f0f560c8 · report
main in 235 papers src/distilling.py unverified MIT (permissive) · 8b5ac074fd9e0047 · report
main in 235 papers src/gene_emb.py unverified MIT (permissive) · 103bb5930b2e4aa5 · report
Xovee/hdgnn community (archive-listed) 2 samples, 2 ran (0 instrument-failed) · 0 unverified
acc in 48 papers
census: 5 implementations from 5 papers, 2 distinct outputs across 2 buckets, one shared input per bucket
codes/gnn_train/tools.py ran fingerprinted MIT (permissive) · 76d79073639d1c3c · report fixture: signature pred:list/1/float, true:list/1/float · returned float · level recorded 2026-09-24
cross_entropy_loss in 58 papers codes/gnn_train/tools.py ran MIT (permissive) · 6dab6885871344ad · report fixture: signature c_embed_batch:Tensor/3/float, pos_embed_batch:Tensor/3/float, neg_embed_batch:Tensor/3/float, embed_d:int/0/int · returned Tensor · level recorded 2026-09-24

Tasks

Feature EngineeringMarketing

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