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/inverse_problems/petab_ode_param_fitting.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,7 +103,8 @@ nothing # hide
103
103
### Fitting parameters
104
104
We are now able to fit our model to the data. First, we create a `PEtabODEProblem`. Here, we use `petab_model` as the only input, but it is also possible to set various [numeric solver and automatic differentiation options](@ref petab_simulation_options) (such as method or tolerance).
@@ -115,6 +116,7 @@ To fit a parameter set we use the `calibrate_model` function. In addition to our
115
116
using Optim
116
117
p0 = generate_startguesses(petab_problem, 1)
117
118
p0 = [0.0, 0.0, 0.0] # hide
119
+
res = calibrate_model(petab_problem, p0, IPNewton()) # hide
118
120
res = calibrate_model(petab_problem, p0, IPNewton())
119
121
```
120
122
@@ -382,10 +384,7 @@ While in our basic example, we do not provide any additional information to our
382
384
383
385
Here is an example, taken from the [more detailed PEtab.jl documentation](https://sebapersson.github.io/PEtab.jl/dev/Boehm/#Creating-a-PEtabODEProblem)
@@ -484,6 +483,7 @@ Here, the event only triggers whenever the condition changes from `false` to `tr
484
483
485
484
Whenever we have several events or not, we bundle them together in a single vector which is later passed to the `PEtabODEProblem` using the `events` argument:
0 commit comments