Skip to content

Commit 06e1d99

Browse files
committed
expand intro example note
1 parent 8f93464 commit 06e1d99

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/src/model_creation/functional_parameters.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ sol = solve(oprob)
3232
plot(sol)
3333
```
3434
!!! note
35-
For this simple example, $(2 + t)/(1 + t)$ could have been used directly as a reaction rate, technically making the functional parameter approach unnecessary.
35+
For this simple example, $(2 + t)/(1 + t)$ could have been used directly as a reaction rate (or written as a normal function), technically making the functional parameter approach unnecessary. However, here we used this function as a simple example of how discrete data can be made continuous using DataInterpolations, and then have its values inserted using a (functional) parameter.
3636

3737
## [Inserting a customised, time-dependent, input](@id functional_parameters_circ_rhythm)
3838
Let us now go through everything again, but providing some more details. Let us first consider the input parameter. We have previously described how a [time-dependent rate can model a circadian rhythm](@ref dsl_description_nonconstant_rates_time). For real applications, due to e.g. clouds, sunlight is not a perfect sine wave. Here, a common solution is to take real sunlight data from some location and use in the model. Here, we will create synthetic (noisy) data as our light input:

0 commit comments

Comments
 (0)