dynamic_multiplex (Python)
dynamic_multiplex is the Python implementation of DynMux. DynMux is a suite of tools for temporal networks that change over time. Nodes enter and leave, groups form, split, merge and dissolve, and periods can differ in size. The temporal fitters track nodes and communities across periods. A community keeps one id for as long as it persists, and a newly formed group gets a new id. The two-stage fitters detect communities in each period and link them to communities in the linked periods. layer_links sets which periods are directly linked, and by default that is adjacent periods only. With the default tracking = "smoothed", all periods are fitted jointly, so later periods can change earlier labels. tracking = "filtered" prevents that. Multislice modularity (Mucha et al. 2010) and Hungarian matching are included as comparison methods. The bootstrap stability score helps choose between DynMux and multislice.
Why this package
Standard multislice approaches (Mucha et al. 2010) connect all layers to all layers, meaning community structure at distant time periods influences assignments everywhere. When applied to temporal data, this creates a pooling problem: the community configuration at 2010 affects the structure detected at 1950. dynamic_multiplex provides explicit control over which layers influence which layers via a layer_links argument (from, to, weight), defaulting to adjacent-only temporal coupling.
Functions
Note: with
directed=True, Leiden keeps edge direction in the per-layer detection; Louvain collapses directed layers to undirected weighted graphs (reciprocal arcs summed). The community-graph second stage is undirected; the multislice stage for identity ties keeps edge direction in each slice (directed null model), with undirected identity ties.
fit_multilayer_jaccard()- Fits Leiden (default) or Louvain communities on each layer, links communities in the selected layer pairs by the Jaccard index of their members, and groups the linked communities into cross-layer meta-communities with a second community detection on the community graph.
fit_multilayer_overlap()- Fits Leiden (default) or Louvain communities on each layer, links communities in the selected layer pairs by the overlap coefficient of their members, and groups the linked communities into cross-layer meta-communities with a second community detection on the community graph.
fit_multilayer_weighted_jaccard()- Fits Leiden (default) or Louvain communities on each layer, links communities in the selected layer pairs by a node-strength weighted Jaccard index, and groups the linked communities into cross-layer meta-communities with a second community detection on the community graph.
fit_multilayer_weighted_overlap()- Fits Leiden (default) or Louvain communities on each layer, links communities in the selected layer pairs by a node-strength weighted overlap coefficient, and groups the linked communities into cross-layer meta-communities with a second community detection on the community graph.
fit_multilayer_identity_ties()- Multislice modularity (Mucha et al. 2010): ties each node to its own copy in the selected layer pairs (weight = layer-link weight times
omega) and detects meta-communities jointly on the coupled layers.
- Multislice modularity (Mucha et al. 2010): ties each node to its own copy in the selected layer pairs (weight = layer-link weight times
fit_multilayer_hungarian()- Fits communities on each layer independently, then aligns labels between consecutive layers with Hungarian matching on community overlap (a snapshot-and-match baseline).
simulate_and_fit_multilayer()- Simulates multiplex layers from a planted partition process and runs one of the five fit types (
jaccard,overlap,weighted_jaccard,weighted_overlap,identity).
- Simulates multiplex layers from a planted partition process and runs one of the five fit types (
layers_from_membership()- Builds one weighted layer per time slice from group memberships (for example states in IGOs): shared-group counts, size-weighted, or Kumar hypergraph reweighting. No weighting is the default; each slice is built on its own.
partition_membership_bipartite(),partition_membership_strict(),fit_multilayer_from_partitions()(Python only)- Per-slice partitions of membership data without projection: Barber's bipartite modularity (Leiden) and strict (all-or-nothing) hypergraph modularity (hypernetx;
pip install dynamic-multiplex[hypergraph], which needs pandas < 3).fit_multilayer_from_partitions()tracks any per-slice partitions over time with the DynMux second stage or Hungarian matching. These are comparison specifications; in pilot simulations both did worse than the projections. The R package deliberately has no counterpart.
- Per-slice partitions of membership data without projection: Barber's bipartite modularity (Leiden) and strict (all-or-nothing) hypergraph modularity (hypernetx;
bootstrap_multilayer(),partition_stability()- Parametric network bootstrap of a fit and the stability score s, for comparing two fits of the same network. Since 1.4.0 no interval or accuracy-floor outputs are reported.
Input handling
- Layers must share one node set unless
allow_unequal_nodes=True. Nodes may then enter and leave, with or without a change in layer size; pass networkx graphs with node labels, and nodes are matched across layers by label and keep their labels as ids. This holds for every fit function and forbootstrap_multilayer(). - Within-layer self-loops and zero-weight edges are dropped (the same rule as the R package).
- Two-stage fits:
repair_chains=Truerejoins groups that stage 2 cut along time (mutual best match with similarity at leastrepair_min_similarity, default 0.2);tracking="filtered"makes the meta ids of layers 1..t depend only on layers 1..t. Both are off by default. objectivesets the first-stage (per-layer) objective only; the second stage always maximizes modularity.seed=123by default, as in the R package since 1.4.0; passseed=Nonefor unseeded detection.
Installation (development)
pip install -e ./python_code
Optional algorithms:
pip install -e ./python_code[louvain]
pip install -e ./python_code[leiden]
Quick example
from dynamic_multiplex import simulate_and_fit_multilayer, fit_multilayer_overlap
sim = simulate_and_fit_multilayer(
directed=True,
n_nodes=50,
n_layers=4,
n_communities=3,
fit_type="jaccard",
algorithm="louvain",
seed=123,
)
print(sim["fit"]["interlayer_ties"].head())
custom_links = [
{"from": 1, "to": 2, "weight": 1.0},
{"from": 2, "to": 4, "weight": 0.6},
]
fit_overlap = fit_multilayer_overlap(
sim["layers"],
algorithm="leiden",
layer_links=custom_links,
min_similarity=0.1,
add_self_loops=True,
self_loop_multiplier=1.0,
)
Testing
pip install -e ./python_code[dev,louvain]
pytest
Metadata
Release files for dynamic-multiplex 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dynamic_multiplex-1.4.0.tar.gz | 62.4 kB | Without provenance | Details for dynamic_multiplex-1.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dynamic_multiplex-1.4.0-py3-none-any.whl | Python 3 | none | any | Details for dynamic_multiplex-1.4.0-py3-none-any.whl |
Total release size: 110.8 kB
Release files / dynamic_multiplex-1.4.0.tar.gz
| Download URL | dynamic_multiplex-1.4.0.tar.gz |
|---|---|
| Size | 62.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28a9f3e078666839d4013c4f0bd84511c053ce36988f3a65d0ada49115e4baaf
|
|
BLAKE2b-256 checksum How to use checksums |
d4e1851f738e54881faf1d57be53a5044f6043d1631be2fd64b5acefcf85069f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / dynamic_multiplex-1.4.0-py3-none-any.whl
| Download URL | dynamic_multiplex-1.4.0-py3-none-any.whl |
|---|---|
| Size | 48.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
786a52aaf0bfa873c9ad2d708722544f767a094afb0c17d1956e4a8e6f63a65b
|
|
BLAKE2b-256 checksum How to use checksums |
031c6c23e978b7863cebca3b9b0919e103e0c6d73cade76fa7a880b0b4719dcb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for dynamic-multiplex 1.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.