Skip to content

Commit a54a6ba

Browse files
authored
docs: performative -> performant
Update input_component.md: s/performative/performant/
1 parent 672c96c commit a54a6ba

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/src/tutorials/input_component.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ This tutorial demonstrate each case and explain the pros and cons of each.
1010

1111
## `TimeVaryingFunction` Component
1212

13-
The `ModelingToolkitStandardLibrary.Blocks.TimeVaryingFunction` component is easy to use and is performative. However the data is locked to the `ODESystem` and can only be changed by building a new `ODESystem`. Therefore, running a batch of data would not be efficient. Below is an example of how to use the `TimeVaryingFunction` with `DataInterpolations` to build the function from sampled discrete data.
13+
The `ModelingToolkitStandardLibrary.Blocks.TimeVaryingFunction` component is easy to use and is performant. However the data is locked to the `ODESystem` and can only be changed by building a new `ODESystem`. Therefore, running a batch of data would not be efficient. Below is an example of how to use the `TimeVaryingFunction` with `DataInterpolations` to build the function from sampled discrete data.
1414

1515
```julia
1616
using ModelingToolkit
@@ -86,7 +86,7 @@ sys = structural_simplify(system)
8686
prob = ODEProblem(sys, [], (0, time[end]))
8787

8888
rdata[] = data1
89-
sol1 = solve(prob, ImplicitEuler(); dt, adaptive = false);
89+
sol1 = solve(prob, ImplicitEuler(); dt, adaptive = false)
9090
ddx1 = sol1[sys.ddx]
9191

9292
rdata[] = data2

0 commit comments

Comments
 (0)