Hi all,
Thanks for the suggestions and comments. I found a way to allow nimble to work
and avoid the note when checking the package. My solution is to use:
requireNamespace(nimble)
attachNamespace("nimble")
I have a feeling that this may be against the spirit of the check (I believe
that it
e:
"But that usually will create another problem."
"
Best
Jens
#
> Gesendet: Donnerstag, 06. August 2020 um 01:30 Uhr
> Von: "Dirk Eddelbuettel"
> An: "William Dunlap"
> Cc: "r-package-devel@r-project.org"
> Betreff: Re: [R-pkg-devel
You might make a second package that depends only on nimble and your
main package can then suggest that second package and JAGS.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Wed, Aug 5, 2020 at 3:36 PM Simon Bonner wrote:
>
> Hi all,
>
> I’m wondering if someone an offer advice on a problem
On 5 August 2020 at 16:25, William Dunlap wrote:
| You might make a second package that depends only on nimble and your
| main package can then suggest that second package and JAGS.
Nice. "We can solve any problem by introducing an extra level of indirection."
See
I think the key line = " Unfortunately, nimble will not work with this
mechanism. "
Given that, depends seems like a good short-term solution. Change it to
suggests once the upstream problem is fixed.
On Wed, Aug 5, 2020 at 3:36 PM Simon Bonner wrote:
> Hi all,
>
> I’m wondering if someone an
Hi all,
I’m wondering if someone an offer advice on a problem I’m facing in developing
a package.
My package essentially generates code and formats data for one of two MCMC
sampling engines, JAGS accessed via rjags or nimble (a native R package), calls
the engines, and then provides functions
