Minimal Rust version: 1.55.0
Implements simple sampling and monte carlo (or rather markov-) steps, that can be used to create a markov chain.
This is intended to be used for various different use cases. As such, you can easily define additional data that should be stored at each vertex.
Add this to your Cargo.toml:
[dependencies]
net_ensembles = "0.5"
# for feature "serde_support" (enabled by default) also use
serde = { version = "1.0", features = ["derive"] }If you do not need serde support, add this instead:
[dependencies]
net_ensembles = { version = "0.5", default-features = false }See changelog. Note that savestates (created with serde) of v0.4 are incompatible with savestates generated by older versions and vise versa. Braking changes may or may not affect the loading of save states, you have to test that out yourself
- Erdős-Rényi (x2)
- small-world
- Barabási-Albert
- Configuration Model
- spacial networks
On a 64 bit system drawing an usize consumes more randomness than on a 32 bit system,
therefore ensembles drawn etc. are affected by the size of usize.
- you can always visualize the current graph by creating a
.dotfile from it. There are different options for that, choose which one fits you best.
- average degree
- connected components
- diameter
- is_connected
- leaf count
- q_core
- transitivity
- biconnected component
- vertex_load (closely related, often equal to betweeness)
- depth first search from index
- breadth first search from index
- over additional data
- …
- degree
- check adjacency with other nodes
- access additional data
- iterate over indices stored in adjacency list
- …
No warranties whatsoever, but since I am writing this library for my own scientific simulations, I do my best to avoid errors.
You can learn more about me and my research on my homepage.
If you notice any bugs, or want to request new features: do not hesitate to open a new issue on the repository.
- The number of vertices has to be decided when creating a graph and cannot be changed later - at least for now.
- I might add a method to add vertices if requested or I need it myself.
Due to implementation details, where I prioritize fast access of vertices, it is unlikely, that I will implement the option to remove vertices. If I do, it will likely be a relatively costly operation, so keep that in mind.
- I might move the
samplingmodule into a different crate in the future. If I do, everything will likely be reexported at the same position as currently
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.