No, sorry, I misunderstood your question.
a) Read the NAMESPACE file of package B? If they use importFrom that would be
specific enough.
b) "Suggests" can refer to usage that does not even appear in the loaded
package at all.
c) Try asking in the r-package-devel mailing list?
On January 3, 20
On 03/01/2020 4:45 p.m., Hans W Borchers wrote:
You are absolutely right. I forgot that there is a difference between
the unpacked and the installed directory of a package. The
documentation of the *pkgapi* package in development is quite scarce
and does not mention the details. Thanks for the ti
Jeff, the problem is:
There I see the packages that depend on mine, but not which functions are used
Or maybe I misunderstood your comment.
On Fri, 3 Jan 2020 at 22:49, Jeff Newmiller wrote:
>
> If you are so lucky as to have this problem, perhaps you could take a look at
> the reverse dependenc
If you are so lucky as to have this problem, perhaps you could take a look at
the reverse dependencies on your packages' CRAN web page.
On January 3, 2020 1:45:42 PM PST, Hans W Borchers wrote:
>You are absolutely right. I forgot that there is a difference between
>the unpacked and the installed
You are absolutely right. I forgot that there is a difference between
the unpacked and the installed directory of a package. The
documentation of the *pkgapi* package in development is quite scarce
and does not mention the details. Thanks for the tip.
--HW
PS: Still I would like to learn about ot
Also, note that the p-values will probably not exactly correspond to
conclusions drawn from the bootstrapped confidence limits. They are
two different approaches to the research question. Broadly speaking,
the bootstrapped limits avoid the assumption of a symmetric sampling
distribution that underl
Hello,
Your code is correctly extracting the bootstrapped r-squared confidence
intervals calculated using the adjusted bootstrap percentile (BCa) method.
If you want the p-values, do
summary(fit)$coefficients[, 4]
in the function.
Also, function boot calls a function statistic that expects
On 03/01/2020 12:26 p.m., Hans W Borchers wrote:
How can I find out which functions of my package A are called within
another package B that depends on, imports, or suggests package A ?
And more specifically, which functions in B are calling functions in A ?
I tried to utilize the *pkgapi* packa
How can I find out which functions of my package A are called within
another package B that depends on, imports, or suggests package A ?
And more specifically, which functions in B are calling functions in A ?
I tried to utilize the *pkgapi* package, but get error messages like
> map_package(
I've been trying to get the pvalue of my samples from a bootstrap rsquared test
in R. I'm not very good with statistics so could someone please take a look at
my below code and point me in the right direction with regards to how I can
extract the p-values per sample (basically input a Descriptor
Hi Joshua,
Thanks for the comment but I guess I prefer a different behavior. If
merge.xts() cannot handle the objects I pass in, I want it to fail.
In fact, I typically adopt a naming convention where the variable name
indicates the type. In my normal coding style my example would look
like:
aXts <
On Fri, Jan 3, 2020 at 1:14 AM Eric Berger wrote:
>
> Hi Gabor and Duncan,
> Thanks for your comments. As Gabor points out, Duncan's suggestion
> does not work.
> For those interested, here is some minimal reproducible example to illustrate
>
> library(xts)
> dtV <- as.Date("2019-01-01")+1:5
> a <
12 matches
Mail list logo