You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/multiscale/multiscale.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -210,7 +210,7 @@ This graph has a root node that defines a scene, then a soil, and a plant with t
210
210
For long simulations on plants with many organs, the output data can be very significant. It's possible to restrict the output variables that are tracked for the whole simulation to a subset of all the variables:
Get the model dependency graph given a ModelList or a multiscale model mapping. If one graph is returned,
8
+
Get the model dependency graph given a ModelMapping or a multiscale model mapping. If one graph is returned,
9
9
then all models are coupled. If several graphs are returned, then only the models inside each graph are coupled, and
10
10
the models in different graphs are not coupled.
11
11
`nsteps` is the number of steps the dependency graph will be used over. It is used to determine
@@ -39,7 +39,7 @@ these graphs independently to r
39
39
40
40
# Notes
41
41
42
-
The difference between `dep(m::ModelList)` and `dep!(m::ModelList, nsteps)` is that the first one returns the dependency graph found in the model list, while the
42
+
The difference between `dep(m::ModelMapping)` and `dep!(m::ModelMapping, nsteps)` is that the first one returns the dependency graph found in the model list, while the
43
43
second one returns the dependency graph with the specified number of steps, modifying the simulation IDs of each node in the graph (`simulation_id=fill(0, nsteps)`).
0 commit comments