News blog
Blog archive
Subscribe to this newsfeed
pomp version 6
10 December 2024
The current release contains two breaking changes over pomp versions 5.11.X.X.
-
With version 5.8.4, the manner in which one supplies extra model elements (the so-called
userdata
, elements other than parameters, state variables, observations, and covariates that are available to the basic model components) was changed. The old way of doing things remained available, but using it generated a warning message, with the promise that the warning would someday become an error. That day has come. As of version 6, to supply userdata to the basic model components, one must explicitly use theuserdata
argument in pomp constructors, elementary algorithms, or inference algorithms. Users who have already adjusted their codes to eliminate the aforementioned warning should experience no change in pomp behavior. -
While it has always been good practice in pomp function calls to pass arguments by name (as opposed to by position), with version 6.0.1, this becomes (almost) mandatory. This is meant to prevent a class of difficult-to-trace errors in which an unnamed argument is passed to a lower-level function and potentially ignored, silently. The chief exception to this rule is the first argument in many pomp functions, which is typically a pomp object or a data frame. Users who are in the habit of passing named arguments will not notice any change in pomp behavior.
pomp version 5.11 released
13 September 2024
pomp version 5.11 has been released to CRAN and will soon appear on CRAN mirrors everywhere. This is a bug-fix release, with no user-visible changes.
See the package NEWS for details.
pomp version 5.10 released
1 July 2024
pomp version 5.10 has been released to CRAN and will soon appear on CRAN mirrors everywhere.
This release contains a change to the onestep
rprocess simulator and some minor documentation improvements.
User-visible change
Suppose P
is a ‘pomp’ object, with an rprocess component specified as onestep(f)
, where f
is a C snippet or R function.
Suppose also that t==time(P,t0=TRUE)
.
In previous package versions, f
would be executed to go from t[i]
to t[i+1]
if and only if t[i+1] > t[i]
.
As of version 5.9.1, f
is executed exactly once even if t[i] == t[i+1]
.
If f
is written correctly, this change will introduce no error.
However, if the user’s code assumes that the time-step t[i+1]-t[i]
(furnished to f
as delta.t
if f
is an R function and dt
if it is a C snippet) is strictly positive, then this change may introduce errors.
Please contact me via the package Issues page if you notice a change in the behavior of your codes upon update to pomp version 5.10.
pomp version 5.9 released
2 June 2024
pomp version 5.9 has been released to CRAN and will soon appear on a mirror near you. This release contains an important change to the user interface, as well as a bug fix and one new experimental feature.
User-visible change
As documented in the manual, basic model components have access to parameters, covariates, state variables, and in some cases, the data.
To make additional elements available to the basic model components, pomp provides the “userdata” facility.
From this version, such elements should be furnished to pomp functions in a list via the argument userdata
.
For the present, the old behavior will still work, but will generate a warning.
In a future release, this will become an error.
Bug fix
A bug in covariate-table extrapolation for the case order="constant"
has been fixed.
Feature enhancement
A new experimental function repair_lookup_table
is provided to help eliminate unnecessary warnings about extrapolation.
One can use it “repair” a covariate table that does not span the full temporal range of observations.
This is simply a matter of performing the extrapolations and adding them to the lookup table.
See the manual for more information and an example.
Other changes
Functions with names that include dots (.
), which have been defunct since version 4.7, have now been expunged entirely.
Blog archive
Subscribe to this newsfeed