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: vignettes/FAQ.Rmd
+9-6
Original file line number
Diff line number
Diff line change
@@ -87,8 +87,11 @@ By letting us know when messages are confusing or uninformative, you help us to
87
87
## I am running a piece of **pomp** code I got from a guy, but I get errors. What is going on? {#old-code}
88
88
89
89
Of course, there could be many reasons for this.
90
-
However, you should know that **pomp** version 2 made many changes to the **pomp** interface so that older code will not run under versions ≥ 2.
91
-
See the [**pomp** version 2 upgrade guide](./upgrade_guide.html) for information on how to fix broken code from earlier versions.
90
+
However, you should know that each time the major version number for the packageincreases (e.g., from 5.11 to 6.1), at least one change has been introduced that has the potential to break existing code.
91
+
Consult the [news blog](./blog.html) (including the [blog archive](./archive.html) if the code you are testing is more than a few months old):
92
+
these contain succinct summaries of the changes associated with each release.
93
+
Note also that the [online manual](https://kingaa.github.io/manuals/pomp/) is kept up to date.
94
+
There is also the [**pomp** version 2 upgrade guide](./upgrade_guide.html) which gives information on how to update codes from versions <2.
92
95
93
96
## Where in the peer-reviewed literature is **pomp** described?
Copy file name to clipboardexpand all lines: vignettes/FAQ.html
+5-5
Original file line number
Diff line number
Diff line change
@@ -260,7 +260,7 @@ <h2 number="1.2"><span class="header-section-number">1.2</span> What’s the pro
260
260
<p>To cite the ‘pomp’ package in publications, use:</p>
261
261
<p>A. A. King, D. Nguyen, E. L. Ionides (2016). Statistical Inference for Partially Observed Markov Processes via the R Package pomp. Journal of Statistical Software 69(12): 1–43. <a href="DOI:10.18637/jss.v069.i12" class="uri">DOI:10.18637/jss.v069.i12</a>.</p>
262
262
<p>Additionally, consider citing the package itself:</p>
263
-
<p>A. A. King, E. L. Ionides, C. M. Breto, S. P. Ellner, M. J. Ferrari, S. Funk, S. G. Johnson, B. E. Kendall, M. Lavine, D. Nguyen, E. B. O’Dea, D. C. Reuman, H. Wearing, and S. N. Wood (2024). pomp: Statistical Inference for Partially Observed Markov Processes. (R package, version 5.11.1.0). <a href="https://kingaa.github.io/pomp/" class="uri">https://kingaa.github.io/pomp/</a></p>
263
+
<p>A. A. King, E. L. Ionides, C. M. Breto, S. P. Ellner, M. J. Ferrari, S. Funk, S. G. Johnson, B. E. Kendall, M. Lavine, D. Nguyen, E. B. O’Dea, D. C. Reuman, H. Wearing, and S. N. Wood (2024). pomp: Statistical Inference for Partially Observed Markov Processes. (R package, version 6.0.1.0). <a href="https://kingaa.github.io/pomp/" class="uri">https://kingaa.github.io/pomp/</a></p>
264
264
<p>You can get this information by executing <code>citation("pomp")</code> in an <strong>R</strong> session. LaTeX users can get a BibTeX entry for these publications by executing <code>toBibtex(citation("pomp"))</code>.</p>
265
265
<p>If you use <strong>pomp</strong> in a publication, please take a moment to let us know! Send an email with the citation, and we’ll include it in <a href="./biblio.html">the bibliography</a>.</p>
266
266
</div>
@@ -271,7 +271,7 @@ <h2 number="1.3"><span class="header-section-number">1.3</span> I have an error
<h2 number="1.4"><span class="header-section-number">1.4</span> I am running a piece of <strong>pomp</strong> code I got from a guy, but I get errors. What is going on?</h2>
274
-
<p>Of course, there could be many reasons for this. However, you should know that <strong>pomp</strong> version 2 made many changes to the <strong>pomp</strong> interface so that older code will not run under versions ≥ 2. See the <a href="./upgrade_guide.html"><strong>pomp</strong> version 2 upgrade guide</a> for information on how to fix broken code from earlier versions.</p>
274
+
<p>Of course, there could be many reasons for this. However, you should know that each time the major version number for the packageincreases (e.g., from 5.11 to 6.1), at least one change has been introduced that has the potential to break existing code. Consult the <a href="./blog.html">news blog</a> (including the <a href="./archive.html">blog archive</a> if the code you are testing is more than a few months old): these contain succinct summaries of the changes associated with each release. Note also that the <a href="https://kingaa.github.io/manuals/pomp/">online manual</a> is kept up to date. There is also the <a href="./upgrade_guide.html"><strong>pomp</strong> version 2 upgrade guide</a> which gives information on how to update codes from versions <2.</p>
0 commit comments