bug.reports.mgcv

<code>mgcv</code> works largely because many people have reported bugs over the years. If you find something that looks like a bug, please report it, so that the package can be improved. <code>mgcv</code> does not have a large development budget, so it is a big help if bug reports follow the following guidelines.The ideal report consists of an email to <a href="/link/simon.wood%40r-project.org?package=mgcv&version=1.8-16" data-mini-rdoc="mgcv::simon.wood@r-project.org">simon.wood@r-project.org</a> with a subject line including <code>mgcv</code> somewhere, containing<ol>
<li> The results of running <code><a rd-options="" href="/link/sessionInfo?package=mgcv&version=1.8-16" data-mini-rdoc="mgcv::sessionInfo">sessionInfo</a></code> in the R session where the problem occurs. This provides platform details, R and package version numbers, etc.
</li>
<li> A brief description of the problem.
</li>
<li> Short cut and paste-able code that produces the problem, including the code for loading/generating the data (using standard R functions like <code>load</code>, <code>read.table</code> etc).
</li>
<li> Any required data files. If you send real data it will only be used for the purposes of de-bugging.
</li>
</ol>
Of course if you have dug deeper and have an idea of what is causing the problem, that is also helpful to know, as is any suggested code fix. (Don't send a fixed package .tar.gz file, however - I can't use this).

GAMs, GAMMs and other generalized ridge regression with
multiple smoothing parameter estimation by GCV, REML or UBRE/AIC.
Includes a gam() function, a wide variety of smoothers, JAGS
support and distributions beyond the exponential family.

Simon Wood

mgcv

Mixed GAM Computation Vehicle with GCV/AIC/REML Smoothness
Estimation

bug.reports.mgcv function

<code>mgcv</code> works largely because many people have reported bugs over the years. If you find something that looks like a bug, please report it, so that the package can be improved. <code>mgcv</code> does not have a large development budget, so it is a big help if bug reports follow the following guidelines.

The ideal report consists of an email to <a href='mailto:simon.wood@r-project.org'>simon.wood@r-project.org</a> with a subject line including <code>mgcv</code> somewhere, containing

<ol>
<li> The results of running <code><a rd-options='' href='sessionInfo'>sessionInfo</a></code> in the R session where the problem occurs. This provides platform details, R and package version numbers, etc.
</li>
<li> A brief description of the problem.
</li>
<li> Short cut and paste-able code that produces the problem, including the code for loading/generating the data (using standard R functions like <code>load</code>, <code>read.table</code> etc).
</li>
<li> Any required data files. If you send real data it will only be used for the purposes of de-bugging.
</li>
</ol>


Of course if you have dug deeper and have an idea of what is causing the problem, that is also helpful to know, as is any suggested code fix. (Don't send a fixed package .tar.gz file, however - I can't use this).

bug.reports.mgcv: Reporting mgcv bugs.

Description

Arguments