Skip to content

Releases: kingaa/pomp

4.1.0.0

13 Jan 10:18
7986193
Compare
Choose a tag to compare
identical to 4.1

4.0.11.0

04 Nov 02:20
d7125fd
Compare
Choose a tag to compare
fix date

4.0.8.0

21 Oct 18:44
67da8f0
Compare
Choose a tag to compare
negative binomial model for SIR

4.0.7.0

13 Oct 01:45
11d2466
Compare
Choose a tag to compare
update NEWS

4.0.5.0

05 Oct 11:57
c0fa6c7
Compare
Choose a tag to compare
new 'names' argument for 'parmat'

4.0.4.1

24 Sep 22:41
dceb8c5
Compare
Choose a tag to compare
proper .id for 'trajectory' and 'flow'

4.0.4.0

17 Sep 00:42
0180aae
Compare
Choose a tag to compare
add 'nocov' to the 3 remaining uncovered lines

4.0.2.1

10 Sep 13:54
e5a5e9a
Compare
Choose a tag to compare
fix minor problem in ebola documentation; improve tests

4.0.0.0

07 Sep 14:01
51b28ed
Compare
Choose a tag to compare

Version 4 contains a few changes that are not backward compatible. These are all to do with the elementary function ‘trajectory’, which computes trajectories of the deterministic dynamical skeleton. See below for details.

• The behavior of ‘trajectory’ now fully conforms to the behavior of other ‘pomp’ elementary functions. In particular, one can now add, remove, or modify basic model components in a call to ‘trajectory’ just as one can with ‘simulate’, ‘pfilter’, ‘probe’, etc. Before version 4, additional arguments to ‘trajectory’ (i.e., those passed via ‘...’) were passed on to the ODE integrator in the case of continuous-time deterministic skeletons (i.e., vectorfields) and ignored in the case of discrete-time skeletons (i.e., maps). As of version 4, in order to adjust ODE integrator settings it is necessary to use the ‘ode_control’ argument of ‘trajectory’. This behavior matches that of ‘traj_objfun’.

• It is now possible to create a ‘pomp’ object from scratch using ‘trajectory’, together with a specification of the rinit and skeleton components. Prior to version 4, in order to do so, it was necessary to first create a dummy data set, then call ‘pomp’, and then pass the resulting ‘pomp’ object to ‘trajectory’. This can now be achieved in one call.

• The user now has the option, in a call to ‘trajectory’, to have the results returned as one or ‘pomp’ objects. In this regard, its behavior matches that of ‘simulate’.

3.5.5.0

02 Sep 23:31
a4e9cc0
Compare
Choose a tag to compare
update NEWS