Skip to content

Commit 5efd6e2

Browse files
Move spatial tutorial from SciMLTutorials
Now that we have package docs for all of the packages and doctests, it makes sense for the tutorials to be built as part of the testing process. It also keeps everything organized by package. Thus SciMLTutorials is getting cannibalized into separate package docs, and this is the one for JumpProcesses. I did a few updates (DiffEqJump, LightGraphs, links) so hopefully this is enough. I might need a little bit of help getting this one completed though, since there are a few I need to tend to.
1 parent 833194d commit 5efd6e2

File tree

1 file changed

+217
-0
lines changed

1 file changed

+217
-0
lines changed

docs/src/tutorials/spatial.md

Lines changed: 217 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,217 @@
1+
# Spatial SSAs with JumpProcesses.jl
2+
author: Vasily Ilin
3+
---
4+
5+
This tutorial shows how to use spatial solvers.
6+
7+
## Reversible binding model on a grid
8+
9+
A 5 by 5 Cartesian grid:
10+
11+
| <!-- --> | <!-- --> | <!-- --> | <!-- --> | <!-- --> |
12+
|---|---|---|---|---|
13+
| . | . | . | . | B |
14+
| . | . | . | . | . |
15+
| . | . | . | . | . |
16+
| . | . | . | . | . |
17+
| A | . | . | . | . |
18+
19+
Suppose we have a reversible binding system described by $$A+B \to C$$ at rate $$k_1$$ and $$C \to A+B$$ at rate $$k_2$$. Further suppose that all $$A$$ molecules start in the lower left corner, while all $$B$$ molecules start in the upper right corner of a 5 by 5 grid. There are no $$C$$ molecules at the start.
20+
21+
We first create the grid:
22+
23+
```@example spatial
24+
using JumpProcesses
25+
dims = (5,5)
26+
num_nodes = prod(dims) # number of sites
27+
grid = CartesianGrid(dims) # or use Graphs.grid(dims)
28+
```
29+
30+
Now we set the initial state of the simulation. It has to be a matrix with entry $$(s,i)$$ being the number of species $$s$$ at site $$i$$ (with the standard column-major ordering of the grid).
31+
32+
```@example spatial
33+
num_species = 3
34+
starting_state = zeros(Int, num_species, num_nodes)
35+
starting_state[1,1] = 25
36+
starting_state[2,end] = 25
37+
starting_state
38+
```
39+
40+
We now set the time-span of the simulation and the reaction rates. These can be chosen arbitrarily.
41+
42+
```@example spatial
43+
tspan = (0.0, 3.0)
44+
rates = [6.0, 0.05] # k_1 = rates[1], k_2 = rates[2]
45+
```
46+
47+
Now we can create the `DiscreteProblem`:
48+
49+
```@example spatial
50+
prob = DiscreteProblem(starting_state, tspan, rates)
51+
```
52+
53+
Since both reactions are [massaction reactions](https://en.wikipedia.org/wiki/Law_of_mass_action), we put them together in a `MassActionJump`. In order to do that we create two stoichiometry vectors. The net stoichiometry vector describes which molecules change in number and how much after each reaction; for example, `[1 => -1]` is the first molecule disappearing. The reaction stoichiometry vector describes what the reactants of each reaction are; for example, `[1 => 1, 2 => 1]` would mean that the reactants are one molecule of type 1 and one molecule of type 2.
54+
55+
```@example spatial
56+
netstoch = [[1 => -1, 2 => -1, 3 => 1],[1 => 1, 2 => 1, 3 => -1]]
57+
reactstoch = [[1 => 1, 2 => 1],[3 => 1]]
58+
majumps = MassActionJump(rates, reactstoch, netstoch)
59+
```
60+
61+
The last thing to set up is the hopping constants -- the probability per time of an individual molecule of each species hopping from one site to another site. In practice this parameter, as well as reaction rates, are obtained empirically. Suppose that molecule $$C$$ cannot diffuse, while molecules $$A$$ and $$B$$ diffuse at probability per time 1 (i.e. the time of the diffusive hop is exponentially distributed with mean 1). Entry $$(s,i)$$ of `hopping_constants` is the hopping rate of species $$s$$ at site $$i$$ to any of its neighboring sites (diagonal hops are not allowed).
62+
63+
```@example spatial
64+
hopping_constants = ones(num_species, num_nodes)
65+
hopping_constants[3, :] .= 0.0
66+
hopping_constants
67+
```
68+
69+
We are now ready to set up the `JumpProblem` with the Next Subvolume Method.
70+
71+
```@example spatial
72+
alg = NSM()
73+
jump_prob = JumpProblem(prob, alg, majumps, hopping_constants=hopping_constants, spatial_system = grid, save_positions=(true, false))
74+
```
75+
76+
The `save_positions` keyword tells the solver to save the positions just before the jumps. To solve the jump problem do
77+
78+
```@example spatial
79+
solution = solve(jump_prob, SSAStepper())
80+
```
81+
82+
## Animation
83+
84+
Visualizing solutions of spatial jump problems is best done with animations.
85+
86+
```@example spatial
87+
using Plots
88+
is_static(spec) = (spec == 3) # true if spec does not hop
89+
"get frame k"
90+
function get_frame(k, sol, linear_size, labels, title)
91+
num_species = length(labels)
92+
h = 1/linear_size
93+
t = sol.t[k]
94+
state = sol.u[k]
95+
xlim=(0,1+3h/2); ylim=(0,1+3h/2);
96+
plt = plot(xlim=xlim, ylim=ylim, title = "$title, $(round(t, sigdigits=3)) seconds")
97+
98+
species_seriess_x = [[] for i in 1:num_species]
99+
species_seriess_y = [[] for i in 1:num_species]
100+
CI = CartesianIndices((linear_size, linear_size))
101+
for ci in CartesianIndices(state)
102+
species, site = Tuple(ci)
103+
x,y = Tuple(CI[site])
104+
num_molecules = state[ci]
105+
sizehint!(species_seriess_x[species], num_molecules)
106+
sizehint!(species_seriess_y[species], num_molecules)
107+
if !is_static(species)
108+
randsx = rand(num_molecules)
109+
randsy = rand(num_molecules)
110+
else
111+
randsx = zeros(num_molecules)
112+
randsy = zeros(num_molecules)
113+
end
114+
for k in 1:num_molecules
115+
push!(species_seriess_x[species], x*h - h/4 + 0.5h*randsx[k])
116+
push!(species_seriess_y[species], y*h - h/4 + 0.5h*randsy[k])
117+
end
118+
end
119+
for species in 1:num_species
120+
scatter!(plt, species_seriess_x[species], species_seriess_y[species], label = labels[species], marker = 6)
121+
end
122+
xticks!(plt, range(xlim...,length = linear_size+1))
123+
yticks!(plt, range(ylim...,length = linear_size+1))
124+
xgrid!(plt, 1, 0.7)
125+
ygrid!(plt, 1, 0.7)
126+
return plt
127+
end
128+
129+
"make an animation of solution sol in 2 dimensions"
130+
function animate_2d(sol, linear_size; species_labels, title, verbose = true)
131+
num_frames = length(sol.t)
132+
anim = @animate for k=1:num_frames
133+
verbose && println("Making frame $k")
134+
get_frame(k, sol, linear_size, species_labels, title)
135+
end
136+
anim
137+
end
138+
# animate
139+
anim=animate_2d(solution, 5, species_labels = ["A", "B", "C"], title = "A + B <--> C", verbose = false)
140+
fps = 5
141+
gif(anim, fps = fps)
142+
```
143+
144+
## Making changes to the model
145+
146+
Now suppose we want to make some changes to the reversible binding model above. There are three "dimensions" that can be changed: the topology of the system, the structure of hopping rates and the solver. The supported topologies are `CartesianGrid` -- used above, and any `AbstractGraph` from `Graphs`. The supported forms of hopping rates are $$D_{s,i}, D_{s,i,j}, D_s * L_{i,j}$$, and $$D_{s,i} * L_{i,j}$$, where $$s$$ denotes the species, $$i$$ -- the source site, and $$j$$ -- the destination. The supported solvers are `NSM`, `DirectCRDirect` and any of the standard non-spatial solvers.
147+
148+
### Topology
149+
150+
If our mesh is a grid (1D, 2D and 3D are supported), we can create the mesh as follows.
151+
152+
```@example spatial
153+
dims = (2,3,4) # can pass in a 1-Tuple, a 2-Tuple or a 3-Tuple
154+
num_nodes = prod(dims)
155+
grid = CartesianGrid(dims)
156+
```
157+
158+
The interface is the same as for [`Graphs.grid`](https://juliagraphs.org/Graphs.jl/dev/core_functions/simplegraphs_generators/#Graphs.SimpleGraphs.grid-Union{Tuple{AbstractVector{T}},%20Tuple{T}}%20where%20T%3C:Integer). If we want to use an unstructured mesh, we can simply use any `AbstractGraph` from `Graphs` as follows:
159+
160+
```@example spatial
161+
using Graphs
162+
graph = cycle_digraph(5) # directed cyclic graph on 5 nodes
163+
```
164+
165+
Now either `graph` or `grid` can be used as `spatial_system` in creation of the `JumpProblem`.
166+
167+
### Hopping rates
168+
169+
The most general form of hopping rates that is supported is $$D_{s,i,j}$$ -- each (species, source, destination) triple gets its own independent hopping rate. To use this, `hopping_constants` must be of type `Matrix{Vector{F}} where F <: Number` (usually `F` is `Float64`) with `hopping_constants[s,i][j]` being the hopping rate of species $$s$$ at site $$i$$ to neighbor at index $$j$$. Note that neighbors are in ascending order, like in `Graphs`. Here is an example where only hopping up and left is allowed.
170+
171+
```@example spatial
172+
hopping_constants = Matrix{Vector{Float64}}(undef, num_species, num_nodes)
173+
for ci in CartesianIndices(hopping_constants)
174+
(species, site) = Tuple(ci)
175+
hopping_constants[species, site] = zeros(outdegree(grid, site))
176+
for (n, nb) in enumerate(neighbors(grid, site))
177+
if nb < site
178+
hopping_constants[species, site][n] = 1.0
179+
end
180+
end
181+
end
182+
```
183+
184+
To pass in `hopping_constants` of form $$D_s * L_{i,j}$$ we need two vectors -- one for $$D_s$$ and one for $$L_{i,j}$$. Here is an example.
185+
186+
```@example spatial
187+
species_hop_constants = ones(num_species)
188+
site_hop_constants = Vector{Vector{Float64}}(undef, num_nodes)
189+
for site in 1:num_nodes
190+
site_hop_constants[site] = ones(outdegree(grid, site))
191+
end
192+
hopping_constants=Pair(species_hop_constants, site_hop_constants)
193+
```
194+
195+
We must combine both vectors into a pair as in the last line above.
196+
197+
Finally, to use in `hopping_constants` of form $$D_{s,i} * L_{i,j}$$ we construct a matrix instead of a vector for $$D_{s,j}$$.
198+
199+
```@example spatial
200+
species_hop_constants = ones(num_species, num_nodes)
201+
site_hop_constants = Vector{Vector{Float64}}(undef, num_nodes)
202+
for site in 1:num_nodes
203+
site_hop_constants[site] = ones(outdegree(grid, site))
204+
end
205+
hopping_constants=Pair(species_hop_constants, site_hop_constants)
206+
```
207+
208+
We can use either of the four versions of `hopping_constants` to construct a `JumpProblem` with the same syntax as in the original example. The different forms of hopping rates are supported not only for convenience but also for better memory usage and performance. So it is recommended that the most specialized form of hopping rates is used.
209+
210+
### Solvers
211+
212+
There are currently two specialized "spatial" solvers: `NSM` and `DirectCRDirect`. The former stands for Next Subvolume Method [^1]. The latter employs Composition-Rejection to sample the next site to fire, similar to the ordinary DirectCR method. For larger networks `DirectCRDirect` is expected to be faster. Both methods can be used interchangeably.
213+
214+
Additionally, all standard solvers are supported as well, although they are expected to use more memory and be slower. They "flatten" the problem, i.e. turn all hops into reactions, resulting in a much larger system. For example, to use the Next Reaction Method (`NRM`), simply pass in `NRM()` instead of `NSM()` in the construction of the `JumpProblem`. Importantly, you *must* pass in `hopping_constants` in the `D_{s,i,j}` or `D_{s,i}` form to use any of the non-specialized solvers.
215+
216+
## References
217+
[^1]: Elf, Johan and Ehrenberg, Mäns. “Spontaneous separation of bi-stable biochemical systems into spatial domains of opposite phases”. In: _Systems biology_ 1.2 (2004), pp. 230–236.

0 commit comments

Comments
 (0)